Sierra Wireless 340u - NotInitialized

Bjørn Mork bjorn at mork.no
Thu May 30 00:42:12 PDT 2013


"Shawn J. Goff" <shawn7400 at gmail.com> writes:

> I'm working with a Sierra Wireless (now NetGear) AirCard 340u, and
> there are some problems.
>
> When trying to connect, the modem returns a NotInitialized status. I'm
> not sure what this means. It's registered and attached to the packet
> service. The verbose output is attached.

Yes, I've seen similar on the MC7710 (which I assume use pretty much the
same firmware).  Didn't have time researching it then and forgot all
about it. Sorry about that.

Anyway, testing now I still see the same issue:

bjorn at nemi:~$ mbimcli -nd /dev/cdc-wdm0   --query-subscriber-ready-status
[/dev/cdc-wdm0] Subscriber ready status retrieved:
              Ready state: 'initialized'
            Subscriber ID: '242013050xxxxxx'
                SIM ICCID: '89470305121011xxxxxx'
               Ready info: 'id'
        Telephone numbers: (0) 'unknown'


bjorn at nemi:~$ mbimcli -nd /dev/cdc-wdm0    --attach-packet-service
error: operation failed: NotInitialized


The weird thing, which explains why I could forget about this, is that
ModemManager works fine and always has.

Looking at the commands sent, and trying to figure out what could be
wrong, I believe the primary suspect is the "OPEN" command which is sent
for each and every mbimcli command:


bjorn at nemi:~$ mbimcli -nvd /dev/cdc-wdm0    --attach-packet-service

[30 May 2013, 09:18:12] [Debug] [/dev/cdc-wdm0] Queried max control message size: 4096
[30 May 2013, 09:18:12] [Debug] [/dev/cdc-wdm0] Sent message...
<<<<<< RAW:
<<<<<<   length = 16
<<<<<<   data   = 01:00:00:00:10:00:00:00:01:00:00:00:00:10:00:00

[30 May 2013, 09:18:12] [Debug] [/dev/cdc-wdm0] Sent message (translated)...
<<<<<< Header:
<<<<<<   length      = 16
<<<<<<   type        = open (0x00000001)
<<<<<<   transaction = 1
<<<<<< Contents:
<<<<<<   max_control_transfer = 4096

[30 May 2013, 09:18:12] [Debug] [/dev/cdc-wdm0] Received message...
>>>>>> RAW:
>>>>>>   length = 64
>>>>>>   data   = 07:00:00:80:40:00:00:00:00:00:00:00:01:00:00:00:00:00:00:00:4B:F3:84:76:1E:6A:41:DB:B1:D8:BE:D2:89:C2:5B:DB:01:00:00:00:14:00:00:00:01:00:00:00:F0:00:00:00:02:00:00:00:50:00:00:00:16:00:00:00

[30 May 2013, 09:18:12] [Debug] [/dev/cdc-wdm0] Received message (translated)...
>>>>>> Header:
>>>>>>   length      = 64
>>>>>>   type        = indicate-status (0x80000007)
>>>>>>   transaction = 0
>>>>>> Fragment header:
>>>>>>   total   = 1
>>>>>>   current = 0
>>>>>> Contents:
>>>>>>   service = 'phonebook' (4bf38476-1e6a-41db-b1d8-bed289c25bdb)
>>>>>>   cid     = 'configuration' (0x00000001)

[30 May 2013, 09:18:12] [Debug] [/dev/cdc-wdm0] Received message (translated)...
>>>>>> Header:
>>>>>>   length      = 64
>>>>>>   type        = indicate-status (0x80000007)
>>>>>>   transaction = 0
>>>>>> Fragment header:
>>>>>>   total   = 1
>>>>>>   current = 0
>>>>>> Contents:
>>>>>>   service = 'phonebook' (4bf38476-1e6a-41db-b1d8-bed289c25bdb)
>>>>>>   cid     = 'configuration' (0x00000001)

