Debugging invalid USB device descriptor, SAMR34 L21

Go To Last Post
7 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I added a USB driver to my project and when plugging it into Windows I immediately see "USB device not recognized".  I inspected the traffic with a USB inspector application and the first packet that is sent has a VID of 0.  The device is removed after this and there are no other packets

 

I'm wondering where in the USB classes (usb.c, usb_device_udd.c, etc.) I need to set a breakpoint to see this first packet getting sent, I've been unable to hit a breakpoint in the USB code so far.  This is the data for the first packet, I'd just like to see where this is coming from so that I can further debug the issue.  USB_DEVICE_VENDOR_ID is defined but never read from

 

\\??\\USB#VID_0000&PID_0002#5&1f3e3f24&0&3#{a6782bce-4376-4de2-8096-70aa9e8fed19}

Last Edited: Fri. Jul 26, 2019 - 04:51 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I'm at a loss for where I need to set a breakpoint to see this packet getting sent.  I've set breakpoints all over i2c_master, usb, usb_device_udd and I don't see it sent.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Before you get too frustrated wondering why you have not gotten a reply has to do with the placement of the ASF forum in the 8 bit AVRFreaks community, as few if any freaks ever use ASF.

Strongly suggest you post your question in a 32 bit forum, or better take it to Microchip support and open a ticket there.   Good luck!

 

Click Link: Get Free Stock: Retire early! PM for strategy

share.robinhood.com/jamesc3274
get $5 free gold/silver https://www.onegold.com/join/713...

 

 

 

 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Ok, thanks!

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

davis_g wrote:

 

\\??\\USB#VID_0000&PID_0002#5&1f3e3f24&0&3#{a6782bce-4376-4de2-8096-70aa9e8fed19}

The first thing sent to the host should be a device descriptor.  That's not a device descriptor.  The part in braces looks like a GUID.

 

A VID of 0 could possibly be okay.  It works here when using WinUSB.

 

 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0


I found something like that in the registry.  I recognize the VID (I made it 0), PID, and "chip name".  USB calls the "chip name" the serial number.   I don't think I send that GUID though or the complete string.

 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

My project was missing the entire UART implementation, so adding that now