ModemManager with Sierra EM7305 and GPS
Dan Williams
dcbw at redhat.com
Tue Jun 13 15:11:15 UTC 2017
On Mon, 2017-06-12 at 22:03 +0000, Petr Kloc wrote:
> Hi Dan
>
> Thank you for the link. It allowed me to activate the NMEA port and
> to use my GPS capability. However I still need to find a way to
> activate the modem at the same time.
>
>
> My device is Toshiba Z20T-C. I use the udev rules from https://wiki.a
> rchlinux.org/index.php/Toshiba_Portege_Z20t to switch the device
> configuration and to force-load the modules. Unfortunately I end up
> with either qcserial or qmi_wwan grabbing all the interfaces
> depending on the order specified in the .rules file. I have a feeling
> that is the root of the problem. Do you know, if qmi_wwan require AT
> command port to be accessible at the same time?
Those directions are somewhat suspect, but necessary as qmi_wwan
doesn't have the right IDs for that device yet.
Can you remove the udev rules, reboot, then as root:
1) lsusb -v -d 1199:9063
2) cd -P /sys/class/usbmisc/cdc-wdm0/device/driver/*-*.*/../
3) echo "1" > bConfigurationValue
4) wait about 20 - 30 seconds for it to come back
5) lsusb -v -d 1199:9063
and we'll see what *should* really be happening, and then add the
device IDs to the right kernel drivers.
Thanks!
Dan
> In an attachment you can find logs from ModemManager for qcserial an
> qmi_wwan respectively alongside the output of usb-devices.
>
> Regards
> Petr Kloc
>
>
>
>
>
> --------------------------------------------
> On Mon, 6/12/17, Dan Williams <dcbw at redhat.com> wrote:
>
> Subject: Re: ModemManager with Sierra EM7305 and GPS
> To: "Petr Kloc" <petr_kloc at yahoo.com>, modemmanager-devel at lists.free
> desktop.org
> Date: Monday, June 12, 2017, 8:27 PM
>
>
> Yes, the MBIM standard does not define any kind of location API, so
> we are left with non-standard/proprietary mechanism when the modem
> supports MBIM. That could be via AT commands if the modem also
> exposes an AT port, or it could be that we have to reverse-engineer
> an MBIM proprietary device service.
>
> Can you share ModemManager debug logs when the modem does not work
> correctly in this configuration? Assuming the modem is always
> connected, you can run ModemManager like so:
>
> sudo ModemManager --debug &> /tmp/mm.log
>
> and then attach mm.log to a reply (don't copy and paste into the
> mail, as that adds line breaks and makes it hard to read...).
>
> If you want GPS, then a mode that includes QMI would be easiest for
> you. ModemManager will then read location details through QMI and
> provide those for you via the D-Bus interface, eg something like:
>
> mmcli -m 0 --location-enable-gps-nmea
> mmcli -m 0 --location-set-gps-refresh-rate=5 (refresh every 5
> seconds)
> mmcli -m 0 --location-get-gps-nmea (report NMEA traces)
>
> Alternatively when you're in this mode, you may be able to use the
> NMEA port directly by doing what is suggested in:
> http://www.thinkwiki.org/wiki/Qualcomm_Gobi_2000#GPS
>
> Dan
More information about the ModemManager-devel
mailing list