Nickez/dont boot to ff #1332
Merged
Nickez/dont boot to ff #1332
Conversation
This file contains 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
NickeZ
force-pushed
the
nickez/dont-boot-to-ff
branch
from
1be239a to
de1cc9f
Compare
If no firmware is flashed, then flash contains all 1's. The firmware's reset handler (stored in the exception table) would then be 0xffffffff. Jumping that address is very bad because that is the same as setting the cpu in LOCKUP state. * The common way to get to the LOCKUP state is with a double fault (fault in a fault handler), so this natuarally makes you go debug the wrong things. * The debugger cannot access the CPU when it is in LOCKUP state.
NickeZ
force-pushed
the
nickez/dont-boot-to-ff
branch
from
de1cc9f to
b163c7e
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
You can test with "Erase firmware" option in send message helper.