NCS doesnt create correct bootloader for custom board

RE: NCS doesnt create correct bootloader for custom board

Peter.J — Wed, 05 Jul 2023 08:47:07 GMT

Hi Priyanka,

thanx for the suggestion. It looks that this workaround fixes the problem with creating a correct bootloader image.

I will use this workaround while the standard approach for the mcuboot is fixed.

Best regards,

peter

RE: NCS doesnt create correct bootloader for custom board

Priyanka — Tue, 04 Jul 2023 11:04:40 GMT

Hi Peter,

In order to configure mcuboot, instead of making changes to the cmake file, could you try to create a child_image folder as shown here ?

You can take a look at defining a child image.

-Priyanka

RE: NCS doesnt create correct bootloader for custom board

Peter.J — Tue, 04 Jul 2023 10:36:21 GMT

Hi Priyanka,

the above mentioned warning is probably not relevant to the bootloader image problem. I tried NCS v2.0.0 where the warning is not present and the bootloader problem is present also there.

Best regards,

peter

RE: NCS doesnt create correct bootloader for custom board

Peter.J — Mon, 03 Jul 2023 13:59:34 GMT

Hi Priyanka,

when building the mcuboot image I am getting this warning, could point to the root cause:

=== child image mcuboot - begin ===
loading initial cache file D:/Dev/zephyr_blinky/blinky_pwm/build/mcuboot/child_image_preload.cmake
CMake Warning (dev) at D:/Dev/zephyr_blinky/blinky_pwm/build/mcuboot/child_image_preload.cmake:7 (set):
Syntax error in cmake code at

D:/Dev/zephyr_blinky/blinky_pwm/build/mcuboot/child_image_preload.cmake:7

when parsing string

d:\ncs\toolchains\31f4403e35\opt\bin\python.exe

Invalid escape sequence \3

Policy CMP0010 is not set: Bad variable reference syntax is an error. Run
"cmake --help-policy CMP0010" for policy details. Use the cmake_policy
command to set the policy and suppress this warning.
This warning is for project developers. Use -Wno-dev to suppress it.

Please pass this to the developers.

Best regards,

peter

RE: NCS doesnt create correct bootloader for custom board

Peter.J — Mon, 03 Jul 2023 12:55:00 GMT

Hi Priyanka,

you can try reproducing my problem by using the mcuboot.conf from my project in any sample project and using dev kit. I am interested to see how it works for you.

Best regards,

peter

RE: NCS doesnt create correct bootloader for custom board

Peter.J — Mon, 03 Jul 2023 12:50:31 GMT

I saw your reply. Based on my latest finding it looks that root cause of my problem is different than yours. Also changing NCS version doesnt help in my case.

Best regards,

peter

RE: NCS doesnt create correct bootloader for custom board

zachwork — Mon, 03 Jul 2023 12:46:38 GMT

Saw your post in my thread, have you read this discussion thread related to bootloader issues and are they related to your problem?

Unable to find bootable image - MCUBoot

RE: NCS doesnt create correct bootloader for custom board

Peter.J — Mon, 03 Jul 2023 12:40:31 GMT

Hi Priyanka,

please find attached the project with some relevant build files.

There is no error log. I run the bootloader, then pause it in a never ending loop and I can see where it is executed.

Best regards,

peter

devzone.nordicsemi.com/.../5488.blinky_5F00_pwm.zip

RE: NCS doesnt create correct bootloader for custom board

Priyanka — Mon, 03 Jul 2023 12:33:07 GMT

Hi Peter,

Could you attach the error logs? Also, could you attach the modified blinky sample?

Best Regards,

Priyanka

RE: NCS doesnt create correct bootloader for custom board

Peter.J — Mon, 03 Jul 2023 12:17:44 GMT

Hello again,

it looks the problem is related to using mcuboot.conf file. My custom board uses external LFCLK source that is not configured during kernel start so I have to configure using RC oscillator instead and thus to use mcuboot.conf file.

When I removed the mcuboot.conf file, the dev kit was able to start and run the application. The custom board waits in a loop for starting LFCLK, that is ok, as LFCLK cant start in this case.

The mcuboot.conf file is simple:

CONFIG_BOARD_ENABLE_DCDC=n

CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC=y

and the CMakelists.txt file contains:

set(mcuboot_OVERLAY_CONFIG

${CMAKE_CURRENT_LIST_DIR}/mcuboot.conf

)

So I need a help - to identify what is wrong with my mcuboot.conf configuration?

Best regards,

peter