• State Verified Answer
  • Locked Locked
  • Replies 4 replies
  • Subscribers 67 subscribers
  • Views 4720 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 104394
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Bootloader only update with DFU

Adrian Eggenberger

I have added the DFU service to our own project. Normal application updates work perfectly and even the update of bootloader and softdevice is fine.

In a new case we had to update the bootloader only. The resulting behavior is a bit odd:

  1. The App downloads the new bootloader (hex-file)
  2. After the new bootloader has been downloaded the device resets to application
  3. This seams to be ok, but when checking the flash the bootloader didn't get updated
  4. After a power cycle the device enters bootmode (Why?)
  5. I download the application to the device and the device reboots to application again
  6. Now the bootloader is updated??? What happens here?

How is the update of only the bootloader working? What should happen after download of the bootloader hex-file?

Regards Adrian

Parents
  • 0

    Hi

    Have you read through the Bootloader chapter in the S110 Softdevice Specification v1.3, in order to know what happens after the bootloader+softdevice hex file is downloaded to the nRF51.

    You could debug the bootloader in order to better understand what is going on. The guide on how to enable bootloader debug is here

Reply
  • 0

    Hi

    Have you read through the Bootloader chapter in the S110 Softdevice Specification v1.3, in order to know what happens after the bootloader+softdevice hex file is downloaded to the nRF51.

    You could debug the bootloader in order to better understand what is going on. The guide on how to enable bootloader debug is here

Children
No Data
Related