• State Suggested Answer
  • Replies 18 replies
  • Answers 1 answer
  • Subscribers 74 subscribers
  • Views 6673 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 240634
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

nrfutil DFU upload extremely slow

Florian Zierer

as already written in other threads (two years old) the DFU upload with nrfutil is extremely slow.

Transferring the same data from a smartphone (with BLE5) takes about 20seconds, with nrfutil 2 minutes or more.

We use nrf52840 DKs for the PC side and our board.

We use the following command to run the update.

nrfutil dfu ble -ic NRF52 -pkg app_dfu_package.zip -snr $(NRF52840_SNR_BLE) -n "MY_NAME" -f -cd 0

nrfutil version 6.0.0a1

What could be the reason for the slow update. Is there anything we can do to speed this up?

Parents
  • 0

    Hello,

    So the device that is "connected" to nrfutil, the nRF52840 DK. Can you please test by using the same DK on nRF Connect for Desktop to perform the DFU? Is the speed the same there?

    What nRF chip does your target use? I assume that this is not the issue, since it is faster using the smartphone.

    The nRF52840 DK is erased at one point between two years ago and now? So that it is not running the nrfutil FW flashed 2 years ago? Try "nrfjprog -e" before the "nrfutil dfu ble ..."

    So. 

    1. Please test nRF Connect for Desktop.

    2. Please try to update nrfutil to the non-alpha version 6.0.0 found here. 

    Let me know about your results. 

    BR,
    Edvin

  • 0 in reply to Edvin

    Hi Edvin,

    the connectivity firmware on the nrf52840 DK was recently flashed.When using nrfConnect (2.6.2) another fw is flashed.

    With nrfConnect the upload speed is similar as from a smartphone.

    The target uses also nrf52840.

    The non alpha version shows the same behaviour.

    We tested this from Linux and Windows.

    Florian

  • 0 in reply to Florian Zierer

    Hello Florian,

    I am struggling a bit with reproducing this. In my case it takes roughly the same time to transfer a DFU image using nRF Connect for Desktop and nrfutil. I didn't time it, but it was roughly 20 seconds, and nowhere near the 2 minutes. 

    Is your DFU image, i.e. the application particularly big, or similar to the size of the examples in the SDK?

    Did you change anything in the bootloader? What SDK is the bootloader from, and what softdevice do you use?

    Best regards,

    Edvin

  • 0 in reply to Edvin

    Hi Edvin,

    the .zip package has 230 kByte.

    I just checked again with a stopwatch. It takes 2 minutes with nrfutil and 25 seconds with nrfConnect Desktop.

    We are using SDK 15.0.0 for the app and the bootloader and s140_nrf52_6.0.0_softdevice.hex

    The bootloader is minimally modified (jumps automatically after 5s into app), but no changes on the transmission code.

    Could it be, thath the 2MBit mode is not used from nrfutil?

    I tried changing the mtu but it doen't make a difference when setting it to 23 or 247. Perhaps it is always using 23?

    -> I just saw when running with -v -v -v -v that the MTU change seems to work

    2019-12-06 16:28:48,045 BLE: Enabling longer ATT MTUs
    2019-12-06 16:28:48,105 ATT MTU exchanged: conn_handle=0 att_mtu=247
    2019-12-06 16:28:48,105 New ATT MTU is 247
    2019-12-06 16:28:48,106 BLE: Enabling Notifications

    Best Regards,

    Florian

  • 0 in reply to Florian Zierer

    Hello,

    Do you have an application hex that I can try that is about the same size as the one you use?

    What is the throughput (approximately) when you use nRF Connect for Desktop?

    When you measure the time using nrfutil, do you time it from you see the progress bar, or from you start programming the connectivity board (the pca10056)?

  • 0 in reply to Edvin

    Hi Edvin,

    unfortunately, I can't share the hexfile.

    nrfConnect shows 8-9 kb/s.

    With nrfutil, I stop only the time when the progress bar is visible. Usually, the connectivity fw is already flashed so I start it without -f.

    Could it be the missing 2MBit mode in nrfutil? At least in pc-ble-driver-py it is not directly available. (https://devzone.nordicsemi.com/f/nordic-q-a/54895/phy-update-procedure)

  • 0 in reply to Florian Zierer

    I don't think 2MBPs is supported in nrfutil, no, but it isn't in nRF Connect for Desktop either. 

    Can you please double check what version of nrfutil you have in your path? You can use the command "nrfutil version" from a folder that isn't in the same folder as nrfutil.exe, to make sure that you have the correct version in your path.

    nrfutil and nRF Connect use a very similar FW. What was updated in a recent version (not sure which one) was that they started to use longer MTU and DLE, which significantly increases the speed.

    BR,
    Edvin

Reply
  • 0 in reply to Florian Zierer

    I don't think 2MBPs is supported in nrfutil, no, but it isn't in nRF Connect for Desktop either. 

    Can you please double check what version of nrfutil you have in your path? You can use the command "nrfutil version" from a folder that isn't in the same folder as nrfutil.exe, to make sure that you have the correct version in your path.

    nrfutil and nRF Connect use a very similar FW. What was updated in a recent version (not sure which one) was that they started to use longer MTU and DLE, which significantly increases the speed.

    BR,
    Edvin

Children
Related
Terms of service