Assistance with --dms-set-firmware-preference

[Bjørn Mork]

Paul Gildea <gildeap at tcd.ie> writes:

> Hi, I am trying to use the above command instead of the AT commands to set
> the firmware preference. The command appears to run successfully as below.
> An unexpected outcome (to me) is that it says that the modem will wait in
> QDL mode once I reboot it (and it did stay in that mode, which it currently
> is stuck in), why is this?

Well, that is a a feature when you specify files which are not there.

I believe the QDL mode will timeout eventually if you don't load any new
files, and boot into low power mode so you can fix the image preferences


> Should it not just switch to the firmware I have
> chosen that is already stored on the device, did I do something wrong?
>
> *--dms-set-firmware-preference=01.08.04.00_VERIZON,002.015_000,verizon*


I could be wrong, but I believe that is supposed to be 

   --dms-set-firmware-preference=01.08.04.00,002.015_000,verizon

Would be good to see the output of

   --dms-get-firmware-preference

if/when your modem boots into application mode again.

> [14 Nov 2018, 08:06:35] -Warning ** [/dev/cdc-wdm0] requested auto mode but
> no MBIM QMUX support available
> [/dev/cdc-wdm0] Firmware preference successfully selected
>
>         You may want to power-cycle the modem now, or just set it offline
> and reset it:
>                 $> sudo qmicli ... --dms-set-operating-mode=offline
>                 $> sudo qmicli ... --dms-set-operating-mode=reset
>
>
> * After reset, the modem will wait in QDL mode for new firmware.
> Images to download: 'pri'*


This means that the 'modem' image was found, but the selected 'pri' was
not. 

>         [1] Type:    'pri'
>             Maximum: '50'
>
>                 [pri0]
>                 Unique ID:     '002.008_002'
>                 Build ID:      '01.07.02.00_ATT'
>
>                 >>>>>>>>>> [CURRENT] <<<<<<<<<<
>                 [pri1]
>                 Unique ID:     '002.019_000'
>                 Build ID:      '01.09.04.00_GENERIC'
>
>                 [pri2]
>                 Unique ID:     '*002.015_000*'
>                 Build ID:      '*01.08.04.00_VERIZON*'
>


So the "01.08.04.00_VERIZON" build id is there, but the firmware
might be looking for 01.08.04.00_VERIZON_VERIZON if my assumption is
correct.



Bjørn