USB Not Recognised

[bnt2025]

Hello,

My desktop cut out while flashing firmware to my BladeRF, now nothing is recognising it as a proper device. Not Windows or even Ubuntu.

I have tried connection a jumper to j64, but it is still shown as an unknown device.

Any recommendations?
Thanks

[jynik]

Could you post the output of dmesg from when you plug in the device? Include both cases where do and do not have the J64 jumpered.

Even if powered dropped out during firmware flashing, I would expect that you'd land back in the bootloader (which is what you enter when you boot with J64 jumpered). I say this for the following reasons:

• The FX3 bootloader expects the first 2 bytes of flash to be the ascii characters, "CY". If not, it will immediately drop to the USB bootloader. IIRC, these characters are written at the very end of programming.
• The FX3 firmware image format contains a checksum. To the best of my knowledge, the FX3 probably checks this and falls back to the USB bootloader otherwise.

If you see a Cypress device in the dmesg output, you can proceed with the bladeRF-cli 'recover' command to load firmware into the FX3's RAM, and then flash firmware. This is documented in the firmware upgrade wiki page.

For what it's worth, from my experience with the bladeRF and other FX3-based devices, you really have to go out of your way to "brick" a device (as in, drive I/Os incorrectly and such)...I'm sure we'll figure out something to get you back up and running.

- Jon

[bnt2025]

When I plug it in to my computer I get this error message over and over;

[54433.262883] usb 1-1.4: new full-speed USB device number 5 using ehci-pci
[54433.334813] usb 1-1.4: device descriptor read/64, error -32
[54433.510636] usb 1-1.4: device descriptor read/64, error -32
[54433.686468] usb 1-1.4: new full-speed USB device number 6 using ehci-pci
[54433.758395] usb 1-1.4: device descriptor read/64, error -32
[54433.934224] usb 1-1.4: device descriptor read/64, error -32
[54434.110053] usb 1-1.4: new full-speed USB device number 7 using ehci-pci
[54434.517552] usb 1-1.4: device not accepting address 7, error -32
[54434.589584] usb 1-1.4: new full-speed USB device number 8 using ehci-pci

Really hope it can be recovered.

[bpadalino]

Are you trying the same USB port, or a different one?

Coming up as a full speed device over EHCI sounds like a pretty terrible thing.

Have you tried a different cable?

[jynik]

Just to double-check... that dmesg output does indeed include both cases where J64 is and is not jumpered?

Cutting out a firmware upgrade of the bladeRF FW should definitely not cause the bootloader to misbehave...very weird...

[bnt2025]

Sorry for the massive delay,

but yes the dmesg is the same for bout USB 2 and 3. Below I have pasted in the results.

USB 3 without J64 attached

Code: Select all

[ 5511.272336] usb 3-2: new full-speed USB device number 3 using xhci_hcd
[ 5511.272539] usb 3-2: Device not responding to set address.
[ 5511.476452] usb 3-2: Device not responding to set address.
[ 5511.680257] usb 3-2: device not accepting address 3, error -71
[ 5511.792328] usb 3-2: new full-speed USB device number 4 using xhci_hcd
[ 5511.792502] usb 3-2: Device not responding to set address.
[ 5511.996404] usb 3-2: Device not responding to set address.
[ 5512.200206] usb 3-2: device not accepting address 4, error -71
[ 5512.312258] usb 3-2: new full-speed USB device number 5 using xhci_hcd
[ 5512.312432] usb 3-2: Device not responding to set address.
[ 5512.516404] usb 3-2: Device not responding to set address.
[ 5512.720168] usb 3-2: device not accepting address 5, error -71
[ 5512.832285] usb 3-2: new full-speed USB device number 6 using xhci_hcd
[ 5512.832457] usb 3-2: Device not responding to set address.
[ 5513.036386] usb 3-2: Device not responding to set address.
[ 5513.240202] usb 3-2: device not accepting address 6, error -71

USB 2 without J64 attached

Code: Select all

[ 5573.577977] usb 3-4: new full-speed USB device number 7 using xhci_hcd
[ 5573.578083] usb 3-4: Device not responding to set address.
[ 5573.781978] usb 3-4: Device not responding to set address.
[ 5573.985889] usb 3-4: device not accepting address 7, error -71
[ 5574.377896] usb 3-4: new full-speed USB device number 9 using xhci_hcd
[ 5574.378072] usb 3-4: Device not responding to set address.
[ 5574.581928] usb 3-4: Device not responding to set address.
[ 5574.785800] usb 3-4: device not accepting address 9, error -71
[ 5574.897887] usb 3-4: new full-speed USB device number 10 using xhci_hcd
[ 5574.898073] usb 3-4: Device not responding to set address.
[ 5575.101914] usb 3-4: Device not responding to set address.
[ 5575.305786] usb 3-4: device not accepting address 10, error -71
[ 5575.417860] usb 3-4: new full-speed USB device number 11 using xhci_hcd
[ 5575.418034] usb 3-4: Device not responding to set address.
[ 5575.621943] usb 3-4: Device not responding to set address.
[ 5575.825776] usb 3-4: device not accepting address 11, error -71
[ 5575.937845] usb 3-4: new full-speed USB device number 12 using xhci_hcd
[ 5575.938018] usb 3-4: Device not responding to set address.
[ 5576.142040] usb 3-4: Device not responding to set address.
[ 5576.345780] usb 3-4: device not accepting address 12, error -71

