Nrfutil not finding dfu target

RE: Nrfutil not finding dfu target

Einar Thorsrud — Thu, 15 Apr 2021 11:53:38 GMT

Regarding time to update that probably mostly liked by the low throughput of the pc-ble-driver and serialization scheme. There is not much optimization that can be done here as there are fundamental limits in the way it is designed. There have also been a few nrfutil versions with very slow DFU performance but that is fixed in >= 6.0.1 by this PR.

RE: Nrfutil not finding dfu target

Michal — Thu, 15 Apr 2021 10:44:59 GMT

I updated to nrfutil 6.1.0. Python version 3.7.4. I still get the same behaviour. I tested with different name but still not connecting. Also I notice that updating using nrfutil is much much longer in compare to using mobile app on my iOS device. Why is that? Is there any way to optimize it?

RE: Nrfutil not finding dfu target

Einar Thorsrud — Tue, 13 Apr 2021 12:17:04 GMT

I see. I do not see any reason it should have changed, but what if you update to the latest nrfutil? And which Python version do you use (I use 3.7.2)?

RE: Nrfutil not finding dfu target

Michal — Mon, 12 Apr 2021 13:52:55 GMT

I am using nrfutil 6.0.1. Tested with nrf52 dk and nrf52840 dk. Fails every single time, but when using address it works on each attempt.

RE: Nrfutil not finding dfu target

Einar Thorsrud — Thu, 08 Apr 2021 16:03:47 GMT

I see. I tested this now using nrfutil 6.1.0 and the nRF52 DK (also tested nRF52840 dongle) and with that both works for me. (I did experience a few times over quite a few tests that nrfutil did not manage to connect before it timed out though.)

Does this consistently fail for you, or just occasionally? Which nrfutil version do you use?

RE: Nrfutil not finding dfu target

Michal — Thu, 08 Apr 2021 12:15:42 GMT

Hi Einar,

I am running on Windows 10 64bit. Yes it worked when I tried to use address instead of name.

RE: Nrfutil not finding dfu target

Einar Thorsrud — Thu, 08 Apr 2021 11:55:13 GMT

Hi Michal,

I agree this looks odd. Which platform do you run nrfutil on? Does it work if you specify BLE address with the -a option instead of the name?