On Wed, Aug 16, 2017 at 11:32 PM, R0b0t1 <[email protected]> wrote: > Hello again, I believe I have cause to bring this thread back to life. > > On Sun, Aug 6, 2017 at 11:50 AM, <[email protected]> wrote: >> When I plug in such a little board into my PC, demesg >> reports: >> [ 1429.834140] usb 7-4: new low-speed USB device number 15 using ohci-pci >> [ 1429.965142] usb 7-4: device descriptor read/64, error -62 >> [ 1430.203151] usb 7-4: device descriptor read/64, error -62 >> [ 1430.438161] usb 7-4: new low-speed USB device number 16 using ohci-pci >> [ 1430.569151] usb 7-4: device descriptor read/64, error -62 >> [ 1430.803174] usb 7-4: device descriptor read/64, error -62 >> [ 1431.038184] usb 7-4: new low-speed USB device number 17 using ohci-pci >> [ 1431.456157] usb 7-4: device not accepting address 17, error -62 >> [ 1431.582204] usb 7-4: new low-speed USB device number 18 using ohci-pci >> [ 1432.000209] usb 7-4: device not accepting address 18, error -62 >> [ 1432.000244] usb usb7-port4: unable to enumerate USB device >> > > This is with a NUCLEO-L432KC, an STM32 development board: > > [1817074.986238] usb usb3-port14: unable to enumerate USB device > [1817075.429167] usb 3-14: new low-speed USB device number 50 using xhci_hcd > [1817075.586133] usb 3-14: device descriptor read/64, error -71 > [1817075.847136] usb 3-14: device descriptor read/64, error -71 > [1817076.110100] usb 3-14: new low-speed USB device number 51 using xhci_hcd > [1817076.267102] usb 3-14: device descriptor read/64, error -71 > [1817076.527036] usb 3-14: device descriptor read/64, error -71 > [1817076.790003] usb 3-14: new low-speed USB device number 52 using xhci_hcd > [1817076.790470] usb 3-14: Device not responding to setup address. > [1817076.994569] usb 3-14: Device not responding to setup address. > [1817077.201986] usb 3-14: device not accepting address 52, error -71 > [1817077.357969] usb 3-14: new low-speed USB device number 53 using xhci_hcd > [1817077.358525] usb 3-14: Device not responding to setup address. > [1817077.562503] usb 3-14: Device not responding to setup address. > [1817077.769930] usb 3-14: device not accepting address 53, error -71 > [1817077.769959] usb usb3-port14: unable to enumerate USB device > [1817080.134131] usb 3-5: USB disconnect, device number 29 > > Admittedly, I cut apart a USB cable and am using socketed pin headers > to attach it to the development board (I'd like to keep it looking > nice). However, this same board properly identifies as a USB CDC > device to Windows. > > There may be an issue with the kernel driver, Meino. I'm going to see > how I should follow up on this. Can you test your ATtiny85 with > Windows? >
The fix was switching USB D+ and D-. My USB cable had them backwards (green is supposed to be D+, but there is a popular StackExchange answer with it reversed). [1826600.135854] usb 3-14: New USB device found, idVendor=0483, idProduct=5740 [1826600.135855] usb 3-14: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [1826600.135856] usb 3-14: Product: STM32 Virtual ComPort [1826600.135857] usb 3-14: Manufacturer: STMicroelectronics [1826600.135857] usb 3-14: SerialNumber: 00000000001A [1826600.136272] cdc_acm 3-14:1.0: ttyACM0: USB ACM device Notice how it registers as a fullspeed device. Device detection relies on how D+ and D- are used. It seems this isn't applicable to your device then, but it's something to check. What is strange is if this is wired improperly it shows up on some Windows hardware. I need to check again. R0b0t1.
