OpenMoko missing after firmware upload

  • 6 Replies
  • 868 Views
OpenMoko missing after firmware upload
« on: January 27, 2021, 05:55:58 PM »
I'm using Ubuntu 18.04. The oscilloscope was working before, I was able to do some measurements and generate signal. Unfortunately, I'm not sure what exactly happened but now when I open the device, upload the firmware, nothing happens when I press "Capture". The "OpenMoko" vendorId:1d50 and deviceId:6104 goes missing with "lsusb".

I've tried EEPROM->Write FX3 Firmware and EEPROM->Write Calibration. The software mentions that the firmware and the calibration worked fine but "Upload Firmware" still won't work.

Any suggestions on how to fix this?

Regards,
Jeremy

*

Dejan

  • *****
  • 117
    • View Profile
Re: OpenMoko missing after firmware upload
« Reply #1 on: January 28, 2021, 09:53:05 AM »
Please check the response of EEPROM -> Read FX3 Firmware and also EEPROM -> Read Calibration and copy the response here.

Re: OpenMoko missing after firmware upload
« Reply #2 on: January 28, 2021, 03:29:03 PM »
Read FX3 Firmware:
ScopeFun v2.00
43 59 1c b0 e0 08 00 00 00 01 00 00 10 40 2d e9
12 00 a0 e3 cc 08 00 eb 10 40 bd e8 80 00 9f e5
00 20 a0 e3 40 10 a0 e3 d5 08 00 ea 10 40 2d e9
0f 00 a0 e3 c4 08 00 eb 10 40 bd e8 60 00 9f e5
00 20 a0 e3 20 10 a0 e3 cd 08 00 ea 10 40 2d e9
10 00 a0 e3 bc 08 00 eb 10 40 bd e8 40 00 9f e5
00 20 a0 e3 10 10 a0 e3 c5 08 00 ea 34 00 9f e5
10 00 90 e5 00 00 50 e3 13 00 a0 03 b2 08 00 0a
10 ff 2f 11 10 40 2d e9 11 00 a0 e3 ae 08 00 eb
10 40 bd e8 08 00 9f e5 00 20 a0 e3 80 10 a0 e3
b7 08 00 ea a0 0b 03 40 8c 0b 03 40 f0 41 2d e9
5c 67 9f e5 0c 00 96 e5 10 10 96 e5 01 40 00 e0
0c 40 86 e5 4c 57 9f e5 01 00 14 e3 03 70 a0 e3
0e 00 00 0a 00 00 d5 e5 0b 00 50 e3 00 70 c5 05
02 00 00 0a a0 08 00 eb 00 00 a0 e3 00 00 c5 e5
70 00 96 e5 02 01 80 e3 70 00 86 e5 0c 20 95 e5



Read calibration:
02 00 00 00 60 aa 18 ae 00 00 00 00 00 00 00 00
00 00 00 00 50 1d 00 00 04 61 00 00 2a 00 00 00
64 61 74 61 2f 66 69 72 6d 77 61 72 65 2f 66 78
33 2e 69 6d 67 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

*

Dejan

  • *****
  • 117
    • View Profile
Re: OpenMoko missing after firmware upload
« Reply #3 on: January 28, 2021, 08:35:52 PM »
This output looks normal, the FX3 firmware is OK. If the USB device disappears after clicking "Upload Firmware" there could be some other reasons.
Are you using original FPGA firmware?
Please make sure you using original USB cable, no extension cables or USB hubs?
Does any LED's flash after clicking "Upload Firmware" ?
« Last Edit: January 28, 2021, 08:37:30 PM by Dejan »

Re: OpenMoko missing after firmware upload
« Reply #4 on: January 29, 2021, 08:20:30 PM »
It suddenly worked one morning when uploading the firmware.
Both LEDs (between AWG and CH1/CH2) blinked once.
Then LEDs between CH1/CH2 blinked twice.
Unfortunately, for some reason, the acquisition later hung.


I tried it opening the USB and uploading the firmware again but then it failed again.
Both LEDs (between AWG and CH1/CH2) blinked once.
Then LEDs between CH1/CH2 blinked once.

