Building MCUBoot separate from application.

RE: Building MCUBoot separate from application.

dejans — Fri, 08 Apr 2022 12:01:18 GMT

Hi,

I am glad to help.

Best regards,
Dejan

RE: Building MCUBoot separate from application.

Epasta — Fri, 08 Apr 2022 09:42:13 GMT

Thanks a lot for all the informations!!

RE: Building MCUBoot separate from application.

dejans — Fri, 08 Apr 2022 09:38:53 GMT

Hi,

As I have already suggested to you, building MCUboot separately from the application is not recommended. If you still insist on doing so, you would need to ensure that configuration for the images and key matches the way they should. In addition, your cmake is invoked from the application folder instead of build folder and your environment is not setup correctly.
The best way forward would probably be not to build MCUboot separately from the application.

Best regards,
Dejan

RE: Building MCUBoot separate from application.

dejans — Thu, 07 Apr 2022 16:12:39 GMT

Hi,

There is an obvious error of missing Kconfig.modules.

It is not usual to build bootloader separately. You could consider using provided MCUboot with NCS and changing it according to your particular needs.

I have made a report internally in the effort to assist you.
I'll come back to you with more information.

Best regards,
Dejan

RE: Building MCUBoot separate from application.

Frikkie Badenhorst — Wed, 06 Apr 2022 14:34:48 GMT

I uninstalled ALL instances of the SDK in the toolchain manager and only installed the latest v1.9.1.

Still, we have the same issue:

Microsoft Windows [Version 10.0.19043.1586]
(c) Microsoft Corporation. All rights reserved.


C:\nordic\v1.9.1\bootloader\mcuboot>cd boot/zephyr

C:\nordic\v1.9.1\bootloader\mcuboot\boot\zephyr>mkdir build && cd build
A subdirectory or file build already exists.

C:\nordic\v1.9.1\bootloader\mcuboot\boot\zephyr>cmake -GNinja -DBOARD=nrf5340dk_nrf5340_cpuapp
CMake Warning:
  No source or binary directory provided.  Both will be assumed to be the
  same as the current working directory, but note that this warning will
  become a fatal error in future CMake releases.


Including boilerplate (Zephyr workspace): C:/nordic/v1.9.1/zephyr/cmake/app/boilerplate.cmake
-- Application: C:/nordic/v1.9.1/bootloader/mcuboot/boot/zephyr
-- Using NCS Toolchain 1.9.1 for building. (C:/nordic/v1.9.1/toolchain/cmake)
-- Zephyr version: 2.7.99 (C:/nordic/v1.9.1/zephyr), build: v2.7.99-ncs1-1
-- Found Python3: C:/nordic/v1.9.1/toolchain/opt/bin/python.exe (found suitable exact version "3.8.2") found components: Interpreter
-- Found west (found suitable version "0.12.0", minimum required is "0.7.1")
CMake Error at C:/nordic/v1.9.1/zephyr/cmake/app/boilerplate.cmake:174 (file):
  file problem creating directory:
  C:/nordic/v1.9.1/bootloader/mcuboot/boot/zephyr/Kconfig
Call Stack (most recent call first):
  C:/nordic/v1.9.1/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:24 (include)
  C:/nordic/v1.9.1/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:91 (include_boilerplate)
  CMakeLists.txt:44 (find_package)


CMake Error at C:/nordic/v1.9.1/zephyr/cmake/zephyr_module.cmake:61 (message):
  Traceback (most recent call last):

    File "C:/nordic/v1.9.1/zephyr/scripts/zephyr_module.py", line 542, in <module>
      main()
    File "C:/nordic/v1.9.1/zephyr/scripts/zephyr_module.py", line 508, in main
      with open(args.kconfig_out, 'w', encoding="utf-8") as fp:

  FileNotFoundError: [Errno 2] No such file or directory:
  'C:/nordic/v1.9.1/bootloader/mcuboot/boot/zephyr/Kconfig/Kconfig.modules'

Call Stack (most recent call first):
  C:/nordic/v1.9.1/zephyr/cmake/app/boilerplate.cmake:175 (include)
  C:/nordic/v1.9.1/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:24 (include)
  C:/nordic/v1.9.1/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:91 (include_boilerplate)
  CMakeLists.txt:44 (find_package)


-- Configuring incomplete, errors occurred!

RE: Building MCUBoot separate from application.

dejans — Wed, 06 Apr 2022 13:31:50 GMT

Hi,

I noticed that there is an inconsistency of using both "C:/nordic/v1.9.0" and "C:/nordic/v1.6.0". Your Zephyr version is OK.
What were the SDK and Toolchain versions used when creating the application?

Best regards,
Dejan

RE: Building MCUBoot separate from application.

Frikkie Badenhorst — Wed, 06 Apr 2022 12:42:40 GMT

Hi Sigurd, we are having similar issues. We are not able to build the bootloader. When trying to install the necessary dependencies, we get a lot of warnings:

C:\nordic\v1.9.0\bootloader\mcuboot>pip3 install --user -r scripts/requirements.txt
WARNING: Ignoring invalid distribution -ip (c:\python39\lib\site-packages)
WARNING: Ignoring invalid distribution -ip (c:\python39\lib\site-packages)
Requirement already satisfied: cryptography>=2.6 in c:\users\frikkiebadenhorst\appdata\roaming\python\python39\site-packages (from -r scripts/requirements.txt (line 1)) (36.0.2)
Requirement already satisfied: intelhex in c:\users\frikkiebadenhorst\appdata\roaming\python\python39\site-packages (from -r scripts/requirements.txt (line 2)) (2.3.0)
Requirement already satisfied: click in c:\users\frikkiebadenhorst\appdata\roaming\python\python39\site-packages (from -r scripts/requirements.txt (line 3)) (8.1.0)
Requirement already satisfied: cbor2 in c:\users\frikkiebadenhorst\appdata\roaming\python\python39\site-packages (from -r scripts/requirements.txt (line 4)) (5.4.2.post1)
Requirement already satisfied: cffi>=1.12 in c:\users\frikkiebadenhorst\appdata\roaming\python\python39\site-packages (from cryptography>=2.6->-r scripts/requirements.txt (line 1)) (1.15.0)
Requirement already satisfied: colorama in c:\python39\lib\site-packages (from click->-r scripts/requirements.txt (line 3)) (0.4.4)
Requirement already satisfied: pycparser in c:\users\frikkiebadenhorst\appdata\roaming\python\python39\site-packages (from cffi>=1.12->cryptography>=2.6->-r scripts/requirements.txt (line 1)) (2.21)
WARNING: Ignoring invalid distribution -ip (c:\python39\lib\site-packages)
WARNING: Ignoring invalid distribution -ip (c:\python39\lib\site-packages)

Then after trying to build the bootloader for the nrf5340, we get errors:

C:\nordic\v1.9.0\bootloader\mcuboot>cd boot/zephyr

C:\nordic\v1.9.0\bootloader\mcuboot\boot\zephyr>mkdir build && cd build
A subdirectory or file build already exists.

C:\nordic\v1.9.0\bootloader\mcuboot\boot\zephyr>cmake -GNinja -DBOARD=nrf5340dk_nrf5340_cpuapp
CMake Warning:
  No source or binary directory provided.  Both will be assumed to be the
  same as the current working directory, but note that this warning will
  become a fatal error in future CMake releases.


Including boilerplate (Zephyr workspace): C:/nordic/v1.9.0/zephyr/cmake/app/boilerplate.cmake
-- Application: C:/nordic/v1.9.0/bootloader/mcuboot/boot/zephyr
-- Using NCS Toolchain 1.9.0 for building. (C:/nordic/v1.9.0/toolchain/cmake)
-- Zephyr version: 2.7.99 (C:/nordic/v1.9.0/zephyr), build: v2.7.99-ncs1
-- Found Python3: C:/nordic/v1.9.0/toolchain/opt/bin/python.exe (found suitable exact version "3.8.2") found components: Interpreter
-- Found west (found suitable version "0.12.0", minimum required is "0.7.1")
CMake Error at C:/nordic/v1.9.0/zephyr/cmake/app/boilerplate.cmake:174 (file):
  file problem creating directory:
  C:/nordic/v1.9.0/bootloader/mcuboot/boot/zephyr/Kconfig
Call Stack (most recent call first):
  C:/nordic/v1.9.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:24 (include)
  C:/nordic/v1.9.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:68 (include_boilerplate)
  C:/nordic/v1.6.0/zephyr/share/zephyr-package/cmake/zephyr_package_search.cmake:101 (include)
  C:/nordic/v1.6.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:95 (check_zephyr_package)
  CMakeLists.txt:44 (find_package)


CMake Error at C:/nordic/v1.9.0/zephyr/cmake/zephyr_module.cmake:61 (message):
  Traceback (most recent call last):

    File "C:/nordic/v1.9.0/zephyr/scripts/zephyr_module.py", line 542, in <module>
      main()
    File "C:/nordic/v1.9.0/zephyr/scripts/zephyr_module.py", line 508, in main
      with open(args.kconfig_out, 'w', encoding="utf-8") as fp:

  FileNotFoundError: [Errno 2] No such file or directory:
  'C:/nordic/v1.9.0/bootloader/mcuboot/boot/zephyr/Kconfig/Kconfig.modules'

Call Stack (most recent call first):
  C:/nordic/v1.9.0/zephyr/cmake/app/boilerplate.cmake:175 (include)
  C:/nordic/v1.9.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:24 (include)
  C:/nordic/v1.9.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:68 (include_boilerplate)
  C:/nordic/v1.6.0/zephyr/share/zephyr-package/cmake/zephyr_package_search.cmake:101 (include)
  C:/nordic/v1.6.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:95 (check_zephyr_package)
  CMakeLists.txt:44 (find_package)


-- Configuring incomplete, errors occurred!

This is quite frustrating, as we are experiencing a lot of issues when using NCS tools. Please advise

RE: Building MCUBoot separate from application.

dejans — Wed, 06 Apr 2022 12:15:12 GMT

Hi,

<board> is the name of the board in your project that you want to build for. This can be your custom board or the board included in NCS.
For example, for the custom board named reel_board

Use cmake to configure a Ninja-based build system:
cmake -B build -GNinja -DBOARD=reel_board samples/hello_world

As another example, for nRF9160-DK the option would be

-DBOARD=nrf9160dk_nrf9160ns

Best regards,
Dejan

RE: Building MCUBoot separate from application.

Epasta — Tue, 05 Apr 2022 15:20:45 GMT

Hello,

sorry to border you but i'm stucked in the building procedure of the mcuboot.

I'm following that documentation Build MCUBoot with zephyr but i can not undestand this command:
"cmake -GNinja -DBOARD=<board> .."

Which is the file that i have to put instead of "borad"? Which is the right path?
Every time that i insert a board i receive back from the cmc "Access Denied".
Can you provide me an example about this command?

Thank's for your help

RE: Building MCUBoot separate from application.

dejans — Wed, 30 Mar 2022 14:26:01 GMT

Hi Frikkie,

[quote user=""]

We however would like to be able to build MCUBoot in its own seperate project (SES/VS Code). This will allow us to easily customize the bootloader where needed and also access the sources:

1) Is this possible? Is there an example project for this?

[/quote]

Yes, it should be possible to build MCUboot as a separate project. You can find more information about bootloader and mcuboot repositories on bootloader, mcuboot and sdk-mcuboot.

[quote user=""]2) Please provide information on how to set this up/configure/build MCUBoot separately.[/quote]

This is dependent on the operating system you choose. We have extensive documentation regarding bootloader and building and using MCUboot with Zephyr.

Best regards,
Dejan