Cant get mcuboot to work on a Fanstel module with BT840F (nRF52840)

[BobS]

I've had success getting the Sigurd Hellesvik Serial Recovery sample to work on an nRF52840 DK with mcumgr cli commands.  I'm able to flash the Fanstel 840 with the same bootloader sample with a simple dts overlay file.   I have the timeout flags set in the mcuboot.conf file:

CONFIG_BOOT_SERIAL_WAIT_FOR_DFU=y

CONFIG_BOOT_SERIAL_WAIT_FOR_DFU_TIMEOUT=5000

"hello world" is written 5 sec after reboot, so I assume its running correctly.  But any mcumgr command times out:

"mcumgr -c acm0 image list"

Error: NMP timeout

The led from CONFIG_MCUBOOT_INDICATION_LED=y only works with the button trigger, not with the wait for DFU. But it doesn't work on the DK either, so I'm not concerned.

I've verified that the mcumgr cli works.  As I say, all works fine on an nRF52840 DK.

I used the nRF52840 DK ->All boards base for the project.  Maybe I should use another?  Don't see anything special for a Fanstel module.  

I've only had to move the uart0 pins with an overlay and that works. 

I've seen references to these flags, but it fails to build.

CONFIG_MCUMGR=y

CONFIG_MCUMGR_SMP_UART=y

I appreciate any and all suggestions.  Thanks.

Bob

[BobS]

I've found no solution to this yet...mcumgr commands timeout.

• Should mcuboot work on the Fanstel module with a BT840F?
  
• Should I be using the nRF52840 DK as the platform template for the project? NC for pins 6 and 8 (uart0) on the BT840X.  But moving uart0 to 12 and 13 works for the application, not bootloader. 
• It acts like the overlay doesn't effect the bootloader.  Could this be a separate config flag?

Thanks again for any help.

Bob

[Tristen]

 BobS , you need to provide overlays for a child image (e.g. mcuboot) using it's own overlay file. The build system automatically applies any device tree overlay located in the child_image folder provided you follow the schema (e.g. <project_root>/child_image/mcuboot/boards/nrf52840dk_nrf52840.overlay). So make sure your uart0 overlay changes are also applied in the mcuboot child image overlay. By the way, the same thing applies to *.conf files, which can configure the way mcuboot is built. If you haven't already, make sure to set in your parent image conf CONFIG_BOOTLOADER_MCUBOOT=y to signify it will be chain loaded by MCUboot. 

For more information regarding multi-image builds, you may be interested in Nordic's documentation here.