First Time DFU

[dayizhang]

I am adding the secure DFU bootloader examples/dfu/secure_bootloader/pca10056_s140_ble/ to my existing BLE UART peripheral project. I am using SDK 16.0.0 and nrf52840.

I used mergehex to merge the bootloader, application and softdevice hex files into one file, and programmed the chip using the nrf programmer.

After programming, I found the chip is staying in the dfu mode and broadcasting as "dfutarg". I have to upload a zip file to exit the dfu mode.

I found a workaround in here: https://devzone.nordicsemi.com/f/nordic-q-a/18335/avoid-first-ota-dfu

But it seems like is out of date. 

Could you advise me how to avoid this first time DFU? It's really costing time in production lines.

[Einar Thorsrud]

Hi,

I used mergehex to merge the bootloader, application and softdevice hex files into one file, and programmed the chip using the nrf programmer.

After programming, I found the chip is staying in the dfu mode and broadcasting as "dfutarg". I have to upload a zip file to exit the dfu mode.

That is expected, as you have not flashed a valid bootloader settings page. In that case, the bootloader is not aware that a valid application is present and cannot start it. In order to avoid having to perform a DFU update to get the app running you need to generate the BL settings page as described under Generating and displaying bootloader settings, and flash that together with the app, bootloader and SoftDevice.