PXE boot PI2B with USB device plugged in

detule commented 5 years ago

Hello: I am experiencing an issue PXE booting my PI 2B (via bootcode.bin on the SDCard).

More specifically, everything works as it should - except when trying to boot with a particular USB device plugged in: Hauppauge WinTV-DualHD usb tuner.

More about my setup and what I believe to be happening:

I am using the latest bootcode.bin from master, md5 hash: 8caa083dfa5897d32eb9b8b06dc127a9
I do have a non-OEM charger: It is a 12W (5V, 2.4A) adapter, with what I believe is a solid cable from a reputable brand. The same charger/setup is powering a pi3B+ without issues: no under-voltage, throttling, etc.
My tftp server is dnsmasq set-up precisely as in the official instructions.
The PI2B successfully boots with other USB devices plugged in (an older generation powered Hauppauge tuner, HID device). Logs for these successful boots are provided below. In addition, my PI3B+, which is also set-up for PXE boot (no sdcard), successfully comes up with the offending USB device plugged in - no log from this as I am not sure if I can pull the comparable (bootrom?) log.
Failure happens when enumerating/querying the USB devices plugged into the hub. It finds the device - the device pulls D+ high ("Found highspeed device"), and then the process hangs - presumably as we are querying for the interface class. The device does have an alternate interface (lsusb output below); not sure if that's causing a confusion somehow.

Logs and diagnostics below - all logs from the PI2B, booting with different USB set-ups.

[BASELINE] Successful boot, no USB devices plugged in: bootlog
[ISSUE] Failed boot, WinTV-DualHD (Hauppauge 1595) plugged in: bootlog ; lsusb output for the device
[COMPARABLE] Successful boot, Hauppauge 1950 (powered usb) plugged in: bootlog ; lsusb output for the device
[COMPARABLE] Successful boot, Lenovo HID device plugged in: bootlog ; lsusb output for the device

Appreciate your help

zbrozek commented 5 years ago

How are you pulling the pre-kernel boot log? I suspect I'm seeing something similar (but with different devices and on the 3B+). I'd like to compare to your observations. https://github.com/raspberrypi/firmware/issues/1060

ghollingworth commented 5 years ago

You can't get this log from the bootrom, you'll need to use an SD card with bootcode.bin on it and add a file UART to it or do:

sed -i -e "s/BOOT_UART=0/BOOT_UART=1/" bootcode.bin

raspberrypi / firmware

PXE boot PI2B with USB device plugged in #1059