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

[Bjørn Mork]

Christophe Ronco <c.ronco-externe at kerlink.fr> writes:

> I see a small problem in dms-list-stored-images after that:
>
> 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.14.03.00_?'
>         Storage index: '1'
>         Failure count: '0'
>
>         [modem1]
>         Unique ID:     '?_?'
>         Build ID:      '02.20.03.00_?'
>         Storage index: '2'
>         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.012_000'
>         Build ID:      '02.14.03.00_GENERIC'
>
>
> There is no CURRENT for modem images.

I guess this is a minor issue I hope I have mentioned before.  I have
seen it as well, as an off-by-one in the modem index:

root at miraculix:/tmp# qmicli -p --device-open-mbim -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'

                >>>>>>>>>> [CURRENT] <<<<<<<<<<
                [modem1]
                Unique ID:     '?_?'
                Build ID:      '02.08.02.00_?'
                Storage index: '2'
                Failure count: '0'

                [modem2]
                Unique ID:     '?_?'
                Build ID:      '02.14.03.00_?'
                Storage index: '3'
                Failure count: '0'

                [modem3]
                Unique ID:     '?_?'
                Build ID:      '02.18.02.00_?'
                Storage index: '4'
                Failure count: '0'

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

                >>>>>>>>>> [CURRENT] <<<<<<<<<<
                [pri0]
                Unique ID:     '002.018_000'
                Build ID:      '02.23.00.00_GENERIC'

                [pri1]
                Unique ID:     '002.006_000'
                Build ID:      '02.08.02.00_ORANGE-EU'



As you might guess from the build ids, the above CURRENT 'modem' line is
wrong.  The modem is currently running the 'modem0' image, *not* the
'modem1' image.

I assume you see this as a missing CURRENT because the index points to a
non-existing 'modem2' image in your case.


> I executed command with debug and saw three problems:
>
> 1) All Get Stored Image Info failed. Is it something you've seen?

I believe that is known.

> 2) In List Stored Images response, index of running image is given but
> it is "2" with only image 0 and 1 after. Maybe it is a storage index
> and not an index in the table of answers. Do you know that?

I assume that is the off-by-one mentioned above.

> 3) In List Stored Images response,the two modem images have the same
> unique_id. I am not sure this is a problem because in
> --dms-select-stored-image command, both unique-id and build_id are
> used to identify an image.

The modem image ids are using wildcards to allow a single modem image to
be used with several different pri setting.  And both ids have to match,
so it's not a problem they unique_id is the same.  All modem images I've
seen so far are using '?_?' for the unique_id. That's the only value
making any sense.  If you change a modem image, then you will change the
version too.  You don't want two different modem images with the same
build_id.


Bjørn