DFU OTA does not work from application

RE: DFU OTA does not work from application

Jarmo — Thu, 10 Dec 2015 08:07:34 GMT

What I did yesterday was that I replaced every single Noridic's file with the version from SDK 8.1.0 (they were from 8.0.0). Now it finally works. Unfortunately I don't have any clue what specific thing did the magic.

RE: DFU OTA does not work from application

Jarmo — Thu, 10 Dec 2015 08:06:22 GMT

Thanks for comment! But I want to share the bond information, if it means that then I can upload my application without the need to first enter the bootloader, separately. What I did yesterday was that I replaced every single Noridic's file with the version from SDK 8.1.0 (they were from 8.0.0). Now it finally works. Unfortunately I don't have any clue what specific thing did the magic. This exercise took me over 40 hours blood, toil, tears and sweat... But anyway, thanks for your support :)

RE: DFU OTA does not work from application

Hung Bui — Wed, 09 Dec 2015 16:29:33 GMT

@Jarmo: You should not copy the ble_app_hrs_dfu main to your project. It's not needed. What you should do is described in the instruction I linked before. There are 3 files need to be added as mentioned in the instruction.

But if you don't plan to share bond information. You can do these simple steps:

Write to GPREGRET a value, let say 0x55
Reset the chip using (sd_nvic_SystemReset)
Remove "if (init_softdevice)" in ble_stack_init
The bootloader should start advertise as DFUTarg.

If you still have the issue " it jams into its event loop, not being able to connect any more" Please capture a sniffer trace when you try to connect to it. You can use the nRF Master Control panel app to try to connect to the DFUTarg.

RE: DFU OTA does not work from application

Jarmo — Tue, 08 Dec 2015 20:40:30 GMT

What is the way application's connection information is passed into the bootloader? If I understood right, the existing connection with the OTA DFU central point is passed to bootloader when entering there (shared RAM or something like that?). In my case this thing seems to fail and the central point is instantly disconnected. After that, bootloader sets up its BLE stack (it becomes visible as DfuTarg) but then it jams into its event loop, not being able to connect any more.

RE: DFU OTA does not work from application

Jarmo — Tue, 08 Dec 2015 20:18:41 GMT

What should I put here?

cp_init.start_on_notify_cccd_handle    = m_hrs.hrm_handles.cccd_handle;

I do not have heart rate monitor service, thus I guess something else should be put there. And I already forgot what was that stupid CCCCCCCCCD...

RE: DFU OTA does not work from application

Jarmo — Tue, 08 Dec 2015 20:14:28 GMT

Thanks, I have followed those instructions earlier and double-checked it now, still. Also, I just converted the main file from app_hrs_dfu -example into my project, and thought my application would then do ota dfu, as well. But nope! I have really run out of ideas. Is there some size limit for the application, realated to bootloader? My app's binary is now around 21 KB in size. I guess the error might be very trivial, but since there's no feedback from the system, expect jamming, this is very difficult case :'(

RE: DFU OTA does not work from application

Hung Bui — Tue, 08 Dec 2015 14:51:22 GMT

Hi Jarmo, If you don't plan to share bond information, then you don't need device manager or app_context_load. The BSP module is to handle LED and button, I don't think it's needed. What make the difference is that we branch (jump) from application to bootloader, and we don't reinitialize the bootloader. When you reset the bootloader and have to reinitialize. They should both work (with some modification with your approach to remove the app_reset thingy, just call ble_stack_init(true);)

Have you followed the instruction here ? It should work.

RE: DFU OTA does not work from application

Jarmo — Tue, 08 Dec 2015 10:09:17 GMT

Yep, ble_app_hrs_s110_with_dfu_pca10028 seems to work well. I noted that app_context_load() and device_manager_evt_handler() -functions were missing in my app (I think those were not mentioned in dfu guide). So I added them similarly as in hrs example. However, it did not change anything, it is still not working. Now I am wondering what is BSP module? I don't have things related to that, but maybe it is something important?

RE: DFU OTA does not work from application

Hung Bui — Mon, 07 Dec 2015 13:00:00 GMT

Hi Jarmo,

Looked like you have reset the application when you jump from application to bootloader.

Could you try to test with the ble_app_hrs_with_dfu in our SDK ?

Note that in our application, we branch directly to the bootloader, not reset. Please have a look at the question C in this FAQ.

RE: DFU OTA does not work from application

Jarmo — Sat, 05 Dec 2015 14:51:35 GMT

Well, I am not actually sure if that reset thing is needed at all, because I had to change also two other lines as follows:

ble_stack_init(true); // was "ble_stack_init(!app_reset);"

RE: DFU OTA does not work from application

Jarmo — Sat, 05 Dec 2015 11:09:53 GMT

Yes it works without the application.

RE: DFU OTA does not work from application

Hung Bui — Fri, 04 Dec 2015 14:22:36 GMT

Hi Jarmo,

Have you flashed and tested with the bootloader (not the application integrate with DFU service) ? Note that the instruction in the link is to integrate the DFU service only, what this service does is to jump to the bootloader (trigger bootloader without a button). You should test and make sure the bootloader worked fine first.

Please have a look at this tutorial.