Enabling MCUBOOT does not run application

RE: Enabling MCUBOOT does not run application

thang47 — Thu, 17 Aug 2023 10:40:56 GMT

Hi,I have the same problem, I have the same problem, but I did as you said and it didn't work

RE: Enabling MCUBOOT does not run application

vgoof — Fri, 28 Oct 2022 10:05:02 GMT

Dear Vidar,

Thanks for the quick response. Yes you are correct about not having a crystal.

I added the child_image folder and the mcuboot.conf with

CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC=y inside

That indeed works! I also tried with the BLE set up and that is also working, very nice! Many thanks!

As a side note, I actually tried this before but I also read somewhere you need to tell cmakelists to use this conf file

set(mcuboot_CONF_FILE ${CMAKE_CURRENT_SOURCE_DIR}/child_image/mcuboot.conf)

the combination of those does not work.

One detail I am still curious about is that in the examples people share I can see output from the MCU bootloader but I do not get this, I only see the output from the app. (I tried to add the segger set up to the mcuboot.conf file but that does not help.

RE: Enabling MCUBOOT does not run application

Vidar Berg — Fri, 28 Oct 2022 09:16:14 GMT

Hello,

Please correct me if I'm wrong, but I assume you don't have a 32KHz crystal mounted on your custom board since you are setting CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC=y in your application.

This setting will not be applied to the MCUBoot child image, instead it will be built with the default board configuration. So, if you build for 'nrf52833dk_nrf52833' the LF crystal oscillator will end up being selected and the bootloader would become stuck waiting for the crystal to ramp up.

To override this setting in the bootloader, you can create a folder named 'child_image' in your project directory, then define a kconfig fragment named mcuboot.conf (Ref. https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/ug_multi_image.html#image-specific-variables). Config settings in this file will automatically be applied to the mcuboot build.

The folder structure should look like this:

├── child_image
│ └── mcuboot.conf
├── CMakeLists.txt
├── prj.conf
├── README.rst
├── sample.yaml
└── src
└── main.c

where mcuboot.conf contains CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC=y.

Best regards,

Vidar