build mcuboot on nrf52dk-52832

[jwillner1958]

I have tried to build the bootloader mcuboot on my nrf52dk-nrf52832

with an hello world example and the above mentioned board 

for that I set 

CONFIG_BOOTLOADER_MCUBOOT=y

there is a description in case 

https://devzone.nordicsemi.com/f/nordic-q-a/69147/what-is-the-right-hex-file-to-use-to-program-the-device-via-mcuboot-dfu

that explained, that now several additional hex-files should be generated.... 

When you build an application/sample with CONFIG_BOOTLOADER_MCUBOOT=y in prj.conf, the build system will automatically build the MCUboot sample \ncs\v1.4.0\bootloader\mcuboot\boot\zephyr and the generated MCUboot build output wil get put into <your sample>\<build folder>\mcuboot\zephyr. The mcuboot hex file is the file <your sample>\<build folder>\mcuboot\zephyr\zephyr.hex

But can't find any of them in my build directory ....
A collegue of mine tried that with visual studio and there it was working. 

Any Idea of additional steps to do...?

is there a fools-rush-in for working with mcuboot and mcumgr ?

br joachim 

[Edvin]

Hello Joachim,

What nRF Connect SDK version are you using? How are you building your application? Did you build using command line? Does the application build successfully after you added CONFIG_BOOTLOADER_MCUBOOT=y in your prj.conf?

Best regards,

Edvin

[jwillner1958]

Hello Edvin. I am working on a Mac with vscode 

I am using

nRF Connect SDK = Zephyr 3.0.0-rcs (/Users/jw/zephyrproject)

rRF Connect Toolchain = 2.2.0 (/opt/nordic/ncs/toolchains/v2.2.0)

If I set CONFIG_BOOTLOADER_MCUBOOT=y
project will be build and flashed but don't start any more (before I have erased the complete memory with nrfjprog -e) 

In VSCode output files only zephyr.hex is available. 

br joachim 

[jwillner1958]

I have found, that I should use 
nRF Connect SDK = V2.2.0 and everything is working well.
br joachim