Application doesn't start after updateing with BLE DFU

[RomainExo]

Hi all,

I am having issues with the BLE DFU process with both nRF51822 and nRF52832 (with different applications). I use the nRF Connect application to update my device with a .zip (Distribution packet).

The bootloader starts and the transfert of the application is OK (100%).

My problem is that after the transfert, the application doesn't starts. I am obliged to remove the power supply and put it back to make it start ...

Is someone has an idea of where it could come from?

[bjorn-spockeli]

Are you using the bootloader from SDK v11.0.0 or SDK v12.x.0? Are you having issues with DFU on the nRF51822, the nRF52832 or both?

[RomainExo]

I am using SDK 10. The problem is present with nRF51822 and nRF52832. I am working with a debugger and it seems that after the update by DFU, the application is well launched crashes afetr BLE initialisations ...

The softdevice is:

For the nRF52832: s132_nrf52_2.0.0-7.alpha_softdevice. For the nRF51822: s110_nrf51_8.0.0_softdevice.

[bjorn-spockeli]

You're using the standard bootloader or the experimental bootloader with signing? Could you provide the version number of the kit if you're using a nRF52 DK or the chip marking if you're using a custom board with a nRF52? I strongly suggest that you use a production-ready SoftDevice on the nRF52 instead of the alpha version.

[RomainExo]

I use custom boards. The chip is : N52832 QFAAB0 1619BL

[bjorn-spockeli]

Ok, then you should use either S132 v2.0.x or the newer S132 v3.0.0, please see this Infocenter page. Are you using the standard bootloader, i.e. no signing?