Thank you. I will use it
I have one more query. In my adlink atom board, I see /dev/ttyUSB0 and /dev/ttyUSB1 created. But I dont see the device /dev/cdc_mbim created on my intel adlink. Any kernel flag is missing. I see the flag CONFIG_USB_NET_QMI_WWAN is not set which set on my ubuntu PC. Is it required to set this flag? When I set this flag and build for my adlink atom board it fails due to sierra mbpl conflict. Please help out.
How about enable mbim flag and rebuild for your platform?
Which kernel flag I have to enable ? Can you please confirm and I will try .
Do you have menuconfig in your board?
Yes I can change the configuration via menuconfig . What flag I should look for ?
Did you search anything about mbim inside menuconfig?
CONFIG_USB_NET_CDC_MBIM is it correct ?
Maybe, you can make some test
Thanks, will do some test with this flag enabled
I am testing on windows 10. I see beloe AT command o/p. It says no network service… What could be the issue?
AT+cpin?
+CPIN: READY
OK
AT+cpin?
+CPIN: READY
OK
AT+CMEE=2
OK
AT+cpin?
+CPIN: READY
OK
AT+COPS?
+COPS: 0,0,“AT&T”,7
OK
AT!SCACT=1,1
+CME ERROR: no network service
AT+CGREG?
+CGREG: 0,0
also on windows how do I start a connection? Is there a connection manager binary available?
Also tested on ubuntu PC and got the same AT commands ouptput.
When I tried to use the tool ./bin/mbim-test-hostx86_64 /dev/cdc-wdm0 it return error MbimTransport_Initialize failure. What could be the issue?
i used MBIM command to establish data connection in linux PC:
owner@CNHKG-EX-001367:~/legato/workspace/git/mangOH_2-7-2019$ cat /etc/mbim-network.conf
APN=hkcsl
APN_USER=
APN_PASS=
APN_AUTH=
PROXY=yes
owner@CNHKG-EX-001367:~/legato/workspace/git/mangOH_2-7-2019$sudo mbim-network /dev/cdc-wdm0 start
Loading profile...
APN: hkcsl
Querying subscriber ready status 'mbimcli -d /dev/cdc-wdm0 --query-subscriber-ready-status --no-close'...
[/dev/cdc-wdm0] Subscriber ready status retrieved: Ready state: 'initialized' Subscriber ID: '454003074112345' SIM ICCID: '8985200012741512345' Ready info: 'unknown' Telephone numbers: (0) 'unknown' [/dev/cdc-wdm0] Session not closed: TRID: '3'
Saving state... (TRID: 3)
Querying registration state 'mbimcli -d /dev/cdc-wdm0 --query-registration-state --no-open=3 --no-close'...
[/dev/cdc-wdm0] Registration status: Network error: 'unknown' Register state: 'home' Register mode: 'automatic' Available data classes: 'lte' Current cellular class: 'gsm' Provider ID: '45400' Provider name: '1O1O' Roaming text: 'unknown' Registration flags: 'unknown' [/dev/cdc-wdm0] Session not closed: TRID: '4'
Saving state... (TRID: 4)
Attaching to packet service with 'mbimcli -d /dev/cdc-wdm0 --attach-packet-service --no-open=4 --no-close'...
Saving state... (TRID: 5)
Starting network with 'mbimcli -d /dev/cdc-wdm0 --connect=hkcsl --no-open=5 --no-close'...
Network started successfully
Saving state... (TRID: 6)
I will try the same steps . Any tool in windows to make a connection ?
the MBIM tool is by default from Windows.
I don’t configure anything…
How do i pass augments to mbim in windows . Sorry I never used it .
What argument do you want to pass in Windows?
Do you see this?
BTW, I suggest you to test in linux PC first
Sure . I will test in Ubuntu pc and let you know the results . Are you suggesting to connect using the mbim command tool instead of using the connection manager provided in the mbpl sdk sample apps ?
you can double check if the connection manager is working fine with EM9191.
Normally i just use MBIM command to establish data connection
Sounds good. Thank you for helping .
I have also tried lite-qmi-connection-manager + EM9191 on FW 03.10.07.00 GENERIC PRI.
it is working fine in Ubuntu 18.
owner@ubuntu:~/QMI/MBPL/MBPL_SDK_R30_ENG6-lite.src/MBPL_SDK_R30_ENG6-lite.src/SampleApps/lite-qmi-connection-manager$ sudo ./bin/lite-qmi-connection-managerhostx86_64
[sudo] password for owner:
lite-qmi-connection-manager v1.0.2211.0
Open transport "/dev/cdc-wdm0" on USB device in MBIM mode
Device interface: MBIM
Model: EM9191
Device Power Status: 0 - Online
HomeNetwork: CMHK
Network Selection Preference: auto
SessionStatus (0:ipv4): Disconnected
SessionStatus (1:ipv6): Disconnected
SessionStatus (2:ipv4): Disconnected
SessionStatus (3:ipv6): Disconnected
SessionStatus (4:ipv4): Disconnected
SessionStatus (5:ipv6): Disconnected
SessionStatus (6:ipv4): Disconnected
SessionStatus (7:ipv6): Disconnected
Auto-ping check on connection: enabled
Routing table update on connection: enabled
Please select one of the following options or press 'q' to exit:
1. start a single-PDN data session
2. Start one connection of a multi-PDN data session
3. Stop one connection
4. Stop all active connections
5. Display all profiles on the device
6. Display one profile on the device
7. Create a profile on the device
8. Modify an existing profile on the device
9. Delete a profile from the device
10. Scan available networks
11. Lock PCI
12. Disable PCI locking
13. Get PCI locking
14. Enable QOS Event
15. Disable QOS Event
16. Request QOS Expanded
17. Get QOS Information
18. QOS Indication Register
19. Read QOS Data Statistics (SWIQOS)
20. Read QOS Extra APN Parameters (SWIQOS)
21. Get Packet Statistics
22. Get Current Channel Rate
23. Toggle pinging on connection
24. Toggle routing table update on connection
27. Enable QMAP
28. Disable QMAP
29. Enable/disable WDS event report indication
30. Enable/disable keep data session alive
(q)uit to exit:
1
Please enter Network selection preference (0: Auto (default), 1: Manual) (up to 3 Characters), or press <Enter> to use default value:
Please enter Connect via 0: existing profile (default) or 1: explicit APN (up to 3 Characters), or press <Enter> to use default value:
ID PDPType IPAddress PrimaryDNS SecondaryDNS Auth ProfileName APNName UserName
1 0 0.0.0.0 0.0.0.0 0.0.0.0 0 profile1 CMHK
2 0 0.0.0.0 0.0.0.0 0.0.0.0 0 CMHK
Please enter a profile id (1-42) (up to 4 Characters), or press <Enter> to exit: 1
1: IPV4 (default)
2: IPV6
3: IPV4V6
Please enter IP family preference for the call (up to 3 Characters), or press <Enter> to use default value:
WDS[0] setIPFamily preference 4 returns 0
Starting data session via profile 1
WDS[0] IPv4 data session started successfully for Profile ID: 1
<< receiving WDS_PKT_STATUS_IND
WDS IND: msgid 0x22, type:4
[unpack_wds_SLQSSetPacketSrvStatusCallback]
Packet Service 7 Status: 0x2, Reconfig required: 0
IP Family: 4
Technology: 0x8881
Bearer ID: 0x0
<< receiving WDS_PKT_STATUS_IND
WDS IND: msgid 0x22, type:4
[unpack_wds_SLQSSetPacketSrvStatusCallback]
Packet Service 6 Status: 0x2, Reconfig required: 0
IP Family: 4
Technology: 0x8881
Bearer ID: 0x0
<< receiving WDS_PKT_STATUS_IND
WDS IND: msgid 0x22, type:4
[unpack_wds_SLQSSetPacketSrvStatusCallback]
Packet Service 5 Status: 0x2, Reconfig required: 0
IP Family: 4
Technology: 0x8881
Bearer ID: 0x0
<< receiving WDS_PKT_STATUS_IND
WDS IND: msgid 0x22, type:4
[unpack_wds_SLQSSetPacketSrvStatusCallback]
Packet Service 4 Status: 0x2, Reconfig required: 0
IP Family: 4
Technology: 0x8881
Bearer ID: 0x0
<< receiving WDS_PKT_STATUS_IND
WDS IND: msgid 0x22, type:4
[unpack_wds_SLQSSetPacketSrvStatusCallback]
Packet Service 3 Status: 0x2, Reconfig required: 0
IP Family: 4
Technology: 0x8881
Bearer ID: 0x0
<< receiving WDS_PKT_STATUS_IND
WDS IND: msgid 0x22, type:4
[unpack_wds_SLQSSetPacketSrvStatusCallback]
Packet Service 2 Status: 0x2, Reconfig required: 0
IP Family: 4
Technology: 0x8881
Bearer ID: 0x0
<< receiving WDS_PKT_STATUS_IND
WDS IND: msgid 0x22, type:4
[unpack_wds_SLQSSetPacketSrvStatusCallback]
Packet Service 1 Status: 0x2, Reconfig required: 0
IP Family: 4
Technology: 0x8881
Bearer ID: 0x0
<< receiving WDS_PKT_STATUS_IND
WDS IND: msgid 0x22, type:4
[unpack_wds_SLQSSetPacketSrvStatusCallback]
Packet Service 0 Status: 0x2, Reconfig required: 0
IP Family: 4
Technology: 0x8881
Bearer ID: 0x0
SessionStatus (0:ipv4): Connected
SetAdaptorMtu(wwan0:3) mtu 1500
Up adaptor wwan0(3)
SetAdaptorAddress(family 2): ip addr add 10.33.207.146:30 dev wwan0(3)
IsAdaptorUp - Adaptor wwan0 is up
SetRoute(family 2): route add 0.0.0.0:0 dev wwan0(3) gw 0.0.0.0
PING 8.8.8.8 56 bytes data in ICMP packets.
64 bytes from 8.8.8.8 icmp_seq=1 ttl=58 rtt=4003.000 ms
64 bytes from 8.8.8.8 icmp_seq=2 ttl=58 rtt=3002.000 ms
64 bytes from 8.8.8.8 icmp_seq=3 ttl=58 rtt=2001.000 ms
64 bytes from 8.8.8.8 icmp_seq=4 ttl=58 rtt=1000.000 ms
--------------------PING statistics-------------------
4 packets transmitted, 4 received , %0 lost
I tried this binary and failed with Transport initialize failed. Can it be bacause the FW is not the correct one ? Do I need to change the default FW from 9191 ?
One more query . How did you configure the APN when you used lite-qmi-connectionmgr ?