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
I attach the kernel traces (DMESG).modem_blocked_dmesg.txt (35.3 KB)
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?
Best regards, Christian.