OTA Bootloader dosen't start

RE: OTA Bootloader dosen't start

Hung Bui — Mon, 28 Sep 2015 14:47:25 GMT

Hi Jane,

Note that if you are using 16kB RAM variant, you would need to reconfigure the project setting as mentioned here.

If that doesn't help, please let me know your testing steps, including SDK version, chip version, your board schematics.

RE: OTA Bootloader dosen't start

jane_raid — Thu, 24 Sep 2015 15:17:58 GMT

@HungBui Ok, I try to use a standart Nordic's bootloader, but at function crc16_compute() I have a jump to HardFaultHandler() throw the some jumps to SystemCoreClockUpdate(). I think I have problem like this devzone.nordicsemi.com/.../ P.S. I have similar errors at SDK 7.2.0 and 9.0.0

RE: OTA Bootloader dosen't start

Hung Bui — Mon, 21 Sep 2015 07:36:30 GMT

@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.

RE: OTA Bootloader dosen't start

jane_raid — Fri, 18 Sep 2015 10:25:19 GMT

@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.

RE: OTA Bootloader dosen't start

Wojtek — Fri, 18 Sep 2015 09:50:41 GMT

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

RE: OTA Bootloader dosen't start

jane_raid — Fri, 18 Sep 2015 09:34:45 GMT

@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) :-(

RE: OTA Bootloader dosen't start

Wojtek — Thu, 17 Sep 2015 15:11:13 GMT

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.