samples: boot: Adjustments for mcuboot crypto #201
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
|
needs some way of programming the kmu similar to what ncs with the auto provision sysbuild Kconfig has because I'm sitting here trying to work out how to get the .pem file loaded to the kmu and really haven't got a clue, and users should not have to deal with that |
nordicjm
requested changes
Jul 17, 2025
There was a problem hiding this comment.
with changes, device no longer boots into firmware loader image (either that or it does and crashes)
*** Booting My Application v2.1.0-dev-c3950c6eea9c ***
*** Using nRF Connect SDK Bare Metal v0.7.99-9e877ea1d228 ***
I: Starting bootloader
I: Booting main application
I: Bootloader chainload address offset: 0xa000
I: Image version: v0.0.0
I: Jumping to the first image slot
Waiting...
*** Booting My Application v2.1.0-dev-c3950c6eea9c ***
*** Using nRF Connect SDK Bare Metal v0.7.99-9e877ea1d228 ***
I: Starting bootloader
I: Booting firmware loader
I: Bootloader chainload address offset: 0x14c800
I: Image version: v0.0.0
I: Jumping to the first image slot
*** Booting nRF Connect SDK Bare Metal v0.7.99-9e877ea1d228 ***
I: BLE MCUmgr sample started
I: State change request: enable
*** Booting My Application v2.1.0-dev-c3950c6eea9c ***
*** Using nRF Connect SDK Bare Metal v0.7.99-9e877ea1d228 ***
I: Starting bootloader
I: Booting main application
I: Bootloader chainload address offset: 0xa000
I: Image version: v0.0.0
I: Jumping to the first image slot
Waiting...
The softdevice targets for the nRF54L series had the softdevice memory placed on the starting address of RAM and the application RAM placed next. This is problematic because the Cracen driver for these devices assumes that it owns the top 64 bytes of memory (starting from 0x2000000). Rearrange the memory layout of these devices so that it it places the softdevice memory is placed after the application memory. I also noticed that the partitions softdevice_static_ram and softdevice_dynamic_ram had a gap between them. I removed this gap since I cannot see why it is needed. Signed-off-by: Georgios Vasilakis <[email protected]>
Enables mcuboot with crypto. Signed-off-by: Georgios Vasilakis <[email protected]> Signed-off-by: Mateusz Michalek <[email protected]>
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.
Enables mcuboot with crypto.