-
Notifications
You must be signed in to change notification settings - Fork 762
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[top] Provide list of desired vectors for power estimation #9297
Comments
Thanks! |
@zi-v let me know if there are other scenarios of interest. |
For the max instantaneous step, please also consider adding concurrent IO toggling. |
yes that is the plan.
…On Mon, Nov 22, 2021 at 9:58 PM zi-v ***@***.***> wrote:
For the max instantaneous step, please also consider adding concurrent IO
toggling.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#9297 (comment)>,
or unsubscribe
<https:/notifications/unsubscribe-auth/AAH2RSQI6BEGDT27ROBVK2TUNMUQ3ANCNFSM5IK363PA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
More power scenarios:
|
@zi-v are the latter two not covered by transition in and out of low power states? That was my intent. |
They are. I was just not clear to me that the above covers it already. I thought it only talk about the static state and wanted to make sure that the transitions are also covered. |
power virus test that simulates maximum instantaneous step. This should include
- kmac / aes would need to take turns being fed data
- kmac activation should be a combination of otp background, key manager background and software
- for otbn, any signature verification / signing event is sufficient
- reseed / update operation ongoing
- instruction scrambling gated by script availability
- ideally for digital activity, 3xuart / 2xi2c modules should be activated
- for first pass simplicity can activate IO portion only for now through GPIO
- for dedicated pins, focus on SPI device quad activity
- USB activity should be activated
- for first pass simplicity activate IO portion only for now via pin forcing in usbdev.
- servicing ongoing threads and random read/write data to memory
- icache needs to be activated, otherwise the system may spend most of its time fetching code
- flash verification is currently insufficient to turn on icache
- rstmgr background checks
- others?
low power test that simulates deep sleep state
low power test that simulates light sleep state
general system idle that is NOT low power
Make sure to document these test cases in the test plan.
The text was updated successfully, but these errors were encountered: