OTA Bootloader dosen't start

[jane_raid]

Hello! I try to use "ble_default_bootloader_app.hex" with my app to allow OTA option for my device. (nrf51822 and SDK 7.2.0) With NRFToolbox I can connect to the device (there is no messages about missing handlers etc.) but when starting upload a .hex file, I've got a message "DFU connection has been lost." In debug mode I see that bootloader_start() func called and I can reach the last asm command as jump to bootloader. Thank you for your attention!

[Wojtek]

I assume You are using DFU service to initialize DFU-OTA? If yes, please check that Your device is advertising with the same address BEFORE connecting to that service, and AFTER initializing DFU. Device in DFU mode will advert named as DfuTarg. Also, check this blog post.

[jane_raid]

@Wojtek I see that device has the name as I define at my app. But when I connect to this with USB Dongle, I see DFU button and special DFU characteritic. By the way, device can't respond after trying to load firmware over the air (maybe it's from fail in bootloader start) :-(

[Wojtek]

Ok, so You have DFU service implemented in your app, but do You have bootloader flashed besides your app?

[jane_raid]

@wojtek I have a bootloader in Flash, when I write to Flash bootloader only, I can use OTA. Yes, I've DFU service in my app, it' s included into code like it's realised in examples.

[Hung Bui]

@jane_raid: It seems that you were using mbed bootloader but uploading nRF51 SDK's application. It should work. But could you try with the nRF51 SDK's bootloader, located at \examples\dfu\bootloader ?

You should test first by updating a normal application, not the one with DFU integrated.