• State Verified Answer
  • Replies 31 replies
  • Subscribers 73 subscribers
  • Views 10961 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 117593
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Buttonless DFU Example broken

parco

Hi there,

I know you guys are very busy and I appreciate your quick response on Devzone.

I'd like to make a request for a more polished example of Buttonless DFU using SDK 12.1 with nRF52.

We are nearing production and if there's anything I'd like to get in concrete, it's a reliable way to upgrade firmware in the field.

The current example is not working out of the box, and the documentation doesn't offer a complete start to finish of how to upgrade. For example, what should we do after we send a 0x01 to the characteristic?

Thanks, Paul

Parents
  • 0

    Hi Paul,

    I guess you got part of the answer from here already.

    What is exactly the issue you are having ?

    After you send 0x01 to the characteristic, would it switch to the DFU bootloader ? Have you done any test with the DFU bootloader to update a new firmware ?

    Note that bonding information is not forward from the application to the bootloader in the current bootloader and experimental buttonless application.

    There are some bug fixes in the current experimental buttonless application, please use this version made by my colleague, Vidar. nRF5_SDK_12.1.0_buttonless_dfu.zip

  • 0 in reply to Hung Bui

    Hi Kevin,

    Sorry for misunderstanding. It's most likely the phone cached the ATT table so that you can't find the DFU control point characteristic you should write. What was the "a write/notify Characteristic" you used ? What was the UUID ? The UUID for the DFU buttonless char is 50-EA-DA-30-88-83-B8-9F-60-4F-15-F3-01-00-40-8E. You should try to turn off and on bluetooth on the phone, then use nRFConnect to connect and service discovery.

Reply
  • 0 in reply to Hung Bui

    Hi Kevin,

    Sorry for misunderstanding. It's most likely the phone cached the ATT table so that you can't find the DFU control point characteristic you should write. What was the "a write/notify Characteristic" you used ? What was the UUID ? The UUID for the DFU buttonless char is 50-EA-DA-30-88-83-B8-9F-60-4F-15-F3-01-00-40-8E. You should try to turn off and on bluetooth on the phone, then use nRFConnect to connect and service discovery.

Children
No Data
Related
Terms of service