Issue with OTA DFU on NRF 52832

[pastagas]

Hello,

I have tested secure_bootloader_ble_s132_pca10040 project with Segger Embedded Studio. it works fine and I can update my application.zip via nrfConnect android application. Once it is finished, my application start without problem.

After that, I made an hex image of bootloader. I put it with softdevice.hex in the windows programmer of nfrConnect and I flashed the nrf52832. The bootloader runs and 

I can update my application via OTA. But once updating is finished, the bootloader don't launch my application.it keeps running and the only thing I can do is updating again....

Best regards

[pastagas]

Hello Hung,

Sorry for late reply, I was busy with another project.

You find below two pictures. They show memory mapping after a dump.

"Mapping_Bootloader_Only_SES" is a dump after programming device with SES. This image works well.

"Mapping_Bootloader_Only_Nrf_Programmer" is a dump after programming device with nrf programmer. In this case I have add separately bootloader.hex and softdevice 6.1.1.hex in the file memory layout window. After that I programmed the device. This image doesn't work

As you can see there are many differences that can explain why the second image doesn't work. 

Best regards

Mapping_Bootloader_Only_SES"

Mapping_Bootloader_Only_Nrf_Programmer

[Hung Bui]

Hi,
After you do hex dump do you have the .hex files ? 
You can use Notepad++ for example to compare the 2 hex files and can better see the difference. 
From what you showed it's only the difference in the bootloader setting and the MBR page param.

Please try to test programming (and hex dumping) using the nrfjprog.exe tool.