Using SEGGER embedded studio for ARM (Nordic Edition) v5.60. using Project-> Configure nRF Connect SDK Project Fails in configuring MCUBoot in Zephyr.
No Documentation on HOW TO USE!
Using SEGGER embedded studio for ARM (Nordic Edition) v5.60. using Project-> Configure nRF Connect SDK Project Fails in configuring MCUBoot in Zephyr.
No Documentation on HOW TO USE!
In the SEGGER embedded studio goto the tab 'Project' then goto the tab 'Configure nRF Connect SDK Project'. It will open up a window and populate the window from the "<project> / <build> / zephyr / .config " file.
If you look 'Available Modules' you will see mcuboot is available. Scroll down and expand 'Boot Options' click the 'MCUboot bootloader support'. the variable 'Path to the mcuboot signing key file' is set to my <project>/src, which has a mykey.pem file I manually generated from 'bootloader/mcuboot/scripts/imgtool.py '. The variable field 'Extra arguments to pass to imgtool' is left blank(since just did it by hand).
Then click the box 'Configure'.
SWIRLS around and the RED banner " Cannot Configure project " create_nordic_project.py failed (1). Then click OK on the error banner.
Go back to the tab 'Project' then goto the tab 'Configure nRF Connect SDK Project'. The window comes up blank. And MCUboot project is not in my solution.
I am attaching .config and .config.old.
Do You Need Screenshots?
Do you need error logs? and where would they be found?
In the SEGGER embedded studio goto the tab 'Project' then goto the tab 'Configure nRF Connect SDK Project'. It will open up a window and populate the window from the "<project> / <build> / zephyr / .config " file.
If you look 'Available Modules' you will see mcuboot is available. Scroll down and expand 'Boot Options' click the 'MCUboot bootloader support'. the variable 'Path to the mcuboot signing key file' is set to my <project>/src, which has a mykey.pem file I manually generated from 'bootloader/mcuboot/scripts/imgtool.py '. The variable field 'Extra arguments to pass to imgtool' is left blank(since just did it by hand).
Then click the box 'Configure'.
SWIRLS around and the RED banner " Cannot Configure project " create_nordic_project.py failed (1). Then click OK on the error banner.
Go back to the tab 'Project' then goto the tab 'Configure nRF Connect SDK Project'. The window comes up blank. And MCUboot project is not in my solution.
I am attaching .config and .config.old.
Do You Need Screenshots?
Do you need error logs? and where would they be found?
Hi,
Aha, I see the same. This works if you set CONFIG_BOOTLOADER_MCUBOOT=y in prj.conf instead of setting it via Configure nRF Connect SDK Project', and that is anyway where you need to set it for this to be persistent after you clean the build folder. So that should be an OK workaround. I have not been able to clarify why this fails though, but it seems there is a problem adding sub-images via SES like this.
all of the errors suggest the solution is lacking proper cmake directions. And you must be able run 'Configure nRF Connect Project' otherwise you will have a bad ZEPHYR build.
Hi,
MikeSix said:No , that does not work. This is the error log...
Can you explain exactly what you did? And perhaps even better if it is possible to reproduce this by modifying a sample project so that I can reproduce on my side? Adding the MCUBoot configuration in prj.conf and opening the project in SES (from File -> Open nRF Connect DK Project...) should work and does on my side.
MikeSix said:you must be able run 'Configure nRF Connect Project' otherwise you will have a bad ZEPHYR build.
I did not understand that. Can you elaborate? (Generally, using Configure nRF Connect Project (or menuconfig/guiconfig for that matter) is mostly relevant for experimenting. To make changes persistent after cleaning the build folder you need to make the changes in prj.conf or similar, and not within the build folder.)
Here is a project I just tried.
Hi,
This fails because of other things regardless of the state of CONFIG_BOOTLOADER_MCUBOOT=y when I test with NCS 1.7.0. Which NCS version is this supposed to work with? I also see references to GAZELL_* configs which are not part of the SDK. Can you explain the environment that you use with this?
(Independent of the issue with getting your sample to run, as it fails regardless of how I try, I suggest you consider if SES is what you want to use going forward. Building from the command line or using the recently released VS Code plugin typically gives you a better experience and less problems).