soc: stm32n6: Support running zephyr as a chainloaded application #91941
+165
−35
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
github-actions
bot
requested review from
djiatsaf-st,
etienne-lms,
FRASTM,
gautierg-st,
GeorgeCGV,
marwaiehm-st and
mathieuchopstm
|
The following west manifest projects have changed revision in this Pull Request:
✅ All manifest checks OK Note: This message is automatically posted and updated by the Manifest GitHub Action. |
github-actions
bot
added
manifest
manifest-hal_stm32
DNM (manifest)
erwango
commented
Jun 23, 2025
github-actions
bot
removed
the
DNM (manifest)
gautierg-st
reviewed
Jun 25, 2025
gautierg-st
previously approved these changes
Jun 25, 2025
etienne-lms
reviewed
Jun 25, 2025
Add a new /fsbl variant which replaces the default variant and typically fits for development or bootloader (MCUBoot typical target). Image is limited to 511KB. Default variant now stands for the real application which is supposed to be loaded by the bootloader. It runs from axisram1 and could be both XIP or RAMLOADED. Image has access to the whole AXISRAM1 and 2 (2MB). Signed-off-by: Erwan Gouriou <erwan.gouriou@st.com>
Offset is 400 for a good reason (yet to be defined). Signed-off-by: Erwan Gouriou <erwan.gouriou@st.com>
This signature is only valid for FSBL images. MCUBooot will sign images by itself. Signed-off-by: Erwan Gouriou <erwan.gouriou@st.com>
- Provide external flash partition - Define external flash and flash controller - Defined flashing address depending on image (FSBL/Chainloaded) Signed-off-by: Erwan Gouriou <erwan.gouriou@st.com>
Point to hal_stm32 change allowing to start chainloaded app (_s profile). Signed-off-by: Erwan Gouriou <erwan.gouriou@st.com>
Make axisram2 which is used in fsbl mode available as well to chainloaded application in order not to loose 1M of RAM In order to avoid conflicts with bootloader, verify that code + ro data of the loaded application won't go further than bootloader start address. This is done with a linker assert. Signed-off-by: Erwan Gouriou <erwan.gouriou@st.com>
Due to a BootROM clock switching issue, XSPI1 should use HCLK otherwise app won't restart on reset. Signed-off-by: Erwan Gouriou <erwan.gouriou@st.com>
Add a sysbuild configuration to specify that mcuboot uses fsbl variant. Signed-off-by: Erwan Gouriou <erwan.gouriou@st.com>
mathieuchopstm
approved these changes
Jun 25, 2025
|
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.
Set of required adaptations to allow running the zephyr image following a bootloader (mcuboot for now).
Introduce a new board variant, fsbl which replaces previous default variant.
Default variant now stands for the chain-loaded application.
Could be used with sysbuild:
west build -b stm32n6570_dk --sysbuild <your sample> -DSB_CONFIG_BOOTLOADER_MCUBOOT=y(XIP)Add
-DSB_CONFIG_MCUBOOT_MODE_RAM_LOAD=yto use RAMLOADED mode.Requires mcu-tools/mcuboot#2348