TECHSHIP IS A GLOBAL SUPPLIER OF WIRELESS COMPONENTS
How to step by step set up a data connection over QMI interface using qmicli and in-kernel driver qmi_wwan in Linux?
Several cellular modules based on Qualcomm chipsets implements the Qualcomm Qualcomm MSM (QMI) Interface.
There is a open source Linux in-kernel driver supporting this interface and it is called qmi_wwan. This driver can be used together with ModemManager and NetworkManager to automate connection establishment and as a connection manager.
The library libqmi which ModemManager uses can also be used to communicate in a more direct way with the cellular devices over the QMI interface and to step by step do necessary configurations and trigger the data connection over the cellular network.
A selection of cellular modules can be supported:
Using RAW IP kernel configuration:
Sierra Wireless MC74 series, EM74 series, EM75** series
Telit LM940, LM960
Telit LN94x series (requires USB mode switch)
Simcom SIM7500 series, SIM7600 series, SIM7600 -H series
(can be supported in qmi_wwan driver from kernel 4.18 or by applying the following one line qmi_wwan source code patch on previous kernel builds: qmi_wwan: apply SET_DTR quirk to the SIMCOM shared device ID)
Using 802.3 IP framing kernel configuration:
Simcom SIM7100 series
Sierra Wireless MC73**/EM73** series
ModemManager combined with NetworkManager will detect the cellular modules automatically in most cases, please refer to their respective documentations on how to establish a data connection using them.
Example on how to set up the data connection step by step manually with libqmi:
First install the libqmi Linux library e.g. by using your system package manager like apt or preferably latest version from source on the Freedesktop pages for libqmi project: https://www.freedesktop.org/wiki/Software/libqmi/
Verify that you have the Linux in-kernel qmi_wwan driver installed and attached for the cellular modules QMI interface over USB:
Can look e.g. like this:
|__ Port 1: Dev 3, If 2, Class=Vendor Specific Class, Driver=qmi_wwan, 480M
If the driver is not correctly loaded, please verify that the module is set to expose the correct USB endpoints configuration toward the host system and that you have followed the provided guides from the cellular module vendors, regarding how to implement the module in Linux.
Libqmi expose a command line interface that can be used to communication with the module over QMI interface.
The qmicli help will output information about all commands available:
The cellular modules QMI control interface are usually named cdc-wdm* e.g.:
In order to allow parallel commands to be execute on the module over QMI interface, it is recommended to use the libqmi proxy function. This can be done by including the attribute -p or --device-open-proxy in every qmicli command.
If a SIM pin is required for the SIM card, use command bellow:
qmicli --device=/dev/cdc-wdm0 -p --dms-uim-verify-pin=PIN,1234
The name of the related network interface to QMI control channel can be acquired with the command:
qmicli --device=/dev/cdc-wdm0 --device-open-proxy --get-wwan-iface
The most recent Qualcomm based cellular modules only expose QMI interfaces that can support Raw-IP mode. Sierra Wireless EM/MC74 and EM75 series modules, Telit LM940 and LN940 series for example require this.
Check what IP-mode the host system is configured for:
qmicli --device=/dev/cdc-wdm0 --get-expected-data-format
Check what IP-mode the cellular module require:
qmicli --device=/dev/cdc-wdm0 --device-open-proxy --wda-get-data-format
to change qmi_wwan driver to use Raw-IP.
Disable the network interfaces exposed by the cellular module:
ip link set dev wwan0 down
Trigger the Raw-IP support:
echo Y > /sys/class/net/wwan0/qmi/raw_ip
Enable the network interfaces again:
ip link set dev wwan0 up
Now the data connection in the cellular module can be activated e.g. with a IPv4 type configuration on the specified APN:
qmicli --device=/dev/cdc-wdm0 --device-open-proxy --wds-start-network="ip-type=4,apn=data.tre.se" --client-no-release-cid
Once "Network started" is displayed, you can send a DHCP request on the network interface.
Please note that not all DHCP clients in Linux can support Raw-IP format, udhcpc however support this for IPv4 over Raw-IP.
udhcpc -q -f -n -i wwan0
Disconnect the data bearer and data connection over QMI by command bellow and providing the network handle and CID returned at connection activation:
qmicli --device=/dev/cdc-wdm0 --device-open-proxy --wds-stop-network=NETWORK_HANDLE --client-cid=CID
Additional useful commands:
Request module manufacturer:
qmicli --device=/dev/cdc-wdm0 --device-open-proxy --dms-get-manufacturer
Get module model:
qmicli --device=/dev/cdc-wdm0 --device-open-proxy --dms-get-model
Get firmware version:
qmicli --device=/dev/cdc-wdm0 --device-open-proxy --dms-get-revision
Get module IDs (IMEI etc.):
qmicli --device=/dev/cdc-wdm0 --device-open-proxy --dms-get-ids
Get SIM card status:
qmicli --device=/dev/cdc-wdm0 --device-open-proxy --uim-get-card-status
Recent cellular modules like Sierra Wireless EM7565 require at least libqmi V1.20. Check version with command:
If the connection was successfully set up established, you now have data connectivity. A ping to a remote server using the cellular network interface can for example prove this:
ping -I wwan0 220.127.116.11
The ifconfig Linux tool can show the current details for the network interface:
libqmi is well integrated and supported in ModemManager tool for Linux. ModemManager again is well integrated and supported when using NetworkManager tool in Linux. Please note however that these two tools expect the cellular module interfaces to only be used by them so if you manually want to use the libqmi library or AT commands interfaces, please turn off/disable ModemManager and NetworkManager first.
The libqmi is a generic open source library for Linux systems and QMI protocol from Qualcomm, therefor there are commands only working on selected devices and not necessarily supported on the device you use, resulting in an error message.
We cannot acquire an DHCP address over qmi_wwan driver when using Raspbian Linux OS?
Raspbian uses dhcpd to probe all available network interfaces found in the system, which is problematic for the qmi_wwan driver interface, if it is done before being configured properly when using cellular modules supporting only Raw-IP.
This can be avoided by setting dhcpd to deny the related cellular module network interface (most often named wwan0 by the system).
Add to the /etc/dhcpcd.conf file in Raspbian the following line (in the end):
Now, restart the system (preferably re-power it) so cellular module fully restarts also.
At next startup, the settings should be applied and you can now configure and use the qmi interface as described in some of the others faq's, found on the Techship webpage.
How can we use the Simcom SIM7000 series with ECM network interface over USB in Linux systems?
In the recent firmware releases for the Simcom SIM7000 series it is possible to take advantage of the ECM network interface type over USB in order to establish data connectivity to host system instead of using Modem/PPP protocol or QMI. This how-to FAQ shows how it can be done.
The Simcom SIM7000 series expose a set of serial and QMI/RMNET interface over USB in default configuration.
By sending command:
The USB QMI/RMNET network interface can be configured to become a ECM interface instead. If this is supported in your current firmware version the module will re-enumerate in the host system with a ECM interface.
T: Bus=03 Lev=01 Prnt=01 Port=01 Cnt=03 Dev#= 16 Spd=480 MxCh= 0
D: Ver= 2.00 Cls=ef(misc ) Sub=02 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=1e0e ProdID=9001 Rev=00.00
S: Manufacturer=SimTech, Incorporated
S: Product=SimTech SIM7000
C: #Ifs= 7 Cfg#= 1 Atr=e0 MxPwr=500mA
I: If#=0x0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
I: If#=0x1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
I: If#=0x2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
I: If#=0x3 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
I: If#=0x4 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=fe Prot=ff Driver=option
I: If#=0x5 Alt= 0 #EPs= 1 Cls=02(commc) Sub=06 Prot=00 Driver=cdc_ether
I: If#=0x6 Alt= 1 #EPs= 2 Cls=0a(data ) Sub=00 Prot=00 Driver=cdc_ether
Activate the related network interface in Linux
(check assigned interface name e.g. in dmesg output)
root@linux:~# ip link set dev enx00a0c6047450 up
Run a DHCP client on the network interface:
root@linux:~# dhclient -v enx00a0c6047450
Listening on LPF/enx00a0c6047450/00:a0:c6:04:74:50
Sending on LPF/enx00a0c6047450/00:a0:c6:04:74:50
Sending on Socket/fallback
DHCPREQUEST for 192.168.225.20 on enx00a0c6047450 to 255.255.255.255 port 67 (xid=0x301a9d68)
DHCPACK of 192.168.225.20 from 192.168.225.1 (xid=0x689d1a30)
bound to 192.168.225.20 -- renewal in 16549 seconds.
The only thing needed now is to make sure that you have defined a APN for the subscription and are registered to a cellular network.
If APN name, IP etc. is returned with AT+CGCONTRDP, you should now be able to use the ECM network interface.
root@linux:~# ping -I enx00a0c6047450 18.104.22.168
PING 22.214.171.124 (126.96.36.199) from 192.168.225.20 enx00a0c6047450: 56(84) bytes of data.
64 bytes from 188.8.131.52: icmp_seq=1 ttl=54 time=696 ms
64 bytes from 184.108.40.206: icmp_seq=2 ttl=54 time=155 ms
64 bytes from 220.127.116.11: icmp_seq=3 ttl=54 time=150 ms
64 bytes from 18.104.22.168: icmp_seq=4 ttl=54 time=151 ms
64 bytes from 22.214.171.124: icmp_seq=5 ttl=54 time=127 ms
64 bytes from 126.96.36.199: icmp_seq=6 ttl=54 time=146 ms
--- 188.8.131.52 ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 12ms
rtt min/avg/max/mdev = 127.379/237.402/695.622/205.108 ms
Tested on SIM7000G miniPCIe with firmware:
How can we activate and use dual stack IPv4 and IPv6 functionality on the Gosuncn ZTE Welink ME3630 series cellular modules in Linux?
This can be done by configuring and using the Gosuncn ZTE Welink ME3630 module in Linux the following way:
Check with AT commands that you are using the most recent firmware version on the cellular module:
ME3630E1CV1.0B19 [Jan 15 2019 16:03:19]
The module have to be switched from default USB mode in order to support this, in this mode it uses RNDIS interface and drivers instead in host.
This mode can be switched with AT commands:
The module will restart now and appear in system with the following USB IDs:
T: Bus=03 Lev=01 Prnt=01 Port=01 Cnt=03 Dev#= 9 Spd=480 MxCh= 0
D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=19d2 ProdID=0601 Rev=03.18
C: #Ifs= 5 Cfg#= 1 Atr=a0 MxPwr=500mA
I: If#=0x0 Alt= 0 #EPs= 1 Cls=e0(wlcon) Sub=01 Prot=03 Driver=rndis_host
I: If#=0x1 Alt= 0 #EPs= 2 Cls=0a(data ) Sub=00 Prot=00 Driver=rndis_host
I: If#=0x2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
I: If#=0x3 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=00 Driver=option
I: If#=0x4 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=00 Driver=option
If the option driver is not attached initially it can be done so by force loading the driver:
echo 19d2 0601 > /sys/bus/usb-serial/drivers/option1/new_id
Activate the network interface in the Linux host system (check e.g. with dmesg what system named it to):
ip link set enp0s20u2 up
Make sure you have a cellular subscription and APN that allow usage of IPV4 and IPV6 functionality combined.
Default configuration with setting a empty string lets the module subscribe for an APN from cellular network:
With defined APN:
If you have to modify/set AT+CGDCONT, please re-register in cellular network e.g. by toggling:
(Enter PIN again with AT+CPIN if necessary)
Check that you are registered in the cellular network and module are attached on packet switched network and have got an IP:
Now start the network interface data connection:
With empty string APN details in second parameter, then module try to request them from network:
Or with APN defined:
You should receive bellow if successful:
Check the status of the network interface activation, both IPV4 and IPV6 information should be listed as bellow if successful:
+ZECMCALL: IPV4, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124
+ZECMCALL: IPV6, 2a02:aa1:1018:5fc2:b532:a78c:7e20:fedb, , 2a02:aa0::55, 2a02:a6
In Linux you should now run a DHCP client on the network interface in order to acquire an IPV4 adress:
dhclient -v enp0s20u2
Listening on LPF/enp0s20u2/56:60:35:1b:9f:7f
Sending on LPF/enp0s20u2/56:60:35:1b:9f:7f
Sending on Socket/fallback
DHCPDISCOVER on enp0s20u2 to 255.255.255.255 port 67 interval 3 (xid=0x914b302a)
DHCPOFFER of 126.96.36.199 from 188.8.131.52
DHCPREQUEST for 184.108.40.206 on enp0s20u2 to 255.255.255.255 port 67 (xid=0x2a304b91)
DHCPACK of 220.127.116.11 from 18.104.22.168 (xid=0x914b302a)
bound to 22.214.171.124 -- renewal in 19393 seconds.
Try ping an IPv4 address using the module network interface:
ping -4 -I enp0s20u2 126.96.36.199
PING 188.8.131.52 (184.108.40.206) from 220.127.116.11 enp0s20u2: 56(84) bytes of data.
64 bytes from 18.104.22.168: icmp_seq=1 ttl=55 time=31.1 ms
64 bytes from 22.214.171.124: icmp_seq=2 ttl=55 time=26.8 ms
64 bytes from 126.96.36.199: icmp_seq=3 ttl=55 time=44.7 ms
--- 188.8.131.52 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 5ms
rtt min/avg/max/mdev = 26.776/34.198/44.722/7.650 ms
Try ping an IPv6 address over the module interface:
ping -6 -I enp0s20u2 2600::
PING 2600::(2600::) from 2a02:aa1:1018:5fc2:c2:afb2:2c6e:66f3 enp0s20u2: 56 data bytes
64 bytes from 2600::: icmp_seq=1 ttl=47 time=200 ms
64 bytes from 2600::: icmp_seq=2 ttl=47 time=177 ms
64 bytes from 2600::: icmp_seq=3 ttl=47 time=177 ms
64 bytes from 2600::: icmp_seq=4 ttl=47 time=176 ms
64 bytes from 2600::: icmp_seq=5 ttl=47 time=175 ms
64 bytes from 2600::: icmp_seq=6 ttl=47 time=174 ms
--- 2600:: ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 12ms
rtt min/avg/max/mdev = 174.342/180.176/200.333/9.096 ms
Please note that this functionality is not supported in all firmware versions and target regional variants of the ME3630 series yet. Here tested on the ME3630 E1C version for European target region using ME3630E1CV1.0B19
How-to use automated connection establishment with SIM7600E-h when using RNDIS USB mode
Both Windows and Linux systems can support RNDIS host drivers for the SIM7600 series modules, this example is done in Linux. There is a open source Linux in-kernel driver supporting rndis host USB endpoints called rndis_host.
By default the Simcom modules are delivered with QMI/RMNET interface enabled, so you will have to change the default USB mode with AT command on the Modem/AT serial ports available over USB.
Bus 001 Device 006: ID 1e0e:9001 Qualcomm / Option
Switch from 9001 to mode 9011 for RNDIS:
The module should restart automatically and re-enumerate with the new USB IDs
Check with lsusb that you have the Simcom SIM7600 module loaded, VID PID value: 1e0e 9011
Bus 001 Device 006: ID 1e0e:9011 Qualcomm / Option
Verify with lsusb -t that the Linux in-kernel driver rndis_host or cdc-ecm drivers are loaded correctly for interface 0 and 1.
It can look e.g. like this:
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M
|__ Port 4: Dev 6, If 3, Class=Vendor Specific Class, Driver=option, 480M
|__ Port 4: Dev 6, If 1, Class=CDC Data, Driver=rndis_host, 480M
|__ Port 4: Dev 6, If 6, Class=Vendor Specific Class, Driver=option, 480M
|__ Port 4: Dev 6, If 4, Class=Vendor Specific Class, Driver=option, 480M
|__ Port 4: Dev 6, If 2, Class=Vendor Specific Class, Driver=option, 480M
|__ Port 4: Dev 6, If 0, Class=Communications, Driver=rndis_host, 480M
|__ Port 4: Dev 6, If 5, Class=Vendor Specific Class, Driver=option, 480M
If your system don't load the option serial interfaces correctly, then they can be forcefully loaded as bellow:
echo 1e0e 9011 > /sys/bus/usb-serial/drivers/option1/new_id
See the following Linux kernel commit for details on how to modify the option.c driver in order to auto load the driver:
USB: serial: option: add support for Simcom SIM7500/SIM7600 RNDIS mode
For the modules network connection and interface to automatically activate you should have the SIM PIN deactivated or script it so host system provides it to module at every startup.
A APN name provided by the network carrier which is used to establish a packet data connection to the cellular network is required. If you define a empty string as its default value, will make the module try to subscribe for correct APN name from network, however this works in many cases but not always. If so it has to be configured with commands as bellow:
Check configured APN profiles:
You should have minimum the following defined to have module try request details from cellular network:
+CGDCONT Profile 1 is used for cellular network registration and profile 6 for the RNDIS network interface data connection.
Define both APN profiles according to the details you have obtained with your cellular subscription. Most often the APN details are same for both registration and data connection, define them to profile 1 and 6.
Some APN names require additional authentication also, please refer to the AT command: AT+CGAUTH in the AT commands guide on how to define it correctly. Current auth configurations can be checked with command:
Most often no auth details are needed for the profiles and they should be empty, profile 1 can be cleared with command:
If you have modified the APN information, username and passwords it is needed to re-attach to the packet switched network or re-register in the cellular network to activate the new settings. It can be done e.g. with AT+CFUN=0 command followed by AT+CFUN=1 to switch module operation mode (SIM card will be re-initialized also so PIN code have to be given again if PIN check activated).
The module will now establish the data connection according to the new settings.
If everything is working correctly and connection established you can now run a dhcp client on the network interface.
dhclient -v usb0
Listening on LPF/usb0/4a:de:a7:7e:46:07
Sending on LPF/usb0/4a:de:a7:7e:46:07
Sending on Socket/fallback
DHCPREQUEST of 192.168.225.46 on usb0 to 255.255.255.255 port 67 (xid=0xaabce35)
DHCPACK of 192.168.225.46 from 192.168.225.1
RTNETLINK answers: File exists
bound to 192.168.225.46 -- renewal in 21475 seconds.
ping -I usb0 184.108.40.206
PING 220.127.116.11 (18.104.22.168) from 192.168.225.46 usb0: 56(84) bytes of data.
64 bytes from 22.214.171.124: icmp_seq=1 ttl=52 time=167 ms
64 bytes from 126.96.36.199: icmp_seq=2 ttl=52 time=37.6 ms
64 bytes from 188.8.131.52: icmp_seq=3 ttl=52 time=44.4 ms
64 bytes from 184.108.40.206: icmp_seq=4 ttl=52 time=33.6 ms
--- 220.127.116.11 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 8ms
rtt min/avg/max/mdev = 33.600/70.635/166.972/55.753 ms
Tested on firmware release LE11B12SIM7600M22
What Linux kernel modules and configs are commonly used for communicating with cellular modules over their USB interface?
Most cellular modules can be supported in Linux by using som of the in-kernel drivers. The physical data interface to the host Linux system is usually done over USB which enumerates a set of different endpoints/interfaces. A set of serial interfaces for Modem/PPP, AT commands, NMEA location data and chipset debug information are almost always available in all configurations.
In addition some type of network endpoint/interface are also available and exposed. This can vary between manufacturers and chipset vendors and can also commonly be configurable by using USB configuration mode switching or through vendor specific AT commands.
Recommended kernel configurations to enable are listed bellow. Many cellular modules base their Linux support on these modules and drivers. Once included in the kernel build, the USB interfaces will be detected and bound correctly out-of-the-box or after applying source code patches to the driver modules.
Configs for USB serial drivers:
Configs for Modem/PPP support:
Configs for USB network drivers:
Please relate to the Techship product specific web pages for vendor specific Linux integration guides.
Below is a selection of kernel commits relating to cellular module support in Linux kernels:
qmi_wwan: Add support for Fibocom NL678 series
qmi_wwan: Added support for Telit LN940 series
qmi_wwan: Added support for Fibocom NL668 series
USB: serial: option: add support for GosunCn ME3630 RNDIS mode
USB: serial: option: add support for Simcom SIM7500/SIM7600 RNDIS mode
USB: serial: option: add Simcom SIM7500/SIM7600 (MBIM mode)
USB: serial: option: add Fibocom NL678 series
USB: serial: option: add Telit LN940 series
USB: serial: option: add Fibocom NL668 series
USB: serial: option: add GosunCn ZTE WeLink ME3630
qmi_wwan: apply SET_DTR quirk to the SIMCOM shared device ID
If you use any of the listed cellular modules, drivers and specified USB modes in the commits above, ensure that your kernel version already include the patch or apply it to your build.
The importance of using multiple antennas on LTE and 3G cellular modules
When designing in an LTE or 3G cellular module, using two antennas always offer the best possible signal reception and module performance. For LTE modules, usage of two antennas are mandatory if you want to take full potential in terms of signal quality and downlink data throughput.
Using just one antenna will disable the advance signal processing benefits you can achieve with MIMO antenna technology and approximately decrease downlink throughput by half on a LTE Cat-4 capable device. As we move onwards to even higher data throughputs, even more antenna channels will be required. For example, the new LTE Cat-18 Telit LM960 module need four antennas to utilize its full data throughput capabilities with 4x4 MIMO.
Although MIMO is not available on 3G modules, a second diversity antenna will allow the modules signal processors to improve the received signal quality especially in areas with poor reception. To further maximize the antenna performances and get proper isolation between the antennas, you should also preferably position them as far apart as possible and in different polarization.
A preferred alternative is to use a combined antenna instead of including several antenna elements. These antennas can combine different MIMO/diversity configurations with other RF elements, e.g. GNSS and Wi-Fi and are also available in different forms and mounting options.
Having everything combined in a single antenna unit also eases the installation and decreases the mounting space as well as passthrough holes required, essential for example when installed on a vehicle roof.
Our cellular module, Huawei ME909s series miniPCIe, is not detected in the MikroTik RouterBoard embedded board running RouterOs, what can we do?
Many host systems running e.g. operating systems like Linux have a very short detection time for peripheral USB devices on the internal miniPCIe sockets before the host system continues to load.
This can result in the cellular module not being detected at all in the host system due to the cellular modules internal boot-up procedure have not yet finished. The D+ signal will be pulled high first after the modules internal boot-up process have completed and then signal its device presence on the USB interface to host system.
When you intend to use a cellular module in these systems and the cellular module cannot be detected, please try to add in a delay to the host systems boot-up procedure in the earliest possible stage, this to allow the cellular module to boot-up correctly first and show its presence to host system before it have passed the peripheral devices detection phase.
The boot-up times for the cellular module can commonly be found in the products hardware guide.
For Huawei ME909s series it is approximately 9 seconds.
For example in Mikrotik RouterOS, this often can be the reason for the cellular module not being detected. Then you can try to adjusting the "boot-delay" parameter from its default 1 second.
Please refer to the RouterOS Wiki for further details on boot-up delays and other useful parameters.
How to collect initial diagnostics data and logs for Simcom SIM7000 series cellular modules, needed when requesting Techship technical support?
In order to troubleshoot and solve a technical problem, we ask you to please provide information about your system and logs from the related Simcom module when creating a technical support ticket.
Problem description of what exact problem is and in what precise situations present.
Describe the host system:
-Hardware (system board, peripherals...)
-Operating system and detailed versions (E.g. Windows, Linux release, kernel...)
-Drivers and driver versions
Identify the precise details of cellular module found on label:
-SKU/BOM or P/N code
(For RMA returns the IMEI number is mandatory)
If you are running on a Linux based system, please capture the terminal logs bellow:
ls -l /dev/serial/by-id
ls -l /sys/bus/usb-serial/devices
The logs from the cellular module firmware can be acquired by accessing the USB enumerated serial (COM) interfaces accepting AT commands. They can be named modem, AT, PC UI etc. (In Windows device manager, found under modem or serial interfaces). Send the following AT commands bellow to module and capture the output and include them when creating the the technical support ticket.
Test that you get a reply with command:
Command echo enabled:
Basic module info:
Detailed module version info:
Verbose error reporting:
Get mobile operation band:
Preferred band selection:
Show network system mode:
Preferred order CAT-M and NB-IoT:
Preferred network mode:
List network operator info:
Network registration status:
Network GPRS registration status:
Network EPS registration status:
Request UE system info:
Packet domain attach status
List APN details/PDP profiles:
PDP profiles attach status:
Show PDP IP address:
RM network interface status:
Power Saving Mode Setting:
Get Network APN in CAT-M or NB-IOT:
Service Domain Preference:
LTE Cat-M cell lock configuration:
LTE NB-IOT cell lock configuration:
NB-IOT Scrambling Feature config:
APN configuration mode:
Query RRC State:
CAT-M and NB-IOT band config:
Module crash reset status:
NB-IOT band scan optimization config:
Service Domain Preference For NB-IOT:
The support ticket can be created after login at: https://techship.com/technical_support/
How do we integrate SparkLan devices using Mediatek MT7612U chipset in Linux systems?
The Mediatek MT7612U chipset can be supported by the Linux in-kernels wireless drivers starting from kernel version 4.19.
(For older kernels please relate to driver source downloadable package "Sparklan Linux Drivers 18.104.22.168 v4" linked in the FAQ attached files section)
Usage of in-kernel driver in Linux kernel 4.19 and later:
Plug in the device and check if the correct Linux driver module is loaded correctly for the wifi module by command lsusb and lsusb -t as bellow:
Bus 002 Device 005: ID 0e8d:7612 MediaTek Inc.
|__ Port 3: Dev 5, If 0, Class=Vendor Specific Class, Driver=mt76x2u, 5000M
If the "Driver=mt76x2u" is not shown the driver module fails to load correctly for the wifi module, please check with command dmesg if the device has been detected at all and if the firmware file have failed to load:
usb 2-3: USB disconnect, device number 2
usb 1-3: new high-speed USB device number 2 using xhci_hcd
usb 2-3: new SuperSpeed Gen 1 USB device number 3 using xhci_hcd
usb 2-3: New USB device found, idVendor=0e8d, idProduct=7612, bcdDevice= 1.00
usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 2-3: Product: 802.11ac WLAN
usb 2-3: Manufacturer: MediaTek Inc.
usb 2-3: SerialNumber: 000000000
usb 2-3: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
mt76x2u 2-3:1.0: ASIC revision: 76120044
mt76x2u 2-3:1.0: Direct firmware load for mediatek/mt7662u_rom_patch.bin failed with error -2
mt76x2u: probe of 2-3:1.0 failed with error -2
If that is the case, make sure to download the latest firmware files bellow from https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/mediatek and place the firmware files in the directory:
Once in place, reboot the system or replug the USB device and the the correct driver should be loaded for the module.
What firmware versions are related to the specific SKU/BOM codes of cellular modules?
10839 Sierra Wireless EM7565, CAT-12, M.2 CBRS ENABLED
SKU: 1104207 Firmware: 01.07.02.00 GENERIC
10692 Sierra Wireless EM7565 LTE CAT-12 M.2
SKU: 1103520 Firmware: 01.07.02.00 GENERIC
10375 Sierra Wireless EM7455 LTE Cat 6
SKU: 1103582 Firmware: 02.24.05.06 GENERIC/AT&T/SPRINT/VERIZON
SKU: 1103780 Firmware: 02.24.05.06 GENERIC/AT&T/SPRINT/VERIZON
10427 Sierra Wireless EM7430
SKU: 1103733 Firmware: 02.24.05.06 GENERIC/DOCOMO/KDDI/SOFTBANK/TELSTRA
10374 Sierra Wireless MC7455 LTE Cat 6
SKU: 1103789 Firmware: 02.24.05.06 GENERIC/AT&T/BELL/ROGERS/SPRINT/TELUS/US CELLULAR/VERIZON/VODAFONE
10397 Sierra Wireless MC7430 mPCIe
SKU: 1103737 Firmware: 02.24.05.06 GENERIC/DOCOMO/KDDI/SOFTBANK/TELSTRA
10840 Sierra Wireless EM7511
SKU: 1103989 Firmware: 01.07.02.00 AT&T/GENERIC
10278 Huawei ME909s-120 mPCIe:
SKU: 55010273 Firmware: 11.617.01.00.00
SKU: 55010782 Firmware: 11.617.09.00.00
SKU: 55010946 Firmware: 11.617.14.00.00
SKU: 55010983 Firmware: 11.617.15.00.00
10279 Huawei ME909s-120 LGA EU:
SKU: 55010781 Firmware: 11.617.09.00.00
SKU: 55010782 Firmware: 11.617.15.00.00
10689 SIMCom SIM7600E-H LTE SMT EU
SKU: S2-107EQ-Z1W27 Firmware: LE11 B07 SIM7600M22
SKU: S2-107EQ-Z1W2L Firmware: LE11 B08 SIM7600M22
SKU: S2-107EQ-Z1W3S Firmware: LE11 B09 SIM7600M22
SKU: S2-107EQ-Z1W4J Firmware: LE11 B10 SIM7600M22
SKU: S2-107EQ-Z1W51 Firmware: LE11 B11 SIM7600M22
10690 SIMCom SIM7600E-H LTE mPCIe EU
SKU: S2-107ER-Z1W2L Firmware: LE11 B07 SIM7600M22
SKU: S2-107ER-Z1W2L Firmware: LE11 B08 SIM7600M22
SKU: S2-107ER-Z1W3S Firmware: LE11 B09 SIM7600M22
SKU: S2-107ER-Z1W4J Firmware: LE11 B10 SIM7600M22
SKU: S2-107ES-Z1W51 Firmware: LE11 B11 SIM7600M22
10818 SIMCom SIM7600E-H LTE CAT 4 -mPCIE with Audio
SKU: S2-107ES-Z1W27 Firmware: Firmware: LE11B07SIM7600M22
SKU: S2-107ES-Z1W2L Firmware: LE11B08SIM7600M22
SKU: S2-107ES-Z1W3S Firmware: LE11B09SIM7600M22
SKU: S2-107ES-Z1W4J Firmware: LE11B10SIM7600M22
SKU: S2-107ES-Z1W51 Firmware: LE11B11SIM7600M22
10710 SIMCom SIM7600E-H LTE CAT-4 mPCIe SIM
SKU: S2-107Q0-Z1W27 Firmware: LE11 B07 SIM7600M22
SKU: S2-107Q0-Z1W2L Firmware: LE11 B08 SIM7600M22
SKU: S2-107Q0-Z1W3S Firmware: LE11 B09 SIM7600M22
SKU: S2-107Q0-Z1W4J Firmware: LE11 B10 SIM7600M22
SKU: S2-107Q0-Z1W51 Firmware: LE11 B11 SIM7600M22
SIM7600SA-H SMT type
SKU: S2-107BH-Z1W27 Firmware: LE11 B07 SIM7600M22
SKU: S2-107BH-Z1W2L Firmware: LE11 B08 SIM7600M22
SKU: S2-107BH-Z1W3S Firmware: LE11 B09 SIM7600M22
SKU: S2-107BH-Z1W4J Firmware: LE11 B10 SIM7600M22
SKU: S2-107BH-Z1W51 Firmware: LE11 B11 SIM7600M22
10757 SIMCom SIM7600SA-H LTE CAT-4 mPCIe
SKU: S2-107KX-Z1W27 Firmware: LE11 B07 SIM7600M22
SKU: S2-107KX-Z1W2L Firmware: LE11 B08 SIM7600M22
SKU: S2-107KX-Z1W3S Firmware: LE11 B09 SIM7600M22
SKU: S2-107KX-Z1W4J Firmware: LE11 B10 SIM7600M22
SKU: S2-107KX-Z1W51 Firmware: LE11 B11 SIM7600M22
SIM7600SA-H LTE CAT 4 -mPCIE with Audio
SKU: S2-107KY-Z1W27 Firmware: LE11 B07 SIM7600M22
SKU: S2-107KY-Z1W2L Firmware: LE11 B08 SIM7600M22
SKU: S2-107KY-Z1W3S Firmware: LE11 B09 SIM7600M22
SKU: S2-107KY-Z1W4J Firmware: LE11 B10 SIM7600M22
SKU: S2-107KY-Z1W51 Firmware: LE11 B11 SIM7600M22
10810 SIMCom SIM7600SA-H LTE CAT-4 mPCIe with SIM holder
SKU: S2-107QZ-Z1W2L Firmware: LE11 B08 SIM7600M22
SKU: S2-107QZ-Z1W3S Firmware: LE11 B09 SIM7600M22
SKU: S2-107QZ-Z1W4J Firmware: LE11 B10 SIM7600M22
SKU: S2-107QZ-Z1W51 Firmware: LE11 B11 SIM7600M22
SIM7600E SMT type
SKU: S2-107EP-Z1W2P Firmware: LE11 B01 SIM7600M21-A
SKU: S2-107EP-Z1W4D Firmware: LE11 B02 SIM7600M21-A
10812 SIMCom SIM7600E CAT-1 mPCIe
SKU: S2-107ET-Z1W2P Firmware: LE11 B01 SIM7600M21-A
SKU: S2-107ET-Z1W4D Firmware: LE11 B02 SIM7600M21-A
SIM7600E LTE CAT 1 -mPCIE with Audio
SKU: S2-107EV-Z1W2P Firmware: LE11 B01 SIM7600M21-A
SKU: S2-107EV-Z1W4D Firmware: LE11 B02 SIM7600M21-A
10813 SIMCom SIM7600SA LTE CAT-1 mPCIe
SKU: S2-107KV-Z1W2P Firmware: LE11 B01 SIM7600M21-A
SKU: S2-107KV-Z1W4D Firmware: LE11 B02 SIM7600M21-A
SIM7600SA SMT type
SKU: S2-107BG-Z1W2P Firmware: LE11 B01 SIM7600M21-A
SKU: S2-107BG-Z1W4D Firmware: LE11 B02 SIM7600M21-A
SIM7600SA LTE CAT 1 -mPCIE with Audio
SKU: S2-107KW-Z1W2P Firmware: LE11 B01 SIM7600M21-A
SKU: S2-107KW-Z1W4D Firmware: LE11 B02 SIM7600M21-A
10305 SimCom SIM7100 LTE mPCIe US
SKU: S2-106EW-Z1L7X Firmware: 4534B03SIM7100A
SKU: S2-106EW-Z1L72 Firmware: 4534B03SIM7100A