This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Issue with OTA DFU on NRF 52832

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

Parents
  • Hello,

    In brief again:

    - when sdk + bootloader programmed with Segger Embedded Studio, updating works.

    -  when sdk + bootloader programmed from an image (sames binaries than those working SES) with nordic programmer V 1.4.2, updating works but application is not launched. Worst: With pca10040_ble_debug, I can upload the firmware but after nothing occurs. A new upload is impossible, device seems not working and there is not advertising anymore.

    "f it's the case I would suggest to try printing out logging on UART and check what's the issue"

    Bjorn asked me to do the same thing and my response was:

    Which uart are you talking about ?

    Ble module is soldered on our own card and its uart is connectect to MCU uart of the card. I put a breakpoint on MCU uart interrupt to see at least if ble module send log frames, but nothing happens...

    Best regards

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

Reply
  • 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.

Children
No Data
Related