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

Secure bootloader example not working

Hi all,

I'm trying to add to our application BLE DFU feature. Therefore I'm testing first the secure bootloader example provided in the SDK v16.0.0

I managed to build the bootloader successfully and I can see the target ready for DFU and the package is sent succefully. However, the application doesn't start after the system reset although I can see in the memory layout ( using nrf connect) that the new firmware is installed. 

My question is if I'm missing something concerning the DFU mode that doesn't make the application start?

Thanks in advance

Parents
  • Hi,

    The application should be started after a successful DFU. Can you try with the debug bootloader and test again? All example bootloaders have an equivalent project sufficed with "_debug", and these have extensive RTT logging. In most cases, the log will give a good indication of what is going on.

    Generally, the bootloader will start the application if a flag indicates that it is present and the hash of the application matches a stored hash. If not, the bootloader will enter DFU mode.

Reply
  • Hi,

    The application should be started after a successful DFU. Can you try with the debug bootloader and test again? All example bootloaders have an equivalent project sufficed with "_debug", and these have extensive RTT logging. In most cases, the log will give a good indication of what is going on.

    Generally, the bootloader will start the application if a flag indicates that it is present and the hash of the application matches a stored hash. If not, the bootloader will enter DFU mode.

Children
No Data
Related