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

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

Vidar Berg — Mon, 29 Jun 2020 08:15:22 GMT

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.

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

leey — Sun, 28 Jun 2020 15:10:48 GMT

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...).

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

DamienB — Thu, 20 Feb 2020 15:11:37 GMT

I upgraded to V6.62b without any success.
I upgraded and downgraded nRF Command Line Tools without success too..

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

Vidar Berg — Thu, 20 Feb 2020 10:10:17 GMT

Thanks for confirming that it does work with the native USB. I suspect it may be an issue introduced by a more recent version of the J-link driver. So it might be worth trying to update or downgrade the driver, although I have not been able to reproduce the error here.

[quote userid="74452" url="~/f/nordic-q-a/56570/dfu-with-nrf-connect-linux-write-failure-with-unknown-value-0x8005/235361"]It seems also working without connecting P0.18 to P0.24. What is that for ?[/quote]

It seems to be required to support the DFU triggering mechanism, which is optional. This connectivity FW is really compiled for nRF52840 Dongle, see https://github.com/NordicSemiconductor/pc-ble-driver#supported-development-kits

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

DamienB — Thu, 20 Feb 2020 08:57:28 GMT

It seems also working without connecting P0.18 to P0.24. What is that for ?

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

DamienB — Thu, 20 Feb 2020 08:52:04 GMT

Oh okay sorry i did not understand. Now it works, it DFU properly my board and it was quicker than how i used to do it before.

Do you know why it doesn't work with the previous way ?

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

Vidar Berg — Thu, 20 Feb 2020 08:39:52 GMT

It looks like you are still connecting with the Jlink. Do you have a USB cable connected to the nRF USB?

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

DamienB — Thu, 20 Feb 2020 08:29:59 GMT

Are you sure it is the right file ? It shouldn't be s140 ?
I am getting an error with this FW when i connect to it using nRF Connect :

09:25:03.909

Application data folder: C:\Users\D.Berger\AppData\Roaming\nrfconnect\pc-nrfconnect-ble

09:25:05.907

Validating connectivity firmware for device with serial number 000683954026...

09:25:06.885

Connectivity firmware is valid.

09:25:06.885

Getting information from J-Link debugger...

09:25:08.119

Found device type: unknown. J-Link firmware: J-Link OB-SAM3U128-V2-NordicSemi compiled Jan 21 2020 17:30:48.

09:25:08.120

Connectivity firmware version: 4.1.1. SoftDevice API version: 3. Baud rate: 1000000.

09:25:08.120

Opening adapter connected to COM6

09:25:09.042

Successfully opened COM6. Baud rate: 1000000. Flow control: none. Parity: none.

09:25:09.043

Reset performed on adapter COM6

09:25:10.846

Received status with code 0 PKT_SEND_MAX_RETRIES_REACHED, message: 'No response from device. Tried to send packet 6 times.'

09:25:12.043

serial port COM6 closed.

09:25:12.061

Error occured when opening port. Errorcode: NRF_ERROR_TIMEOUT (0xd)

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

Vidar Berg — Thu, 20 Feb 2020 07:37:41 GMT

Maybe you have a newer version of the JLinkARMdll now? You may try to use the nRF USB instead and see if you get the same result. To do that you need to flash the connectivity FW attached below that includes the nRF USB stack and connect P0.18 to P0.24 on your board.

Connectivity FW used for nRF52840 Dongle:

devzone.nordicsemi.com/.../connectivity_5F00_4.1.1_5F00_usb_5F00_with_5F00_s132_5F00_3.1.0.hex

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

DamienB — Wed, 19 Feb 2020 09:45:38 GMT

Trying to DFU my custom board using nRF Connect for mobile phone works properly. It used to work (two weeks ago) using nRF Connect for PC and the nRF52840-DK, i do not know what changed since, i just re-installed nRF Connect on my PC, boards are the same.

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

DamienB — Wed, 19 Feb 2020 09:43:16 GMT

I don't, i am using an nRF52840-DK in version 1.0.0

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

Vidar Berg — Wed, 19 Feb 2020 09:22:31 GMT

Do you have access to a nRF52840 dongle you can try with? The Jlink will act as a UART<->USB bridge unless you are using the nRF USB port next to the reset button.

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

DamienB — Wed, 19 Feb 2020 09:17:42 GMT

I tried to power cycled the device and disable the mass storage functionnality in my device manager and it didn't change anything. I am not using any J-link, just the USB cable.

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

Vidar Berg — Wed, 19 Feb 2020 09:00:48 GMT

Hi,

Even though you are on Windows, did you try to disable mass storage functionality on the Segger chip and power-cycle the board as I suggested? I managed to reproduce the same problem with my Windows 10 PC before I did that. Not sure if it was because of the MSD or if it had to do with the fact that I power-cycled the board afterwards. Either way, I suspect it has something to do with the Jlink. Maybe the recent Jlink driver update triggered this. I have not seen this with the nRF52840 Dongle, which uses the built-in nRF USB and not the Jlink USB.

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

DamienB — Mon, 17 Feb 2020 15:19:33 GMT

Hi,

I am getting the same error when I try to DFU my board, it seems coming from the nrf connect version 3.3 I recently updated..

I am using an nRF52840-DK in version 1.0.0 and Windows 10,

nrfjprog version: 10.6.0
JLinkARM.dll version: 6.62a

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

Vidar Berg — Thu, 16 Jan 2020 13:24:54 GMT

Hi,

I'm running the same Ubuntu version as you, but have not managed to replicate these two errors. Maybe you can try to disable MSD in jlink as explained here https://docs.zephyrproject.org/1.12.0/tools/nordic_segger.html#disabling-the-mass-storage-device-functionality (remember to power-cycle the board as instructed before trying again)? I don't think this issue is related to permissions.