aleksander/qmi-firmware-update v2: dms-list-stored-images on MC7430

[Aleksander Morgado]

On Thu, Jan 19, 2017 at 11:19 AM, Aleksander Morgado
<aleksander at aleksander.es> wrote:
> On Wed, Jan 18, 2017 at 9:06 PM, Aleksander Morgado
> <aleksander at aleksander.es> wrote:
>>> 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.
>>
>> That is actually in line with what you originally reported, isn't it?
>> In your first log the CURRENT was correctly selected, and you were
>> running 2.14. Only after going to 2.20 you got the issue, right? Time
>> for me to test that here.
>
> When a 02.20.03.xx image is selected, the "index of running image" in
> the "modem" images seems to refer to the storage index. The "index of
> running image" in the "pri" images refers to the index in the returned
> list.
>
> When a 02.14.03.xx image is selected, the "index of running image" in
> both the "modem" and "pri" images refers to the index in the running
> list, which is what we expected.
>
> I've also checked the values shown in AT!IMAGE? for both cases and
> this command does show the correct index always in the "Active FW
> image is at slot..." field (although they don't show the active slot
> for PRI images). Maybe they're using another command to query active
> fw image, equivalent to SLQSSwiGetFirmwareCurr() or something. Need to
> investigate that.

Interesting find; the customer release notes for the 9x30 firmware
says that in SWI9X30C 2.0 Release 15 (version 02.18.02.00) they
"fixed" this:

ID: 89775
Title: QMI_GET_STORED_IMAGES
Description: QMI_GET_STORED_IMAGES reports incorrect running image if
AUTO-SIM feature is enabled.

I wonder if that "fix" broke the QMI_GET_STORED_IMAGES current index logic.

-- 
Aleksander
https://aleksander.es