tests: pm: Adding tests based on new approach to PM testing. #80692
Conversation
gbarkadiusz
changed the title
gbarkadiusz
force-pushed
the
topic/rfc/power_management
branch
8 times, most recently
from
bb6e11e to
cc760a2
Compare
This commit adds debug scripts, including `pwsh_stm32l562.py` and `abstract_power_monitor.py`. These scripts are part of the proposed changes in pull request zephyrproject-rtos#80692. Signed-off-by: Arkadiusz Cholewinski <[email protected]>
| data = current_measurement_output | ||
| # Empirical RMS values in mA with descriptive keys | ||
| rms_expected = { | ||
| "k_cpu_idle":57.0, # K_cpu_idle |
There was a problem hiding this comment.
can we move those expected data to a yaml file for different platform?
There was a problem hiding this comment.
Of course we can, the good hint. Thank you.
There was a problem hiding this comment.
PS: Btw, Please take a look. #80989. Feel free to share ideas or warries. :)
| while (1) { | ||
| printk("\nGoing to k_cpu_idle.\n"); | ||
| k_msleep(400); | ||
| printk("\nWake Up.\n"); |
There was a problem hiding this comment.
can we use this tests\subsys\pm\power_mgmt_soc\src\power_mgmt.c, instead of the sleep time?
There was a problem hiding this comment.
I don't know yet, let me see.
There was a problem hiding this comment.
Yep, get the information from the device tree is the way to go imho, otherwise it will not be portable and the previous comment is useless.
There was a problem hiding this comment.
@ceolin I added the use of DTS, is this what you meant?
| @@ -0,0 +1,30 @@ | |||
| # Copyright (c) 2024 Intel Corporation. | |||
There was a problem hiding this comment.
would this be better to move this function to scripts/pm/pm_helper.py, and rms is not the only implement, e.g. we can have average mean
gbarkadiusz
force-pushed
the
topic/rfc/power_management
branch
3 times, most recently
from
f959bb2 to
980a943
Compare
gbarkadiusz
force-pushed
the
topic/rfc/power_management
branch
18 times, most recently
from
1f00e48 to
69e3a4f
Compare
gbarkadiusz
force-pushed
the
topic/rfc/power_management
branch
6 times, most recently
from
2525c2f to
dc18404
Compare
|
@hakehuang I've moved the hardcoded expected value to the appropriate yaml file. Please take a look. |
Introduces scripts for powerShiled on stm32l562e_dk board. Adds three new power management pytests based on a new approach. Signed-off-by: Arkadiusz Cholewinski <[email protected]>
Introduces two scripts
abstract_power_monitor.pyandpwsh_stm32l562.py.Adds three new power management pytests based on a new approach.
SETUP
TESTS
pm.states: Verifies the transition to all available power states on
stm32l562e_dk.During the test, pytest detects each step and calculates the RMS (Root Mean Square) current for every detected state. The test then compares the calculated RMS values against the expected values, which have been determined manually through experimental observation
pm.residency_time: Tests the residency time of each power state.
This test evaluates the residency time of different power states on the
stm32l562e_dkboard.pm.wakeup_timer: Tests the RTC alarm’s ability to wake the CPU from the lowest power state.
Each test calculates RMS current values for each detected state and compares them to expected values, which were manually set based on experimental data.
To Reproduce
Power Monitor: e.g.,
/dev/ttyACM0or/dev/serial/by-id/usb-STMicroelectronics_PowerShield__Virtual_ComPort_in_FS_Mode__FFFFFFFEFFFF-if00Target: e.g.,
/dev/ttyACM1or/dev/serial/by-id/usb-STMicroelectronics_STLINK-V3_004##############39-if02<path_to_power_monitor>in thetests/subsys/pm/power_states/testcase.yamlfile under the pytest_args section as follows:pytest_args: [--powershield=<path_to_power_monitor>]twister --device-testing --device-serial <path_to_target> -p stm32l562e_dk -s <test_name> -x=CONFIG_BOOT_DELAY=500