• State Not Answered
  • Replies 11 replies
  • Subscribers 75 subscribers
  • Views 225 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 346338
Options

Bricked PCA10056 nrf52840 DK

cheston2

I have recently bought two nrf52840dk, version 3.0.0, unboxed and plugged into usb. One would show up with a usb storage on the side and in vscode a J-link window prompted for a device update on the interface nrf5340 chip on the dk, but the other one doesn't have either. How can I factory reset the non working one? Here are some logs to show.

lsusb:

Working one:

Bus 003 Device 045: ID 1366:1061 SEGGER J-Link

Non working one:

Bus 003 Device 056: ID 1366:0101 SEGGER J-Link PLUS

dmesg messages:

Working one:

usb 3-1: new full-speed USB device number 21 using xhci_hcd
usb 3-1: New USB device found, idVendor=1366, idProduct=1051, bcdDevice= 1.00
usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 3-1: Product: J-Link
usb 3-1: Manufacturer: SEGGER
usb 3-1: SerialNumber: 001050220349
cdc_acm 3-1:1.0: ttyACM0: USB ACM device
cdc_acm 3-1:1.2: ttyACM1: USB ACM device
usb-storage 3-1:1.5: USB Mass Storage device detected
scsi host0: usb-storage 3-1:1.5
scsi 0:0:0:0: Direct-Access SEGGER MSD Volume 1.00 PQ: 0 ANSI: 4
sd 0:0:0:0: Attached scsi generic sg0 type 0
sd 0:0:0:0: [sda] 21829 512-byte logical blocks: (11.2 MB/10.7 MiB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 0b 00 00 08
sd 0:0:0:0: [sda] No Caching mode page found
sd 0:0:0:0: [sda] Assuming drive cache: write through
sda:
sd 0:0:0:0: [sda] Attached SCSI removable disk
usb 3-1: USB disconnect, device number 21
umount: attempt to access beyond end of device
sda: rw=0, sector=0, nr_sectors = 1 limit=0
FAT-fs (sda): unable to read boot sector to mark fs as dirty

Non working one:

usb 3-1: new full-speed USB device number 23 using xhci_hcd
usb 3-1: New USB device found, idVendor=1366, idProduct=0101, bcdDevice= 1.00
usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 3-1: Product: J-Link
usb 3-1: Manufacturer: SEGGER
usb 3-1: SerialNumber: 001050261048
usb 3-1: USB disconnect, device number 23

VSCode nrf connect extension

Working one:

Non-working one:

Parents
  • 0

    Hi,

    We have two versions of the On-Board debugger. One with the sticker on the chip (the old one), and one with the sticker directly on the PCB (The new version).

    This will work for the new version, which should be the one that you got:

    Hold the reset button while plugging in the USB of the DK. You will see no change, but the On-Board Debugger should now be in recovery mode.

    Run "nrfutil device x-update-debug-probe-firmware"

    This should update the firmware on the On-Board Debugger. So if it is a software problem, then this should fix it.

    Regards,
    Sigurd Hellesvik

  • 0 in reply to Sigurd Hellesvik

    3.0.0 is the newer version. Holding reset button doesn't really work. What else could I do?

    ```
    $ lsusb
    Bus 003 Device 010: ID 1366:0101 SEGGER J-Link PLUS
    Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
    $ nrfutil device x-update-debug-probe-firmware
    Error: One or more update debug probe firmware tasks failed:
     * 1050261048: Timed out waiting for response from worker. (Generic)

    ```

Reply
  • 0 in reply to Sigurd Hellesvik

    3.0.0 is the newer version. Holding reset button doesn't really work. What else could I do?

    ```
    $ lsusb
    Bus 003 Device 010: ID 1366:0101 SEGGER J-Link PLUS
    Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
    $ nrfutil device x-update-debug-probe-firmware
    Error: One or more update debug probe firmware tasks failed:
     * 1050261048: Timed out waiting for response from worker. (Generic)

    ```

Children
Related
Terms of service