Example CDC ACM in 15.3

RE: Example CDC ACM in 15.3

Bjørn Kvaale — Mon, 27 May 2019 06:45:21 GMT

Great to hear! 🙂

RE: Example CDC ACM in 15.3

Jimmy@zone — Fri, 24 May 2019 17:06:34 GMT

The new board work ! Thanks

RE: Example CDC ACM in 15.3

Bjørn Kvaale — Wed, 22 May 2019 08:29:33 GMT

It seems there are still some issues regarding usb on the v0.9.3 52840 PDK (see answer here). I tested with a v1.0.0 52840 DK, which worked fine. I have sent you a PM on DevZone.

RE: Example CDC ACM in 15.3

Bjørn Kvaale — Mon, 20 May 2019 11:53:21 GMT

Sorry for the delayed response. I have tried this example again & unfortunately I can still not replicate the issue. After a bit of setup time, I can see the JLink CDC UART Port in the device manager of Windows. Which version of the 52840 DK do you have? Do you have another 52840 DK that you could test with? Are you connecting one USB cable to the J2 on the DK & one other USB cable to the nRF USB connector on the DK? Is the nRF Power Source switch in the VDD position? These two cases may also be helpful: link 1, link 2.

RE: Example CDC ACM in 15.3

Jimmy@zone — Mon, 13 May 2019 16:28:42 GMT

I tried a different New Windows 10 pc.

Downloaded the latest Segger studio and installed the Nordic addon.

Downloaded the SDK

Connect the Dev kit, it installed 13.2 serial port ok, it was installed.

Build the C:\nRF5_SDK_15.3.0_59ac345\nRF5_SDK_15.3.0_59ac345\examples\peripheral\usbd_cdc_acm\pca10056\blank\ses

Start it on the Dev kit

Efter a few secons the error appers and a broken device is show in device manager.

Unknown USB Device(Device Descriptor Request Failed)

RE: Example CDC ACM in 15.3

Jimmy@zone — Mon, 13 May 2019 07:21:56 GMT

Tested the new url with the same result, still looking for a new windows 10 that I can play around with.

Here are the event logs for the device when I plugg in the usb cable to the "serial usb port".

Device USB\VID_0000&PID_0002\5&cd2441b&0&3 was configured.

Driver Name: usb.inf
Class Guid: {36fc9e60-c465-11cf-8056-444553540000}
Driver Date: 06/21/2006
Driver Version: 10.0.17763.1
Driver Provider: Microsoft
Driver Section: BADDEVICE.Dev.NT
Driver Rank: 0xFF0000
Matching Device Id: USB\DEVICE_DESCRIPTOR_FAILURE
Outranked Drivers: usb.inf:USB\DEVICE_DESCRIPTOR_FAILURE:00FF2000
Device Updated: false
Parent Device: USB\ROOT_HUB30\4&2df969f2&0&0

Device USB\VID_0000&PID_0002\5&cd2441b&0&3 had a problem starting.

Driver Name: usb.inf
Class Guid: {36fc9e60-c465-11cf-8056-444553540000}
Service: 
Lower Filters: 
Upper Filters: 
Problem: 0x2B
Problem Status: 0x0

RE: Example CDC ACM in 15.3

Bjørn Kvaale — Fri, 10 May 2019 12:47:53 GMT

Nope, downloaded the sdk v15.3 from here. Could you try the example there, if you have not done so already?

RE: Example CDC ACM in 15.3

Jimmy@zone — Fri, 10 May 2019 12:21:24 GMT

Did you donwload it from www.nordicsemi.com/.../nRF5SDKforThreadandZigbeev300d310e71.zip

Ill try to find a second window10 box to test on.

RE: Example CDC ACM in 15.3

Bjørn Kvaale — Fri, 10 May 2019 10:27:12 GMT

Hi Jimmy, I have talked to another application engineer & he did not see this issue on his Windows 10 machine. Could you test on another PC to see if that issue appears there?

RE: Example CDC ACM in 15.3

Jimmy@zone — Tue, 07 May 2019 12:00:17 GMT

Any update or a guest when this might be fixed?

RE: Example CDC ACM in 15.3

Bjørn Kvaale — Wed, 01 May 2019 06:50:21 GMT

Then I would suggest to use sdk v15.2. I will report this error internally.

RE: Example CDC ACM in 15.3

Jimmy@zone — Thu, 25 Apr 2019 12:27:41 GMT

I am using Windows 10 and switching back to 15.2 instead makes it work directly with out any issue. Rebooting the pc didn't help.

RE: Example CDC ACM in 15.3

Bjørn Kvaale — Thu, 25 Apr 2019 11:22:41 GMT

Are you by any chance using Windows 7? If that is the case, you will need to run step 4 here. I have tested with a 52840 DK on Windows 10 & did not receive any issues at all. Are you by any chance using a usb hub? Maybe it would help to connect directly to your PC instead?

I have also noticed once in a while that I receive issues seeing my dev kits in the device manager & connecting to them via J-Link. The only workaround to this issue I have found is to restart the computer.