LimUtil --update scrogged - how to start over?

cswiger · 6 February 2017 20:50

Got a new USB3.1 card installed, limesdr device found ok - anyway it look like an update failed and now I need to reprogram something manually?

All was OK:

root@OSCompute1:~# SoapySDRUtil --find
linux; GNU C++ version 4.8.4; Boost_105400; UHD_3.11.0.git-71-g2016126f

Found device 0
addr = 1d50:6108
driver = lime
media = USB
module = STREAM
name = USB 2.0 (LimeSDR-USB)
serial = 0009060B00471F23

Preparing to update to 17.01.1 (dry run with current version):

root@OSCompute1:~# LimeUtil --update
Connected to [USB 2.0 (LimeSDR-USB), media=USB, module=STREAM, addr=1d50:6108, serial=0009060B00471F23]
Estimated reference clock 30.7193 MHz
Selected reference clock 30.720 MHz
[ 20%] 36800/186040 Bytes Programming failed! Read operation failed (/root/.local/share/LimeSuite/images/17.01/LimeSDR-USB_HW_1.3_r3.0.img)
Programming update failed! : Programming failed! Read operation failed

Now I’m scrogged??

Feb 6 14:55:01 compute1 CRON[26062]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 6 14:55:59 compute1 kernel: [ 9321.613179] usb 3-2: new high-speed USB device number 17 using xhci_hcd
Feb 6 14:55:59 compute1 kernel: [ 9321.613206] xhci_hcd 0001:58:00.0: ERROR: unexpected command completion code 0x0.
Feb 6 14:56:05 compute1 kernel: [ 9326.835714] usb 3-2: device descriptor read/8, error -110

cswiger · 6 February 2017 20:56

Anything I do in LimeSuiteGUI for the programming gets segfault - kind of thrashing around without instructions Plug the board in after powercycle nothing appears, but if I push the little button it at least appears as:

Found device 0
addr = 04b4:00f3
driver = lime
label = WestBridge [USB 2.0] 4BE
media = USB 2.0
module = STREAM
name = WestBridge
serial = 0000000004BE

In the above state:

root@OSCompute1:~# LimeUtil --fw=“/root/.local/share/LimeSuite/images/17.01/LimeSDR-USB_HW_1.3_r3.0.img”
Connected to [WestBridge [USB 2.0] 4BE]
Unsupported hardware connected: UNKNOWN[HW=0]
[ 0%] 0/186040 Bytes Programming failed! Write operation failed
Programming failed! : Programming failed! Write operation failed

Zack · 7 February 2017 09:06

hi @cswiger,

It looks like there was firmware update interrupt. Now FX3 MCU boots into bootloader mode.
You may try the following steps using LimeSuiteGUI:

Download the latest firmware image file;
Connect the LimeSDR board;
Run LimeSuiteGUI and connect to the device;
Go to Modules -> Programming menu;
Select FX3 in Device list and Firmware to RAM in Programming mode. Open image file you downloaded in the step 1;
Push Program and wait till programming is finished;
Connect to the device again in LimeSuiteGUI. Now you will see it as usually;
Perform step 4;
Set everything as in step 5 just choose Firmware to Flash instead of Firmware to RAM in Programming mode;
Push Program and wait till programming is finished.

Check if everything is OK by re-connecting the board.

cswiger · 7 February 2017 23:55

Huh - no luck with that - In short, new usb3.1 card (ORICO 2 Ports USB3.1 Desktop Computer Board PCI-E) plugged into an hp xw9400 - brought up Ubuntu 14.04 “trusty” - plugged in power and connected lime board to the usb3.1 port. Finds it ok, started a LimeUtil --update and it starts - later find the above failure at 20%. At this point the usb card is deaf and responds to nothing else, until just recently restarted.

The Lime board shows nothing when plugged in by itself (no other power - the usb3 card takes an aux power from sata connectors) - and with power it we see this:

Feb 7 18:26:09 compute1 kernel: [ 418.474883] usb 3-2: new high-speed USB device number 3 using xhci_hcd
Feb 7 18:26:14 compute1 kernel: [ 423.493406] usb 3-2: device descriptor read/8, error -110
Feb 7 18:26:19 compute1 kernel: [ 428.615686] usb 3-2: device descriptor read/8, error -110
Feb 7 18:26:20 compute1 kernel: [ 428.886792] usb 3-2: new high-speed USB device number 4 using xhci_hcd
Feb 7 18:26:29 compute1 kernel: [ 433.888603] xhci_hcd 0001:58:00.0: Timeout while waiting for address device command
Feb 7 18:26:29 compute1 kernel: [ 438.494273] [sched_delayed] sched: RT throttling activated
Feb 7 18:26:29 compute1 kernel: [ 438.694414] usb 3-2: Device not responding to set address.
Feb 7 18:26:30 compute1 kernel: [ 438.898487] usb 3-2: device not accepting address 4, error -71
Feb 7 18:26:30 compute1 kernel: [ 438.899677] xhci_hcd 0001:58:00.0: Bad Slot ID 3
Feb 7 18:26:30 compute1 kernel: [ 438.899690] xhci_hcd 0001:58:00.0: Could not allocate xHCI USB device data structures
Feb 7 18:26:30 compute1 kernel: [ 438.899705] hub 3-0:1.0: couldn’t allocate port 2 usb_device

