MC7455 and MC7430--query-subscriber-ready-status timeout
Chris Lockwood
Chris.Lockwood at avi.com.au
Thu Sep 7 06:05:05 UTC 2017
Hi Aleksander,
I poll it using at command interface and see that its already attached to the network with the first profile before I even try to run --query-subscriber-ready-status. Its registered on the network (S1 trace from the enodeB).
But to isolate the problem, I power cycled the modem (using one with default firmware), and waited a minute (no other connections made to card: AT, mbim etc), then ran:
root at avios:~# mbimcli -p -d /dev/cdc-wdm0 --query-device-caps
[/dev/cdc-wdm0] Device capabilities retrieved:
Device type: 'remote'
Cellular class: 'gsm'
Voice class: 'no-voice'
SIM class: 'removable'
Data class: 'umts, hsdpa, hsupa, lte'
SMS caps: 'pdu-receive, pdu-send'
Ctrl caps: 'reg-manual'
Max sessions: '8'
Custom data class: 'unknown'
Device ID: '35907xxxxxxxxxxxxxx'
Firmware info: 'SWI9X30C_02.14.03.00'
Hardware info: 'MC7430'
root at avios:~# mbimcli -p -d /dev/cdc-wdm0 --query-radio-state
[/dev/cdc-wdm0] Radio state retrieved:
Hardware radio state: 'on'
Software radio state: 'on'
root at avios:~# mbimcli -p -d /dev/cdc-wdm0 --query-pin-state
[/dev/cdc-wdm0] PIN info:
PIN state: 'locked'
PIN type: 'pin2'
Remaining attempts: '3'
And then --query-subscriber-ready-status which times out as below.
Thanks for your time.
cheers
Chris
root at avios:~# time mbimcli -v -p -d /dev/cdc-wdm0 --query-subscriber-ready-status
[07 Sep 2017, 05:45:15] [Debug] opening device...
[07 Sep 2017, 05:45:15] [Debug] [/dev/cdc-wdm0] Read max control message size from descriptors file: 4096
[07 Sep 2017, 05:45:15] [Debug] [/dev/cdc-wdm0] Sent message...
<<<<<< RAW:
<<<<<< length = 88
<<<<<< data = 03:00:00:00:58:00:00:00:01:00:00:00:01:00:00:00:00:00:00:00:83:8C:F7:FB:8D:0D:4D:7F:87:1E:D7:1D:BE:FB:B3:9B:01:00:00:00:01:00:00:00:28:00:00:00:0C:00:00:00:1A:00:00:00:1E:00:00:00:2F:00:64:00:65:00:76:00:2F:00:63:00:64:00:63:00:2D:00:77:00:64:00:6D:00:30:00:00:00
[07 Sep 2017, 05:45:15] [Debug] [/dev/cdc-wdm0] Sent message (translated)...
<<<<<< Header:
<<<<<< length = 88
<<<<<< type = command (0x00000003)
<<<<<< transaction = 1
<<<<<< Fragment header:
<<<<<< total = 1
<<<<<< current = 0
<<<<<< Contents:
<<<<<< service = 'proxy-control' (838cf7fb-8d0d-4d7f-871e-d71dbefbb39b)
<<<<<< cid = 'configuration' (0x00000001)
<<<<<< type = 'set' (0x00000001)
[07 Sep 2017, 05:45:15] [Debug] [/dev/cdc-wdm0] Received message...
>>>>>> RAW:
>>>>>> length = 48
>>>>>> data = 03:00:00:80:30:00:00:00:01:00:00:00:01:00:00:00:00:00:00:00:83:8C:F7:FB:8D:0D:4D:7F:87:1E:D7:1D:BE:FB:B3:9B:01:00:00:00:00:00:00:00:00:00:00:00
[07 Sep 2017, 05:45:15] [Debug] [/dev/cdc-wdm0] Received message (translated)...
>>>>>> Header:
>>>>>> length = 48
>>>>>> type = command-done (0x80000003)
>>>>>> transaction = 1
>>>>>> Fragment header:
>>>>>> total = 1
>>>>>> current = 0
>>>>>> Contents:
>>>>>> status error = 'None' (0x00000000)
>>>>>> service = 'proxy-control' (838cf7fb-8d0d-4d7f-871e-d71dbefbb39b)
>>>>>> cid = 'configuration' (0x00000001)
[07 Sep 2017, 05:45:15] [Debug] [/dev/cdc-wdm0] Sent message...
<<<<<< RAW:
<<<<<< length = 16
<<<<<< data = 01:00:00:00:10:00:00:00:02:00:00:00:00:10:00:00
[07 Sep 2017, 05:45:15] [Debug] [/dev/cdc-wdm0] Sent message (translated)...
<<<<<< Header:
<<<<<< length = 16
<<<<<< type = open (0x00000001)
<<<<<< transaction = 2
<<<<<< Contents:
<<<<<< max_control_transfer = 4096
[07 Sep 2017, 05:45:15] [Debug] [/dev/cdc-wdm0] Received message...
>>>>>> RAW:
>>>>>> length = 16
>>>>>> data = 01:00:00:80:10:00:00:00:02:00:00:00:00:00:00:00
[07 Sep 2017, 05:45:15] [Debug] MBIM Device at '/dev/cdc-wdm0' ready
[07 Sep 2017, 05:45:15] [Debug] Asynchronously querying subscriber ready status...
[07 Sep 2017, 05:45:15] [Debug] [/dev/cdc-wdm0] Sent message...
<<<<<< RAW:
<<<<<< length = 48
<<<<<< data = 03:00:00:00:30:00:00:00:03:00:00:00:01:00:00:00:00:00:00:00:A2:89:CC:33:BC:BB:8B:4F:B6:B0:13:3E:C2:AA:E6:DF:02:00:00:00:00:00:00:00:00:00:00:00
[07 Sep 2017, 05:45:15] [Debug] [/dev/cdc-wdm0] Sent message (translated)...
<<<<<< Header:
<<<<<< length = 48
<<<<<< type = command (0x00000003)
<<<<<< transaction = 3
<<<<<< Fragment header:
<<<<<< total = 1
<<<<<< current = 0
<<<<<< Contents:
<<<<<< service = 'basic-connect' (a289cc33-bcbb-8b4f-b6b0-133ec2aae6df)
<<<<<< cid = 'subscriber-ready-status' (0x00000002)
<<<<<< type = 'query' (0x00000000)
error: operation failed: Transaction timed out
[07 Sep 2017, 05:45:25] [Debug] [/dev/cdc-wdm0] Sent message...
<<<<<< RAW:
<<<<<< length = 12
<<<<<< data = 02:00:00:00:0C:00:00:00:04:00:00:00
[07 Sep 2017, 05:45:25] [Debug] [/dev/cdc-wdm0] Sent message (translated)...
<<<<<< Header:
<<<<<< length = 12
<<<<<< type = close (0x00000002)
<<<<<< transaction = 4
[07 Sep 2017, 05:45:25] [Debug] [/dev/cdc-wdm0] Received message...
>>>>>> RAW:
>>>>>> length = 16
>>>>>> data = 02:00:00:80:10:00:00:00:04:00:00:00:00:00:00:00
[07 Sep 2017, 05:45:25] [Debug] [/dev/cdc-wdm0] channel destroyed
[07 Sep 2017, 05:45:25] [Debug] Device closed
Command exited with non-zero status 1
real 0m 10.04s
user 0m 0.02s
sys 0m 0.00s
-----Original Message-----
From: Aleksander Morgado [mailto:aleksander at aleksander.es]
Sent: Thursday, 7 September 2017 1:30 PM
To: Chris Lockwood <Chris.Lockwood at avi.com.au>
Cc: libmbim-devel at lists.freedesktop.org
Subject: Re: MC7455 and MC7430--query-subscriber-ready-status timeout
Hey,
> I have MC7455 and MC7430 cards. Both are loaded with SWI9X30C_02.24.03.00.
>
>
>
> I’m using the latest git commit 5bb673fe87... but the same behaviour
> is observed with 5c3935b75fc4dd46...
>
>
>
> To get these cards to connect, I first need to run
> --query-subscriber-ready-status, then --attach-packet-service command
> and then the --connect commands.
>
>
>
> From a clean start, first command run is:
>
> root at avios:~# mbimcli -p -d /dev/cdc-wdm0
> --query-subscriber-ready-status --no-close
>
> error: operation failed: Transaction timed out
>
> [/dev/cdc-wdm0] Session not closed:
>
> TRID: '4'
>
>
>
> The command takes a bit more than 10 seconds before it times out (I
> can see the 10 second timeout in the libmbim source).
>
>
>
> But I can then --attach-packet-service and –connect and its all
> working fine. Without the --query-subscriber-ready-status command I cannot connect.
>
>
>
> Any ideas why it might time out? It’s not a huge problem but it does
> add another 10 seconds to the start time.
>
Could just be that the modem is initializing the SIM card and that takes some time?
Does the command timeout if you wait some time (e.g. 1 min) between powering the module+sim and running that command?
Does the command timeout if you send other commands before (e.g.
querying capabilities)?
--
Aleksander
https://aleksander.es
More information about the libmbim-devel
mailing list