I've got a project that I'm going to want to do DFU through the UART, and in order to transfer files in a follow-on activity, I want SMP running in the application. Therefore the smp_srv sample.
In my development and test activities, I'm using a nRF52840 DK.
Following instructions at SMP server (docs.nordicsemi.com/.../README.html). The build of MCUboot works, after I specify the complete path to the code:
"west build -b nrf52840dk_nrf52840 -d build_mcuboot /c/ncs/v2.6.0/bootloader/mcuboot/boot/zephyr", and flash it. (I use "west flash -d build_mcuboot --erase", because otherwise, it finds and runs the image from a previous effort!)
However, when I build the application, it includes CONFIG_BOOTLOADER_MCUBOOT=y which apparently builds MCUboot as a child image. So building separately isn't necessary. Makes me think the sample instructions are out-of-date.
Toward the end of the build process, I try to follow the instructions for signing the image, but they don't work. However, I can flash any of the bin files of the application and they will load and run.
It's like MCUboot isn't really looking for a signature, and I didn't see anything in the instructions to tell MCUboot to do so when it was being built.