How can I ensure a hard reset during west flash with stm32cubeprogrammer runner when using Twister? #92385
Replies: 2 comments
-
[URGENT REMINDER] STM32CubeProgrammer Hard Reset Option Not Working with Twister Dear Zephyr Team, This is a follow-up reminder regarding my previous ticket about integrating the --tool-opt="-hardRst" option with Twister for STM32 H7 and U5 boards. Requested: Impact: This issue is currently blocking our release testing cycle. Thanks, |
Beta Was this translation helpful? Give feedback.
-
Please add the following in your board.cmake file:
or
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Background:
I need to perform a hard reset on STM32 H7 and U5 boards after flashing, using the STM32CubeProgrammer runner.
When I run: west flash --runner stm32cubeprogrammer --tool-opt="-hardRst"
the board performs a hard reset as expected.
However, when I try to integrate this with Twister(zephyr version - 3.6)
set ZEPHYR_FLASH_EXTRA_ARGS=--tool-opt="-hardRst"'
west flash --runner stm32cubeprogrammer
or
python twister --device-testing --hardware-map "map.yml" -T <path_to_yaml file>
But in both cases, the board only performs a soft reset (not a hard reset).
Question:
How can I ensure that Twister (and west flash when called by Twister) uses the --tool-opt="-hardRst" option so that a hard reset is performed after flashing with STM32CubeProgrammer?
Is there a way to integrate this option into Twister’s workflow, or is there a recommended approach for this scenario?
Support required:
How do I make sure that west flash --runner stm32cubeprogrammer --tool-opt="-hardRst" is effectively used by Twister for hardware reset on STM32 H7/U5 boards?
Beta Was this translation helpful? Give feedback.
All reactions