Hey all-
I purchased 16 MC7455 modules from an online retailer within the last 6 months. They are not new, they are pulled from working devices (so I’m told). Out of these 16, 10 of them seem to be DOA.
I’ve tried them in a MOFI device, as well as a USB adapter on both Windows and Linux machines. The 6 working devices are recgonized by the MOFI device and the USB adapter just fine (blue LED lights up on adapter) but with the non-working ones I get nothing. They’re not picked up by windows or linux. No blue LED, no sounds, nothing.
Anyone have any ideas? Is there a way to “wake up” these modules? I’m having a hard time accepting the fact that I received this many dead units. My first order was for 10 and when I realized 6 weren’t working, the company sent me 6 replacements of which only one is working.
Any and all help is appreciated.
On Linux do you see the modem VID/PID (lsusb)?
I assume the USB adapter is a standalone unit and you can plug it into a PC.
James
I can see it in Linux with lsusb or usb-devices command but that’s it. I’m assuming it’s stuck in a bootloader mode but I also suspect the PID being 9070 is also causing a problem.
There’s a script out there that flashes the device and changes the USB composition all in one but it’s not recognizing the modem when I try to execute it.
Is there a way (without AT commands) to change the PID? I really have a feeling that’s what’s blocking me
Yes the modem is in boot & hold mode.
The Sierra serial Linux drivers should recognize boot mode.
For example:
[1112057.744063] usb 3-2: new high-speed USB device number 14 using xhci_hcd
[1112057.872790] usb 3-2: New USB device found, idVendor=1199, idProduct=9070
[1112057.872795] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[1112057.872797] usb 3-2: Product: Sierra Wireless MC7455 Qualcomm
[1112057.872800] usb 3-2: Manufacturer: Sierra Wireless, Incorporated
[1112057.872801] usb 3-2: SerialNumber: LQ61430015021006
[1112057.873699] GobiSerial 3-2:1.0: GobiSerial converter detected
[1112057.873785] usb 3-2: GobiSerial converter now attached to ttyUSB0
You cannot change the USB composition because the FW is not loading.
You could try to push a FW with SDKLite Sample app: fwdwl-litehostx86_64
Specify the model family to 9x30 ( -m3)
For your request, here is an example how to upgrade the modem , while the modem is in boot mode:
[1289352.480699] GobiNet 3-6:1.8 enp0s20u6i8: unregister ‘GobiNet’ usb-0000:00:14.0-6, GobiNet Ethernet Device
[1289353.268383] usb 3-6: new high-speed USB device number 18 using xhci_hcd
[1289353.397415] usb 3-6: New USB device found, idVendor=1199, idProduct=9070
[1289353.397419] usb 3-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[1289353.397421] usb 3-6: Product: Sierra Wireless MC7455 Qualcomm
[1289353.397423] usb 3-6: Manufacturer: Sierra Wireless, Incorporated
[1289353.397424] usb 3-6: SerialNumber: LQ61430015021006
[1289353.398382] GobiSerial 3-6:1.0: GobiSerial converter detected
[1289353.398473] usb 3-6: GobiSerial converter now attached to ttyUSB0
root@nano:/home/sierra/SLQSSDK/SLQS04.00.21_lite/SampleApps/lite-fw-download/bin# ./fwdwl-litehostx86_64 -m 3 -f /mnt/FW/MC7455_Rel23_02.30.01.01_VZW
litefw version :lite-fwSLQS04.00.21
INFO: QDL Port : /dev/ttyUSB0
INFO: Device Path: /dev/qcqmi0
INFO: FW Path : /mnt/FW/MC7455_Rel23_02.30.01.01_VZW
Package Info:
Carrier :VERIZON
FW Version :02.30.01.01
Model ID :SWI9X30C
Package ID :002
PRI Version:002.052
SKU :9999999
Part Number:9904780
file_type : 6
Modem is QDL mode. Skipping FW preference setting
Waiting for modem to come up in BOOT and HOLD mode …
BOOT and HOLD Mode. Downloading firmware …
litefw_DownloadFW succeeded.
Waiting for modem to come up in ONLINE mode …
FW info from modem:
Model ID : MC7455
FW Version : SWI9X30C_02.30.01.01
Carrier Name : GENERIC
Carrier PRI Revision: 002.045_000
Firmware Download Process completed
Exiting Application!!!
root@nano:/home/sierra/SLQSSDK/SLQS04.00.21_lite/SampleApps/lite-fw-download/bin#
you can download the FW image from the source:
root@nano:/home/sierra/SLQSSDK/SLQS04.00.23/SampleApps/lite-qmi-demo/lite-manual-test-qmi# ls -la /mnt/FW/MC7455_Rel23_02.30.01.01_VZW/
total 64512
drwxr-xr-x 2 root root 0 Oct 4 12:14 .
drwxr-xr-x 2 root root 0 Jan 28 09:53 …
-rwxr-xr-x 1 root root 64478657 Feb 14 2019 SWI9X30C_02.30.01.01.cwe
-rwxr-xr-x 1 root root 17227 Feb 7 2019 SWI9X30C_02.30.01.01_VERIZON_002.052_002.nvu
root@nano:/home/sierra/SLQSSDK/SLQS04.00.23/SampleApps/lite-qmi-demo/lite-manual-test-qmi#
Ok, so here’s where I’m at. Following your instructions I’ve reached this point. However, it freezes here. I’m not sure where I’m making a wrong turn but I do see some differences compared to what you have.
root@jt:/sierra/SampleApps/lite-fw-download/bin# ./fwdwl-litehostx86_64 -m 3 -f /mnt/FW/SWI9X30C_02.33.03.00.cwe
litefw version :lite-fwSLQS04.00.23
INFO: QDL Port : /dev/ttyUSB0
INFO: Device Path: /dev/qcqmi0
INFO: FW Path : /mnt/FW/SWI9X30C_02.33.03.00.cwe
file_type : 2
Modem is QDL mode. Skipping FW preference setting
Waiting for modem to come up in BOOT and HOLD mode …
BOOT and HOLD Mode. Downloading firmware … <---- THIS is where it freezes
Now I noticed you have a directory listed at the end of this command but I could only get the pricess to start by using the cwe file. Where am I going wrong here?
Your example: ./fwdwl-litehostx86_64 -m 3 -f /mnt/FW/MC7455_Rel23_02.30.01.01_VZW
My command: ./fwdwl-litehostx86_64 -m 3 -f /mnt/FW/SWI9X30C_02.33.03.00.cwe
What if you specify the directory not the file? in my case the directory has two files , cwe and nvu.
The FW upgrader will grab both.
what error do you get when you specify the directory.
/mnt is a mounted dir? , try to copy the directory with FW files to a local dir,