DFU bootloader not getting along with softdevice and the app

RE: DFU bootloader not getting along with softdevice and the app

Hung Bui — Tue, 14 Apr 2020 09:21:27 GMT

Hi Meme,

I'm sorry for late response. I was on Easter vacation.
To rule out any issue with your app, could you try updating the default hrs example or a blinky example ?
Please make sure the app works fine when you simply flash it with the softdevice (no bootloader) before testing.

RE: DFU bootloader not getting along with softdevice and the app

meme — Fri, 03 Apr 2020 20:26:47 GMT

Thanks Hung Bui. Yes, I already read in implemented your excellent tutorial to get to this stage. It is well written and I followed it fully.

I tried the following based on your suggestions:

- erased the device fully, then flashed the bootloader from V16. The device reboots into DFU mode and advertises as dfutarg.

- I used DFU in the iPhone app to then just flash the app. The app uploads without any error but the app fails to run.

- I then erased everything, put in the bootloader, then DFU'd the soft device (s132) and the device rebooted into bootloader mode

- I then DFU'd the app alone and the headset reboots but the app does not run.

For all the above I set the hw-version to 52. In the sdk_config.h file of the bootloader example I am using this is set to 34; that's why I originally used 34 in the nrfutil task.

Perhaps what is wrong is that the destination address of my app, or SD are in error now that I have a bootloader loaded. Can you explain how these destinations are chosen, or where I can inspect them? Are they the prefixes in the .hex files?

Thank you for your time.

RE: DFU bootloader not getting along with softdevice and the app

Hung Bui — Fri, 03 Apr 2020 13:24:40 GMT

Hi Meme,

Have you tried to test DFU just the app first before testing with app+softdevice. Would DFU only app works ?
I assume when you test DFU softdevice+app you were updating the same softdevice ?
Why did you use hw-version 34 ? By default the hw-version would be either 52 (nRF52) or 51 (nRF51).

It's possible to debug the bootloader by removing the optimization , set it to 0. But you would need to change the start address of your bootloader to move it down to make more space for it (make sure you do an erase all before re-testing)

I have a step by step guide here for DFU, maybe you can have a look ? https://devzone.nordicsemi.com/nordic/short-range-guides/b/software-development-kit/posts/getting-started-with-nordics-secure-dfu-bootloader