Using SDK17.0.2 and added secure, dual bank, button based bootloader DFU for use with our application.
Was based on DK52 secure bootloader debug example.
It all works as expected when programming Bootloader, SD (and application) using nRF Connect .
After programming the debug indicates bootloader/DFU is working as expected and will enter DFU update mode if the button is pressed on powerup.
Can successfully do the DFU update using a signed and versioned package.
The problem is that I cant get a production single .hex package to work.
I do a nrfjprog -f nrf52 --recover before programming using nrfjprog --program and then the .hex package.
It programs ok but the bootloader/DFU don't run.
I don't see any of the debug info that worked when the device was programmed using three files and nRF Connect to program.
Are there additional steps in the process or changes in sdk17.0.2 that are automatically handled by nRF Connect ?
Does (for example) nRF Connect generate and program bootloader settings that need to be addressed in the nrfprog process steps ?
If so please point me to an example or related documentation.
