tests: add external memory erase step for b_u585 board #109
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Patrick Robb <[email protected]>
1 task
kr-t
approved these changes
Dec 5, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Per a new Ocre Runtime update, external memory is now used on the B_u585 board. Consequently, we now need to erase this memory before flashing a new container to the board. This PR is adding that needed pre-step.
Type of change
Please delete options that are not relevant.
How Has This Been Tested?
I have run the STM32_Programmer_CLI locally on the zephyr-xlarge-runner at UNH, and it printed to stdout that it had erased the b_u585 board. When this PR is run, we will be able to see if it works also when invoked via GHA.