Sierra Wireless EM7355
Aleksander Morgado
aleksander at aleksander.es
Mon Jun 23 09:17:06 PDT 2014
On Mon, Jun 23, 2014 at 4:07 PM, Erinn Looney-Triggs
<erinn.looneytriggs at gmail.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> On 06/21/2014 05:58 AM, Bjørn Mork wrote:
>> Aleksander Morgado <aleksander at aleksander.es> writes:
>>> On Fri, Jun 20, 2014 at 8:37 PM, Erinn Looney-Triggs
>>> <erinn.looneytriggs at gmail.com> wrote:
>>>> [20 Jun 2014, 12:36:33] [Debug] [/dev/cdc-wdm0] Sent message
>>>> (translated)... <<<<<< Header: <<<<<< length = 16 <<<<<<
>>>> type = open (0x00000001) <<<<<< transaction = 3 <<<<<<
>>>> Contents: <<<<<< max_control_transfer = 4096
>>>>
>>>> [20 Jun 2014, 12:36:33] [Debug] [/dev/cdc-wdm0] Received
>>>> message...
>>>>>>>>>> RAW: length = 16 data =
>>>>>>>>>> 01:00:00:80:10:00:00:00:03:00:00:00:02:00:00:00
>>>>
>>>> error: couldn't open the MbimDevice: Failure
>>>
>>>
>>> Oh well... this is the device returning
>>> MBIM_STATUS_ERROR_FAILURE during the Open sequence... No idea.
>>> Maybe the device is already open and we shouldn't re-open it?
>>
>> Hmm, it would not be correct to return failure in that case. The
>> spec is quite explicit that the function should try to resyncronize
>> state again by silently closing the existing session and opening a
>> new one, returning success.
>>
>> What the spec says and what the firmware does are of course
>> different things, but I cannot remember having seen failures in
>> such cases either.
>>
>>> Can you try to run it again, but this time like this?
>>>
>>> $ sudo mbimcli -d /dev/cdc-wdm0 --query-device-caps --verbose
>>> --no-open=10
>>
>> Yes, that would be useful anyway just to eliminate that cause.
>>
>> I wonder what else could make the open fail? I note that the
>> firmware could have returned MBIM_STATUS_BUSY if that was the
>> problem. 'FAILURE' seems so much more permanent...
>>
>>
>> Bjørn
>>
>
> Ok y'all here you go:
>
> sudo mbimcli -d /dev/cdc-wdm0 --query-device-caps --verbose --no-open=10
> [23 Jun 2014, 08:03:55] [Debug] [/dev/cdc-wdm0] Queried max control
> message size: 4096
> [23 Jun 2014, 08:03:55] [Debug] MBIM Device at '/dev/cdc-wdm0' ready
> [23 Jun 2014, 08:03:55] [Debug] Asynchronously querying device
> capabilities...
> [23 Jun 2014, 08:03:55] [Debug] [/dev/cdc-wdm0] Sent message...
> <<<<<< RAW:
> <<<<<< length = 48
> <<<<<< data =
> 03:00:00:00:30:00:00:00:0A: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:01:00:00:00:00:00:00:00:00:00:00:00
>
> [23 Jun 2014, 08:03:55] [Debug] [/dev/cdc-wdm0] Sent message
> (translated)...
> <<<<<< Header:
> <<<<<< length = 48
> <<<<<< type = command (0x00000003)
> <<<<<< transaction = 10
> <<<<<< Fragment header:
> <<<<<< total = 1
> <<<<<< current = 0
> <<<<<< Contents:
> <<<<<< service = 'basic-connect' (a289cc33-bcbb-8b4f-b6b0-133ec2aae6df)
> <<<<<< cid = 'device-caps' (0x00000001)
> <<<<<< type = 'query' (0x00000000)
>
> [23 Jun 2014, 08:03:55] [Debug] [/dev/cdc-wdm0] Received message...
>>>>>>> RAW: length = 16 data =
>>>>>>> 04:00:00:80:10:00:00:00:0A:00:00:00:05:00:00:00
>
> [23 Jun 2014, 08:03:55] [Debug] [/dev/cdc-wdm0] Received message
> (translated)...
>>>>>>> Header: length = 16 type = function-error
>>>>>>> (0x80000004) transaction = 10 Contents: error =
>>>>>>> 'NotOpened' (0x00000005)
>
> error: operation failed: Transaction timed out
> [23 Jun 2014, 08:04:05] [Debug] [/dev/cdc-wdm0] Sent message...
> <<<<<< RAW:
> <<<<<< length = 12
> <<<<<< data = 02:00:00:00:0C:00:00:00:0B:00:00:00
>
> [23 Jun 2014, 08:04:05] [Debug] [/dev/cdc-wdm0] Sent message
> (translated)...
> <<<<<< Header:
> <<<<<< length = 12
> <<<<<< type = close (0x00000002)
> <<<<<< transaction = 11
>
> [23 Jun 2014, 08:04:05] [Debug] [/dev/cdc-wdm0] Received message...
>>>>>>> RAW: length = 16 data =
>>>>>>> 02:00:00:80:10:00:00:00:0B:00:00:00:00:00:00:00
>
> [23 Jun 2014, 08:04:05] [Debug] Device closed
>
Ok, so NotOpened error, which was the expected thing.
So, all in all, we still don't have a clear idea why the modem returns
Failure to the Open requests. I'll try to ask Sierra.
--
Aleksander
https://aleksander.es
More information about the ModemManager-devel
mailing list