RFC: aleksander/qmi-firmware-update branch

[Dan Williams]

On Wed, 2017-01-11 at 16:02 +0100, Bjørn Mork wrote:
> 
> On January 11, 2017 3:24:13 PM CET, Aleksander Morgado <aleksander at al
> eksander.es> wrote:
> > On Thu, Jan 5, 2017 at 8:09 PM, Bjørn Mork <bjorn at mork.no> wrote:
> > > > > But resetting by USB device ID and then uploading in QDL mode
> > > > > work
> > > > > flawlessly.  Although I didn't expect "reset" to use the AT
> > 
> > command:
> > > > > 
> > > > 
> > > > It was the "suggested" way to reset the devices that don't
> > > > support
> > 
> > the
> > > > set firwmware preference command, at least that is what I could
> > 
> > find.
> > > 
> > > OK.  But what about modems without an AT port?
> > > 
> > > I don't remember and am too lazy to search old mailing list
> > > posts,
> > 
> > but I
> > > believe the MC7710 updater had a "magic" DMS boot-and-hold QMI
> > 
> > request.
> > > 0x003e?
> > 
> > Where did you see that command?
> 
> In requests sent by the mc7710 firmware updater from the SWI SDK.

DMS 0x003E is eQMI_DMS_SET_FIRMWARE_ID though... right?

Dan

> 
> > I implemented support for "DMS Get/Set Boot Image Download Mode"
> > (0x004f and 0x0050), but those doesn't seem to work in the Sierra
> > modules. The command does work in a Novatel E396 I have around,
> > though.
> 
> I wonder if these requests are vendor specific, or maybe reflecting a
> specific bootloader or image format?
> 
> 
> Bjørn