-
-
Notifications
You must be signed in to change notification settings - Fork 938
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
Fix full chip erase #3405
Fix full chip erase #3405
Conversation
Kudos, SonarCloud Quality Gate passed!
|
Do you want to test this code? Here you have an automated build: |
AUTOMERGE: (FAIL)
|
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.
- verified on two FC's
Verified here as well. |
@haslinghuis flash is still erased if expert mode is disabled |
Yes that's by design (only hidden now as requested by @blckmn ) - but has not changed as part of this PR. It's an expert setting as normally we want to have this enabled to minimize support issues. |
Breaks H730 unless expert mode enabled. Why break by default? At least target the config partition specifically and do the wipe cleanly. |
H730 needs custom flash address? is this why it breaks? |
Also in the documentation for the SPRacing Flight Controllers it's stated to disable full chip erase IIRC. |
We might need to have a disable flash erase option for some targets. Perhaps as part of the populating cloud build options we can include if it's on or off. |
If the intent is to wipe configuration then the DFU command could target the config partition only for erasure. |
Fixes: #3404