Hello Nordic-team,
I´m currently developing an application which has been based on a 54L15DK an I´m using an overlay file for adjusting the ports to my own hardware. That runs fine with regards to the application. Now I have tried to get the entire thing to work with MCUboot in order to do a FOTA in future. So what I did is adding a Sysbuild.conf with the following lines:
SB_CONFIG_BOOTLOADER_MCUBOOT=n
# SB_CONFIG_SECURE_BOOT_APPCORE=y
SB_CONFIG_SECURE_BOOT_SIGNING_KEY_FILE="keys/root-ec-p256.pem"
SB_CONFIG_BOOT_SIGNATURE_TYPE_ECDSA_P256=y
The entire thing compiles fine. It is giving me the images and a merged.hex as I was expecting it. When trying to flash the merged.hex it seem that it doesn´t boot up at all. My debug-uart, which I have assigned to a port in my overlay-file does not send any bit of information.
So I digged a bit into the MCUboot and found that MCUboot is using an other overlay-file which is located in the bootloader//boot/zephyr folder called app.overlay. Even when doing the pinctrl modifications here the entire thing seems not to boot up.
Some more information: For the application I have used the internal RC-Oscillator for the 32kHz. So there is no crystal attached to the pins. Not sure if this is making any difference.
I have attached my application Overlay-file and the MCUboot overlay (app.overlay) for reference.
Thanks and best regards
Frank
