Page 1 of 1

EM12-G on Raspberry PI 5B

Posted: Sun Feb 04, 2024 3:33 am
by johnichan
I tried instructions in 2 posts on EM12 before posting my issue here. My EM12-G on a M.2 to USB(from aliexpress) adapter works in Verizon and in windows 10 and the same sim was working ON 8800L(bought in USA) hotspot before starting the experiments to add to a raspberry pi and later add to an openwrt router and later convert to an openmptcp router :D

Anyway here goes what I see in the raspberry pi. It detects usb device; but qmi-network fails to connect. If i disable pi modem manager, i can see AT commands and EM12-G connected to verizon also as per AT commands. I followed mostly EC25 guides there is no option to run qmi mode like AT+QCFG="usbnet" is not accepted in EM12-G

[39346.544083] usb 3-1.2: New USB device found, idVendor=2c7c, idProduct=0512, bcdDevice= 3.18
[39346.544091] usb 3-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[39346.544095] usb 3-1.2: Product: Surface Mobile Broadband
[39346.544098] usb 3-1.2: Manufacturer: Surface
[39346.544101] usb 3-1.2: SerialNumber: 0123456789ABCDEF
[39346.675623] option 3-1.2:1.0: GSM modem (1-port) converter detected
[39346.675735] usb 3-1.2: GSM modem (1-port) converter now attached to ttyUSB0
[39346.675852] option 3-1.2:1.1: GSM modem (1-port) converter detected
[39346.675932] usb 3-1.2: GSM modem (1-port) converter now attached to ttyUSB1
[39346.676032] option 3-1.2:1.2: GSM modem (1-port) converter detected
[39346.676093] usb 3-1.2: GSM modem (1-port) converter now attached to ttyUSB2
[39346.676197] option 3-1.2:1.3: GSM modem (1-port) converter detected
[39346.676258] usb 3-1.2: GSM modem (1-port) converter now attached to ttyUSB3
[39346.697420] cdc_mbim 3-1.2:1.4: cdc-wdm0: USB WDM device
[39346.697677] cdc_mbim 3-1.2:1.4 wwan0: register 'cdc_mbim' at usb-xhci-hcd.1-1.2, CDC MBIM, be:4b:5f:33:6b:17
Johnz@pi5bp1:~ $ ifconfig wwan0
wwan0: flags=4226<BROADCAST,NOARP,MULTICAST> mtu 1500
ether be:4b:5f:33:6b:17 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Johnz@pi5bp1:~ $ sudo ifconfig wwan0 up
Johnz@pi5bp1:~ $ ifconfig wwan0
wwan0: flags=4291<UP,BROADCAST,RUNNING,NOARP,MULTICAST> mtu 1500
inet6 fe80::bc4b:5fff:fe33:6b17 prefixlen 64 scopeid 0x20<link>
ether be:4b:5f:33:6b:17 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 14 bytes 1771 (1.7 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

Johnz@pi5bp1:~ $ ls /dev| grep cdc
cdc-wdm0
Johnz@pi5bp1:~ $ sudo qmi-network /dev/cdc-wdm0 start
Loading profile at /etc/qmi-network.conf...
APN: vzwinternet
APN user: unset
APN password: unset
qmi-proxy: no
IP_TYPE: unset
PROFILE: unset
Checking data format with 'qmicli -d /dev/cdc-wdm0 --wda-get-data-format '...
error: operation failed: Transaction timed out
Device link layer protocol not retrieved: WDA unsupported
Starting network with 'qmicli -d /dev/cdc-wdm0 --wds-start-network=apn='vzwinternet' --client-no-release-cid '...
error: couldn't open the QmiDevice: Operation timed out: device is closed
error: network start failed, client not allocated
Johnz@pi5bp1:~ $

ohnz@pi5bp1:~ $ atcom --port /dev/ttyUSB3 AT+GMI
[ERR] Couldn't open serial communication
------------reconneted device---

[46122.809230] cdc_mbim 3-1.2:1.4 wwan0: unregister 'cdc_mbim' usb-xhci-hcd.1-1.2, CDC MBIM
[46131.732078] usb 3-1.2: new high-speed USB device number 9 using xhci-hcd
[46131.880734] usb 3-1.2: New USB device found, idVendor=2c7c, idProduct=0512, bcdDevice= 3.18
[46131.880738] usb 3-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[46131.880741] usb 3-1.2: Product: Surface Mobile Broadband
[46131.880743] usb 3-1.2: Manufacturer: Surface
[46131.880745] usb 3-1.2: SerialNumber: 0123456789ABCDEF
[46132.024685] option 3-1.2:1.0: GSM modem (1-port) converter detected
[46132.024784] usb 3-1.2: GSM modem (1-port) converter now attached to ttyUSB0
[46132.024881] option 3-1.2:1.1: GSM modem (1-port) converter detected
[46132.024937] usb 3-1.2: GSM modem (1-port) converter now attached to ttyUSB1
[46132.025016] option 3-1.2:1.2: GSM modem (1-port) converter detected
[46132.025071] usb 3-1.2: GSM modem (1-port) converter now attached to ttyUSB2
[46132.025148] option 3-1.2:1.3: GSM modem (1-port) converter detected
[46132.025196] usb 3-1.2: GSM modem (1-port) converter now attached to ttyUSB3
[46132.044478] cdc_mbim 3-1.2:1.4: cdc-wdm0: USB WDM device
[46132.044718] cdc_mbim 3-1.2:1.4 wwan0: register 'cdc_mbim' at usb-xhci-hcd.1-1.2, CDC MBIM, be:4b:5f:33:6b:17
Johnz@pi5bp1:~ $ ls /dev | grep ttyUSB
ttyUSB0
ttyUSB1
ttyUSB2
ttyUSB3
Johnz@pi5bp1:~ $


------------------

Johnz@pi5bp1:~ $ atcom --port /dev/ttyUSB3 AT+GMI

RDY
AT+GMI
Quectel

OK

Johnz@pi5bp1:~ $ sudo qmi-network /dev/cdc-wdm0 status
Loading profile at /etc/qmi-network.conf...
APN: vzwinternet
APN user: unset
APN password: unset
qmi-proxy: no
IP_TYPE: unset
PROFILE: unset
Getting status with 'qmicli -d /dev/cdc-wdm0 --wds-get-packet-service-status '...
error: couldn't open the QmiDevice: Operation timed out: device is closed
error: couldn't get packet service status
Johnz@pi5bp1:~ $ atcom --port /dev/ttyUSB3 AT+ATI
[ERR] Couldn't open serial communication
Johnz@pi5bp1:~ $ atcom --port /dev/ttyUSB3 AT+CGMM
[ERR] Couldn't open serial communication
Johnz@pi5bp1:~ $ atcom --port /dev/ttyUSB3 AT+CASS
[ERR] Couldn't open serial communication
Johnz@pi5bp1:~ $ atcom --port /dev/ttyUSB2 AT+CASS
[ERR] Couldn't open serial communication
Johnz@pi5bp1:~ $ atcom --port /dev/ttyUSB3 AT+CPAS
[ERR] Couldn't open serial communication

Johnz@pi5bp1:~ $ sudo systemctl stop ModemManager
Johnz@pi5bp1:~ $ sudo systemctl disable ModemManager
Removed "/etc/systemd/system/multi-user.target.wants/ModemManager.service".
Removed "/etc/systemd/system/dbus-org.freedesktop.ModemManager1.service".
Johnz@pi5bp1:~ $ atcom --port /dev/ttyUSB3 AT+CASS

ERROR

Johnz@pi5bp1:~ $ atcom --port /dev/ttyUSB3 AT+CPAS

+CPAS: 0

OK

Johnz@pi5bp1:~ $ atcom --port /dev/ttyUSB3 AT+CASS

ERROR

Johnz@pi5bp1:~ $ atcom --port /dev/ttyUSB3 AT+CGMM

EM12

OK

Johnz@pi5bp1:~ $ atcom --port /dev/ttyUSB3 AT+CREG

OK

Johnz@pi5bp1:~ $ atcom --port /dev/ttyUSB3 AT+CSQ

+CSQ: 20,99

OK

Johnz@pi5bp1:~ $ atcom --port /dev/ttyUSB3 AT+QSPN

+QSPN: "Verizon ","Verizon ","",0,"311480"

OK

Johnz@pi5bp1:~ $ atcom --port /dev/ttyUSB3 AT+QNWINFO

+QNWINFO: "FDD LTE","311480","LTE BAND 66",66536

OK

Johnz@pi5bp1:~ $ atcom --port /dev/ttyUSB3 AT+CGDCONT?

+CGDCONT: 1,"IPV4V6","ims","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
+CGDCONT: 2,"IPV4V6","vzwadmin","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
+CGDCONT: 3,"IPV4V6","vzwinternet","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
+CGDCONT: 4,"IPV4V6","vzwapp","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
+CGDCONT: 5,"IPV4V6","vzwemergency","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,1

OK

Johnz@pi5bp1:~ $ atcom --port /dev/ttyUSB3 AT+CFUN?

+CFUN: 1

OK

Johnz@pi5bp1:~ $ atcom --port /dev/ttyUSB3 AT+COPS?

+COPS: 0,0,"Verizon ",7

OK

Johnz@pi5bp1:~ $


I am expecting your valuable feedbacks to proceed further. My windows 10 speed test result is attached as proof(I always keep proofs for myself). My issue is in raspberry pi. I am pretty new in usb modems.

Re: EM12-G on Raspberry PI 5B

Posted: Mon Feb 05, 2024 8:21 am
by Didneywhorl
Why not load in the mbim drivers and let modemmanager run the modem in it's current mbim config?

Otherwise at+qcfg="usbnet",0 should do it to convert it to qmi.

Which firmware version is on it, as I notice it says its out of a laptop or something.

39346.544095] usb 3-1.2: Product: Surface Mobile Broadband
This should normally say 'Quectel Wireless EM12G'

Re: EM12-G on Raspberry PI 5B

Posted: Tue Feb 06, 2024 10:14 pm
by johnichan
@Didneywhorl Thanks for the response. The purchase link is added below. Device id and vendor id also reported correctly. USB should not be depending on anything.

https://www.aliexpress.com/item/3256804768101282.html
https://www.aliexpress.com/item/3256806124760648.html

Re: EM12-G on Raspberry PI 5B

Posted: Mon Mar 11, 2024 11:18 pm
by johnichan
The issue was sorted out by https://github.com/4IceG He found that this module has a custom firmware and was taken from a laptop and suggested to use MBIM mode and it worked on OpenWRT