Hi,
I want to enable QMAP on WP76XX. But I am blocked by making a data connection in Linux platform, no matter on Ubuntu 16.04 or Pi(4.19.66-v7+).And Gobi driver is S2.42N2.64.
QMAP is enabled by AT!NETNUM command.
gobi-0-0 and gobi-0-1 are enumerated.
But I can’t make a data connection successfully by AT!SCACT command or ‘dhclient gobi-0-0’.
Anyone can help on this?
can you paste the dmesg ?
What is the return of the following?
AT!GSTATUS?
AT+CGDCONT?
AT!SCACT=1,1
Hi Jyijyi，
Please see check results.
ATI3
Manufacturer: Sierra Wireless, Incorporated
Model: WP7607-2
Revision: SWI9X07Y_02.37.03.00 73df45 jenkins 2020/04/08 10:59:14
IMEI: 359781080000252
IMEI SV: 14
FSN: VQ738570011002
+GCAP: +CGSM
OK
ATI8
Legato Ver: 19.11.1_b573da4376cbd9a3e348ac6432151b7e
Yocto Ver: SWI9X07Y_02.37.03.00 2020-04-08_13:07:02
OS Ver: Linux version 3.18.140 (oe-user@oe-host) (gcc version 7.3.0 (GCC) ) #1 PREEMPT Wed Apr 8 12:26:41 UTC 2020
LK Ver: SWI9X07Y_02.37.03.00
RootFS Ver: SWI9X07Y_02.37.03.00 2020-04-08_13:07:02
UserFS Ver: unknown
MCU Ver: unknown
OK
AT!GSTATUS?
!GSTATUS:
Current Time: 9478 Temperature: 26
Modem Mitigate Level: 0 ModemProc Mitigate Level: 0
Reset Counter: 3 Mode: ONLINE
System mode: LTE PS state: Attached
IMS reg state: UNKNOWN IMS mode: Not Support
IMS Srv State: UNKNOWN SMS,UNKNOWN VoIP
LTE band: B3 LTE bw: 20 MHz
LTE Rx chan: 1850 LTE Tx chan: 19850
LTE CA state: INACTIVE
EMM state: Registered Normal Service
RRC state: RRC Idle
PCC RxM RSSI: -55 RSRP (dBm): -89
PCC RxD RSSI: -82 RSRP (dBm): -119
Tx Power: – TAC: 7721 (30497)
RSRQ (dB): -13 Cell ID: 077F5F35 (125787957)
SINR (dB): -2.6
OK
AT+CGDCONT?
+CGDCONT: 1,“IP”,“internet”,“0.0.0.0”,0,0,0,0
+CGDCONT: 2,“IP”,“ims”,“0.0.0.0”,0,0,0,0
+CGDCONT: 3,“IPV4V6”,“3gnet”,“0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0”,0,0,0,0
OK
AT+CGPADDR
+CGPADDR: 1,10.167.56.93
+CGPADDR: 2,0.0.0.0
+CGPADDR: 3,0.0.0.0,0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0
OK
AT+COPS?
+COPS: 0,0,"",7
OK
AT!SCACT=1,1
OK
AT!SCACT?
!SCACT: 1,1
!SCACT: 2,0
!SCACT: 3,0
OK
After AT!SCACT=1,1, the network flag in my Pi would show “eth1: Link is up, configuring”
BTW, it works well in Windows host with AT!SCACT command.
I think there is no problem on module side.
can you paste the dmesg of ubuntu?
Sure. Please see it below:
[ 2.883484] usb 1-1.4: new full-speed USB device number 6 using dwc_otg
[ 2.973638] systemd-journald[105]: Received request to flush runtime journal from PID 1
[ 3.082004] usb 1-1.4: new high-speed USB device number 7 using dwc_otg
[ 3.217643] usb 1-1.4: config 1 has an invalid interface number: 8 but max is 3
[ 3.217662] usb 1-1.4: config 1 has no interface number 1
[ 3.225649] usb 1-1.4: New USB device found, idVendor=1199, idProduct=68c0, bcdDevice= 3.18
[ 3.225669] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3.225679] usb 1-1.4: Product: Sierra Wireless WP7607-2
[ 3.225688] usb 1-1.4: Manufacturer: Sierra Wireless, Incorporated
[ 3.225698] usb 1-1.4: SerialNumber: VQ73857001100216
[ 3.426149] GobiNet: loading out-of-tree module taints kernel.
[ 3.452825] GobiNet: 2020-08-17/SWI_2.64
[ 3.459804] GobiNet 1-1.4:1.8 eth1: register ‘GobiNet’ at usb-3f980000.usb-1.4, GobiNet Ethernet Device, b6:be:e3:7c:ad:08
[ 3.460060] QMAP Enabled
[ 3.464510] USB Speed : USB 2.0
[ 3.464790] usbcore: registered new interface driver GobiNet
[ 3.478516] usbcore: registered new interface driver usbserial_generic
[ 3.478590] usbserial: USB Serial support registered for generic
[ 3.490221] usbcore: registered new interface driver GobiSerial
[ 3.490303] usbserial: USB Serial support registered for GobiSerial
[ 3.492165] GobiSerial 1-1.4:1.0: GobiSerial converter detected
[ 3.492650] usb 1-1.4: GobiSerial converter now attached to ttyUSB0
[ 3.493733] GobiSerial 1-1.4:1.2: GobiSerial converter detected
[ 3.494263] usb 1-1.4: GobiSerial converter now attached to ttyUSB1
[ 3.496069] GobiSerial 1-1.4:1.3: GobiSerial converter detected
[ 3.496554] usb 1-1.4: GobiSerial converter now attached to ttyUSB2
[ 3.496743] GobiSerial: 2020-08-17/SWI_2.42:GobiSerial
[ 3.840184] snd_bcm2835: module is from the staging directory, the quality is unknown, you have been warned.
[ 3.842519] vc_sm_cma: module is from the staging directory, the quality is unknown, you have been warned.
[ 3.846437] bcm2835_vc_sm_cma_probe: Videocore shared memory driver
[ 3.846460] [vc_sm_connected_init]: start
[ 3.858213] [vc_sm_connected_init]: installed successfully
[ 3.865069] bcm2835_audio soc:audio: card created with 8 channels
[ 3.866752] media: Linux media interface: v0.10
[ 4.007375] videodev: Linux video capture interface: v2.00
[ 4.011127] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[ 4.045855] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned.
[ 4.046743] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned.
[ 4.061071] bcm2835_v4l2: module is from the staging directory, the quality is unknown, you have been warned.
[ 4.093309] bcm2835_codec: module is from the staging directory, the quality is unknown, you have been warned.
[ 4.110035] bcm2835-codec bcm2835-codec: Device registered as /dev/video10
[ 4.118054] cfg80211: Loaded X.509 cert ‘sforshee: 00b28ddf47aef9cea7’
[ 4.118683] bcm2835-codec bcm2835-codec: Loaded V4L2 decode
[ 4.125888] bcm2835-codec bcm2835-codec: Device registered as /dev/video11
[ 4.125907] bcm2835-codec bcm2835-codec: Loaded V4L2 encode
[ 4.137454] bcm2835-codec bcm2835-codec: Device registered as /dev/video12
[ 4.137471] bcm2835-codec bcm2835-codec: Loaded V4L2 isp
[ 4.210816] brcmfmac: F1 signature read @0x18000000=0x1541a9a6
[ 4.217012] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1
[ 4.217324] usbcore: registered new interface driver brcmfmac
[ 4.440250] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1
[ 4.440375] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available
[ 4.441078] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43430/1 wl0: Oct 23 2017 03:55:53 version 7.45.98.38 (r674442 CY) FWID 01-e58d219f
[ 5.330158] uart-pl011 3f201000.serial: no DMA platform data
[ 6.054448] smsc95xx 1-1.1:1.0 eth0: hardware isn’t capable of remote wakeup
[ 6.054939] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 6.915598] Adding 102396k swap on /var/swap. Priority:-2 extents:1 across:102396k SSFS
[ 7.730277] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 7.731511] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xC1E1
[ 9.883721] Bluetooth: Core ver 2.22
[ 9.883825] NET: Registered protocol family 31
[ 9.883833] Bluetooth: HCI device and connection manager initialized
[ 9.883858] Bluetooth: HCI socket layer initialized
[ 9.883872] Bluetooth: L2CAP socket layer initialized
[ 9.883914] Bluetooth: SCO socket layer initialized
[ 9.908634] Bluetooth: HCI UART driver ver 2.3
[ 9.908652] Bluetooth: HCI UART protocol H4 registered
[ 9.908748] Bluetooth: HCI UART protocol Three-wire (H5) registered
[ 9.908968] Bluetooth: HCI UART protocol Broadcom registered
[ 10.252028] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 10.252037] Bluetooth: BNEP filters: protocol multicast
[ 10.252057] Bluetooth: BNEP socket layer initialized
[ 10.319908] Bluetooth: RFCOMM TTY layer initialized
[ 10.319942] Bluetooth: RFCOMM socket layer initialized
[ 10.319967] Bluetooth: RFCOMM ver 1.11
[ 11.779685] fuse init (API version 7.27)
[ 17.681938] creating qcqmi0
[ 17.827067] RawIP mode
[ 62.984462] random: crng init done
[ 62.984480] random: 7 urandom warning(s) missed due to ratelimiting
[ 319.220977] usbcore: deregistering interface driver GobiNet
[ 319.878708] GobiNet 1-1.4:1.8 eth1: unregister ‘GobiNet’ usb-3f980000.usb-1.4, GobiNet Ethernet Device
[ 356.071037] GobiNet: 2020-08-17/SWI_2.64
[ 356.076636] GobiNet 1-1.4:1.8 eth1: register ‘GobiNet’ at usb-3f980000.usb-1.4, GobiNet Ethernet Device, b6:be:e3:7c:ad:08
[ 356.078732] QMAP Enabled
[ 356.085775] USB Speed : USB 2.0
[ 356.086058] usbcore: registered new interface driver GobiNet
[ 370.273659] creating qcqmi0
[ 370.438766] RawIP mode
It seems to be ok, i can see /dev/qcqmi0 port and eth1 imterface, and the serial port /dev/ttyUSB
What happens when you type at!scact=1,1 ?
Did you type “sudo dhclient eth1” on ubuntu?
Yes, I did.
But it would take about half a minute to complete. No errors or warnings.
No IP address would be found in eth1. And after about 2 minutes, AT!SCACT? would return ‘0,1’
How about using profile id 2 (changing apn to internet) ? Is it the same case?
Also you need to shut down firewall of wp76 module by
iptables -I INPUT -j ACCEPT
Same situation for profile 2.
I try to do it refer to your tips, still failed.
I don’t see problem on FW R13.3, maybe you can give a try:
[ 31.893645] usb 3-2.1: Product: Sierra Wireless WP7605
[ 31.893646] usb 3-2.1: Manufacturer: Sierra Wireless, Incorporated
[ 31.893647] usb 3-2.1: SerialNumber: 2A91728507040403
[ 32.110089] GobiNet: loading out-of-tree module taints kernel.
[ 32.110154] GobiNet: module verification failed: signature and/or required key missing - tainting kernel
[ 32.142825] GobiNet: 2018-03-22/SWI_2.51
[ 32.142884] QMAP Disabled
[ 32.151310] GobiNet 3-2.1:1.8 eth0: register ‘GobiNet’ at usb-0000:03:00.0-2.1, GobiNet Ethernet Device, 36:dd:7e:ff:24:d7
[ 32.172837] USB Speed : USB 2.0
[ 32.174030] usbcore: registered new interface driver GobiNet
[ 32.202296] usbcore: registered new interface driver usbserial
[ 32.204503] usbcore: registered new interface driver usbserial_generic
[ 32.204591] usbserial: USB Serial support registered for generic
[ 32.206290] cdc_ether 3-2.1:1.19 usb0: register ‘cdc_ether’ at usb-0000:03:00.0-2.1, CDC Ethernet Device, 16:92:dd:cc:0e:a8
[ 32.221472] usbcore: registered new interface driver cdc_ether
[ 32.232679] usbcore: registered new interface driver GobiSerial
[ 32.232689] usbserial: USB Serial support registered for GobiSerial
[ 32.236727] GobiSerial 3-2.1:1.0: GobiSerial converter detected
[ 32.236832] usb 3-2.1: GobiSerial converter now attached to ttyUSB0
[ 32.237620] GobiSerial 3-2.1:1.2: GobiSerial converter detected
[ 32.241739] usb 3-2.1: GobiSerial converter now attached to ttyUSB1
[ 32.260773] GobiSerial 3-2.1:1.3: GobiSerial converter detected
[ 32.260849] usb 3-2.1: GobiSerial converter now attached to ttyUSB2
[ 32.261319] GobiSerial: 2018-04-25/SWI_2.32:GobiSerial
[ 32.350904] cdc_ether 3-2.1:1.19 ens160u2u1i19: renamed from usb0
[ 32.365020] GobiNet 3-2.1:1.8 ens160u2u1i8: renamed from eth0
[ 32.491089] IPv6: ADDRCONF(NETDEV_UP): ens160u2u1i8: link is not ready
[ 32.491185] GobiNet 3-2.1:1.8 ens160u2u1i8: kevent 12 may have been dropped
[ 32.491189] IPv6: ADDRCONF(NETDEV_UP): ens160u2u1i8: link is not ready
[ 32.523591] IPv6: ADDRCONF(NETDEV_UP): ens160u2u1i19: link is not ready
[ 32.527316] IPv6: ADDRCONF(NETDEV_UP): ens160u2u1i19: link is not ready
[ 32.528611] IPv6: ADDRCONF(NETDEV_CHANGE): ens160u2u1i19: link becomes ready
[ 32.528617] cdc_ether 3-2.1:1.19 ens160u2u1i19: kevent 12 may have been dropped
[ 32.963468] rfkill: input handler disabled
[ 33.824955] cdc_ether 3-2.1:1.19 ens160u2u1i19: kevent 12 may have been dropped
[ 35.925381] cdc_ether 3-2.1:1.19 ens160u2u1i19: kevent 12 may have been dropped
[ 38.624112] creating qcqmi0
[ 38.624172] RawIP mode
owner@ubuntu:~ sudo dhclient ens160u2u1i8
owner@ubuntu:~ ifconfig ens160u2u1i8
ens160u2u1i8: flags=4291<UP,BROADCAST,RUNNING,NOARP,MULTICAST> mtu 1500
inet 10.104.161.217 netmask 255.255.255.252 broadcast 10.104.161.219
inet6 fe80::6da8:4306:4f87:c21d prefixlen 64 scopeid 0x20
ether 7e:3f:69:b0:de:d6 txqueuelen 1000 (Ethernet)
RX packets 56 bytes 14251 (14.2 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 187 bytes 19236 (19.2 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
owner@ubuntu:~$ ping www.google.com
PING www.google.com (216.58.221.228) 56(84) bytes of data.
64 bytes from hkg07s21-in-f228.1e100.net (216.58.221.228): icmp_seq=1 ttl=117 time=26.0 ms
64 bytes from hkg07s21-in-f228.1e100.net (216.58.221.228): icmp_seq=2 ttl=117 time=45.2 ms
^C
— www.google.com ping statistics —
2 packets transmitted, 2 received, 0% packet loss, time 1002ms
rtt min/avg/max/mdev = 26.022/35.640/45.259/9.620 ms
ati3
Manufacturer: Sierra Wireless, Incorporated
Model: WP7605
Revision: SWI9X07Y_02.28.03.05 000000 jenkins 2019/07/08 11:04:16
IMEI: 353532100020465
IMEI SV: 6
FSN: 2A917285070404
+GCAP: +CGSM
OK
at+Cgdcont?
+CGDCONT: 1,“IP”,“hkcsl”,“0.0.0.0”,0,0,0,0
+CGDCONT: 2,“IP”,“hkcsl”,“0.0.0.0”,0,0,0,0
OK
at!gstatus?
!GSTATUS:
Current Time: 104 Temperature: 28
Modem Mitigate Level: 0 ModemProc Mitigate Level: 0
Reset Counter: 1 Mode: ONLINE
System mode: LTE PS state: Attached
IMS reg state: UNKNOWN IMS mode: Not Support
IMS Srv State: UNKNOWN SMS,UNKNOWN VoIP
LTE band: B3 LTE bw: 10 MHz
LTE Rx chan: 1851 LTE Tx chan: 19851
LTE CA state: INACTIVE
EMM state: Registered Normal Service
RRC state: RRC Idle
PCC RxM RSSI: -59 RSRP (dBm): -86
PCC RxD RSSI: -96 RSRP (dBm): -131
Tx Power: 0 TAC: 0652 (1618)
RSRQ (dB): -10 Cell ID: 01A1560B (27350539)
SINR (dB): 8.2
OK
at!scact=1,1
OK
at!scact?
!SCACT: 1,1
!SCACT: 2,0
OK
at+Cgpaddr
+CGPADDR: 1,10.104.161.217
+CGPADDR: 2,0.0.0.0
OK
Hi ,
In your last comment, QMAP is disabled. Could you enable it and try again?
In QMAP disable mode, I also can make a data connection by AT command directly. But once QMAP is enabled, the rmnet port would change from enp0s20f0u2i8 to eth0,gobi-0-0,gobi-0-1. Then the dhclient would have a problem.
If you use AT!SCACT=1,1 to establish the data connection, you need to set AT!NETNUM to 0.
If you need to enable QMAP, you can try QMI SDK.
There is no way on QMAP mode with AT commands? Could you make a confirmation on this?
Didn’t you already confirm?
Have you tried qmi sdk?
I remember i always set at!netnum to zero in case for at!scact
I am not sure if AT commands could set up the data connection under QMAP mode.
So I need your confirmation about this.
Anyway, I will try use QMI sdk later.
I remember i always need to set at!netnum to zero in case for at!scact
You can try QMI SDK.
If set AT!NETNUM to 0, then QMAP is disabled. That’s not what I want
why do you need to enable QMAP?
We want to set up multiple PDN data connection. As far as I know, QMAP need to be enabled and use virtual rmnet. Normally we only support 1 rmnet. And please see AirPrime - Multiple PDN Support on Newer Sierra Wireless Modules. It said WP76XX support this feature.