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

Multi packets in SDK 7.2.0 bootloader

Hi, We are doing DFU updates through a nrf51422 dongle (data passing from UART to BLE), using our own code, based on the multilink central example.

The DFU peripherals are nrf51822, s110 7.0.0, SDK 7.2.0. The central unit is nrf51422 dongle, s130 3.0.0, SDK 12.2.0.

We are trying to achieve maximum throughput by using multiple packets per connection interval (@ 7.5 ms interval). It works fine when using a single packet and even two packets per interval, but when increasing to 3 or more, packets seem to get lost, even though TX_COMPLETE event is triggered.

Based on the peripheral SD and SDK, are they suppose to support such throughput?

EDIT: I can't seem to find a way to attach the sniffer trace file. The form allows me to select a file, but doesn't seem to do anything with the file I choose.

Try this link.

This is a trace with a 12 packet notifiaction and 4 packets per connection interval (connection interval set at ~18sec). I stopped it brutally at the middle since it was very slow. The 4 sec breaks are the time we wait for a notification on the central side.

Parents
  • Hi Gili,

    Are you using Keil or use GCC, could you attach your bootloader project ? Have you modified anything in the bootloader ?

    What you saw in the hvx.data is normal. It's the acknowledge for DFU command, and the packet receipt notification with the number of byte received.

    Could you capture a sniffer trace that actually show the DFU target crash ? The one you attached showing it was the DFU master didn't want to send data.

Reply
  • Hi Gili,

    Are you using Keil or use GCC, could you attach your bootloader project ? Have you modified anything in the bootloader ?

    What you saw in the hvx.data is normal. It's the acknowledge for DFU command, and the packet receipt notification with the number of byte received.

    Could you capture a sniffer trace that actually show the DFU target crash ? The one you attached showing it was the DFU master didn't want to send data.

Children
No Data
Related