You may want to invest in a USB Protocol Analyzer. I've got a Total Phase Beagle 480, and it's helped me quickly identify USB issues. It's pricey if you're playing along at home, but if this is for a business, get one. Finding the problem in 15 seconds will save you more money than the 2 weeks of lost engineering time stumbling around in the dark.
Here's the model I've got: http://www.totalphase.com/products/beagle-usb480/ On Thursday, August 14, 2014 7:21:02 AM UTC-4, karlka...@gmail.com wrote: > > Sure this is a hardware-problem and not caused by the software on your > board which is accessing the new/other USB port in a wrong way? Did your > firmware ever work properly with the original BBB-hardware? > > > Am Mittwoch, 13. August 2014 21:33:27 UTC+2 schrieb Brendan Bleker: >> >> Hello, >> >> I have a custom board based on the Beaglebone Black, I'm trying to get >> the board to boot from USB, with nothing programmed on or SD card. I'm >> expecting to get the AM335 RNDIS to initiate as an Ethernet device. On our >> board (compared to the Beaglebone Black), we're using USB0 with the OTG >> circuitry (instead of USB1) and forcing USB0 into device mode. The board is >> detected by the Linux PC, however, It will not enumerate. >> >> The following is the dmesg I was able to get (running Ubuntu 12.04): >> >> [424595.900132] usb 5-2: new full-speed USB device number 4 using uhci_hcd >> [424596.075024] usb 5-2: unable to read config index 0 descriptor/all >> [424596.075032] usb 5-2: can't read configurations, error -71 >> [424596.188220] usb 5-2: new full-speed USB device number 5 using uhci_hcd >> [424596.251145] usb 5-2: unable to read config index 0 descriptor/all >> [424596.251158] usb 5-2: can't read configurations, error -71 >> [424596.364184] usb 5-2: new full-speed USB device number 6 using uhci_hcd >> [424596.422150] usb 5-2: unable to read config index 0 descriptor/all >> [424596.422164] usb 5-2: can't read configurations, error -71 >> [424596.423023] hub 5-0:1.0: unable to enumerate USB device on port 2 >> >> The board hardware has been modified slightly from the Beaglebone Black. >> First, we are using a type A usb connector, second, USB0 is now connected >> to the (USB1) OTG hardware, with USB0_ID pin floating (no access to USB1). >> >> >> Are there any other modifications to hardware required to get this >> working? >> >> Thanks >> > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
