Using SES for debug w/ mcuboot

[jbrzozoski]

If I build/flash from the command line with "west build -b nrf9160_pca10090ns" and "west flash -d build" it loads a fully combined image with mcuboot and (spm+application) in the first mcu slot.

If I build/flash from SES it appears to build everything but then the when mcuboot starts immediately reports that the primary slot is not valid, which makes me think that (spm+application) are not being flashed.

Is there any guidance on how to use Segger Embedded Studio to program and debug an application wrapped up in mcuboot?

[jbrzozoski]

As a workaround when my issue is not mcuboot-related, I've been able to adjust these settings in my prj.conf:

CONFIG_NRF_DOWNLOAD_CLIENT=n
CONFIG_IMG_MANAGER=n
CONFIG_BOOTLOADER_MCUBOOT=n

And then modify my code to bypass or stub-out the mcuboot features based on "#if defined(CONFIG_BOOTLOADER_MCUBOOT)".

I am able to program/debug the application in this form.

[Sigurd]

Hi,

This is a bug with SES v4.16, I believe it will be fixed in the next upcoming SES release (v4.17).

[jbrzozoski]

This is now working as of SES v4.18.