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

[Christophe Ronco]

Hi,


I used qmi-firmware-update to upgrade software of my MC7430 modem. I had 
a 2.14 software and upgraded to a 2.20. Here is software before upgrade:

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'

         >>>>>>>>>> [CURRENT] <<<<<<<<<<
         [modem0]
         Unique ID:     '?_?'
         Build ID:      '02.14.03.00_?'
         Storage index: '1'
         Failure count: '0'

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

         >>>>>>>>>> [CURRENT] <<<<<<<<<<
         [pri0]
         Unique ID:     '002.012_000'
         Build ID:      '02.14.03.00_GENERIC'


Upgrade was OK, here is the log:

root at klk-lpbs_040070:~ # qmi-firmware-update --update --cdc-wdm 
/dev/cdc-wdm0 /user/SWI9X30C_02.20.03.00_DoCoMo/SWI9X30C_02.20.03.00.cwe 
/user/SWI9X30C_02.2003.00_DoCoMo/SWI9X30C_02.20.03.00_DoCoMo_001.001_000.nvu 

loading device information before the update...
setting firmware preference:
   firmware version: '02.20.03.00'
   config version:   '001.001_000'
   carrier:          'DOCOMO'
rebooting in download mode...
download mode detected
downloading cwe image: SWI9X30C_02.20.03.00.cwe (64.4 MB)...
finalizing download... (may take more than one minute, be patient)
successfully downloaded in 69.91s (920.9 kB/s)
downloading cwe image: SWI9X30C_02.20.03.00_DoCoMo_001.001_000.nvu (9.0 
kB)...
finalizing download... (may take more than one minute, be patient)
successfully downloaded in 0.06s (145.5 kB/s)
rebooting in normal mode...
normal mode detected

------------------------------------------------------------------------
     NOTE: in order to validate which is the firmware running in the
     module, the program will wait for a complete boot; this process
     may take some time and several retries.
------------------------------------------------------------------------

waiting some time for the device to boot...
loading device information after the update (1/12)...
waiting some time for the device to boot...
loading device information after the update (2/12)...

------------------------------------------------------------------------

    original firmware revision was:
    SWI9X30C_02.14.03.00 r6134 CARMD-EV-FRMWR2 2016/03/28 14:34:14
       image 'modem': unique id '002.012_000', build id 
'02.14.03.00_GENERIC'
       image 'pri': unique id '002.012_000', build id '02.14.03.00_GENERIC'

    new firmware revision is:
    SWI9X30C_02.20.03.00 r6691 CARMD-EV-FRMWR2 2016/06/30 10:54:05
       image 'modem': unique id '001.001_000', build id '02.20.03.00_DOCOMO'
       image 'pri': unique id '001.001_000', build id '02.20.03.00_DOCOMO'

    NOTE: this device supports stored image management
    with qmicli operations:
       --dms-list-stored-images
       --dms-select-stored-image
       --dms-delete-stored-image

    NOTE: this device supports firmware preference management
    with qmicli operations:
       --dms-get-firmware-preference
       --dms-set-firmware-preference

------------------------------------------------------------------------

firmware update operation finished successfully


The only problem I saw is that after upgrade command, I need to reboot 
my board. Before reboot, I have :

root at klk-lpbs_040070:~ # qmicli -d /dev/cdc-wdm0 --dms-list-stored-images
error: couldn't create client for the 'dms' service: CID allocation 
failed in the CTL client: Transaction timed out

And no process is using /dev/cdc-wdm0. I don't use a 4.5 kernel and 
instead patched my 4.1 kernel with needed patches (from Bjorn), maybe I 
forgot a patch.


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 executed command with debug and saw three problems:

1) All Get Stored Image Info failed. Is it something you've seen?

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?

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.


I attach the debug log of --dms-list-stored-images command


Christophe

-------------- next part --------------
A non-text attachment was scrubbed...
Name: listStoredImages.log
Type: text/x-log
Size: 14747 bytes
Desc: not available
URL: <https://lists.freedesktop.org/archives/libqmi-devel/attachments/20170118/8da20007/attachment.bin>