Quectel em12-g minimal kernel version

[Alexander Dydychkin]

Nicholas Smith, how do you change the mode manually?
I try to:
sudo flock -x /dev/ttyUSB2 minicom -D /dev/ttyUSB2
AT!ENTERCND="A710"
AT!USBCOMP="1,3,10D"
AT!RESET

But it does not help.
In addition am I correct that I can re-flash the Quectel only by using
qmu-firmware-update?


Bjørn Mork considering the qmicli:
sudo mbimcli -d /dev/cdc-wdm2  --query-device-services
Service: 'qmi'
UUID: [d1a30bc2-f97a-6e43-bf65-c7e24fb0f0d3]:
DSS payload: 0
Max DSS instances: 0
CIDs: msg (1)

So it seems that it should work but:
sudo qmicli -p -d /dev/cdc-wdm2 --device-open-mbim --nas-get-signal-strength
[/dev/cdc-wdm2] Successfully got signal strength
Current:
        Network 'umts': '-110 dBm'
RSSI:
        Network 'umts': '-110 dBm'
ECIO:
        Network 'umts': '-15.0 dBm'
IO: '-106 dBm'
SINR (8): '9.0 dB'

Yes, it is ok but the commands like:
sudo qmicli -p -d /dev/cdc-wdm2 --device-open-mbim --dms-list-stored-images
error: couldn't list stored images: QMI protocol error (57):
'Wms.InvalidMessageId'
They do not work. Is it a bug or am I doing something not correctly?

Thanks for the help.






пт, 25 июн. 2021 г. в 03:24, Nicholas Smith <nicholas at nbembedded.com>:

> Actually that QMI service is there....
>
> Service: 'qmi'
>              UUID: [d1a30bc2-f97a-6e43-bf65-c7e24fb0f0d3]:
>       DSS payload: 0
> Max DSS instances: 0
>              CIDs: msg (1)
>
> ... but when I try to use qmicli with --device-open-mbim I get this...
>
> qmicli -p -d /dev/cdc-wdm0 --device-open-mbim --nas-get-signal-strength
> [25 Jun 2021, 10:17:27] -Warning ** [/dev/cdc-wdm0] requested MBIM
> mode but no MBIM QMUX support available
> error: couldn't open the QmiDevice: Could not create endpoint
>
> ... Even though I am compiling libqmi  with --enable-mbim-qmux (on OpenWrt)
>
>
> All the best,
> Nick
>
>
>
>
> On Fri, 25 Jun 2021 at 09:22, Bjørn Mork <bjorn at mork.no> wrote:
> >
> > Nicholas Smith <nicholas at nbembedded.com> writes:
> >
> > > I can confirm that the Quectel EM12-G most certainly does not play
> > > nice with qmi_wwan (at least on the vendor firmware versions I have
> > > tested, which includes several, including the latest).  The module
> > > always inexplicably crashes after anywhere from between a couple of
> > > hours to a couple of days of uptime.  When in MBIM mode it is stable,
> > > but you cannot use qmicli to get detailed NAS information, or select
> > > bands, etc... so you lose a huge amount of useful functionality.  So,
> > > if I want to do anything out of the ordinary, I temporarily switch it
> > > into QMI mode before switching back to MBIM mode.
> >
> > So it doesn't export the QMI service in MBIM mode?  That's pretty
> > unusual for a Qualcomm based modem.
> >
> > You can check this with e.g
> >
> >  mbimcli -d /dev/cdc-wdm0  --query-device-services
> >
> > We normally expect an entry like:
> >
> >                          Service: 'qmi'
> >                              UUID:
> [d1a30bc2-f97a-6e43-bf65-c7e24fb0f0d3]:
> >                       DSS payload: 0
> >                 Max DSS instances: 0
> >                              CIDs: msg (1)
> >
> >
> > This MBIM service can be used by libqmi/qmicli for full QMI access.  See
> > the --device-open-mbim option.  Actually, it defaults to autodetecting,
> > so accessing QMI services should just work.
> >
> >
> >
> > Bjørn
> _______________________________________________
> libqmi-devel mailing list
> libqmi-devel at lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/libqmi-devel
>


-- 
With best regards,
Alexander
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/libqmi-devel/attachments/20210625/30015ff8/attachment-0001.htm>