-
Notifications
You must be signed in to change notification settings - Fork 6.7k
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
west: runners: bossac: Honor --erase flag #81894
base: main
Are you sure you want to change the base?
west: runners: bossac: Honor --erase flag #81894
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree with the change, but the default behavior changes now. This should be added to the migration guide.
Will do. Also noticed the test failure, will work on fixing that up. |
64a62d3
to
393d98a
Compare
Added a note to the migration guide, fixed the existing tests, and added a new one for the |
Instead of unconditionally erasing the whole target, add support for using the common --erase flag. Signed-off-by: Peter Johanson <[email protected]>
393d98a
to
6edddd9
Compare
@nandojve should the bossac runner be under SAM in the maintaners file? |
Instead of unconditionally erasing the whole target, add support for using the common --erase flag.
This tweak is needed to avoid the bossac runner from erasing the whole chip every time it's run, helping preserve things like settings stored to flash when using them on samd21, for example.