InvalidTransition after flashing firmware

[Nathaniel Haggard]

After doing something like qmicli -d /dev/cdc-wdm0
--dms-select-stored-image=modem1,pri1

I set the modem as offline, then reset, and then rebooted the host system.
When it booted again MC7455 connected to tmobile, and

root at LEDE:~# qmicli -d /dev/cdc-wdm0 --dms-list-stored-images
[/dev/cdc-wdm0] Device list of stored images retrieved:

[0] Type:    'modem'
   Maximum: '4'

[modem0]
Unique ID:     '?_?'
Build ID:      '02.08.02.00_?'
Storage index: '1'
Failure count: '0'

[modem1]
Unique ID:     '?_?'
Build ID:      '02.24.03.00_?'
Storage index: '2'
Failure count: '0'

>>>>>>>>>> [CURRENT] <<<<<<<<<<
[modem2]
Unique ID:     '?_?'
Build ID:      '02.24.05.06_?'
Storage index: '4'
Failure count: '0'

[1] Type:    'pri'
   Maximum: '50'

[pri0]
Unique ID:     '002.027_000'
Build ID:      '02.24.05.06_ATT'

>>>>>>>>>> [CURRENT] <<<<<<<<<<
[pri1]
Unique ID:     '002.026_000'
Build ID:      '02.24.05.06_GENERIC'

[pri2]
Unique ID:     '002.022_000'
Build ID:      '02.24.03.00_SPRINT'

[pri3]
Unique ID:     '001.000_000'
Build ID:      '00.00.00.00_OEMPRI918'

[pri4]
Unique ID:     '002.034_000'
Build ID:      '02.24.05.06_VERIZON'

root at LEDE:~#


I guess select-stored-image is the last step when flashing new firmware, or
is there a way to avoid that step?  Help doesn't mention it
(qmi-firmware-update -H), so I'm curious.


On Wed, Sep 13, 2017 at 12:40 PM, Nathaniel Haggard <natester at gmail.com>
wrote:

> root at LEDE:~#  qmicli -p -d /dev/cdc-wdm0 --dms-get-firmware-preference
> firmware preference successfully retrieved:
> [image 0]
> Image type: 'modem'
> Unique ID:  '002.026_000'
> Build ID:   '"02.24.05.06_GENERIC'
> [image 1]
> Image type: 'pri'
> Unique ID:  '002.026_000'
> Build ID:   '"02.24.05.06_GENERIC'
> root at LEDE:~#  qmicli -p -d /dev/cdc-wdm0 --dms-list-stored-images
> [/dev/cdc-wdm0] Device list of stored images retrieved:
>
> [0] Type:    'modem'
>    Maximum: '4'
>
> [modem0]
> Unique ID:     '?_?'
> Build ID:      '02.08.02.00_?'
> Storage index: '1'
> Failure count: '0'
>
> [modem1]
> Unique ID:     '?_?'
> Build ID:      '02.24.03.00_?'
> Storage index: '2'
> Failure count: '0'
>
> [modem2]
> Unique ID:     '?_?'
> Build ID:      '02.24.05.06_?'
> Storage index: '4'
> Failure count: '0'
>
> [1] Type:    'pri'
>    Maximum: '50'
>
> [pri0]
> Unique ID:     '002.027_000'
> Build ID:      '02.24.05.06_ATT'
>
> [pri1]
> Unique ID:     '002.026_000'
> Build ID:      '02.24.05.06_GENERIC'
>
> [pri2]
> Unique ID:     '002.022_000'
> Build ID:      '02.24.03.00_SPRINT'
>
> [pri3]
> Unique ID:     '001.000_000'
> Build ID:      '00.00.00.00_OEMPRI918'
>
> [pri4]
> Unique ID:     '002.034_000'
> Build ID:      '02.24.05.06_VERIZON'
>
> root at LEDE:~#  qmicli -p -d /dev/cdc-wdm0 --dms-get-operating-mode
> [/dev/cdc-wdm0] Operating mode retrieved:
> Mode: 'low-power'
> Reason: 'unknown'
> HW restricted: 'no'
>
> On Wed, Sep 13, 2017 at 12:23 PM, Bjørn Mork <bjorn at mork.no> wrote:
>
>> Nathaniel Haggard <natester at gmail.com> writes:
>>
>> > After flashing the firmware to GENERIC (tmobile) on MC7455 I get an
>> error
>> > about InvalidTransition.
>>
>> It is failing to set the modem to 'online' mode from 'low power'
>> mode. My best guess is that this is becasue it is forced in low power
>> mode by a mismatch between the configured and installed firmware
>> versions.
>>
>> What's your output of
>>
>>  qmicli -p -d /dev/cdc-wdm0 --dms-get-firmware-preference
>>  qmicli -p -d /dev/cdc-wdm0 --dms-list-stored-images
>>  qmicli -p -d /dev/cdc-wdm0 --dms-get-operating-mode
>>
>>
>>
>> Bjørn
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/modemmanager-devel/attachments/20170913/4ed07ea3/attachment-0001.html>