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

Device does not start after bootloader/softdevice DFU

[symptom]

I want to update my application/bootloader/softdevice by DFU. Steps are shown below.

  1. bootloder/softdevice update.
  2. if 1 step is done, application update comes next.

I wrote some code for iOS/Android apps based on IOS-Pods-DFU-Library/Android-DFU-Library. As a result, bootloader/sofdevice update is correctly done. However, after bootloader/sofdevice is updated, device don't start automatically for next application update(step 2).

[workaround]

Pushing the power button boots device and application update correctly follows. However, this is not good for user experience. Therefore this could not be our option.

[condition]

  • nrf51
  • S110 SoftDevice v8.0
  • single bank

Could you please give me any clue? Thanks in advance

Parents
  • @shtsht: Please correct me if I am wrong. You meant you can update the bootloader and or softdevice , but the device doesn't start in bootloader mode after you update and it requires you to turn the device off an on with a button pressed ?

    Are you sure you managed to update the bootloader successfully ? Have you verified by for example change the device name in the advertising packet? Have you tested with updating the application ? When you update the application, would the new application start automatically ?

    Have you made sure the APP_VALID bit in the bootloader is not set by accident ? When there is no application , this bit should be set as INVALID_APP.

    You may consider to modify the bootloader so you can debug it after you update the bootloader. You can have a look at question F in this FAQ.

Reply
  • @shtsht: Please correct me if I am wrong. You meant you can update the bootloader and or softdevice , but the device doesn't start in bootloader mode after you update and it requires you to turn the device off an on with a button pressed ?

    Are you sure you managed to update the bootloader successfully ? Have you verified by for example change the device name in the advertising packet? Have you tested with updating the application ? When you update the application, would the new application start automatically ?

    Have you made sure the APP_VALID bit in the bootloader is not set by accident ? When there is no application , this bit should be set as INVALID_APP.

    You may consider to modify the bootloader so you can debug it after you update the bootloader. You can have a look at question F in this FAQ.

Children
No Data
Related