This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Can't detect nRF52 DK by segger

The board has been working well.

Since one day, when I try to connect the board with my laptop using micro usb cable, the led5 starts blinking rapidly and I'm unable to program that board anymore.

I've tried to enter into BOOTLOADER mode, the led 5 blinks every second, even though I don't see any connected devices.

What can it be and what does the rapid blink signal mean?

  • Can you attempt to update the J-Link Interface MCU Firmware? The procedure is described in this post. The nRF52 DK firmware can be downloaded from here.

  • Hi Einar, I tried above solution but it did not work for me. My DK board PCA10040. I programmed the firmware from the second link you shared but still the rapid blinking of the LEd besides the atmel chip has not stopped.

    I was trying to program another board of mine using the Dk board.

  • I am having the same issue and reprogramming the MCU firmware doesn't change anything. I have a feeling the issue is with my PC because when I flash using other computers it works well.

  • Sounds like there is some sort of enumeration issue since it does not show up on your computer but works on other computers. Unfortunately, I do not have any good suggestions. Perhaps you can try to reprogram the JLink interface firmware from another computer and see if that helps?

    If not, can you provide a bit more info? Which DK do you have (nRF52832, nRF52840 etc.)? Does the DK enumerate in some way, so that you can see it from the Device manager (assuming you are using Windows)? What is the approximate frequency and duty cycle of the LED blinking?

  • I had a similar problem matching the description in the question. I got the following dmesg output regardless if I started the device in normal or bootloader mode, and it would not be recognized as a MSD. 

    [ 235.184868] usb 1-4.3: new full-speed USB device number 19 using xhci_hcd
    [ 235.276878] usb 1-4.3: device descriptor read/64, error -32
    [ 235.476904] usb 1-4.3: device descriptor read/64, error -32
    [ 235.676879] usb 1-4.3: new full-speed USB device number 20 using xhci_hcd
    [ 235.768903] usb 1-4.3: device descriptor read/64, error -32
    [ 235.968899] usb 1-4.3: device descriptor read/64, error -32
    [ 236.077209] usb 1-4-port3: attempt power cycle
    [ 236.704869] usb 1-4.3: new full-speed USB device number 21 using xhci_hcd
    [ 236.705070] usb 1-4.3: Device not responding to setup address.
    [ 236.913034] usb 1-4.3: Device not responding to setup address.
    [ 237.120864] usb 1-4.3: device not accepting address 21, error -71
    [ 237.212869] usb 1-4.3: new full-speed USB device number 22 using xhci_hcd
    [ 237.213156] usb 1-4.3: Device not responding to setup address.
    [ 237.421058] usb 1-4.3: Device not responding to setup address.
    [ 237.628858] usb 1-4.3: device not accepting address 22, error -71
    [ 237.629211] usb 1-4-port3: unable to enumerate USB device

    The solution was simply to connect it to a different USB port, after which it worked fine on any port. I am running Ubuntu 18.04 LTS.

Related