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

[Hung Bui]

Without logging it will be difficult to debug. So either you need to output UART to another GPIO pins on the chip and connect to PC (via a NRF52 DK for example) or output out log on RTT. Or you can do the test on a nRF52 DK before testing on your board. 

Another thing you can do is to read out the flash content after you flash using Segger Embedded Studio and when you program using nRF Connect Programmer  and compare them. I don't have any idea why flashing using nRF Connect Programmer would cause an issue. Please also try to program using nrfjprog.exe command line to as well. 

Did you make any modification to the bootloader ? 
If you can provide us the bootloader project, and the DFU files that you used so that we can reproduce the issue here, we can try to debug it from here.

[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. 

[pastagas]

Hello Hung,

I used mergehex to merge both softdevice and bootloader and  after I programmed the  target using nrfjprog.exe...... and it works !!!!

your gui tool programmer seems to be bugged...I hope you will fix this issue.

Thx for helping.

Best regards 

[pastagas]

Hello,

I come back to you because I see that bug is not fixed on new programmer release V1.4.8.

When do you think solving this issue ?

Best regards