Warning messages generated when west build MCUbool sample code

RE: Warning messages generated when west build MCUbool sample code

snowuyl — Fri, 03 Nov 2023 00:43:09 GMT

Thanks for your reply! I have fixed mcuboot_smp_custom_key build error by modifying CMakeLists.txt as follows.

cmake_minimum_required(VERSION 3.20.0)

set(mcuboot_CONFIG_BOOT_SIGNATURE_TYPE_ECDSA_P256 y)
set(mcuboot_CONFIG_BOOT_SIGNATURE_KEY_FILE \"${CMAKE_CURRENT_SOURCE_DIR}/custom_key_dir/custom_priv.pem\")

find_package(Zephyr REQUIRED HINTS $ENV{ZEPHYR_BASE})
project(mcuboot_smp_custom_key)

target_sources(app PRIVATE src/main.c)

RE: Warning messages generated when west build MCUbool sample code

Raoul — Thu, 02 Nov 2023 22:45:14 GMT

Hi Snowuyl,

[quote user="snowuyl"]I asked this question when I use ncs v2.3.0. Now I use ncs v2.4.2.[/quote]

The warning still means exactly the same thing it meant in v2.3.0, so I don't think there is a need to ask this questions again.

If you had doubts or questions about some specific detail being changed between NCS v2.3.0 and v.2.4.2, you could make your question a bit longer and specify that.

[quote user="snowuyl"]I tried to build mcuboot_smp_custom_key on ncs v2.4.2. But west build failed.[/quote]

Is that why you created this case? I see that you created another case for it as well, and an issue for it on GitHub. You didn't mention that here, and I don't really think that's okay. When you create so many cases per week, I don't think you need the attention of 3 engineers for an issue. We are glad to answer you, but please don't occupy us too much! Then we can help more people.

Still, I discussed the build issue with Sigurd, we found a solution, updated the repo, and I see that you've closed your issue on GitHub now. Glad to see that!

In general, it would be fair towards us if you spend more time on researching your issues, and preparing your questions. I hope you could do that! Thanks.

Best regards,

Raoul

RE: Warning messages generated when west build MCUbool sample code

snowuyl — Fri, 20 Oct 2023 02:27:56 GMT

devzone.nordicsemi.com/.../3718.mcuboot_5F00_smp_5F00_custom_5F00_key.zip

RE: Warning messages generated when west build MCUbool sample code

snowuyl — Fri, 20 Oct 2023 02:18:13 GMT

Thanks for your reply! I asked this question when I use ncs v2.3.0. Now I use ncs v2.4.2. I tried to build mcuboot_smp_custom_key on ncs v2.4.2. But west build failed.

C:\ncs\v2.4.2\nrf\samples\mcuboot_smp_custom_key>west build -b nrf5340dk_nrf5340_cpuapp
-- west build: generating a build system
Loading Zephyr default modules (Zephyr base).
-- Application: C:/ncs/v2.4.2/nrf/samples/mcuboot_smp_custom_key
-- CMake version: 3.20.5
-- Using NCS Toolchain 2.4.0 for building. (C:/ncs/toolchains/31f4403e35/cmake)
-- Found Python3: C:/ncs/toolchains/31f4403e35/opt/bin/python.exe (found suitable exact version "3.8.2") found components: Interpreter
-- Cache files will be written to: C:/ncs/v2.4.2/zephyr/.cache
-- Zephyr version: 3.3.99 (C:/ncs/v2.4.2/zephyr)
-- Found west (found suitable version "1.0.0", minimum required is "0.7.1")
-- Board: nrf5340dk_nrf5340_cpuapp
-- Found host-tools: zephyr 0.16.0 (C:/ncs/toolchains/31f4403e35/opt/zephyr-sdk)
-- Found toolchain: zephyr 0.16.0 (C:/ncs/toolchains/31f4403e35/opt/zephyr-sdk)
-- Found Dtc: C:/ncs/toolchains/31f4403e35/opt/bin/dtc.exe (found suitable version "1.4.7", minimum required is "1.4.6")
-- Found BOARD.dts: C:/ncs/v2.4.2/zephyr/boards/arm/nrf5340dk_nrf5340/nrf5340dk_nrf5340_cpuapp.dts
-- Generated zephyr.dts: C:/ncs/v2.4.2/nrf/samples/mcuboot_smp_custom_key/build/zephyr/zephyr.dts
-- Generated devicetree_generated.h: C:/ncs/v2.4.2/nrf/samples/mcuboot_smp_custom_key/build/zephyr/include/generated/devicetree_generated.h
-- Including generated dts.cmake file: C:/ncs/v2.4.2/nrf/samples/mcuboot_smp_custom_key/build/zephyr/dts.cmake

warning: UART_CONSOLE (defined at drivers/console/Kconfig:43) was assigned the value 'y' but got the
value 'n'. Check these unsatisfied dependencies: SERIAL_HAS_DRIVER (=n). See
http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_UART_CONSOLE and/or look up UART_CONSOLE in
the menuconfig/guiconfig interface. The Application Development Primer, Setting Configuration
Values, and Kconfig - Tips and Best Practices sections of the manual might be helpful too.


warning: UART_INTERRUPT_DRIVEN (defined at boards/shields\sparkfun_sara_r4\Kconfig.defconfig:24, boards/shields\wnc_m14a2a\Kconfig.defconfig:17, soc/arm\quicklogic_eos_s3\Kconfig.defconfig:17, drivers/serial/Kconfig:72) has direct dependencies (NETWORKING && SHIELD_SPARKFUN_SARA_R4) || (NETWORKING && SHIELD_WNC_M14A2A) || (SERIAL && SOC_EOS_S3) || (SERIAL_SUPPORT_INTERRUPT && SERIAL) with value n, but is currently being y-selected by the following symbols:
 - UART_MCUMGR (defined at drivers/console/Kconfig:190), with value y, direct dependencParsing C:/ncs/v2.4.2/zephyr/Kconfig
Loaded configuration 'C:/ncs/v2.4.2/zephyr/boards/arm/nrf5340dk_nrf5340/nrf5340dk_nrf5340_cpuapp_defconfig'
Merged configuration 'C:/ncs/v2.4.2/nrf/samples/mcuboot_smp_custom_key/prj.conf'
ies CONSOLE (value: y), and select condition CONSOLE (value: y)

error: Aborting due to Kconfig warnings

CMake Error at C:/ncs/v2.4.2/zephyr/cmake/modules/kconfig.cmake:339 (message):
  command failed with return code: 1
Call Stack (most recent call first):
  C:/ncs/v2.4.2/nrf/cmake/modules/kconfig.cmake:29 (include)
  C:/ncs/v2.4.2/zephyr/cmake/modules/zephyr_default.cmake:115 (include)
  C:/ncs/v2.4.2/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:66 (include)
  C:/ncs/v2.4.2/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:92 (include_boilerplate)
  CMakeLists.txt:7 (find_package)


-- Configuring incomplete, errors occurred!
FATAL ERROR: command exited with status 1: 'C:\ncs\toolchains\31f4403e35\opt\bin\cmake.EXE' -DWEST_PYTHON=C:/ncs/toolchains/31f4    4403e35/opt/bin/python.exe '-BC:\ncs\v2.4.2\nrf\samples\mcuboot_smp_custom_key\build' -GNinja -DBOARD=nrf5340dk_nrf5340_cpuapp '-SC:\ncs\v2.4.2\nrf\samples\mcuboot_smp_custom_key'

Procedures to reproduce this issue are as follows.

1. Unzipping mcuboot_smp_custom_key.zip to C:\ncs\v2.4.2\nrf\samples folder.

2. cd C:\ncs\v2.4.2\nrf\samples\mcuboot_smp_custom_key

3. west build -b nrf5340dk_nrf5340_cpuapp

RE: Warning messages generated when west build MCUbool sample code

Raoul — Wed, 18 Oct 2023 22:52:34 GMT

Hi Snowuyl,

I remember you asking this before! You might have forgotten. Here is your previous case on the same question:

WARNING: Using default MCUBoot key, it should not be used for production

It links to a good explainer on this:

https://github.com/hellesvik-nordic/samples_for_nrf_connect_sdk/tree/main/bootloader_samples/keys_and_signatures

There is also a section on it in our docs:

https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/mcuboot/imgtool.html#incorporating-the-public-key-into-the-code

"There is a development key distributed with MCUboot that can be used for testing. Since this private key is widely distributed, it should never be used for production. Once you have generated a production key, as described above, you should replace the public key in the bootloader with the generated one."

If you don't replace that public key, anyone will be able to create a firmware update for your device, signed with the default private key.

To mitigate this, you replace the default key with your own. See the docs, or my colleague's sample: https://github.com/hellesvik-nordic/samples_for_nrf_connect_sdk/tree/main/bootloader_samples/keys_and_signatures/mcuboot_smp_custom_key

Best regards,

Raoul

PS: We are happy to answer your questions but I would like to encourage you to increase your own research and effort before posting a question to DevZone. You are opening a large number of cases already, no need to double them! Thanks.