Hi Craig,
It looks like you've been fairly thorough with your testing, switching USB
cables, etc. Have you confirmed that the working HackRF works with the
same USB cable, PC and port that the broken one fails with?
Does it look like there is any damage to the USB port? Or anywhere else on
the HackRF?
Thanks,
Dominic
On Wed, 29 Aug 2018 at 06:46, Craig Warnol wrote:
> I have a HackRF One that will not power on and connect to PC. I get no
> LEDs illuminating when connecting to PC with or without the DFU button
> depressed. I've tested on several PCs and with different USB cables. I
> have another HackRF One that works perfectly with the same PC/cables.
>
> I only have Linux boxes. Here's the dmesg logs from this morning.
> Plugged in, no buttons pressed:
> [Wed Aug 29 07:06:32 2018] usb 2-5.3: new low-speed USB device number 37
> using ehci-pci
> [Wed Aug 29 07:06:32 2018] usb 2-5.3: device descriptor read/64, error -32
> [Wed Aug 29 07:06:32 2018] usb 2-5.3: device descriptor read/64, error -32
> [Wed Aug 29 07:06:33 2018] usb 2-5.3: new low-speed USB device number 38
> using ehci-pci
> [Wed Aug 29 07:06:33 2018] usb 2-5.3: device descriptor read/64, error -32
> [Wed Aug 29 07:06:33 2018] usb 2-5.3: device descriptor read/64, error -32
> [Wed Aug 29 07:06:33 2018] usb 2-5-port3: attempt power cycle
>
> Plugged in holding DFU button:
> [Wed Aug 29 07:06:41 2018] usb 2-5.3: new low-speed USB device number 40
> using ehci-pci
> [Wed Aug 29 07:06:41 2018] usb 2-5.3: device descriptor read/64, error -32
> [Wed Aug 29 07:06:41 2018] usb 2-5.3: device descriptor read/64, error -32
> [Wed Aug 29 07:06:41 2018] usb 2-5.3: new low-speed USB device number 41
> using ehci-pci
> [Wed Aug 29 07:06:41 2018] usb 2-5.3: device descriptor read/64, error -32
> [Wed Aug 29 07:06:42 2018] usb 2-5.3: device descriptor read/64, error -32
> [Wed Aug 29 07:06:42 2018] usb 2-5-port3: attempt power cycle
>
> Plugged in holding Reset button:
> [Wed Aug 29 07:06:45 2018] usb 2-5.3: new low-speed USB device number 43
> using ehci-pci
> [Wed Aug 29 07:06:45 2018] usb 2-5.3: device descriptor read/64, error -32
> [Wed Aug 29 07:06:45 2018] usb 2-5.3: device descriptor read/64, error -32
> [Wed Aug 29 07:06:45 2018] usb 2-5.3: new low-speed USB device number 44
> using ehci-pci
> [Wed Aug 29 07:06:46 2018] usb 2-5.3: device descriptor read/64, error -32
> [Wed Aug 29 07:06:46 2018] usb 2-5.3: device descriptor read/64, error -32
> [Wed Aug 29 07:06:46 2018] usb 2-5-port3: attempt power cycle
>
> Plugged in holding Reset and DFU button:
> [Wed Aug 29 07:06:49 2018] usb 2-5.3: new low-speed USB device number 46
> using ehci-pci
> [Wed Aug 29 07:06:49 2018] usb 2-5.3: device descriptor read/64, error -32
> [Wed Aug 29 07:06:50 2018] usb 2-5.3: device descriptor read/64, error -32
> [Wed Aug 29 07:06:50 2018] usb 2-5.3: new low-speed USB device number 47
> using ehci-pci
> [Wed Aug 29 07:06:50 2018] usb 2-5.3: device descriptor read/64, error -32
> [Wed Aug 29 07:06:50 2018] usb 2-5.3: device descriptor read/64, error -32
> [Wed Aug 29 07:06:50 2018] usb 2-5-port3: attempt power cycle
>
> Full Disclosure:
> This unit was purchase from NooElec as a pre-order in June 2014. I
> purchased my second one as a used unit from a ham at the Huntsville
> Hamfest in 2016 after my original stopped working.
> What brings this on now is a comment Michael made on Git Hub about
> replace/repair any HackRF One. I did contact i...@greatscottgadgets.com
> and was referred to post here for further troubleshooting.
>
> Thanks
> Craig
>
> ___
> HackRF-dev mailing list
> HackRF-dev@greatscottgadgets.com
> https://pairlist9.pair.net/mailman/listinfo/hackrf-dev
>
___
HackRF-dev mailing list
HackRF-dev@greatscottgadgets.com
https://pairlist9.pair.net/mailman/listinfo/hackrf-dev
