how about switching the SIM card by AT!UIMS=1 and AT!UIMS=0
Still no internet, I also just tried AT+CEREG=1, AT+CGREG=1, and AT+CREG=1.
did the enforce parameter inside the command “pci=326 freq=1850 enforce=1" make any difference?
Without the enforce, it gives the SetCellConfig error “Incompatible State” when I try to lock a cell. However, this issue of the network freezing happens as soon as I run ./lite-qmi-nasarm.
Do you mean ““pci=326 freq=1850 enforce=0”?
I mean not specifying it. For example, running it as -i 117 -f 68636 gives an error but -i 117 -f 68636 -e 1 works.
how about using “enforce=0”?
Enforce set to 0 also gives the SetCellConfig error “Incompatible State”.
how about using “AT!DAFTMACT” and “AT!DAFTMDEACT”?
Same result (still no internet), seems like maybe a reset is required for it to register and attach properly, even though AT!GSTATUS reports no issues.
actually you need to understand that locking to a cell is not a proper setting in real use case
It can generate a lot of performance issue
So this is only for your own testing
Makes sense, but the issue starts as soon as I run ./lite-qmi-nasarm, not when I lock to the cell. Basically, if I just do ./lite-qmi-nasarm without doing anything else, the LTE signal that I initially have just freezes.
maybe the workaround for you is to use lite-qmi-nasarm to set the cell ID followed by a reset.
After reset, you don’t need to run lite-qmi-nasarm, right?
Yes, I think that’s what I’ll stick to doing. Although, I will be setting different cell IDs sequentially as part of my test, so I’ll need to restart each time. Should be fine but takes time.
actually i suspect the parameter you input has some problem
If you just enter “sudo ./bin/lite-qmi-nasarm" without those -i -f option, will it affect the internet connection?
Yes, just running the lite-qmi-nasarm application freezes the internet connection. Maybe, something happens when lite-qmi-nasarm does this: “Open transport “/dev/cdc-wdm0” on USB device in MBIM mode”
I found that you can follow below sequence to overcome the issue:
- after module reboots, run lite-qmi-nasarm application to set the cell ID
- quit the application
- now run “sudo mbim-network /dev/cdc-wdm0 start” to establish data connection
- dhclient wwan0
- now the data connection should be OK
- after that if I want to run lite-qmi-nasarm application again, I have to disconnect the VMWARE (linux image) USB and reconnect the USB to the VMWARE(linux image), so you might need to consider to use some USB reconnect utility.
Btw, you can also try rmnet interface instead of mbim interface in at!usbcomp and see if it has same problem
1 Like
I just found that this is due to the following in MBPL SDK user guide:
To run two SDK sample applications, you need to do the following:
- run SampleApps/qmux-router by “sudo ./bin/qmux-routerhostx86_64 -m”
- establish data connection by /SampleApps/lite-qmi-connection-manager by " sudo ./bin/lite-qmi-connection-managerhostx86_64 -r"
- sudo dhclient wwan0
- "ping 8.8.8.8 -I wwan0 " should be OK
- now run /SampleApps/lite-qmi-nas to set cell ID by “sudo ./bin/lite-qmi-nashostx86_64 -r”
- ping operation should be still OK to run