Issue with Enabling MCUboot on Custom Board with nRF5340

[Yashaswini S]

Hello,

I am working on a custom Agora board that includes a BT40 module with an nRF5340 MCU. I am trying to enable the MCUboot bootloader by setting CONFIG_BOOTLOADER_MCUBOOT=y in my prj.conf file. However, I encounter an error during the initial configuration stage.

Here are the details of my setup:

• Custom Agora board with BT40 module
• nRF5340 MCU
• Using Nordic SDK version 2.7.0
• The bootloader demo works on the nRF52840 development board using the Nordic course

Error Message:

...depends again on SOC_FAMILY_NRF (defined at C:/ncs/v2.7.0/modules/soc-hwmv1/soc/arm\nordic_nrf\Kconfig:9)
CMake Error at C:/ncs/v2.7.0/zephyr/cmake/modules/kconfig.cmake:392 (message):
command failed with return code: 1
Call Stack (most recent call first):
C:/ncs/v2.7.0/nrf/cmake/modules/kconfig.cmake:29 (include)
C:/ncs/v2.7.0/zephyr/cmake/modules/zephyr_default.cmake:132 (include)
C:/ncs/v2.7.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:66 (include)
C:/ncs/v2.7.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:97 (include_boilerplate)
CMakeLists.txt:12 (find_package)

-- Configuring incomplete, errors occurred!
See also "C:/Users/YASHAWS/Agora/xyleminc-wwno-gnode-009afda753b5/build_4/mcuboot/CMakeFiles/CMakeOutput.log".
See also "C:/Users/YASHAWS/Agora/xyleminc-wwno-gnode-009afda753b5/build_4/mcuboot/CMakeFiles/CMakeError.log".
CMake Error at C:/ncs/v2.7.0/nrf/cmake/multi_image.cmake:502 (message):
CMake generation for mcuboot failed, aborting. Command: 1
Call Stack (most recent call first):
C:/ncs/v2.7.0/nrf/cmake/multi_image.cmake:178 (add_child_image_from_source)
C:/ncs/v2.7.0/nrf/modules/mcuboot/CMakeLists.txt:328 (add_child_image)

-- Configuring incomplete, errors occurred!
See also "C:/Users/YASHAWS/Agora/xyleminc-wwno-gnode-009afda753b5/build_4/CMakeFiles/CMakeOutput.log".
See also "C:/Users/YASHAWS/Agora/xyleminc-wwno-gnode-009afda753b5/build_4/CMakeFiles/CMakeError.log".
FAILED: build.ninja
C:\ncs\toolchains\ce3b5ff664\opt\bin\cmake.exe --regenerate-during-build -SC:\Users\YASHAWS\Agora\xyleminc-wwno-gnode-009afda753b5 -BC:\Users\YASHAWS\Agora\xyleminc-wwno-gnode-009afda753b5\build_4
ninja: error: rebuilding 'build.ninja': subcommand failed
FATAL ERROR: command exited with status 1: 'C:\ncs\toolchains\ce3b5ff664\opt\bin\cmake.EXE' --build 'c:\Users\YASHAWS\Agora\xyleminc-wwno-gnode-009afda753b5\build_4'

* The terminal process terminated with exit code: 1.
* Terminal will be reused by tasks, press any key to close it.

Could anyone provide guidance on how to resolve this issue or suggest additional configurations that might be required for the nRF5340 MCU on a custom board?

Thank you!

[Einar Thorsrud]

Hi,

I amo not able to see exactly what the error is, but it the path is long which can cause problems on windows. I sit possible to rename and move things so that you make "C:/Users/YASHAWS/Agora/xyleminc-wwno-gnode-009afda753b5" much shorter? Do you still see the same error after that?

[Yashaswini S]

Hi,

Thank for the suggestion. I'll try to shorten the path.

But the Error is -FAILED: build.ninja
C:\ncs\toolchains\ce3b5ff664\opt\bin\cmake.exe --regenerate-during-build -SC:\Users\YASHAWS\Agora\xyleminc-wwno-gnode-009afda753b5 -BC:\Users\YASHAWS\Agora\xyleminc-wwno-gnode-009afda753b5\build_4
ninja: error: rebuilding 'build.ninja': subcommand failed
FATAL ERROR: command exited with status 1: 'C:\ncs\toolchains\ce3b5ff664\opt\bin\cmake.EXE' --build 'c:\Users\YASHAWS\Agora\xyleminc-wwno-gnode-009afda753b5\build_4'

This is the main issue is facing and after enabling the CONFIG_BOOTLOADER_MCUBOOT=y on prj.conf file.

[Yashaswini S]

Hi,

I tried by creating byown private and public key and adding with to existing project.

Do you any reference for the adding the keys to existing project.since after adding the keys also not reflcting in the project.

and also issue still persists.

Thank you

[Einar Thorsrud]

Hi,

Adding keys are described under Enabling a bootloader chain using sysbuild. For older SDK versions or if you are using the parent-child image, you need to follow the instructions under Enabling a bootloader chain using child and parent images (deprecated).

If you face issues, can you elaborate on what you are doing an in what way it does not work?

[Yashaswini S]

Hi,

We have tried in nRF5340 DK and everything works as per the Nordic exercise: Single slot and Dual slot methods for DFU over UART.Exercise 1 - DFU over UART - Nordic Developer Academy

But when we have a nRF5340 custom board with different or updated board files, following the same procedure gives different results.

Firmware loads but doesn’t reflect in board. Also slot swap doesn’t work.

Thank you

[Einar Thorsrud]

Hi,

I see. We need to know more about what is happening (logging/debug information).

1. What is the difference when you do it on a DK and you custom board?
2. How do you perform the DFU (using MCUmgr or nRF connect on a phone or similar?
   1. Do you do it in the same way?
   2. Can you share logs?
3. Can you enable logging and share logs from the nRF?
4. What else have you found by testing/debugging?

[Yashaswini S]

Hi,

1. The difference between the dk and custom board will be on dts file and peripherals.

2. I am using mcumgr command line tool to perform DFU. I have used same commands mentioned in . Exercise 1 - DFU over UART - Nordic Developer Academy By using this i am able do the DFU for nRF5340dk board and new firmware upgrade sucessfully.

I will share the commands which used to update new firmware using mcumgr commands.

For the custom board, I am using the same commands to update the new firmware.

1.To update new firmware for custom board, do I need to change anything in command?

2.while doing, sometimes I will face error called NMP_timeout.

What could be the reason for this and how to solve this?

Thank you

     

[Einar Thorsrud]

Hi,

I see. NMP timeout indicate UART communication problems. Are you using the UART for something else, or perhaps you have a serial terminal open for the same port at the same time?

[Yashaswini S]

Hi,

I'm not using the UART for different communication and also the not using same port at a time.