MCUBoot on nRF54L15 custom board versus nRF54L15-DK

[nzgupta]

Hello,

We are developing a custom board that uses the nRF54L15 chip, and are trying to flash an application along with MCUBoot to allow for OTA updates. When I flash the application+MCUBoot onto the nRF54L15-DK, the application runs as expected, and I'm able to perform OTA updates. Also, if I flash just the application onto the custom board without MCUBoot, the application runs as expected. However, when I try to flash the same application+MCUBoot onto the custom board, the application no longer runs at all. From the attached screenshots, I can see that the application and MCUBoot programs are being flashed to the same places in memory for the DK (NRF54L15_xxAA_REV2) as the custom board (NRF54L15_xxAA_REV1). What do you think is causing our application to fail to run when MCUBoot is programmed alongside it on the custom board? Any help would be greatly appreciated.

SDK and Software Interface: NCS v3.1.1 and nRF Connect for VS Code

Board Target for Build Configuration: nrf54l15dk/nrf54l15/cpuapp

Development Kit (nRF54L15-DK) Device Marking: N54L15 QFAAC0 2514AA

Custom Board Device Marking: N54L15 CAAAB0 2508RA

[Amanda Hsieh]

Hi, 

Do you use internal or external LF crystal on the custom board?
If you use the internal RC oscillator as 32KHz clock source, the following configs to your prj.conf and sysbuild/mcuboot.conf.

CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC=y

CONFIG_CLOCK_CONTROL_NRF_K32SRC_XTAL=n

Regards,
Amanda H.

[nzgupta]

I'm using the internal LF crystal. I had initially configured those options for the prj.conf file, but not the mcuboot.conf file. Once I added it to the mcuboot.conf file, the application ran as expected. Thanks for the help.

[Amanda Hsieh]

Happy to know it works now.