[30 May 2013, 09:18:12] [Debug] [/dev/cdc-wdm0] Received message...
>>>>>> RAW:
>>>>>>   length = 16
>>>>>>   data   = 01:00:00:80:10:00:00:00:01:00:00:00:00:00:00:00

[30 May 2013, 09:18:12] [Debug] [/dev/cdc-wdm0] Received message (translated)...
>>>>>> Header:
>>>>>>   length      = 16
>>>>>>   type        = open-done (0x80000001)
>>>>>>   transaction = 1
>>>>>> Contents:
>>>>>>   status error = 'None' (0x00000000)

[30 May 2013, 09:18:12] [Debug] MBIM Device at '/dev/cdc-wdm0' ready
[30 May 2013, 09:18:12] [Debug] [/dev/cdc-wdm0] Sent message...
<<<<<< RAW:
<<<<<<   length = 52
<<<<<<   data   = 03:00:00:00:34:00:00:00:02: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:0A:00:00:00:01:00:00:00:04:00:00:00:00:00:00:00

[30 May 2013, 09:18:12] [Debug] [/dev/cdc-wdm0] Sent message (translated)...
<<<<<< Header:
<<<<<<   length      = 52
<<<<<<   type        = command (0x00000003)
<<<<<<   transaction = 2
<<<<<< Fragment header:
<<<<<<   total   = 1
<<<<<<   current = 0
<<<<<< Contents:
<<<<<<   service = 'basic-connect' (a289cc33-bcbb-8b4f-b6b0-133ec2aae6df)
<<<<<<   cid     = 'packet-service' (0x0000000a)
<<<<<<   type    = 'set' (0x00000001)

[30 May 2013, 09:18:12] [Debug] [/dev/cdc-wdm0] Received message...
>>>>>> RAW:
>>>>>>   length = 48
>>>>>>   data   = 03:00:00:80:30:00:00:00:02: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:0A:00:00:00:0E:00:00:00:00:00:00:00

[30 May 2013, 09:18:12] [Debug] [/dev/cdc-wdm0] Received message (translated)...
>>>>>> Header:
>>>>>>   length      = 48
>>>>>>   type        = command-done (0x80000003)
>>>>>>   transaction = 2
>>>>>> Fragment header:
>>>>>>   total   = 1
>>>>>>   current = 0
>>>>>> Contents:
>>>>>>   status error = 'NotInitialized' (0x0000000e)
>>>>>>   service      = 'basic-connect' (a289cc33-bcbb-8b4f-b6b0-133ec2aae6df)
>>>>>>   cid          = 'packet-service' (0x0000000a)

[30 May 2013, 09:18:12] [Debug] [/dev/cdc-wdm0] Received message (translated)...
>>>>>> Header:
>>>>>>   length      = 48
>>>>>>   type        = command-done (0x80000003)
>>>>>>   transaction = 2
>>>>>> Fragment header:
>>>>>>   total   = 1
>>>>>>   current = 0
>>>>>> Contents:
>>>>>>   status error = 'NotInitialized' (0x0000000e)
>>>>>>   service      = 'basic-connect' (a289cc33-bcbb-8b4f-b6b0-133ec2aae6df)
>>>>>>   cid          = 'packet-service' (0x0000000a)

[30 May 2013, 09:18:12] [Debug] Keeping device open...

error: operation failed: NotInitialized


Testing with my primitive perl script support this assumption.  If I
send OPEN after initializing and attaching, then the next attach will
fail with MBIM_STATUS_NOT_INITIALIZED.

I believe the --no-close isn't enough.  We also need a way to tell
mbimcli that the device is already open, just like qmicli has both
--client-cid=<x> and --client-no-release-cid.


> When querying the subscriber ready status, it has a segfault after
> many string conversion errors; subsequent runs complain about a
> failing assertion. The errors came on stderr and the verbose output is
> on stdout, so there are two attached files for that.

This I've never seen.


Bjørn


More information about the libmbim-devel mailing list