Hello!
After some quick searching I found no mention of other people having this problem yet.
I attached a new PocketBeagle to my Thinkpad X230 and it’s not detected as a USB device at all (in any of the three USB ports). I tried attaching the PocketBeagle to a Raspberry Pi (not sure which board version exactly) and had the same issue.
In both cases, Linux is running on the USB host computer. (The Thinkpad runs a pretty old kernel version, 4.19.147, but even if some driver is missing, I’d expect at the very least to see the device listed under lsusb or named in dmesg output).
In `dmesg’ output I only see the following errors upon connecting the PocketBeagle which are very typical of a faulty USB cable, although I’ve tried with three different cables now:
[1420502.380639] usb 3-1.2.4: new low-speed USB device number 6 using ehci-pci
[1420502.507473] usb 3-1.2.4: device descriptor read/64, error -32
[1420502.736150] usb 3-1.2.4: device descriptor read/64, error -32
[1420502.961639] usb 3-1.2.4: new low-speed USB device number 7 using ehci-pci
[1420503.094832] usb 3-1.2.4: device descriptor read/64, error -32
[1420503.323647] usb 3-1.2.4: device descriptor read/64, error -32
[1420503.433153] usb 3-1.2-port4: attempt power cycle
[1420504.127632] usb 3-1.2.4: new low-speed USB device number 8 using ehci-pci
[1420504.545331] usb 3-1.2.4: device not accepting address 8, error -32
[1420504.668668] usb 3-1.2.4: new low-speed USB device number 9 using ehci-pci
[1420505.081208] usb 3-1.2.4: device not accepting address 9, error -32
[1420505.081536] usb 3-1.2-port4: unable to enumerate USB device
And on the Raspberry Pi, similar errors:
[1896708.525343] usb 1-1.1.2.4: new low-speed USB device number 8 using dwc_otg
[1896708.675391] usb 1-1.1.2.4: device descriptor read/64, error -32
[1896708.945516] usb 1-1.1.2.4: device descriptor read/64, error -32
[1896709.215577] usb 1-1.1.2.4: new low-speed USB device number 9 using dwc_otg
[1896709.365625] usb 1-1.1.2.4: device descriptor read/64, error -32
[1896709.635683] usb 1-1.1.2.4: device descriptor read/64, error -32
[1896709.755995] usb 1-1.1.2-port4: attempt power cycle
[1896710.515967] usb 1-1.1.2.4: new low-speed USB device number 10 using dwc_otg
[1896710.956101] usb 1-1.1.2.4: device not accepting address 10, error -32
[1896711.106155] usb 1-1.1.2.4: new low-speed USB device number 11 using dwc_otg
[1896711.546295] usb 1-1.1.2.4: device not accepting address 11, error -32
[1896711.546487] usb 1-1.1.2-port4: unable to enumerate USB device
I also tried adding a powered USB 3.0 hub in between. It has an activity LED for each USB port. That blinks for about 2 seconds after attaching the PocketBeagle, and then switches off. For other USB devices that activity LED blinks upon first connecting, and then stays on continuously.
The PocketBeagle was booted from an SDXC card flashed with bone-debian-10.3-iot-armhf-2020-04-06-4gb.img and looks like it’s actually booting correctly. (After power-on, lots of LED activity suggests it is booting, and after a half a minute only the heartbeat LED blinks regularly.)
I wondered if I may have damaged something when soldering on pin headers. So far I’ve not attached any external wiring to the PocketBeagle.
I was able to very briefly test on a WIndows machine, where surprisingly, it was recognised as a mass storage device containing the drivers and documentation, as expected. But I couldn’t investigate further as I have no administrator rights on that machine to install the CDC driver.
Do I need to run a particular minimum Linux kernel version for the PocketBeagle to be recognised at all as a USB device, or is it known to break with particular USB host controllers, like the ones in the Thinkpad X230 (Intel C210 and C216 series)?
Or what else could I try to do?
Thanks for any help you can offer!