USB 2 with J64 attached

Code: Select all

[ 5861.362745] usb 3-4: new full-speed USB device number 14 using xhci_hcd
[ 5861.362922] usb 3-4: Device not responding to set address.
[ 5861.566903] usb 3-4: Device not responding to set address.
[ 5861.770706] usb 3-4: device not accepting address 14, error -71
[ 5861.882798] usb 3-4: new full-speed USB device number 15 using xhci_hcd
[ 5861.882995] usb 3-4: Device not responding to set address.
[ 5862.086760] usb 3-4: Device not responding to set address.
[ 5862.290592] usb 3-4: device not accepting address 15, error -71
[ 5862.402620] usb 3-4: new full-speed USB device number 16 using xhci_hcd
[ 5862.402792] usb 3-4: Device not responding to set address.
[ 5862.606749] usb 3-4: Device not responding to set address.
[ 5862.810575] usb 3-4: device not accepting address 16, error -71
[ 5862.922686] usb 3-4: new full-speed USB device number 17 using xhci_hcd
[ 5862.922865] usb 3-4: Device not responding to set address.
[ 5863.126733] usb 3-4: Device not responding to set address.
[ 5863.330609] usb 3-4: device not accepting address 17, error -71
[ 5902.293155] usb 3-2: new full-speed USB device number 18 using xhci_hcd

USB 3 with J64 attached

Code: Select all

[ 5902.293336] usb 3-2: Device not responding to set address.
[ 5902.497131] usb 3-2: Device not responding to set address.
[ 5902.701060] usb 3-2: device not accepting address 18, error -71
[ 5902.997134] usb 3-2: new full-speed USB device number 20 using xhci_hcd
[ 5902.997314] usb 3-2: Device not responding to set address.
[ 5903.201178] usb 3-2: Device not responding to set address.
[ 5903.405029] usb 3-2: device not accepting address 20, error -71
[ 5903.517143] usb 3-2: new full-speed USB device number 21 using xhci_hcd
[ 5903.517337] usb 3-2: Device not responding to set address.
[ 5903.721237] usb 3-2: Device not responding to set address.
[ 5903.925062] usb 3-2: device not accepting address 21, error -71
[ 5904.037130] usb 3-2: new full-speed USB device number 22 using xhci_hcd
[ 5904.037317] usb 3-2: Device not responding to set address.
[ 5904.241226] usb 3-2: Device not responding to set address.
[ 5904.445049] usb 3-2: device not accepting address 22, error -71
[ 5904.557115] usb 3-2: new full-speed USB device number 23 using xhci_hcd
[ 5904.557310] usb 3-2: Device not responding to set address.
[ 5904.761164] usb 3-2: Device not responding to set address.
[ 5904.965021] usb 3-2: device not accepting address 23, error -71

Could a corrupted firmware image cause this?

Thanks again

[jynik]

Hi there,

To my knowledge, a bad firmware flash should not be able to cause that. If you double-check my first post, you should drop into bootloader (which I believe is baked into the silicon) if the firmware's corrupted or when using that jumper.

Have you tried testing it on a different machine (the GNU Radio Live DVD might be handy here) and with a different cable in order to isolate the problem to the hardware? Any chance whatever cause the power to cut out originally can be related?

If you have or can get access to a Segger J-Link, you could try loading the FX3 firmware via JTAG.

[bnt2025]

Yes I have tested it on my desktop and laptop (the last set of results were my laptop)
I will install the GNU Radio Live DVD on an other laptop. to see if I can get any better results.

What version do I need of J Link I have found a few on Farnell, such as the 8.08.90, the 8.08.00.

Thanks

[jynik]

Before answering your immediate question, I just wanted to note that I saw something similar tonight. It occurred when the device was plugged in from boot -- apparently my BIOS didn't play nicely with the device, and I had to reboot with the device not plugged in to resolve it. (I've made a note to understand and investigate this further.)

Any chance you've had the device plugged in while your machine was booting? Could you try unplugging the device, rebooting, and then plugging it in only after your OS is up and running? I figured this is worth mentioning before you dive into the JTAG stuff...

Any of the J-Link devices (including the two you listed) should suffice. Seggar's website has a nice model comparsion chart and details on the product page. If you're using the device for educational (non-commercial) purposes, the EDU is definitely a great price.

Lastly, depending on how familiar you are with JTAG debugging with gdb/gdbserver and how much (or little) time you have to spend on it, it may be worth shooting an email to [email protected] to see if you could mail the device for someone to look at, if that's possible. (Reference this thread if you do, so the guys know I suggested this.)

[bnt2025]

Thank you for your suggestion. I have emailed the support address you supplied.

I will update when I hear back from them

Many thank

[jynik]

Hi there,

Would you mind just quickly confirming that one item I mentioned about ensuring the device is not plugged in when you boot your computer.

The team will definitely want to hear about that, I'm sure.

Thanks,
Jon

[bnt2025]

Yes, the device was never plugged in during boot.
Thanks