I’m troubleshooting an issue related to DFU failures using the mcuboot bootloader, and I wanted to ask a clarifying question:
When I follow the steps outline here to build the project and use the Notecard CLI to create a binpack file, does that resulting file include the bootloader itself?
Is the bootloader on the host replaced during outboard DFU?
Right now, when I build my project, Nordic’s SDK produces a merged image with both the bootloader and the app. This image has mcuboot starting at 0x00, and the application is at 0xc200. So when I tell the Notecard CLI to prepare a binpack, would I want to tell it 0x00 (which is where the bootloader begins) or 0xc200 (which is where the actual app begins)?
Troubleshooting issues has shined a spotlight on some gaps in my understanding of the details of what’s going on during outboard DFU.
Thanks for any clarity you can provide!
Scott