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

Christophe Ronco c.ronco-externe at kerlink.fr
Wed Jan 18 16:44:53 UTC 2017


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


More information about the libqmi-devel mailing list