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

DFU from application

Alex Zhang

Hello Expert,

I am using SDK 6.1 and Softdevice 7.1.0 (s110) for our 256K/32K nrf51822 platform. As of now I wanna port DFU feature into our project. Of course, when burnt with bootloader, nRF toolbox can find device and upgrade application correctly. But you know, I dont wanna add DFU service in my application since the limitted flash memeory size and extra BLE power consuming. if so, please guide me how to enter DFU mode in my application. AFAIK, I must handle uncompleted flash operation and ble disconnection, right? And then, any points to be shared with me? Directly excute NVIC_SystemReset? But how does bootloader know it's from DFU not WDT or power-up?

Another question I found is that when my Android phone installed both nRF toolbox and nRF UART application, DFU APP cannot connect nrf51822 DFU service, it will disconnect unexpectedly in a very short time. My Android version is Lollipop. Any clues?

Thanks, Alex

  • 0 in reply to Hung Bui

    No the softdevice won't send the indication automatically, you need to send it by calling sd_ble_gatts_service_changed(). However, the existence of this characteristic can tell the central device that the att table maybe changed, and he can act differently. At least it's the case on iOS device. When you are not bonded and you have service changed characteristic, the phone will try to do service discovery every time it reconnects.

    The option to change the address should be a good solution if you ok with doing bootloader without the encrypted link.

  • 0 in reply to Hung Bui

    OK. I think we can accept unencrypted link druing DFU, so I just call sd_ble_gap_address_set, right? which para can I choose for my case? BLE_GAP_ADDR_CYCLE_MODE_AUTO is not good, it will change every BLE_GAP_DEFAULT_PRIVATE_ADDR_CYCLE_INTERVAL_S seconds.BLE_GAP_ADDR_TYPE_PUBLIC or BLE_GAP_ADDR_TYPE_RANDOM_STATIC, which is better? How to get a private address, any example code?

  • 0 in reply to Hung Bui

    You can have a look at the dfu_transport_update_start() function where we increase the address by 1 when we start bootloader from a button press.

    The default address of our chip is RANDOM STATIC Address. Public address should be the address in address domain your company registered with Bluetooth SIG.

    Private address as far as I remember, is just the name to distinguish with public address and the random static address.

Related