No connection via wwan interface, QMUXError = 0x5e

relu · September 12, 2023, 11:40am

I am trying connect the BG95-M3 Modul to the internet. For this I patched the qmi_wwan.c file in yocto.

The device is now correctly recognized as wwan0:

wwan0 Link encap:Ethernet HWaddr 5E:E3:EE:4E:D3:93
inet6 addr: fe80::5ce3:eeff:fe4e:d393/64 Scope:Link
UP RUNNING NOARP MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:25 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:5375 (5.2 KiB)

I further installed quectel-CM to analyze the connection and set APN. But there seem to be some Errors:

[09-12_13:31:40:213] QConnectManager_Linux_V1.6.5
[09-12_13:31:40:214] Find /sys/bus/usb/devices/3-1 idVendor=0x2c7c idProduct=0x700, bus=0x003, dev=0x002
[09-12_13:31:40:214] Auto find qmichannel = /dev/cdc-wdm0
[09-12_13:31:40:214] Auto find usbnet_adapter = wwan0
[09-12_13:31:40:214] netcard driver = qmi_wwan_q, driver version = V1.2.6
[09-12_13:31:40:215] Modem works in QMI mode
[09-12_13:31:40:225] cdc_wdm_fd = 7
[09-12_13:31:40:243] Get clientWDS = 1
[09-12_13:31:40:248] Get clientDMS = 1
[09-12_13:31:40:255] Get clientNAS = 1
[09-12_13:31:40:261] Get clientUIM = 1
[09-12_13:31:40:267] Get clientWDA = 1
[09-12_13:31:40:272] requestBaseBandVersion BG95M3LAR02A03
[09-12_13:31:40:297] requestGetSIMStatus SIMStatus: SIM_READY
[09-12_13:31:40:303] requestGetProfile QMUXResult = 0x1, QMUXError = 0x5e
[09-12_13:31:40:303] requestSetProfile[pdp:1 index:1] simplex.iot///0/IPV4
[09-12_13:31:40:309] requestSetProfile QMUXResult = 0x1, QMUXError = 0x5e
[09-12_13:31:40:315] requestRegistrationState2 MCC: 228, MNC: 1, PS: Detached, DataCap: UNKNOW
[09-12_13:31:40:321] requestRegistrationState2 MCC: 228, MNC: 1, PS: Detached, DataCap: UNKNOW
[09-12_13:31:40:327] requestQueryDataCall QMUXResult = 0x1, QMUXError = 0xf
[09-12_13:31:40:327] ip addr flush dev wwan0
[09-12_13:31:40:334] ip link set dev wwan0 down
[09-12_13:31:55:362] requestRegistrationState2 MCC: 228, MNC: 1, PS: Detached, DataCap: UNKNOW
[09-12_13:32:10:384] requestRegistrationState2 MCC: 228, MNC: 1, PS: Detached, DataCap: UNKNOW

What could be the reason for the error?
Is there a way to set APN without ConnectManager?
Are there further steps needed that the network device is working?

Linkin-Q · September 13, 2023, 7:45am

HI @relu

BG95 series module not support QMI.

relu · September 13, 2023, 7:58am

Which driver do I have to use and where can I find the newest version for it?

jfrog · September 13, 2023, 10:25am

Average Linux will automatically load standard drivers - option and cdc_ether.
See what you have with cat /sys/kernel/debug/usb/devices

relu · September 15, 2023, 8:02am

Hi and thank you for your response. @jfrog I ran your command an this is the output.

T:  Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=480  MxCh= 1
B:  Alloc=  0/800 us ( 0%), #Int=  0, #Iso=  0
D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=1d6b ProdID=0002 Rev= 5.10
S:  Manufacturer=Linux 5.10.72-bsp-yocto-nxp-i.mx8mp-pd22.1.1 xhci-hcd
S:  Product=xHCI Host Controller
S:  SerialNumber=xhci-hcd.1.auto
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
E:  Ad=81(I) Atr=03(Int.) MxPS=   4 Ivl=256ms

