Add support for NUCLEO-N657X0-Q board #38
Merged
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
Igor-Misic
force-pushed
the
add_nucleo-stm32n657x-q
branch
from
ce8890a to
88c33ee
Compare
Draft
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.
This is the First Stage Bootloader (FSBL) for the NUCLEO-N657X0-Q.
The firmware example is IMLedBlink : IMProject/IMLedBlink#8
There are quite a few limitations with the STM32N657, which also affect the older architecture of IMBootloader.
RAM after reset
Link to reference
With the STM32N657, it is not possible to preserve data in RAM after a reset. This impacts how IMBootloader handles jumping between the firmware and bootloader, as well as the general firmware loading process. Previously, part of the RAM was used to store the last state before a reset, allowing the system to decide what to do on the next boot. In this case, I had to implement a direct jump to the application immediately after flashing. As a result, there is no communication between the firmware and bootloader via RAM. A possible solution for the future is to use external flash memory.
How to enter bootloader
The only way to enter the bootloader is by pressing the USER button during power-up.