Open luckylinux opened 8 months ago
Small update and difference after trying an older version of the firmware from 2022:
deviceid=`lsusb | grep -i -E '1199:9071|1199:9079|413C:81B6' | awk '{print $6}'`
echo $deviceid
qmi-firmware-update --update -d "$deviceid" SWI9X30C_02.33.03.00.cwe SWI9X30C_02.33.03.00_GENERIC_002.072_001.nvu
Enable is successful this time, but connection times out:
root@SierraFirmwareUpdater:/usr/src/autoflash_sierra_firmware_2022# mmcli -m 1 -e
successfully enabled the modem
root@SierraFirmwareUpdater:/usr/src/autoflash_sierra_firmware_2022# mmcli -m 1 --simple-connect="apn=internet" --3gpp-register-in-operator=XXXYY
error: couldn't register the modem: 'Timeout was reached'
For those interested I got it to work. Not very well (bad weather, small antenna, indoor) but approx. 10 Mbps download / 1 Mbps upload.
Solution from my inquiry at SIERRA Wireless Forums https://forum.sierrawireless.com/t/em7455-not-connecting-registering-to-network/31348/16 1
The Solution was to "flash" the APN. Not sure it was stuck on an APN of a different operator (maybe OpenWRT "flashed" the APN into the modem during one of the previous attemps with the other SIM card in QMI/MBIM modem), but it would definitively ignore the correctly specified operator in the "APN" Field.
AT+CGDCONT=1,"IP","internet"
The reboot the modem network stack
AT+CFUN=0
AT+Cfun=1
AT+CGDCONT?
And finally check the status ... Now it's registered
AT!GSTATUS?
I could update the firmware after slightly modifying the script. See https://github.com/danielewood/sierra-wireless-modems/discussions/71 and autoflash-7455.sh.txt
I also trying to force FCC Unlock, given what some other users reported and the general guide at https://modemmanager.org/docs/modemmanager/fcc-unlock/.
Firmware Version is the latest available today (02.38.00.00).
Flashing log (unfortunately I had to flash several times because I got stuck in this , so only the last flash is shown here):
lsusb -v
(only relevant device shown)lsusb
(only relevant device shown)usb-devices
(only relevant device shown)Status of FCC Unlock
And
dmesg
(only relevant device shown)Trying to enable modem
journalctl -xeu ModemManager
More details on
journalctl -xeu ModemManager
aftersystemctl restart ModemManager
. modemmanager.logI tried this (at least the enable modem part) on:
There just seems to be something missing and I cannot figure out what.
Any other idea ?
Could it also be a USB power issue ? 500mA maximum current (if reported correctly) at 5V is only 2.5W. Could this also be the cause of the issue ?
Not sure if this is normal, probably it's NOT:
And this is when I tried some AT commands on OpenWrt. Seems like the device is stuck in low power mode: