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"

[DamienB]

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

[Vidar Berg]

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.

[Vidar Berg]

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.

[DamienB]

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

[DamienB]

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.

[Vidar Berg]

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:

connectivity_4.1.1_usb_with_s132_3.1.0.hex

[DamienB]

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)

[Vidar Berg]

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

[DamienB]

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 ?

[DamienB]

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

[Vidar Berg]

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.

DamienB said:

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

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

[DamienB]

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