and the firmware update cannot even start. When powered and plugged into the previously working usb port we see this:

Feb 7 18:47:55 compute1 kernel: [ 1724.998005] usb 1-4: new high-speed USB device number 4 using ehci-pci
Feb 7 18:48:10 compute1 kernel: [ 1740.115855] usb 1-4: device descriptor read/64, error -110
Feb 7 18:48:26 compute1 kernel: [ 1755.337746] usb 1-4: device descriptor read/64, error -110
Feb 7 18:48:26 compute1 kernel: [ 1755.553783] usb 1-4: new high-speed USB device number 5 using ehci-pci
Feb 7 18:48:41 compute1 kernel: [ 1770.671661] usb 1-4: device descriptor read/64, error -110
Feb 7 18:48:56 compute1 kernel: [ 1785.893499] usb 1-4: device descriptor read/64, error -110
Feb 7 18:48:56 compute1 kernel: [ 1786.109622] usb 1-4: new high-speed USB device number 6 using ehci-pci
Feb 7 18:49:07 compute1 kernel: [ 1796.521591] usb 1-4: device not accepting address 6, error -110
Feb 7 18:49:07 compute1 kernel: [ 1796.633673] usb 1-4: new high-speed USB device number 7 using ehci-pci
Feb 7 18:49:17 compute1 kernel: [ 1807.045653] usb 1-4: device not accepting address 7, error -110
Feb 7 18:49:17 compute1 kernel: [ 1807.045747] hub 1-0:1.0: unable to enumerate USB device on port 4
Feb 7 18:49:18 compute1 kernel: [ 1807.501883] usb 2-4: new full-speed USB device number 4 using ohci-pci

Now -if I press the FX3 reset button we get this:
Feb 7 18:49:51 compute1 kernel: [ 1840.554636] usb 1-4: new high-speed USB device number 8 using ehci-pci
Feb 7 18:49:51 compute1 kernel: [ 1840.687508] usb 1-4: New USB device found, idVendor=04b4, idProduct=00f3
Feb 7 18:49:51 compute1 kernel: [ 1840.687521] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Feb 7 18:49:51 compute1 kernel: [ 1840.687529] usb 1-4: Product: WestBridge
Feb 7 18:49:51 compute1 kernel: [ 1840.687535] usb 1-4: Manufacturer: Cypress
Feb 7 18:49:51 compute1 kernel: [ 1840.687540] usb 1-4: SerialNumber: 0000000004BE
Feb 7 18:49:51 compute1 mtp-probe: checking bus 1, device 8: “/sys/devices/pci0000:00/0000:00:02.1/usb1/1-4”
Feb 7 18:49:51 compute1 mtp-probe: bus: 1, device: 8 was not an MTP device

Interesting that the ‘event’ - whatever happened at 20% --update, took out the new usb3 card and we had to power off/on to recover it and it was just tested with a serial port usb device OK, but the Lime has not been able to be recovered.

cswiger · 8 February 2017 00:00

One last datapoint - when the FX3 reset button is pressed the LimeUtil sees it but cannot update:

root@OSCompute1:~# LimeUtil --find

[WestBridge , media=USB 2.0, module=STREAM, addr=04b4:00f3, serial=0000000004BE]

root@OSCompute1:~# LimeUtil --update
Connected to [WestBridge [USB 2.0] 4BE]
Unsupported hardware connected: UNKNOWN[HW=0]

Programming update failed! : Unsupported hardware connected: UNKNOWN[HW=0]

Zack · 8 February 2017 12:23

Hi @cswiger,

Have you tried the procedure described above (it is not clear from your response, sorry)? By the way, you have to use LimeSuiteGUI, not LimeUtil for this task.

cswiger · 8 February 2017 17:31

Zack - after deep breath yes it was found in the LimeSuiteGUI OK , had to press the FX3 reset button, and now reloading. Thanks!! Apologies for the too much info

Sure is a lot to learn here - I’m going to allocate a good 6 month period before even trying to pretend to know this device.

jherbert · 16 February 2017 12:36

Just received my LimeSDR and tried to install the latest firmware. I almost immediately got “Programming failed”. Reason for updated was enumeration error, Any ideas what might be wrong?

sdr_research · 16 February 2017 12:57

Please read Update Firmware for LimeSDR v1.4 under windows

jherbert · 16 February 2017 13:07

Thank you. Upgrade running right now.

bardia1990 · 6 November 2017 09:37

Hi
i get below error but i don’t know about this. please help me.
libusb: warning [handle_timeout] async cancel failed -5 errno=22