Sierra Wireless 340u - NotInitialized
Aleksander Morgado
aleksander at lanedo.com
Thu May 30 05:06:19 PDT 2013
Hey,
>
>>
>> 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.
>>
>
> Gah, I really thought we wouldn't need it :)
>
> Opened a new bugreport for that:
> https://bugs.freedesktop.org/show_bug.cgi?id=65165
>
>
Can you guys take a look at the 'aleksander/session-support' branch? The
changes in the branch allow to have MBIM 'sessions', using --no-close
and --no-open, while keeping the transaction ID between mbimcli
commands. I updated the mbim-network script accordingly as well.
E.g.:
Open device:
$> sudo mbimcli -d /dev/cdc-wdm0 --noop --no-close
[/dev/cdc-wdm1] Session not closed:
TRID: '2'
Run a command:
$> sudo mbimcli -d /dev/cdc-wdm1 \
--query-radio-state \
--no-open=2 \
--no-close
[/dev/cdc-wdm1] Radio state retrieved:
Hardware Radio State: 'on'
Software Radio State: 'on'
[/dev/cdc-wdm1] Session not closed:
TRID: '3'
Close device:
$> sudo mbimcli -d /dev/cdc-wdm0 --noop --no-open=3
--
Aleksander
More information about the libmbim-devel
mailing list