aleksander/qmi-firmware-update v2: dms-list-stored-images on MC7430
Bjørn Mork
bjorn at mork.no
Wed Jan 18 21:26:42 UTC 2017
Could you please check at!impref? and
qmicli -d /dev/cdc-wdm0 --dms-list-stored-images
before trying out the “qmi-firmware-update" tool?
I suspect that the “fwdldarm” tool is uploading the images to the modem
partition, similar to what we saw with “qmi-firmware-update" when it
used AT!BOOTHOLD to switch into QDL mode. I did look at an old dump I
had of a SWI SDK MC7455 firmware update, and that one didn't modify any
image preferences. It just checked the revisions and booted into QDL
mode using the DMS 0x003e request, just like I've seen on the MC7710.
So I wonder if you are actually running 02.20.03.00 even if it doesn't
show up in any of the 4 slots? And if so, does it show up in
'dms-list-stored-images', possibly with a '0' index?
Bjørn
Sebastian Sjoholm <sebastian.sjoholm at gmail.com> writes:
> Hi,
>
> Maybe not related, but I thought to share it anyway.
>
> I have been using the “fwdldarm” tool from the Sierra SDK to do firmware upgrades on MC7304 and it has been working well, but with MC7455 I have had lot of issues. And it seems that I get the PRI file updated properly but not the firmware file.
>
> Example, I can see that the firmware is still 02.08.02, but the PRI file is from the new firmware file 2.20.03.
>
> at!image?
> TYPE SLOT STATUS LRU FAILURES UNIQUE_ID BUILD_ID
> FW 1 GOOD 1 0 0 ?_? 02.08.02.00_?
> FW 2 EMPTY 0 0 0
> FW 3 EMPTY 0 0 0
> FW 4 EMPTY 0 0 0
> Max FW images: 4
> Active FW image is at slot 1
>
> TYPE SLOT STATUS LRU FAILURES UNIQUE_ID BUILD_ID
> PRI FF GOOD 0 0 0 002.017_000 02.20.03.00_GENERIC
> Max PRI images: 50
>
> OK
>
> I posted on sierra forum as well (https://forum.sierrawireless.com/viewtopic.php?f=117&t=10072&p=39831), but there does not seem to be any clues why this happens.
>
> But it seems that when using the Gobi driver the “fwdldarm” seems to work as intended, but as I have no interest to start trying to get the gobi into a system with kernel 4.6 and newer, so I have not investigated that more.
>
> I will setup a MC7455 and test the “qmi-firmware-update” as well.
>
> Regards,
> Sebastian
>
>
>> On Jan 18, 2017, at 17:44 , Christophe Ronco <c.ronco-externe at kerlink.fr> wrote:
>>
>> On my side, I put firmware 2.14, 2.20 and 2.23 on my MC7430:
>> root at klk-lpbs_040070:~ # 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.23.00.00_?'
>> Storage index: '1'
>> Failure count: '0'
>>
>> [modem1]
>> Unique ID: '?_?'
>> Build ID: '02.20.03.00_?'
>> Storage index: '2'
>> Failure count: '1'
>>
>> >>>>>>>>>> [CURRENT] <<<<<<<<<<
>> [modem2]
>> Unique ID: '?_?'
>> Build ID: '02.14.03.00_?'
>> Storage index: '3'
>> Failure count: '0'
>>
>> [1] Type: 'pri'
>> Maximum: '50'
>>
>> >>>>>>>>>> [CURRENT] <<<<<<<<<<
>> [pri0]
>> Unique ID: '001.001_000'
>> Build ID: '02.20.03.00_DOCOMO'
>>
>> [pri1]
>> Unique ID: '002.018_000'
>> Build ID: '02.23.00.00_GENERIC'
>>
>> [pri2]
>> Unique ID: '002.013_001'
>> Build ID: '02.14.03.00_TELSTRA'
>>
>>
>> First, I don't have to reboot my board after a dms-select-stored-image, I just have to be patient. After reset modem devices disappear, one minute later they reappear, next command ends with timeout and then modem is back alive.
>> I was power cycling my modem or my board but that was just because I am not patient enough.
>>
>> I tried to select the three stored images one after the other. Here are my results:
>> Selecting 2.20 (modem1, pri0)
>> root at klk-lpbs_040070:~ # qmicli -d /dev/cdc-wdm0 --dms-get-revision
>> [/dev/cdc-wdm0] Device revision retrieved:
>> Revision: 'SWI9X30C_02.20.03.00 r6691 CARMD-EV-FRMWR2 2016/06/30 10:54:05'
>> root at klk-lpbs_040070:~ # 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.23.00.00_?'
>> Storage index: '1'
>> Failure count: '0'
>>
>> [modem1]
>> Unique ID: '?_?'
>> Build ID: '02.20.03.00_?'
>> Storage index: '2'
>> Failure count: '1'
>>
>> >>>>>>>>>> [CURRENT] <<<<<<<<<<
>> [modem2]
>> Unique ID: '?_?'
>> Build ID: '02.14.03.00_?'
>> Storage index: '3'
>> Failure count: '0'
>>
>> [1] Type: 'pri'
>> Maximum: '50'
>>
>> >>>>>>>>>> [CURRENT] <<<<<<<<<<
>> [pri0]
>> Unique ID: '001.001_000'
>> Build ID: '02.20.03.00_DOCOMO'
>>
>> [pri1]
>> Unique ID: '002.018_000'
>> Build ID: '02.23.00.00_GENERIC'
>>
>> [pri2]
>> Unique ID: '002.013_001'
>> Build ID: '02.14.03.00_TELSTRA'
>>
>> root at klk-lpbs_040070:~ #
>>
>> Selecting 2.14 (modem2, pri2)
>> root at klk-lpbs_040070:~ # qmicli -d /dev/cdc-wdm0 --dms-get-revision
>> [/dev/cdc-wdm0] Device revision retrieved:
>> Revision: 'SWI9X30C_02.14.03.00 r6134 CARMD-EV-FRMWR2 2016/03/28 14:34:14'
>> root at klk-lpbs_040070:~ # 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.23.00.00_?'
>> Storage index: '1'
>> Failure count: '0'
>>
>> [modem1]
>> Unique ID: '?_?'
>> Build ID: '02.20.03.00_?'
>> Storage index: '2'
>> Failure count: '0'
>>
>> >>>>>>>>>> [CURRENT] <<<<<<<<<<
>> [modem2]
>> Unique ID: '?_?'
>> Build ID: '02.14.03.00_?'
>> Storage index: '3'
>> Failure count: '1'
>>
>> [1] Type: 'pri'
>> Maximum: '50'
>>
>> [pri0]
>> Unique ID: '001.001_000'
>> Build ID: '02.20.03.00_DOCOMO'
>>
>> [pri1]
>> Unique ID: '002.018_000'
>> Build ID: '02.23.00.00_GENERIC'
>>
>> >>>>>>>>>> [CURRENT] <<<<<<<<<<
>> [pri2]
>> Unique ID: '002.013_001'
>> Build ID: '02.14.03.00_TELSTRA'
>>
>> Selecting 2.23 (modem0, pri1)
>> root at klk-lpbs_040070:~ # qmicli -d /dev/cdc-wdm0 --dms-get-revision
>> [/dev/cdc-wdm0] Device revision retrieved:
>> Revision: 'SWI9X30C_02.23.00.00 r6843 CARMD-EV-FRMWR2 2016/10/22 08:55:04'
>> root at klk-lpbs_040070:~ # 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.23.00.00_?'
>> Storage index: '1'
>> Failure count: '1'
>>
>> >>>>>>>>>> [CURRENT] <<<<<<<<<<
>> [modem1]
>> Unique ID: '?_?'
>> Build ID: '02.20.03.00_?'
>> Storage index: '2'
>> Failure count: '0'
>>
>> [modem2]
>> Unique ID: '?_?'
>> Build ID: '02.14.03.00_?'
>> Storage index: '3'
>> Failure count: '0'
>>
>> [1] Type: 'pri'
>> Maximum: '50'
>>
>> [pri0]
>> Unique ID: '001.001_000'
>> Build ID: '02.20.03.00_DOCOMO'
>>
>> >>>>>>>>>> [CURRENT] <<<<<<<<<<
>> [pri1]
>> Unique ID: '002.018_000'
>> Build ID: '02.23.00.00_GENERIC'
>>
>> [pri2]
>> Unique ID: '002.013_001'
>> Build ID: '02.14.03.00_TELSTRA'
>>
>> root at klk-lpbs_040070:~ #
>>
>> So for 2.20 and 2.23, index_of_running_image seems to be image storage index and for 2.14, index_of_running_image seems to be imageindex in list.
>>
>> I don't understand the logic behind that.
>>
>> Christophe
>> _______________________________________________
>> libqmi-devel mailing list
>> libqmi-devel at lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/libqmi-devel
More information about the libqmi-devel
mailing list