Changes between Version 136 and Version 137 of wireless/modem

Timestamp:

11/20/2025 08:09:30 PM (45 hours ago)

Author:

Ryan Erbstoesser

Comment:

add fn920 info

wireless/modem

@@ -9 +9 @@
 M2M Cellular modems allow embedded systems to communicate and connect to the network in places that may not have other standard connections such as !WiFi or Ethernet. Embedded systems are being deployed in more remote locations that still require and mandate an internet connection. Gateworks boards have Mini-PCI-Express slots that allow for a wide range of cellular modems to be connected.
 
-This wiki page is created for use on [https://www.gateworks.com/products/ Gateworks Rugged and Industrial Single Board Computers] Made in the USA.
+This wiki page is created for use on [https://www.gateworks.com/products/ Gateworks Rugged and Industrial Single Board Computers] Made infn the USA.
 
 You will find below examples and setup instructions for many devices Gateworks has qualified.
@@ -2108 +2108 @@
 Confirm the interface is up with an IP with the ifconfig command.
 
+== Telit FN920 PCIe Mode
+
+The Telit FN920C04 supports PCIe, which is new for modems. PCIe is valuable for faster bus speeds compared to USB. This requires a new MHI driver only in latest kernels (6.12+) available on Venice SBCs. Contact Gateworks support for other board families.  
+
+Requirements:
+ * M.2 Slot on Venice GW7400 / GW82xx / Catalina GW9xxx / or M.2 Adapter
+ * Latest 6.12 kernel or newer from Gateworks
+ * Pull pin 20 low to enable PCIe mode (via adapter or GPIO)
+
+Kernel Requirements:
+{{{
+MHI_BUS
+MHI_BUS_PCI_GENERIC
+MHI_NET
+RMNET
+WWAN
+WWAN_CORE
+MHI_WWAN_CTRL
+}}}
+
+These can be found on a live running system with the following example:
+{{{
+root@noble-venice:~# zcat /proc/config.gz | grep MHI
+CONFIG_QRTR_MHI=m
+CONFIG_MHI_BUS=m
+# CONFIG_MHI_BUS_DEBUG is not set
+CONFIG_MHI_BUS_PCI_GENERIC=m
+# CONFIG_MHI_BUS_EP is not set
+CONFIG_MHI_NET=m
+CONFIG_MHI_WWAN_CTRL=m
+CONFIG_MHI_WWAN_MBIM=m
+}}}
+
+Check if modem shows up on PCI bus with a lspci:
+{{{
+root@noble-venice:~# lspci
+03:00.0 Unassigned class [ff00]: Qualcomm Technologies, Inc Device 011a
+}}}
+
+Confirm the mhi_hwip0 interface is seen in /sys/class/net and there are wwan0 devices:
+{{{
+root@noble-venice:~# ls /sys/class/net/
+can0  can1  eth0  eth1  lan1  lan2  lan3  lan4  lan5  lo  mhi_hwip0
+
+root@noble-venice:~# ls /dev/wwan0*
+/dev/wwan0at0  /dev/wwan0at1  /dev/wwan0qcdm0  /dev/wwan0qmi0
+}
+}}
+
+Create a file /etc/qmi-network.conf and enter in the APN:
+{{{
+root@noble-venice:~# cat /etc/qmi-network.conf 
+    APN=HOLOGRAM 
+    APN_USER=
+    APN_PASS=
+    PROXY=yes
+}}}
+
+Now connect to network (example with Hologram sim) 
+{{{
+root@noble-venice:~# qmi-network /dev/wwan0qmi0 start
+Loading profile at /etc/qmi-network.conf...
+    APN: HOLOGRAM
+    APN user: unset
+    APN password: unset
+    qmi-proxy: yes
+    IP_TYPE: unset
+    PROFILE: unset
+Checking data format with 'qmicli -d /dev/wwan0qmi0 --wda-get-data-format --device-open-proxy'...
+Device link layer protocol retrieved: raw-ip
+Getting expected data format with 'qmicli -d /dev/wwan0qmi0 --get-expected-data-format'...
+error: cannot get expected data format: Setting expected data format management is unsupported by the driver
+Expected link layer protocol not retrieved: kernel unsupported
+Updating device link layer protocol with 'qmicli -d /dev/wwan0qmi0 --wda-set-data-format=802-3 --device-open-proxy'...
+New device link layer protocol retrieved: raw-ip
+Starting network with 'qmicli -d /dev/wwan0qmi0 --wds-start-network=apn='HOLOGRAM'  --client-no-release-cid --device-open-proxy'...
+Saving state at /tmp/qmi-network-state-wwan0qmi0... (CID: 14)
+Saving state at /tmp/qmi-network-state-wwan0qmi0... (PDH: 3767202208)
+Network started successfully
+}}}
+
+Get IP address for modem interface mhi_hwip0:
+{{{
+root@noble-venice:~# qmicli -d /dev/wwan0qmi0 --wds-get-current-settings
+[/dev/wwan0qmi0] Current settings retrieved:
+           IP Family: IPv4
+        IPv4 address: 10.200.181.105
+    IPv4 subnet mask: 255.255.255.252
+IPv4 gateway address: 10.200.181.106
+    IPv4 primary DNS: 8.8.8.8
+  IPv4 secondary DNS: 8.8.4.4
+                 MTU: 1500
+             Domains: none
+
+}}}
+
+Manually bring up mhi_hwip0 and assign it the IP from above:
+{{{
+root@noble-venice:~# ifconfig mhi_hwip0 up
+root@noble-venice:~# ifconfig mhi_hwip0 10.200.181.105 netmask 255.255.255.252
+root@noble-venice:~# route add default gw 10.200.181.106 mhi_hwip0
+root@noble-venice:~# echo "nameserver 8.8.8.8" > /etc/resolv.conf
+root@noble-venice:~# echo "nameserver 8.8.4.4" >> /etc/resolv.conf
+root@noble-venice:~# ping www.google.com
+}}}
+
+=== Troubleshooting
+ * Be sure the modem PCIe ID is included the the MHI PCIe driver (kernel commit by Telit in 6.16 kernel [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/bus/mhi/host/pci_generic.c?id=6348f62ef7ecc5855b710a7d4ea682425c38bb80 here])
+ * Be sure pin 20 is pulled low for Mini-PCIe mode
+ * Be sure all MHI related drivers are turned on in the kernel
+{{{
+root@noble-venice:~# dmesg | grep elit
+[    6.426205] mhi-pci-generic 0000:03:00.0: MHI PCI device found: telit-fn920c04
+[   25.232512] usb 1-1.1: Manufacturer: Telit Cinterion
+
+}}}
+
+
+
 [=#gateworksgw16162]
 == Gateworks GW16162 / Telit CMB100