I am facing situations when the Fx30 modem is blocked. It is in OFF state and there are no ways to turn it ON, the command “$> cm radio on” has no effect.
I use customs firmware built from the Yocto environments. I meet this situation when upgrading a firmware from a R13 based firmware to a R14 based firmware. I arrive more systematically in this situation when the USB is disconnected (case of our system already deployed on sites).
When I work with the Fx30 locally, connected by USB, I do not face the problem.
My images contains all parts indicated in the ticket " [Fx30] Building a complete R14 customized image"
I have added to my image the part “user1-single-part-ubifs-empty_wp85” because I want the overlay cleaned from the previous Fx30 usage.
Below are some information about the situation when the modem is blocked:
root@DrBox_default_name:~# cm info
Device: FX30
IMEI: 353984080398397
FSN: LL805402131310
Firmware: SWI9X15Y_07.12.09.00 r34123 CARMD-EV-FRMWR1 2017/04/26 23:34:19
Bootloader: SWI9X15Y_07.12.09.00 r34123 CARMD-EV-FRMWR1 2017/04/26 23:34:19
priIdPn: 9906645
priIdRev: 01.02
skuId: 1103214
root@DrBox_default_name:~# fwupdate query
Connecting to service ...
Firmware Version: SWI9X15Y_07.12.09.00 r34123 CARMD-EV-FRMWR1 2017/04/26 23:34:19
Bootloader Version: SWI9X15Y_07.12.09.00 r34123 CARMD-EV-FRMWR1 2017/04/26 23:34:19
Linux Version: 3.14.29ltsi-a00e464379_935efbf4d8 #2 PREEMPT Wed Jun 17 10:40:52 UTC 2020
FX30 Version: FW_FX_3.08
root@DrBox_default_name:~# microcom -E /dev/ttyAT
AT!FWD?ALVER
ERROR
AT!FWD?HFSN
ERROR
AT+CSQ
+CSQ: 99,99
OK
The modem does not seem to respond any more.
I am able to get out of this situation by connecting the USB, downloading the same R14 based image again, then performing the command “$> fwupgrade download my_image.cwe”. Obviously this is not a solution for my systems already installed remotely.
Could you help me to find what is causing this modem not responding?
Is-there something missing in my image which could lead to this situation?
Is-there a command I could run when I face this problem to reactivate the communication with the modem?
performing the command “AT+CFUN=1” when the modem is not responding is producing an ERROR.
performing the command “AT+CGATT=1” does not return a response, it locks the At communication.
After reboot or electrical power down, the modem is still in the same none responsive state.
root@Fx30-DrBox:~# microcom -E /dev/ttyAT
AT+CFUN=1
ERROR
AT+CGATT?
+CGATT: 0
OK
AT+CGATT=1
…no response…
If you have other ideas to try to restart the modem communication, I’m listening…
I need a solution to upgrade the firmware R13->R14. My software and environment have not yet been ported on the Fx30 R17 firmware.
I have on my systems some working files in the overlay I want to erase when upgrading to a new firmware. That’s why I include the part “user1-single-part-ubifs-empty_wp85”. I will now separate the firmware upgrade load and the user1 erase to avoid the modem none responsive state.
Your module is LOW POWER MODE, so it can’t register the network.
You can try to do the steps below to recover module from LOW POWER MODE.
1.Clear all firmware entries:
AT!ENTERCND=“A710”
AT!IMAGE=0
AT!RESET 2.Download the R14 firmware to the module 3. Set image management preferences
AT!IMPREF=“GENERIC”
AT!RESET
Thanks for the information. I do not have a problem to be able to recover normal operations after being in this situation if the Fx30 is available locally. Connecting via the USB a re-flashing the same R14 based firmware gets the unit back in normal mode.
Where I have a problem is for the devices not available on site. I need a way to detect and recover from this situation for my remote devices.
For the commands you showed, I guess, I can make use of the AT!GSTATUS to detect this situation… then I need a way to get out of it, without a local usb connection, only by processes running on the device.
The AT!IMPREF? gives me a trace which may explain the problem:
root@Fx30-DrBox:~# microcom -E /dev/ttyAT
at!impref?
!IMPREF:
preferred fw version: 07.11.22.00
preferred carrier name: GENERIC
preferred config name: GENERIC_001.032_000
current fw version: 07.12.09.00
current carrier name: GENERIC
current config name: GENERIC_001.032_000
fw version mismatch
OK
A command like ‘at!gobiimpref=“07.12.09.00”,“GENERIC”,“GENERIC_001.034_000"’ may have allowed to re-align the preferred parameters with the current ones… but this AT command is not available on the Fx30.
Using the command at!impref=“AUTO-SIM”, then at!reset, I managed to have the modem restart. The unit came back on a normal state.
I’m going to add a process in my system issuing those AT commands when it detect the modem low power mode.
Is-it OK to leave the modem working in this “AUTO-SIM” mode? as it does not seem possible to come back into the “GENERIC” mode, the command AT!IMPREF=“GENERIC” returning always ERROR.
root@Fx30-DrBox:~# microcom -E /dev/ttyAT
at!impref?
!IMPREF:
preferred fw version: 00.00.00.00
preferred carrier name: AUTO-SIM
preferred config name: AUTO-SIM_000.000_000
current fw version: 07.12.09.00
current carrier name: GENERIC
current config name: GENERIC_001.033_000
OK
at!entercnd="A710"
OK
at!impref="GENERIC"
ERROR
You can load locate the firmware .cwe file into FX30 to re-flashing the same R14 based firmware with steps below:
1.Locate the firmware .cwe file that is to be installed and copy it to FX30:
$ scp file.cwe root@192.168.2.2:/tmp
2.Log in to the FX30:
$ ssh root@FX30’s IP
3.Install the firmware update:
# fwupdate download /tmp/some_file.cwe
4. Restart the device. The device will boot with the new firmware.
Yes, it is. It can come back into the “GENERIC” mode with my FX30 module.
AT!IMPREF?
!IMPREF:
preferred fw version: 00.00.00.00
preferred carrier name: AUTO-SIM
preferred config name: AUTO-SIM_000.000_000
current fw version: 07.12.09.00
current carrier name:
current config name:
carrier name mismatch
config name mismatch
OK
AT!IMPREF=“GENERIC”
OK
AT!RESET
In your case, the best way is to get support is through your commercial channel i/.e. who you bought the unit from.