• State Not Answered
  • Replies 3 replies
  • Subscribers 67 subscribers
  • Views 2383 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 103006
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Updating via DFU on iOS when previously paired as HOGP/HID

davman

Hi,

Repro, using the Nordic hid-profile + iOS 7.1.1:

  • Pair the nrf51822 based hid device via the iOS bluetooth menu.
  • Turn off nrf-device.
  • Boot up the nrf-device directly into DFU-mode.
  • iOS will now instantly list it as connected in the bluetooth menu.
  • as a result, the "iOS system" will steal the device (thinking it's still hid), making the custom dfu profile invisible for the nrf loader (OTA DFU update app).

Any ideas on how to solve this without requiring the user to first manually remove/"forget" the device under the iOS Preferences -> Bluetooth.

Parents
  • 0

    I don't know a lot about bonding since we aren't using it on our project. So, here is a complete guess: I would suspect that bonding used the device address to identify if if the advertising device is one that has been bonded. If that is the case, in the bootloader initialization, change the device address using the sd_ble_gap_address_set() function to one different than the random address programmed in at the factory.

Reply
  • 0

    I don't know a lot about bonding since we aren't using it on our project. So, here is a complete guess: I would suspect that bonding used the device address to identify if if the advertising device is one that has been bonded. If that is the case, in the bootloader initialization, change the device address using the sd_ble_gap_address_set() function to one different than the random address programmed in at the factory.

Children
No Data
Related