USB CDC ACM, Unknown device windows 10, descriptor request failed, code 43.

[Curiosus]

Hi All, 

I am trying to get this example  NRF_SDK\nRF5_SDK_16.0.0_98a08e2\examples\peripheral\usbd_cdc_acm, working on a custom board,using a  BMD-340, The only changes I have made until now is the clock source, as it does not have a XTAL on board.  

I was aiming to get the RTT working, which I successfully have used in a previous project with the following setup. 

#define NRF_LOG_ENABLED 1

#define NRF_LOG_BACKEND_UART_ENABLED 0

#define NRF_LOG_BACKEND_RTT_ENABLED 1

#define NRF_LOG_DEFAULT_LEVEL 3

#define NRF_LOG_DEFERRED 0

I have tried NRF_LOG_DEREFERRED set and cleared. and that did not help yet. 

I got a Blinky running  in the main loop , which is working fine,  However I am getting this error on windows 10, (USB device not recognized), under device manager I get : Windows has stopped this device because it has reported problems. (Code 43). 

I tried installing the USB drivers provided in the SDK but that did not help. 

I got a Dev board nrf52840, and tried it on that as well and got the same results. 

I was wondering if I may be missing something in my setup ? 

Any feedback is highly appreciated. 

Thanks !

[Kenneth]

If you don't have an external 32kHz, then the only change you should need to do is in sdk_config:
#define NRFX_CLOCK_CONFIG_LF_SRC 0

Is this the change you have made?

[Curiosus]

Yes , that is the only change I have made, I am also using the timer app to generate some led patterns on my custom board and that is working fine. 

[Kenneth]

I have verified this works on an nRF52840-DK, do you have an nRF52840-DK? If yes, what is the labeling on the nRF52840-DK?

[Curiosus]

I do, the label is PCA10056,  1.0.0  ,   2018.45.

[Curiosus]

I have opened a new example from SDK17 and flashed it onto my DK and that seems to work, the example from SDK16 did not work.

then I tried it on my custom board and I am getting the same error. 

 I got the following setup to debug the issue via RTT interface but that is not working unfortunately, any idea on what could be going wrong here ? 

As per my clock settings I got the following: 

Thanks ! 

[Kenneth]

Are you able to get any of the USB examples to work on your board (with or without debugging)?

Kenneth

[Curiosus]

Yes, I was able to get this example usbd_cdc_acm working on my DK, however I have not been able to get the example working on my custom board, as mentioned above I would presume the CPU is working since I am able to generate signals from the timer app, but the USB interface fails, with the error mentioned above, as I am no able to debug the issue with the RTT, I have no clue as per what could be failing. 

Thank for looking into this. 

[Kenneth]

Are you able to get any of the USB examples to work on your custom board (with or without debugging)?

Kenneth

[Curiosus]

No, I have not been able to get any of the USB Examples working on my custom board. 

This is how the usb port is wired: 

Quick question in regards to sdk_config file. 

why are basically all the macros definitions on the config file kind of repeated ? 

for instance: 

NRFX_CLOCK_CONFIG_LF_SRC  

and then. 

NRF_CLOCK_CONFIG_LF_SRC  

Which ones should I rely on, when setting up a peripheral or a priority levels ? 

Thanks ! 

[Kenneth]

You may try to connect and oscilloscope to the D+/D- pins to check if there any obvious anomalies.

In terms of getting RTT to work, can you look at this suggestion:
https://devzone.nordicsemi.com/f/nordic-q-a/63214/rtt-stopped-working-in-ses-in-sdk15-3

[Curiosus]

I am waiting at the moment to get new custom boards manufactured , since I suspect I may have burnt the ESD protection chip for the USB lines on my board, and then I will get back with the results. by the way I got all the examples working on my DK, so it must be hardware fault on my side. 

Thanks for looking into this !