T:  Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=5000 MxCh= 1
B:  Alloc=  0/800 us ( 0%), #Int=  0, #Iso=  0
D:  Ver= 3.00 Cls=09(hub  ) Sub=00 Prot=03 MxPS= 9 #Cfgs=  1
P:  Vendor=1d6b ProdID=0003 Rev= 5.10
S:  Manufacturer=Linux 5.10.72-bsp-yocto-nxp-i.mx8mp-pd22.1.1 xhci-hcd
S:  Product=xHCI Host Controller
S:  SerialNumber=xhci-hcd.1.auto
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
E:  Ad=81(I) Atr=03(Int.) MxPS=   4 Ivl=256ms

T:  Bus=03 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=480  MxCh= 1
B:  Alloc=  0/800 us ( 0%), #Int=  0, #Iso=  0
D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=1d6b ProdID=0002 Rev= 5.10
S:  Manufacturer=Linux 5.10.72-bsp-yocto-nxp-i.mx8mp-pd22.1.1 xhci-hcd
S:  Product=xHCI Host Controller
S:  SerialNumber=xhci-hcd.2.auto
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
E:  Ad=81(I) Atr=03(Int.) MxPS=   4 Ivl=256ms

T:  Bus=03 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  5 Spd=480  MxCh= 0
D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
P:  Vendor=2c7c ProdID=0700 Rev= 0.00
S:  Manufacturer=Quectel, Incorporated
S:  Product=Quectel LPWA Module
S:  SerialNumber=1560cb47
C:* #Ifs= 4 Cfg#= 1 Atr=e0 MxPwr=500mA
I:* If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
E:  Ad=81(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=01(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
I:* If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
E:  Ad=82(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
I:* If#= 2 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
E:  Ad=83(I) Atr=03(Int.) MxPS=  64 Ivl=2ms
E:  Ad=84(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=03(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
I:* If#= 3 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=qmi_wwan_q
E:  Ad=85(I) Atr=03(Int.) MxPS=  64 Ivl=2ms
E:  Ad=86(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=04(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms

T:  Bus=04 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=5000 MxCh= 1
B:  Alloc=  0/800 us ( 0%), #Int=  0, #Iso=  0
D:  Ver= 3.00 Cls=09(hub  ) Sub=00 Prot=03 MxPS= 9 #Cfgs=  1
P:  Vendor=1d6b ProdID=0003 Rev= 5.10
S:  Manufacturer=Linux 5.10.72-bsp-yocto-nxp-i.mx8mp-pd22.1.1 xhci-hcd
S:  Product=xHCI Host Controller
S:  SerialNumber=xhci-hcd.2.auto
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
E:  Ad=81(I) Atr=03(Int.) MxPS=   4 Ivl=256ms

@Linkin-Q
Could you please tell us which driver can be used for the BG95-M3 module? As you are selling these devices, you must have a supporting driver or at least some information of what we can try next.
On the other hand would it also be possible to use another LTE module from Quectel. Which one does support the QMI-WWAN driver?

Thanks for your time in advance.

jfrog · September 15, 2023, 8:42am

Well, it shows that you do have a QMI capable modem, you have non-standard QMI driver loaded and 3 serial interfaces are not recognized by the standard option driver.
You can patch option.c to make it looking like this.
Once you have serial ports available you should be able to set your APN, etc using AT command

P.S. that looks a bit strange as Quectel’s document (LTE/5G Module Series LTE&5G Linux USB Driver User Guide) says

BG95, BG77, BG600L-M3 and BC69 only support ECM driver in Linux operating system.

Once you have serial ports working I suggest changing the mode to ECM (AT+QCFGEXT="usbnet","ecm") and use DHCP on the host system.

relu · September 20, 2023, 3:24pm

Hi @jfrog
In the meantime we discarded the idea of the QMI-WWAN driver and changed to the ECM driver as you suggested.
The serial devices appeared and we could reconfigure ttyUSB3 with the AT+QCFGEXT=“usbnet”,“ecm”-command to be an ECM interface. Unlike in the description of Quectel does the ECM appear as a eth2 port and not as a usb0 port.

We also successfully managed to ping with the command AT+QPING=1,“8.8.8.8”,5,5 on ttyUSB2 and got a response. So the internet connection works.

root@device:~#busybox microcom /dev/ttyUSB2
AT+CGPADDR=1
+CGPADDR: 1,10.64.11.124
OK

AT+QPING=1,"8.8.8.8",5,5
OK
+QPING: 0,"8.8.8.8",32,257,255
+QPING: 0,"8.8.8.8",32,77,255
+QPING: 0,"8.8.8.8",32,104,255
+QPING: 0,"8.8.8.8",32,155,255
+QPING: 0,"8.8.8.8",32,155,255
+QPING: 0,5,5,0,77,257,149

BUT:
When we try to ping through the network port eth2, there is no answer.
Here the console log:

root@device:~# ifconfig eth2
eth2      Link encap:Ethernet  HWaddr 00:A0:C6:0C:B4:70  
          inet addr:192.168.5.11  Bcast:192.168.5.255  Mask:255.255.255.0
          inet6 addr: fe80::2a0:c6ff:fe0c:b470/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:5 errors:0 dropped:0 overruns:0 frame:0
          TX packets:19 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:704 (704.0 B)  TX bytes:2062 (2.0 KiB)

root@device:~# ping -I eth2 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
^C
--- 8.8.8.8 ping statistics ---
6 packets transmitted, 0 packets received, 100% packet loss

Do you have any ideas or something else we are missing to get it to work?
Thanks a lot for your assistance in advance!

jfrog · September 20, 2023, 4:08pm

Where 192.168.5.11 on eth2 comes from?

relu · September 21, 2023, 6:43am

We assume it has something to do with our yocto image. I am working on it to get it out. What IP should it usually be? The one I get with the command AT+CGPADDR=1?

jfrog · September 21, 2023, 7:15am

As mentioned earlier:

The interface will typically obtain something like 192.168.225.x from the modem.

relu · September 21, 2023, 8:05am

I managed to change it and it now got an IP according to the one you mentioned.

root@device:~# ifconfig eth2
eth2      Link encap:Ethernet  HWaddr 00:A0:C6:0C:B4:70  
          inet addr:192.168.225.20  Bcast:192.168.225.255  Mask:255.255.255.0
          inet6 addr: fe80::2a0:c6ff:fe0c:b470/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:24 errors:0 dropped:0 overruns:0 frame:0
          TX packets:125 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:1236 (1.2 KiB)  TX bytes:10062 (9.8 KiB)

root@device:~# ping -I eth2 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
^C
--- 8.8.8.8 ping statistics ---
5 packets transmitted, 0 packets received, 100% packet loss

Unfortunately still no internet connection. Any idea why it wouldn’t work?

relu · September 21, 2023, 2:22pm

Status update:
I managed to install the connection manager. When I try to start it, I get this error:

root@device:~# quectel-CM 
[09-21_16:21:23:331] QConnectManager_Linux_V1.6.5
[09-21_16:21:23:332] Find /sys/bus/usb/devices/3-1 idVendor=0x2c7c idProduct=0x700, bus=0x003, dev=0x002
[09-21_16:21:23:332] unknow at interface for USB idProduct:0700

[09-21_16:21:23:333] network interface '' or qmidev '' is not exist
[09-21_16:21:23:333] atdevice_detect failed
[09-21_16:21:23:333] qmidevice_detect failed

Is the connection manager not made for the ECM driver?

jfrog · September 21, 2023, 5:59pm

I don’s see a need for any 3rd party tool like CM.
Your ifconfig output looks good to me and this forum has a few references to successful operation of these modems in ECM mode, with pretty much the same interface configuration.
I would try updating the firmware in the hopes that it would help resolve the issue.

relu · September 22, 2023, 5:49am

@jfrog Thanks a lot for your help so far. It definitely helped!

@Linkin-Q Could you please send the latest firmware to us for the BG95M3LA-64-SGNS module? Thanks in advance.

Linkin-Q · September 25, 2023, 1:41am

Hi @relu

Yes, sure. but Could you please share the FW version via AT+QGMR firstly?

relu · September 26, 2023, 1:03pm

Hi @Linkin-Q

In the meantime I got the firmware from your colleagues and managed to update it as well. We now have the BG95M3LAR02A03_01.202.01.202.

Does the ECM driver work with this firmware and module?

Linkin-Q · October 8, 2023, 6:11am

Hi @relu

Yes, it should be working.