nRF52840-PDK USB not recognized

pbirkner gravatar image

asked 2017-08-11 17:57:39 +0200

Hi,

I am attempting to run the various USB example programs on the nRF52840-PDK USB, but my nRF usb device is not being recognized (in windows OR linux device tree). Is there anything I need to change on the dev board itself? I have tried running various examples, and I don't see why I would be having trouble with the USB HID devices.

Thank you!

edit retag flag offensive close delete report spam

Comments

You are connecting the nRF52840 PDK to your computer through the nRF USB connector and not the one USB connector that goes to the interface MCU?

Bjørn Spockeli ( 2017-08-14 12:53:29 +0200 )editconvert to answer

Yes, I am connecting through the nRF USB. Thank you.

pbirkner ( 2017-08-14 14:51:37 +0200 )editconvert to answer

OK, so NRF Power Source(SW9) is is set to VDD and SW6 is set to Default. If I flash the USB HID Generic Example to the nRF52840 PDK, then a mouse (nRF52 USB HID generic Demo) is added under Devices and Printers in Windows 7 .

Bjørn Spockeli ( 2017-08-14 15:32:51 +0200 )editconvert to answer

I've tried this all with no luck. The program flashes fine, but I've tried plugging it into multiple Windows 7 machines and always get the same error: Error Code 43, USB device not recognized.

pbirkner ( 2017-08-14 18:03:34 +0200 )editconvert to answer

Are you using one USB cable to flash the nRF52840 and then you re-connect it to the nRF USB connector? Or are you using two separate cables?

Bjørn Spockeli ( 2017-08-15 13:19:45 +0200 )editconvert to answer

I have tried both methods with no success.

pbirkner ( 2017-08-15 15:17:25 +0200 )editconvert to answer

Do you see the log output from the examples when you open a terminal(Putty, Termite etc)?

Bjørn Spockeli ( 2017-08-22 09:36:06 +0200 )editconvert to answer

I do see the log output in the RTT viewer. I get the following message:

0> <info> app: Hello USB!

0> <info> app: USB power detected

0> <info> app: USB ready

pbirkner ( 2017-08-22 15:52:53 +0200 )editconvert to answer

The log info is:

J-Link RTT Viewer V6.12a: Logging started.
LOG:  Global terminal added.
LOG:  Terminal 0 added.
LOG:  Device "NRF52832_XXAA" selected.
LOG:  Found SWD-DP with ID 0x2BA01477
LOG:  Found SWD-DP with ID 0x2BA01477
LOG:  AP-IDR: 0x24770011, Type: AHB-AP
LOG:  Found Cortex-M4 r0p1, Little endian.
LOG:  FPUnit: 6 code (BP) slots and 2 literal slots
LOG:  CoreSight components:
LOG:  ROMTbl 0 @ E00FF000
LOG:  ROMTbl 0 [0]: FFF0F000, CID: B105E00D, PID: 000BB00C SCS
LOG:  ROMTbl 0 [1]: FFF02000, CID: B105E00D, PID: 003BB002 DWT
LOG:  ROMTbl 0 [2]: FFF03000, CID: B105E00D, PID: 002BB003 FPB
LOG:  ROMTbl 0 [3]: FFF01000, CID: B105E00D, PID: 003BB001 ITM
LOG:  ROMTbl 0 [4]: FFF41000, CID: B105900D, PID: 000BB9A1 TPIU
LOG:  ROMTbl 0 [5]: FFF42000, CID: B105900D, PID: 000BB925 ETM
LOG:  RTT Viewer connected.
pbirkner ( 2017-08-22 16:30:23 +0200 )editconvert to answer

@pbirkner: The log output indicates that the firmware is running so it could be that this is an issue on the PC side. That, said we've had some issues with bad boards where the nRF52840 is not properly soldered to the PCB. Which version of the PCA100056 do you have?

Bjørn Spockeli ( 2017-09-08 17:52:45 +0200 )editconvert to answer

I believe that the nRF52840 is not properly soldered to the board. I have V0.9.2. I ended up ordering another board and with the exact same procedure, the USB device worked. To my dismay, after a day the second PDK (also v0.9.2) also stopped working. Is there a way to order a new one and ensure that it isn't a faulty board?

pbirkner ( 2017-09-08 17:56:38 +0200 )editconvert to answer

We'll send you another board, free of charge, see my answer in the other question.

Bjørn Spockeli ( 2017-09-08 18:00:20 +0200 )editconvert to answer