Firmware update of MC7455 timing out.

Paul Gildea gildeap at tcd.ie
Fri Dec 1 16:19:13 UTC 2017


Thanks guys, setting the firmware to the default or Verizon image that came
pre-installed worked fine and I regained my radio power modes.
Unusual that I can't upgrade to the official latest firmware on the Sierra
Wireless site (the versions do seem to match somewhat SWI9X30C_02.24.05.06.cwe
and SWI9X30C_02.24.05.06_VERIZON_002.034_000.nvu). I'll try and play around
to get them on there somehow.

--
Paul

On 30 November 2017 at 18:14, Dan Williams <dcbw at redhat.com> wrote:

> On Thu, 2017-11-30 at 18:35 +0100, Bjørn Mork wrote:
> > Paul Gildea <gildeap at tcd.ie> writes:
> >
> > > Thanks for the help Dan,
> > >
> > > Here are both methods for completeness! (The output is the same for
> > > two
> > > MC7455's that I tried to upgrade.)
> > >
> > > AT!ENTERCND="A710"
> > > OK
> > > AT!GOBIIMPREF?
> > > !GOBIIMPREF:
> > >  preferred fw version:    02.24.05.06
> > >  preferred carrier name:  VERIZON
> > >  preferred config name:   VERIZON_002.034_000
> > >  current fw version:      02.08.02.00
> > >
> > >  current carrier name:    GENERIC
> > >
> > >  current config name:     GENERIC_002.007_001
> > >
> > >
> > >
> > >  fw version mismatch
> > >
> > >  carrier name mismatch
> > >
> > >  config name mismatch
> > >
> > >
> > >
> > > OK
> >
> > This is a typical result of failed upgrades: You have told the modem
> > to
> > use the VERIZON 02.24.05.06 firmware, but this version is not yet
> > installed.
> >
> > I don't know why your firmware upgrades fail, but fixing the low
> > power
> > issue by switching to one of the installed images is easy:
> >
> >  AT!ENTERCND="A710"
> >  AT!IMPREF="GENERIC"
> >  AT!RESET
> >
> > or maybe you want
> >
> >  AT!IMPREF="VERIZON"
> >
> > instead? Not sure how that will work out, but I see that you do have
> > a
> > 02.05.07.00 verizon image installed.
> >
> >
> > > qmicli -p -d /dev/cdc-wdm2 --dms-list-stored-images
> >
> > You can list the same in the AT command interface:
> >
> > AT!IMAGE?
> >
> > Or maybe AT!GOBIIMAGE? Some firmware versions use AT!GOBIIMPREF and
> > AT!GOBIIMAGE, as well as the GOBIIM flag.  I believe newer firmwares
> > prefer AT!IMPREF and AT!IMAGE, and use the IMSWITCH flag.  The
> > meaning
> > is the same.  Whatever works is fine.
>
> Also, typically you want the modem and PRI images to match.  For
> example, note that you have a modem image 02.05.07.00_? and a PRI image
> 02.05.07.00_VERIZON.  These obviously match and could be used with --
> dms-set-firmware-preference.
>
> Once you do get the images uploaded to the modem somehow, you can play
> around with the --set-firmware-preference to select the right combo.
> The PRI images are like carrier "profiles" of a sort.  So if for
> example you have a modem image with no CDMA/EVDO support but you try to
> use that with a Verizon PRI that's not gonna work.  But with ATT or
> TMobile it might.  That kind of thing.
>
> Dan
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/libqmi-devel/attachments/20171201/da1c75ce/attachment.html>


More information about the libqmi-devel mailing list