DFU boot USB failures

[mossmann]

Steps to reproduce

1. Use the DFU bootloader to load hackrf_usb.dfu
2. Repeat until there is an enumeration failure of the firmware running from RAM (It usually fails once within about 50 attempts.)

Expected behaviour

The firmware should execute from RAM and should enumerate over USB as a HackRF in Hi-Speed USB mode.

Actual behaviour

Enumeration fails, some messages appear in dmesg indicating failures to enumerate full-speed and/or low-speed devices. No Hi-Speed device is detected. Use of an oscilloscope on the USB data lines reveals a never-ending stream of 12 Mbps data produced by the microcontroller.

Workaround

Reset the device and retry. Since this bug only happens about 3% of the time, retrying usually works.

Version information

Operating system: observed with various Linux distros

hackrf_info output: tested only on 2017.02.1 and more recent firmware

┆Issue is synchronized with this Basecamp todo by Unito

[nikoroxy]

I've bought a used original board online and i'm only getting this error (DFU and normal boot as well). What can i try to do?

[nik@manjaro ~]$ hackrf_info
hackrf_info version: 2018.01.1
libhackrf version: 2018.01.1 (0.5)
No HackRF boards found.

[nik@manjaro ~]$ journalctl -f  # NORMAL BOOT
nov 13 19:05:32 manjaro kernel: debugfs: Directory '54' with parent 'devices' already present!
nov 13 19:05:32 manjaro kernel: usb 1-5: new full-speed USB device number 122 using xhci_hcd
nov 13 19:05:32 manjaro kernel: usb 1-5: device descriptor read/64, error -71
nov 13 19:05:33 manjaro kernel: usb 1-5: device descriptor read/64, error -71
nov 13 19:05:33 manjaro kernel: debugfs: Directory '55' with parent 'devices' already present!
nov 13 19:05:33 manjaro kernel: usb 1-5: new full-speed USB device number 123 using xhci_hcd
nov 13 19:05:33 manjaro kernel: usb 1-5: device descriptor read/64, error -71
nov 13 19:05:33 manjaro kernel: usb 1-5: device descriptor read/64, error -71
nov 13 19:05:33 manjaro kernel: usb usb1-port5: attempt power cycle
nov 13 19:05:34 manjaro kernel: debugfs: Directory '56' with parent 'devices' already present!
nov 13 19:05:34 manjaro kernel: usb 1-5: new full-speed USB device number 124 using xhci_hcd
nov 13 19:05:34 manjaro kernel: usb 1-5: Device not responding to setup address.
nov 13 19:05:34 manjaro kernel: debugfs: Directory '57' with parent 'devices' already present!
nov 13 19:05:34 manjaro kernel: usb 1-5: Device not responding to setup address.
nov 13 19:05:34 manjaro kernel: debugfs: Directory '58' with parent 'devices' already present!
nov 13 19:05:34 manjaro kernel: usb 1-5: device not accepting address 124, error -71
nov 13 19:05:35 manjaro kernel: usb 1-5: new full-speed USB device number 125 using xhci_hcd
nov 13 19:05:35 manjaro kernel: usb 1-5: Device not responding to setup address.
nov 13 19:05:35 manjaro kernel: debugfs: Directory '60' with parent 'devices' already present!
nov 13 19:05:35 manjaro kernel: usb 1-5: Device not responding to setup address.
nov 13 19:05:35 manjaro kernel: debugfs: Directory '61' with parent 'devices' already present!
nov 13 19:05:35 manjaro kernel: usb 1-5: device not accepting address 125, error -71
nov 13 19:05:35 manjaro kernel: usb usb1-port5: unable to enumerate USB device

[nik@manjaro ~]$ journalctl -f # DFU BOOT
nov 13 19:05:42 manjaro kernel: debugfs: Directory '62' with parent 'devices' already present!
nov 13 19:05:42 manjaro kernel: usb 1-5: new full-speed USB device number 126 using xhci_hcd
nov 13 19:05:42 manjaro kernel: usb 1-5: device descriptor read/64, error -71
nov 13 19:05:42 manjaro kernel: usb 1-5: device descriptor read/64, error -71
nov 13 19:05:42 manjaro kernel: debugfs: Directory '63' with parent 'devices' already present!
nov 13 19:05:43 manjaro kernel: usb 1-5: new full-speed USB device number 127 using xhci_hcd
nov 13 19:05:43 manjaro kernel: usb 1-5: device descriptor read/64, error -71
nov 13 19:05:43 manjaro kernel: usb 1-5: device descriptor read/64, error -71
nov 13 19:05:43 manjaro kernel: usb usb1-port5: attempt power cycle
nov 13 19:05:43 manjaro kernel: debugfs: Directory '64' with parent 'devices' already present!
nov 13 19:05:44 manjaro kernel: usb 1-5: new full-speed USB device number 2 using xhci_hcd
nov 13 19:05:44 manjaro kernel: usb 1-5: Device not responding to setup address.
nov 13 19:05:44 manjaro kernel: debugfs: Directory '03' with parent 'devices' already present!
nov 13 19:05:44 manjaro kernel: usb 1-5: Device not responding to setup address.
nov 13 19:05:44 manjaro kernel: debugfs: Directory '04' with parent 'devices' already present!
nov 13 19:05:44 manjaro kernel: usb 1-5: device not accepting address 2, error -71
nov 13 19:05:44 manjaro kernel: debugfs: Directory '05' with parent 'devices' already present!
nov 13 19:05:44 manjaro kernel: usb 1-5: new full-speed USB device number 4 using xhci_hcd
nov 13 19:05:44 manjaro kernel: usb 1-5: Device not responding to setup address.
nov 13 19:05:44 manjaro kernel: debugfs: Directory '06' with parent 'devices' already present!
nov 13 19:05:44 manjaro kernel: usb 1-5: Device not responding to setup address.
nov 13 19:05:44 manjaro kernel: debugfs: Directory '07' with parent 'devices' already present!
nov 13 19:05:45 manjaro kernel: usb 1-5: device not accepting address 4, error -71
nov 13 19:05:45 manjaro kernel: usb usb1-port5: unable to enumerate USB device

[nik@manjaro ~]$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 008: ID 8087:0a2a Intel Corp. 
Bus 001 Device 003: ID 04f2:b424 Chicony Electronics Co., Ltd USB2.0 HD UVC WebCam
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

[SLAE-Student]

looking for any updates on this, I realise this is old, it is now the end of 2021, but I am desperate. I have a bricked Hack RF One, and it will not get recognised by anything. I have tried multiple Linux dists and flavours, (Debian, Kali, Redhat, Pentoo, etc and Win 8,10, Mac OSX). I have tried every hint I can find on the internet and nothing seems to work. Is there a way to bypass USB and reset using GPIO? I will continue to check here and GSGadgets for any changes or updates to this issue wherever it appears on the internet Thanks.

[gozu42]

I have a bricked Hack RF One, and it will not get recognised by anything.

that seems unlikely to be related to this particular issue.

please open a separate issue for your problem, and given your description, include results (dmesg) of an attempted DFU boot (press and hold DFU button, press and release reset button, release dfu button) and pictures of the front and back of the hackrf board.

[martinling]

Possibly related to the PLL issues suspected to be behind #1101. Retest with #1106.