dfu fails only if bonded

[seanbites]

Hello,

Thanks for reading this! I have an odd behavior on my nrf52832 where I am capable of uploading a new firmware via BLE DFU to the peripheral device if it is not bonded to the central device. However, when I bond, the DFU always fails. I suspect it is for this reason, ie the NOINIT section in the ram is not retaining my bond information when passing to the bootloader. I am using Elcipse GCC, so in order to rectify this, I have to modify this linker script: dfu_gcc_nrf52.ld. I dont know how to do so, can anyone point me in the right direction? Is there any way to check that there is indeed bond information retention?

Thank you very much for your time.

edit for phone screenshot:

[Hung Bui]

@seanbites: It worked fine on my Galaxy S6. Make sure you have the latest version of Master Control Panel. I don't see any reason it allowed to selected the file if you use bootloader from SDK v0.9 but not if you bootloader from SDK v11. Could you take a screenshot ?

I would suggest you to update the bootloader so that you can run it in debug mode. Please have a look here. You can debug and find why the bootloader won't jump to the application.

But I suggest to fix the stuff step by step, by first make the bootloader does its job, do DFU.

If you plan to use the sniffer on nRF52 board, you may need to match the UART pins with what we have on the PCA10028 or PCA10031 (08=RTS, 09 = TXD, 10= CTS, 11= RXD)

I don't think you need any modification to make the bootloader work with bonding in SDK v0.9.2