DFU with NRF Connect (linux) write failure with unknown value (0x8005)

[Ramy]

Hi there,
I have been trying recently to DFU a custom device using desktop nrf connect, and I get an error message as in the following picture right after pressing start DFU

I'm using Ubuntu 18.04

as you can see nRF Connect is 3.3V, debugger is PCA10056 (nRF52840 DK)

from Log; Connectivity firmware version 4.1.1, SoftDevice API version: 3. baud rate: 1000000.

nrfjprog version: 10.5.0

JLinkARM.dll version: 6.60a

I've added udev rule, so I'm assuming that DK has permission

also please note that I've tried to DFU using same everything (DK, custom board, firmware same nRF connect version) but different windows 10 setup and it did worked ok.

in the Log, there was a message not showing also, Received status with code 4 Unknown value, message: "Error sending packet to target. Code 0x802a"

[leey]

For future users that is having the same issue; in my case, it is related to the JLink version that was running in my PCA10056; similar issue as above in using nRF_Connect for desktop(Windows 10); same issue with some "python error" messages when using nrfutil as well; my colleagues have no issue at all; been using nrfutil version 3.5.1 with SDK 15.0.0; same issue when upgrading to nrfutil 6.x.x version etc...

Out of frustration, trying to downgrade JLink to older version(from 6.62 to 5.x); but can't find the older installer; so just upgrade JLink to latest version, 6.8; and now it works; been trying all sort of different things(different PCA10056, PCA10040, running CMD in admin mode etc..., switching python from 3.7 to 2.7 etc...); the one that "fix" it is the change to JLink firmware revision(in my case going from 6.62 to 6.8x etc...).

[Vidar Berg]

Thanks for the comment. I didn't find any mention of this bug in the Jlink release notes last time I checked, so it's good to know that it was fixed by updating to Jlink version 6.8x in your case.