Here is the output when I run dmesg after uploading the firmware:
Quote
[  322.580413] usb 2-6.4: USB disconnect, device number 12

EDIT: OpenMoko then disappears with "lsusb" but reappears by restarting the computer.
« Last Edit: January 29, 2021, 08:24:13 PM by jeremyp »

*

Dejan

  • *****
  • 117
    • View Profile
Re: OpenMoko missing after firmware upload
« Reply #5 on: January 31, 2021, 04:33:53 PM »
If all LED's blink after clicking upload then the fpga firmware was uploaded successfully. However, according to the dmesg output as soon as the capture starts the FX3 is getting reset. I think the most common reason for that would be that there is a significant voltage drop on the USB power immediately after starting capture. The FX3 will be disconnected from host if the USB VBUS voltage drops below 4.1 V - this should not happen in normal operation. It can happen, for example when USB extension cable is used.

One thing to check is, if the hardware is connected to the USB 3.0 port?  Please send the output of the following command:
lsusb && lsusb -t

Can you try connecting through a different USB port?

If the issue persist, please let me know. You can also send an email to info@scopefun.com to open a support ticket.
« Last Edit: January 31, 2021, 04:43:29 PM by Dejan »

Re: OpenMoko missing after firmware upload
« Reply #6 on: February 01, 2021, 03:49:19 PM »
Looks like the USB 2.0 port (direct connection, no extender), was not supplying enough power. Moving the ScopeFun to an extension USB powered by an external power supply solved the problem.

Thanks!

By the way, here's the output of lsusb && lsusb -t

Code: [Select]
Bus 001 Device 002: ID 8087:8000 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 009: ID 04d8:00dd Microchip Technology, Inc.
Bus 002 Device 007: ID 04d8:00dd Microchip Technology, Inc.
Bus 002 Device 006: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC
Bus 002 Device 005: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 002 Device 004: ID 0403:6014 Future Technology Devices International, Ltd FT232H Single HS USB-UART/FIFO IC
Bus 002 Device 012: ID 1d50:6104 OpenMoko, Inc.
Bus 002 Device 011: ID 0403:6015 Future Technology Devices International, Ltd Bridge(I2C/SPI/UART/FIFO)
Bus 002 Device 010: ID 0403:6014 Future Technology Devices International, Ltd FT232H Single HS USB-UART/FIFO IC
Bus 002 Device 008: ID 2109:3431 VIA Labs, Inc. Hub
Bus 002 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 002 Device 002: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/9p, 480M
    |__ Port 5: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
    |__ Port 6: Dev 3, If 0, Class=Hub, Driver=hub/4p, 480M
        |__ Port 4: Dev 12, If 0, Class=Vendor Specific Class, Driver=, 480M
        |__ Port 2: Dev 8, If 0, Class=Hub, Driver=hub/4p, 480M
            |__ Port 1: Dev 10, If 0, Class=Vendor Specific Class, Driver=, 480M
            |__ Port 3: Dev 11, If 0, Class=Vendor Specific Class, Driver=ftdi_sio, 12M
    |__ Port 7: Dev 4, If 0, Class=Vendor Specific Class, Driver=, 480M
    |__ Port 8: Dev 5, If 0, Class=Hub, Driver=hub/4p, 480M
        |__ Port 2: Dev 6, If 0, Class=Vendor Specific Class, Driver=ftdi_sio, 12M
        |__ Port 3: Dev 7, If 0, Class=Communications, Driver=cdc_acm, 12M
        |__ Port 3: Dev 7, If 1, Class=CDC Data, Driver=cdc_acm, 12M
        |__ Port 3: Dev 7, If 2, Class=Human Interface Device, Driver=usbhid, 12M
        |__ Port 4: Dev 9, If 1, Class=CDC Data, Driver=cdc_acm, 12M
        |__ Port 4: Dev 9, If 2, Class=Human Interface Device, Driver=usbhid, 12M
        |__ Port 4: Dev 9, If 0, Class=Communications, Driver=cdc_acm, 12M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 480M