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

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"

Parents
  • 0

    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

  • 0 in reply to DamienB

    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.

Reply
  • 0 in reply to DamienB

    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.

Children
Related