[FX30 Cat-M] Modem won't connect after /mnt/userrw/ erasing

IoT Gateways FX30
21

How about modem port and usb ecm port?

22

They are both also present.

23

You can ssh via ecm port
You can check network status via modem port

24

We tried to SSH on the 192.168.2.2 but it doesn’t work.
How can we access to the modem to check the network status?

25

You can enter AT command in modem port

26

I didn’t know that trick, that’s a good one for next time having trouble with the system.

I performed the RMARESET command on the modem port and now the system boot! USB interface is also usable.

However, the modem doesn’t seem to be happy (red led and radio always off):

root@fx30:~# microcom -s 230400 /dev/ttyAT
at!image?
TYPE SLOT STATUS LRU FAILURES UNIQUE_ID   BUILD_ID
FW   1    FOTA   1   0 0      001.071_001 02.36.06.00_GENERIC
FW   2    FOTA   127 0 0      001.000_002 02.16.06.00_SIERRA
FW   3    EMPTY  0   0 0
Max FW images: 3
Active FW image is at slot 255

TYPE SLOT STATUS LRU FAILURES UNIQUE_ID   BUILD_ID
PRI  FF   GOOD   0   0 0      001.012_000 02.14.04.00_GENERIC
Max PRI images: 50

OK
at!impref?
!IMPREF:
 preferred fw version:    02.14.04.00
 preferred carrier name:  GENERIC
 preferred config name:   GENERIC_001.012_000
 preferred subpri index:  000
 current fw version:      02.36.06.00
 current carrier name:    GENERIC
 current config name:     GENERIC_001.012_000
 current subpri index:    000

 fw version mismatch

OK

If I understand properly, it means that the modem can’t use the current modem fw? How is this even possible? I thought using a full FW will replace all parts of the config (including modem files).
How can I force the modem to use the modem fw from the cwe that I just flashed?

27

it is “fw version mismatch”, that is why it cannot go online mode.

28

That’s what I understood but how is this possible? I flashed a full fw that is supposed to “force” the system to a good state.

29

No idea, you might download again and see what happens

30

I flashed again the same FW and this time, the modem seem to boot. However, I’m back at the previous problem:

root@fx30:~# cm radio
Power:                         ON
Current Network Operator:
Current RAT:                   Module not registered on network, RAT not available
Status:                        Not registered but currently searching for a new operator (LE_MRC_REG_SEARCHING)
Signal:                        No signal strength (0)
PS:                            Packet Switched Not registered (LE_MRC_REG_NONE)

root@fx30:~# microcom -s 230400 /dev/ttyAT
at!image?
TYPE SLOT STATUS LRU FAILURES UNIQUE_ID   BUILD_ID
FW   1    FOTA   128 0 0      001.071_001 02.36.06.00_GENERIC
FW   2    FOTA   127 0 0      001.000_002 02.16.06.00_SIERRA
FW   3    EMPTY  0   0 0
Max FW images: 3
Active FW image is at slot 1

TYPE SLOT STATUS LRU FAILURES UNIQUE_ID   BUILD_ID
PRI  FF   GOOD   0   0 0      001.071_001 02.36.06.00_GENERIC
Max PRI images: 50

OK
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.36.06.00
 current carrier name:    GENERIC
 current config name:     GENERIC_001.071_001
 current subpri index:    000

OK
31

Are you downloading generic spk?

How about setting generic instead of autosim

32

Set the impref to GENERIC doesn’t change anything.

I use that fw: FX30_WP77xx_full_R14.1.1.002-generic-SWI9X06Y_02.36.06.00.cwe

33

No idea, you might try other sim card and network operator

34

As I said in the first message, SIM, antenna and network worked properly on the previous FW (and on this FX30).
The problem occurred (or at least seem to be) caused by the erase of /mnt/userrw contents.
Could you confirm that, no matter what was before configured/flashed using a full FW replace all parts (specially on the modem side)?

We tried this erasing on another FX30 and the problem also appeared.

35

Seems you already confirmed, didn’t you?

Suggest you not to erase this folder

36

What I don’t understand is, why with a full firmware the FX30 is not fully restore to a known state.
Erasing folder shouldn’t have impact with a full firmware, isn’t it?

During our FW9.1 → FWR14 upgrade we have found a FX30 that can’t be upgraded (reboot loop due to modem crash). We erased that folder and the box booted with the modem problem. What’s inside that folder? How can we ensure that upgrading our FX30 (they are all remotely connected) will not make crash due to the userrw contents?

It seem after a long time (almost 20min), the modem finally connect to the radio network…

37

Good to know it can register network now

You can see here that FW update is not restoring everything: