RC7620 - MBPL R23 drivers R23 SDK vs AT commands - data sessions

I used

 sudo ./lite-qmi-connection-managerrp 

To create a connection on Context / Profile 5

ID PDPType IPAddress           PrimaryDNS          SecondaryDNS        Auth ProfileName         APNName             UserName
1  0       0.0.0.0             0.0.0.0             0.0.0.0             0    eeb                 everywhere
5  0       0.0.0.0             0.0.0.0             0.0.0.0             1    ee                  everywhere          eesecure

The OS reports a valid connection

wwan0: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST>  mtu 1500
        inet 10.3.191.95  netmask 255.255.255.192  destination 10.3.191.95

AT commands reports

AT+CGPADDR
+CGPADDR: 1,10.103.253.129
+CGPADDR: 5,0.0.0.0

Any ideas what is happening ? I’m thinking that for some reason context 5 is not used

The following is a grab of the connection start

<< receiving WDS_PKT_STATUS_IND
WDS IND: msgid 0x22, type:4
1

QMap data format:
  QOS format: not set -> 0
  QLink protocol: 2 -> 2
  UL format: 0 -> 0  Data Aggregation Max Datagrams: not set -> 16  Size: not set -> 4096
  DL format: 0 -> 0  Data Aggregation Max Datagrams: not set -> 0  Size: not set -> 0
  NDP signature: not set -> 0
  EP type: not set -> unknown  Interface ID: not set -> unknown
  DL minimum padding: not set -> 0
  Flow control: not set -> 0

ModelID: RC7620

Please enter Network selection preference (0: Auto (default), 1: Manual) (up to 1 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    eeb                 everywhere
5  0       0.0.0.0             0.0.0.0             0.0.0.0             1    ee                  everywhere          eesecure

Please enter a profile id (1-42) (up to 2 Characters), or press <Enter> to exit: 5

1: IPV4 (default)
2: IPV6
3: IPV4V6
Please enter IP family preference for the call (up to 1 Characters), or press <Enter> to use default value: 1

WDS[0] setIPFamily preference 4 returns 0
WDS[0] LTE IPv4 data session started successfully for Profile ID: 5


<< receiving WDS_PKT_STATUS_IND
WDS IND: msgid 0x22, type:4
SessionStatus (0:ipv4): Connected
SetAdaptorMtu(wwan0:8) mtu 1500
Up adaptor wwan0(8)
SetAdaptorAddress(family 2): ip addr add 10.3.191.95:26 dev wwan0(8)
IsAdaptorUp - Adaptor wwan0 is up
SetRoute(family 2): route add 8.8.8.0:24 dev wwan0(8) gw 10.3.191.96
PING 8.8.8.8 56 bytes data in ICMP packets.
64 bytes from 8.8.8.8 icmp_seq=1 ttl=114 rtt=4000.000 ms
64 bytes from 8.8.8.8 icmp_seq=2 ttl=114 rtt=3000.000 ms

And syslog

Dec  6 15:01:22 raspberrypi lite-qmi-connection-managerrpi: [1] 04 04 00 22 00 15 00 01  02 00 01 00 10 02 00 02   00 11 04 00 03 00 d0 07  12 01 00 04
Dec  6 15:01:22 raspberrypi lite-qmi-connection-managerrpi: [1] [helper] WDS_PKT_STATUS_IND svc 1 xid 0x0004
Dec  6 15:01:22 raspberrypi lite-qmi-connection-managerrpi: [1] <- QMUX Length=33 QMIType=1 ClientId=4 Payload:
Dec  6 15:01:22 raspberrypi lite-qmi-connection-managerrpi: [1] Read 28 bytes
Dec  6 15:01:22 raspberrypi lite-qmi-connection-managerrpi: [1] 04 04 00 22 00 15 00 01  02 00 01 00 10 02 00 02   00 11 04 00 03 00 d0 07  12 01 00 04
Dec  6 15:01:22 raspberrypi lite-qmi-connection-managerrpi: [1] [helper] WDS_PKT_STATUS_IND svc 1 xid 0x0004
Dec  6 15:01:22 raspberrypi lite-qmi-connection-managerrpi: [1] <- QMUX Length=33 QMIType=1 ClientId=3 Payload:
Dec  6 15:01:22 raspberrypi lite-qmi-connection-managerrpi: [1] Read 28 bytes
Dec  6 15:01:22 raspberrypi lite-qmi-connection-managerrpi: [1] 04 04 00 22 00 15 00 01  02 00 01 00 10 02 00 02   00 11 04 00 03 00 d0 07  12 01 00 04
Dec  6 15:01:22 raspberrypi lite-qmi-connection-managerrpi: [1] [helper] WDS_PKT_STATUS_IND svc 1 xid 0x0004
Dec  6 15:01:40 raspberrypi lite-qmi-connection-managerrpi: [1] CtlService_GetClientId: serviceType=26
Dec  6 15:01:40 raspberrypi lite-qmi-connection-managerrpi: [1] -> QMUX Length=15 QMIType=0 ClientId=0 Payload:
Dec  6 15:01:40 raspberrypi lite-qmi-connection-managerrpi: [1] Send 10 bytes
Dec  6 15:01:40 raspberrypi lite-qmi-connection-managerrpi: [1] 00 0d 22 00 04 00 01 01  00 1a
Dec  6 15:01:40 raspberrypi lite-qmi-connection-managerrpi: [1] <- QMUX Length=23 QMIType=0 ClientId=0 Payload:
Dec  6 15:01:40 raspberrypi lite-qmi-connection-managerrpi: [1] Read 18 bytes
Dec  6 15:01:40 raspberrypi lite-qmi-connection-managerrpi: [1] 01 0d 22 00 0c 00 02 04  00 00 00 00 00 01 02 00   1a 01
Dec  6 15:01:40 raspberrypi lite-qmi-connection-managerrpi: [1] CtlService_GetClientId: succeeded, serviceType=26, clientId=1
Dec  6 15:01:40 raspberrypi lite-qmi-connection-managerrpi: [1] [  pack] WDA_SET_DATA_FORMAT xid 0x0001 returned 0x0
Dec  6 15:01:40 raspberrypi lite-qmi-connection-managerrpi: [1] -> QMUX Length=33 QMIType=26 ClientId=1 Payload:
Dec  6 15:01:40 raspberrypi lite-qmi-connection-managerrpi: [1] Send 28 bytes
Dec  6 15:01:40 raspberrypi lite-qmi-connection-managerrpi: [1] 00 01 00 20 00 15 00 11  04 00 02 00 00 00 12 04   00 00 00 00 00 13 04 00  00 00 00 00
Dec  6 15:01:40 raspberrypi lite-qmi-connection-managerrpi: [1] <- QMUX Length=90 QMIType=26 ClientId=1 Payload:
Dec  6 15:01:40 raspberrypi lite-qmi-connection-managerrpi: [1] Read 85 bytes
Dec  6 15:01:40 raspberrypi lite-qmi-connection-managerrpi: [1] 02 01 00 20 00 4e 00 02  04 00 00 00 00 00 10 01   00 00 11 04 00 02 00 00  00 12 04 00 00 00 00 00
Dec  6 15:01:40 raspberrypi lite-qmi-connection-managerrpi: [1] 13 04 00 00 00 00 00 14  04 00 00 00 00 00 15 04   00 00 00 00 00 16 04 00  00 00 00 00 17 04 00 10
Dec  6 15:01:40 raspberrypi lite-qmi-connection-managerrpi: [1] 00 00 00 18 04 00 00 10  00 00 1a 04 00 00 00 00   00 1b 01 00 00
Dec  6 15:01:40 raspberrypi lite-qmi-connection-managerrpi: [1] [unpack] WDA_SET_DATA_FORMAT xid 0x0001 returned 0x0
Dec  6 15:01:40 raspberrypi lite-qmi-connection-managerrpi: [1] CtlService_ReleaseClientId: serviceType=26 clientId=1
Dec  6 15:01:40 raspberrypi lite-qmi-connection-managerrpi: [1] -> QMUX Length=16 QMIType=0 ClientId=0 Payload:
Dec  6 15:01:40 raspberrypi lite-qmi-connection-managerrpi: [1] Send 11 bytes
Dec  6 15:01:40 raspberrypi lite-qmi-connection-managerrpi: [1] 00 0e 23 00 05 00 01 02  00 1a 01
Dec  6 15:01:40 raspberrypi lite-qmi-connection-managerrpi: [1] <- QMUX Length=23 QMIType=0 ClientId=0 Payload:
Dec  6 15:01:40 raspberrypi lite-qmi-connection-managerrpi: [1] Read 18 bytes
Dec  6 15:01:40 raspberrypi lite-qmi-connection-managerrpi: [1] 01 0e 23 00 0c 00 02 04  00 00 00 00 00 01 02 00   1a 01
Dec  6 15:01:40 raspberrypi lite-qmi-connection-managerrpi: [1] CtlService_ReleaseClientId: succeeded, serviceType=26
Dec  6 15:01:40 raspberrypi lite-qmi-connection-managerrpi: [1] [  pack] QMI_DMS_GET_DEVICE_MODEL_ID xid 0x0004 returned 0x0
Dec  6 15:01:40 raspberrypi lite-qmi-connection-managerrpi: [1] -> QMUX Length=12 QMIType=2 ClientId=1 Payload:
Dec  6 15:01:40 raspberrypi lite-qmi-connection-managerrpi: [1] Send 7 bytes
Dec  6 15:01:40 raspberrypi lite-qmi-connection-managerrpi: [1] 00 04 00 22 00 00 00
Dec  6 15:01:40 raspberrypi lite-qmi-connection-managerrpi: [1] <- QMUX Length=28 QMIType=2 ClientId=1 Payload:
Dec  6 15:01:40 raspberrypi lite-qmi-connection-managerrpi: [1] Read 23 bytes
Dec  6 15:01:40 raspberrypi lite-qmi-connection-managerrpi: [1] 02 04 00 22 00 10 00 02  04 00 00 00 00 00 01 06   00 52 43 37 36 32 30
Dec  6 15:01:40 raspberrypi lite-qmi-connection-managerrpi: [1] [unpack] QMI_DMS_GET_DEVICE_MODEL_ID xid 0x0004 returned 0x0

from the connection manager log, the IP address of context 5 is 10.3.191.95 and it can be used to ping google DNS server.
Just the +CGPADDR cannot show this …

Hi Jyi

Thanks.

Does this mean that the command AT+CGPADDR has a bug or is this expected behaviour?

Might be a bug, but you can still get the IP address in the application.