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

nRF52840 Dongle Installation - WIN10 - LIBUSB Error

I recently picked up an nRF52840 dongle and I cannot seem to get it to work properly on a very new Win10 machine. It does seem to work properly on my Mac however so I believe the dongle physically works.

This is what I see:

After plugging the device in to a USB port, I launch nRF Connect v3.3.1. There is a solid green LED on the dongle. (Yes, the first time I plugged it in it was flashing red at which time nRF Connect asked to program it. I said yes.)

I get a "Confirm" dialog that immediately says "LIBUSB error is detected. Reloading app could resolved the issue. Would you like to reload now?"

Hitting Yes does not help. Tried that multiple times.

There is also a Log message that states "Error while probing usb device at bus.address 2.11: undefined. Please check that a libusb-compatible kernel driver is bound to this device." 

(There is a also an address provided to a GitHub troubleshooting link which I visited. It did not solve my problem.)

If I take a look into the device manager, I see:

From other threads on devzone, I gather that it should look something more like:

So it feels like a driver issue. I tried to manually update the driver as discussed at:

https://devzone.nordicsemi.com/f/nordic-q-a/18592/is-there-a-windows-driver-for-the-nrf52840-usb-cdc-acm

And Windows tells me that either I already have proper drivers (if I attempt to update Ports (COM & LPT) or cannot find a driver if I attempt to update the "nRF52 Connectivity" driver.

I know there have been a couple of different threads on this issue but none seem to have solved this for me.

Any help is appreciated! Thanks in advance.

Parents
  • Hi,

    Which firmware did you flash to the dongle? If the firmware does not include the USB DFU trigger library, you need to press the reset button to enter bootloader mode in order to program it again. See the Programming section in the documentation for more details.

    Best regards,
    Jørgen

  •  Thank you for replying. 

    Yes, I have tried resetting and reprogramming but I get the same result. (As mentioned, this dongle does work properly on my Mac so I question whether it is a firmware issue.) 

    If I perform the reset and reprogram on my (WIN10) PC I get the following log messages in nRF Connect.

    If I close and restart nRF Connect, I am then back to the same LIBUSB error reported in my initial post.

    As far as what firmware I flashed to the dongle, I really don't know. Whatever nRF connect decided it wanted to program into the device after I hit the reset button. It doesn't give me names or versions or anything.

    On my MAC I used the Programmer utility to perform a read on the device and I get the following map:

    Red: Region Name Bootloader, Address range 0x000E0000 - 0x00FDFFF (12880 bytes)

    Green: Region Name Application, Address range 0x0001F000 - 0x00050017 (200728 bytes)

    Blue: Region Name Soft Device, Address range 0x00001000 - 0x0001EFFF (12880 bytes)

    Yellow: Region Name MBR, Address range 0x00000000 - 0x00000FFF (4096 bytes)

    Not sure if that tells you anything or not.

    Other thoughts or ideas?

Reply
  •  Thank you for replying. 

    Yes, I have tried resetting and reprogramming but I get the same result. (As mentioned, this dongle does work properly on my Mac so I question whether it is a firmware issue.) 

    If I perform the reset and reprogram on my (WIN10) PC I get the following log messages in nRF Connect.

    If I close and restart nRF Connect, I am then back to the same LIBUSB error reported in my initial post.

    As far as what firmware I flashed to the dongle, I really don't know. Whatever nRF connect decided it wanted to program into the device after I hit the reset button. It doesn't give me names or versions or anything.

    On my MAC I used the Programmer utility to perform a read on the device and I get the following map:

    Red: Region Name Bootloader, Address range 0x000E0000 - 0x00FDFFF (12880 bytes)

    Green: Region Name Application, Address range 0x0001F000 - 0x00050017 (200728 bytes)

    Blue: Region Name Soft Device, Address range 0x00001000 - 0x0001EFFF (12880 bytes)

    Yellow: Region Name MBR, Address range 0x00000000 - 0x00000FFF (4096 bytes)

    Not sure if that tells you anything or not.

    Other thoughts or ideas?

Children
No Data
Related