Replies: 2 comments 2 replies
-
Those settings indicate it did the clear command, but something went wonky with the flash command. The simple fix is to reflash and it will probably work. |
Beta Was this translation helpful? Give feedback.
1 reply
-
I've stumbled upon exactly the same issue. Here are my full logs
So it looks like `set_modem_settings got skipped because of too short timeout, and IMPREF isn't set by script. No surprise, as my modem after flashing still advertises itself as Dell one. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello everyone,
Thanks a lot for all the work and knowledge shared on this repository !
I've used the autoflash script on a DW5811e (3P10Y) EM7455 airprime module. From what I can see the flashing process does succeed, but I end up with no fw images stored in the 4 devoted slots / active fw image in slot 255 (cf outputs at the bottom). Additionally the IMPREF? command shows a firmware mismatch that I've not been able to get fixed. IMPREF="" results in an error as I believe there is no available fw image in the above mentioned slots. Consequently, I assume, the module stays stuck in low power mode.
The workaround I have found however, is to issue AT!IMPREF="AUTO-SIM", which fixes the fw mismatch and let the module power on. With that, I've been able to successfully use the module in a USB adapter with ModemManager; it performs strongly: north of 150Mb/s DL, connected to a 10+km LTE tower, admittedly with a pair very decent ISKRA P58 antennas.
I would be more than happy with that, but I cannot manage to have ROOter (Goldenorb running on a Mikrotik RBM33G) connect to the modem (ie reproduce the connection process of ModemManager). Any guidance as to how to build a custom connection process within ROOter that "mimics" the way ModemManager handles this modem would be much appreciated.
Back to the modem itself, I've managed to perform an RMARESET=1 command, but it doesn't get rid of the fw mismatch and after I rerun the autoflash script I'm basically back to where I was before the rmareset. I haven't checked that so far (I currently don't have access to the PC I ran the autoflash script for the first time), but it is possible that this modem had this fw mismatch / misconfiguration beforehand. I'm running out of ideas to explore alternative routes to fix that problem and have this modem work for my use case. Any help here would be much appreciated ! Thanks
Some AT commands outputs:
ATI
Manufacturer: Sierra Wireless, Incorporated
Model: EM7455B
Revision: SWI9X30C_02.33.03.00 r8209 CARMD-EV-FRMWR2 2019/08/28 20:59:30
MEID: removed
IMEI: removed
IMEI SV: 20
FSN: LF708107740410
+GCAP: +CGSM
AT!IMAGE?
TYPE SLOT STATUS LRU FAILURES UNIQUE_ID BUILD_ID
FW 1 EMPTY 0 0 0
FW 2 EMPTY 0 0 0
FW 3 EMPTY 0 0 0
FW 4 EMPTY 0 0 0
Max FW images: 4
Active FW image is at slot 255
TYPE SLOT STATUS LRU FAILURES UNIQUE_ID BUILD_ID
PRI FF GOOD 0 0 0 002.072_000 02.33.03.00_GENERIC
Max PRI images: 50
AT!IMPREF?
!IMPREF:
preferred fw version: 02.20.03.00
preferred carrier name: GENERIC
preferred config name: GENERIC_002.017_000
preferred subpri index: 000
current fw version: 02.33.03.00
current carrier name: GENERIC
current config name: GENERIC_002.017_000
current subpri index: 000
fw version mismatch
after AT!IMPREF="AUTO-SIM"
AT!IMPREF?
!IMPREF:
preferred fw version: 00.00.00.00
preferred carrier name: AUTO-SIM
preferred config name: AUTO-SIM_000.000_000
preferred subpri index: 000
current fw version: 02.33.03.00
current carrier name: GENERIC
current config name: GENERIC_002.072_000
current subpri index: 000
Beta Was this translation helpful? Give feedback.
All reactions