I’m trying to get MC7455 working in a linux system.
I’ve had success with Telit module which work completely fine with Linux qmi_wwan functionality. I’m able to bring up the connection via qmicli and then use dhcpcd to get an IP address.
I’ve confirmed that the SIM card is activated and that the associated ICCID / IMEI is activated.
SIM APN: nimblink.gw12.vzwentp
I’ve tested that APN with Telit and it worked just fine.
Hardware | manufacturer: ‘Sierra Wireless, Incorporated’
| model: ‘MC7455’
| revision: ‘SWI9X30C_02.30.01.01 r7792 CARMD-EV-FRMWR2 2018/07/13 02:24:52’
| H/W revision: ‘unknown’
| supported: ‘gsm-umts, lte’
| current: ‘gsm-umts, lte’
However with MC7455 I am having nothing but issues. When I switched over to this hardware I initially tried to also use the qmicli and it failed for me (3,2001) no-service.
Things I have tried:
libqmi - raw-ip mode
libqmi reported that the support for MC7455 was only via raw-ip, so I changed the qmicli to open the device in net-raw-ip|net-no-qos-header for connectivity, but that also replied with the same issue.
I downloaded the SDK for MC7455 which looks like the same as EM7565 (which I’m also looking into). I built the kernel modules for GobiNet and GobiSerial, I blacklisted the qmi_wwan drivers, rebooted the device and verified that only GobiNet was running. I built the SDK and put the sample programs on the device. I ran the ConnectionManager and tried to establish the a connection to the APN in question and I get only that it is disconnected.
./Connection_Manager/bin/connectionmgrhostx86_64 slqssdk 0 Instance ID :0 Session StateV4:1 Session StateV6:1 Instance ID :1 Session StateV4:1 Session StateV6:1 Please select one of the following options or press <Enter> to exit: 1. Start UMTS Data Session 2. Start LTE Data Session 3. Start CDMA Data Session 4. Start RUIM data session 5. Stop the currently active Data Session 6. Display all the profiles stored on the device 7. Display the settings for a particular profile stored on the device 8. Create a Profile on the device 9. Modify the settings of an existing profile stored on the device 10. Delete a profile stored on the device 11. Power cycle the device 12. Set Device Power Mode 13. Qos testing Option : 2 Modem not registered to network, reg state 255 1. IPV4 (default) 2. IPV6 3. IPV4V6 Please select IP family preference for the call, or press <Enter> to exit: 1 ID PDPType IPAddress PrimaryDNS SecondaryDNS Auth ProfileName APNName UserName 1 IPV4 0.0.0.0 0.0.0.0 0.0.0.0 0 nimblink.gw12.vzwentp 2 IPV4V6 0.0.0.0 0.0.0.0 0.0.0.0 0 vzwadmin 3 IPV4V6 0.0.0.0 0.0.0.0 0.0.0.0 0 vzwinternet 4 IPV4V6 0.0.0.0 0.0.0.0 0.0.0.0 0 vzwapp 5 IPV4V6 0.0.0.0 0.0.0.0 0.0.0.0 0 vzw800 6 IPV4V6 0.0.0.0 0.0.0.0 0.0.0.0 0 vzwclass6 7 IPV4V6 0.0.0.0 0.0.0.0 0.0.0.0 0 nimblink nimblink.gw12.vzwentp 8 IPV4 0.0.0.0 0.0.0.0 0.0.0.0 0 nimblink.gw12.vzwentp Please provide a profile id(1-16), or press <Enter> to exit: 1 Failed to start LTE/CDMA Data SessionFailure Code : 1014(0x03f6) WDS Call End Reason : 3(0x0003) Verbose Failure Reason Type: 3(0x0003) Verbose Failure Reason : 2001(0x07d1)
I also created a ConnectionManager2 which uses the SDK API to show SIM status since I didn’t see other functionality for it in the sample programs that come with the SDK.
./Connection_Manager2/bin/connectionmgrhostx86_64 slqssdk 0 Instance ID :0 Session StateV4:1 Session StateV6:1 Instance ID :1 Session StateV4:1 Session StateV6:1 Hello Nodar UIMGetCardStatus: 0 Card Status: ============= Primary GW provisioning application index: 2 Primary 1x provisioning application index: 0 Secondary GW provisioning application index: 65535 Secondary 1x provisioning application index: 65535 numSlot: 2 ------------------------ Slot 0: cardState: 1 Slot 0: upinState: 0 Slot 0: upinRetries: 0 Slot 0: upukRetries: 0 Slot 0: errorState: 0 Slot 0: numApp: 4 ------------------------ Slot 1: cardState: 0 Slot 1: upinState: 0 Slot 1: upinRetries: 0 Slot 1: upukRetries: 0 Slot 1: errorState: 0 Slot 1: numApp: 0
From the above, we see that the SDK sees the SIM card for the module in question, but we’re not able to connect.
Tried using ModemManager
I tried using ModemManager with both qmi_wwan and GobiNet/GobiSerial (separetely) meaning one of the driver sets being loaded at a time. ModemManager is able to recognize the module and finds the SIM card. In both cases (qmi_wwan and Gobi) I’m able to start the connection to the bearer that I create:
mmcli -m 0 --create-bearer="apn=nimblink.gw12.vzwentp" Successfully created new bearer in modem: /org/freedesktop/ModemManager1/Bearer/0
And connect to the bearer
mmcli -b 0 -c
successfully connected the bearer
ModemManager reports that I need to use ppp further
------------------------- IPv4 configuration | method: 'ppp' | address: 'unknown' | prefix: '0' | gateway: 'unknown' | DNS: none
I try various ways of using pppd to connect but that always fails. I found a sample configuration here: not sure if that’s what I should be using. I’ve also tried other configurations but none of them worked. Sierra Wireless Source - PPP sample configuration
With the telit module that fully works with opensource QMI, once the network establishes I just use dhcpcd and I get an IP address.
I also saw mentions to use NetworkManager, however when that is used with ModemManager it fails to register the network and just times out when doing nmcli c up verizon. All we see from ModemManager is Simple connect state (5/8): Register, that’s the last thing that is seen before it times out.
I tried following the guides for using AT commands for MC7455 to start up the connection.
ATI Manufacturer: Sierra Wireless, Incorporated Model: MC7455 Revision: SWI9X30C_02.30.01.01 r7792 CARMD-EV-FRMWR2 2018/07/13 02:24:52 MEID: <not showing> ESN: 12802628024, 802819B8 IMEI: <not showing> IMEI SV: 16 FSN: LQ930446970310 +GCAP: +CGSM at!gstatus? !GSTATUS: Current Time: 1873 Temperature: 29 Reset Counter: 1 Mode: ONLINE System mode: LTE PS state: Not attached LTE band: No band LTE bw: Unknown LTE Rx chan: 0 LTE Tx chan: 4294967295 LTE CA state: INACTIVE LTE Scell band:No band LTE Scell bw:1.4 MHz LTE Scell chan:0 EMM state: Deregistered No Cell RRC state: RRC Idle IMS reg state: No Srv IMS mode: Normal PCC RxM RSSI: 0 RSRP (dBm): 0 PCC RxD RSSI: 0 RSRP (dBm): 0 SCC RxM RSSI: 0 RSRP (dBm): 0 SCC RxD RSSI: 0 RSRP (dBm): 0 Tx Power: -- TAC: 2ADC (10972) RSRQ (dB): -1339.8 Cell ID: 02150D90 (34934160) SINR (dB):
More AT information
+CME ERROR: operation not allowed
Config Index: 1
Config Type: 1 (Generic)
Interface bitmask: 0000050D (diag,nmea,modem,rmnet0,rmnet1)
OK at+cpin? +CPIN: READY OK at+csq +csq: 99,99 OK at+creg OK at+cops? +COPS: 0 OK
Trying to start a data connection fails
OK at!scact=1 ERROR
I followed instructions on changing the USBCOMP to using rmnet
Config Index: 1
Config Type: 1 (Generic)
Interface bitmask: 0000010D (diag,nmea,modem,rmnet0)
I think that the fact that GSTATUS is reporting that PS state is not attached and that some of the states are shoring as inactive are causing issues.
Any help would be appreciated.