how to support EM7565 modem
Bjørn Mork
bjorn at mork.no
Sat Nov 25 13:12:50 UTC 2017
Maybe the function configuration changed, removing the additional rmnet functions, but Sierra didn't update their AT command cli yet? I assume this is still an early firmware version.
The help text is similar to the EM7455 text, including the bugs.. Only the config type has been updated with the PCIE setting. Notice the claimed default. You aren't even allowed to select that value anymore. But you can probably enable adb by other methods, or maybe by unlocking more advanced AT features.
Bjørn
On November 25, 2017 1:02:32 AM GMT+01:00, Sebastian Sjoholm <sebastian.sjoholm at gmail.com> wrote:
>Hi,
>
>Here is some printouts from EM7565 that might be of interest. The
>addition
>in qcserial/qmi_wwan was enough, but I will do some more testing before
>I
>settle for the changes (and post them here).
>
>As default it shows only one ethernet interface, but there is a
>mismatch
>between the USB configuration which is 50D and the interfaces
>available. I
>will test to change these and see if has any effect. Still, it looks
>like
>default, but not according to USBCOMP. I check further.
>
>at+cgmm
>EM7565
>
>OK
>
>AT!USBCOMP?
>Config Index: 1
>Config Type: 3 (Generic)
>Interface bitmask: 0000050D (diag,nmea,modem,rmnet0,rmnet1)
>
>OK
>AT!USBCOMP=?
>!USBCOMP:
>AT!USBCOMP=<Config Index>,<Config Type>,<Interface bitmask>
> <Config Index> - configuration index to which the composition
>applies, should be 1
>
> <Config Type> - 1:MBIM USBIF, 2:PCIE USBIF, 3:Legacy-Generic,
>4:RNDIS
>
> <Interface bitmask> - DIAG - 0x00000001,
> NMEA - 0x00000004,
> MODEM - 0x00000008,
> RMNET0 - 0x00000100,
> RMNET1 - 0x00000400,
> MBIM - 0x00001000,
> e.g.
> 10D - diag, nmea, modem, rmnet interfaces enabled
> 1009 - diag, modem, mbim interfaces enabled
>
> The default configuration is:
> at!usbcomp=1,3,10F
>
>OK
>
>root at SBC-121:~# lsusb -t
>/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ci_hdrc/1p, 480M
> |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
> |__ Port 3: Dev 7, If 0, Class=Vendor Specific Class,
>Driver=qcserial, 480M
> |__ Port 3: Dev 7, If 2, Class=Vendor Specific Class,
>Driver=qcserial, 480M
> |__ Port 3: Dev 7, If 3, Class=Vendor Specific Class,
>Driver=qcserial, 480M
> |__ Port 3: Dev 7, If 8, Class=Vendor Specific Class,
>Driver=qmi_wwan, 480M
>/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ci_hdrc/1p, 480M
>root at SBC-121:~#
>
>[10848.564805] usb 2-1.3: new high-speed USB device number 7 using
>ci_hdrc
>[10848.715709] usb 2-1.3: config 1 has an invalid interface number: 8
>but
>max is 3
>[10848.715731] usb 2-1.3: config 1 has no interface number 1
>[10848.809963] usbcore: registered new interface driver usbserial
>[10848.810103] usbcore: registered new interface driver
>usbserial_generic
>[10848.819141] usbserial: USB Serial support registered for generic
>[10848.836865] usbcore: registered new interface driver qcserial
>[10848.836999] usbserial: USB Serial support registered for Qualcomm
>USB
>modem
>[10848.856466] usbcore: registered new interface driver cdc_wdm
>[10848.856620] qcserial 2-1.3:1.0: Qualcomm USB modem converter
>detected
>[10848.857303] usb 2-1.3: Qualcomm USB modem converter now attached to
>ttyUSB0
>[10848.860395] qcserial 2-1.3:1.2: Qualcomm USB modem converter
>detected
>[10848.863448] usb 2-1.3: Qualcomm USB modem converter now attached to
>ttyUSB1
>[10848.879937] qcserial 2-1.3:1.3: Qualcomm USB modem converter
>detected
>[10848.880268] usb 2-1.3: Qualcomm USB modem converter now attached to
>ttyUSB2
>[10848.884589] qmi_wwan 2-1.3:1.8: cdc-wdm0: USB WDM device
>[10848.885800] qmi_wwan 2-1.3:1.8 wwan0: register 'qmi_wwan' at
>usb-ci_hdrc.1-1.3, WWAN/QMI device, 9a:83:6a:a8:d9:2e
>[10848.889188] usbcore: registered new interface driver qmi_wwan
>
>-Sebastian
>
>
>On Mon, Nov 20, 2017 at 11:03 AM, Bjørn Mork <bjorn at mork.no> wrote:
>
>> Great. Please do. I'll leave it to you then.
>>
>> Please note that this modem should be added to the "qcserial" driver
>and
>> not to "option". It appears to use the same function layout as all
>> other modern Sierra Wireless modems.
>>
>> One extra item to check out: Can it be configured to expose addional
>> QMI/RMNET functions on interface number 10 and possibly 11? I guess
>it
>> might not, if they decided to use the new QMI muxing functionality
>> instead. But this need verification
>>
>>
>> Bjørn
>>
>> Sebastian Sjoholm <sebastian.sjoholm at gmail.com> writes:
>>
>> > Hi,
>> >
>> > I should receive EM7565 end of this week, if I am lucky. And since
>I am
>> > starting be on roll with this patching (or soon), I could do this
>one as
>> > well. If there is no critical rush on it, of course.
>> >
>> > -Sebastian
>> >
>> > On Mon, Nov 20, 2017 at 10:50 AM, dailijin <dailijin126 at 126.com>
>wrote:
>> >
>> >>
>> >> Hi Bjorn,
>> >>
>> >> I don't know how to commit the patch. so need you do that.
>> >>
>> >> The modem information as below :
>> >>
>> >> [ 11.420430] usb 1-5.6: new high-speed USB device number 9 using
>> xhci_hcd
>> >> [ 11.513262] usb 1-5.6: config 1 has an invalid interface
>number: 8
>> but
>> >> max is 3
>> >> [ 11.513265] usb 1-5.6: config 1 has no interface number 1
>> >> [ 11.514059] usb 1-5.6: New USB device found, idVendor=1199,
>> >> idProduct=9091
>> >> [ 11.514061] usb 1-5.6: New USB device strings: Mfr=1,
>Product=2,
>> >> SerialNumber=3
>> >> [ 11.514062] usb 1-5.6: Product: Sierra Wireless EM7565
>Qualcomm®
>> >> Snapdragon™ X16 LTE-A
>> >> [ 11.514063] usb 1-5.6: Manufacturer: Sierra Wireless,
>Incorporated
>> >> [ 11.514064] usb 1-5.6: SerialNumber: dbb8769f
>> >> [ 11.516208] qmi_wwan 1-5.6:1.8: cdc-wdm1: USB WDM device
>> >> [ 11.516330] qmi_wwan 1-5.6:1.8 wwan0: register 'qmi_wwan' at
>> >> usb-0000:00:14.0-5.6, WWAN/QMI device, e2:e8:55:d3:8a:cc
>> >> [ 11.520855] GobiSerial 1-5.6:1.0: GobiSerial converter detected
>> >> [ 11.520913] usb 1-5.6: GobiSerial converter now attached to
>ttyUSB1
>> >> [ 11.521378] GobiSerial 1-5.6:1.2: GobiSerial converter detected
>> >> [ 11.521420] usb 1-5.6: GobiSerial converter now attached to
>ttyUSB2
>> >> [ 11.521974] GobiSerial 1-5.6:1.3: GobiSerial converter detected
>> >> [ 11.522026] usb 1-5.6: GobiSerial converter now attached to
>ttyUSB3
>> >>
>> >> Now only ttyUSB3 can respond AT command, should be modem port. not
>sure
>> >> the other two serial is NMEA port or DM port
>> >>
>> >>
>> >> --
>> >> *Best Regards,*
>> >> *Dai,Lijin*
>> >>
>> >>
>> >> 在 2017-11-20 17:34:12，"Bjørn Mork" <bjorn at mork.no> 写道：
>> >> >Great! Thanks. Will you submit a patch, or should I? How about
>the
>> >> >serial functions? Er they mapped similar to previous Sierra
>modems
>> >> >(0 - diag, 2 - nmea, 3 - modem)? If so, then the ID should also
>be
>> >> >added as DEVICE_SWI to qcserial.
>> >> >
>> >> >
>> >> >Bjørn
>> >> >
>> >> >dailijin <dailijin126 at 126.com> writes:
>> >> >
>> >> >> Hi Bjorn,
>> >> >>
>> >> >>
>> >> >> Only update investigation result.
>> >> >>
>> >> >>
>> >> >> After add 1199:9091 into qmi_wwan, the modem will create one
>wwan
>> interface and one cdc-wdmx interface. then I can make it work with
>RAW-IP
>> mode.
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >> --
>> >> >>
>> >> >> Best Regards,
>> >> >> Dai,Lijin
>> >> >>
>> >> >>
>> >> >>
>> >> >> At 2017-11-14 22:27:34, "Bjørn Mork" <bjorn at mork.no> wrote:
>> >> >>>dailijin <dailijin126 at 126.com> writes:
>> >> >>>
>> >> >>>> I just tested GobiNet driver for the modem, seems only the
>latest
>> >> >>>> GobiNet driver can support the modem. so not sure whether
>also need
>> >> >>>> new qmi_wwan driver to support it. the modem pid:vid is
>1199:9091
>> >> >>>> which is not included in qmi_wwan driver now.
>> >> >>>>
>> >> >>>>
>> >> >>>> I have no environment now. will update my investigation
>result
>> when I
>> >> >>>> have the modem again.
>> >> >>>
>> >> >>>Looking forward to that. Please post as much details as you
>can
>> about
>> >> >>>the modem and testing. I guess it will take some time before
>this
>> modem
>> >> >>>is generally available, based on the MC/EM7455 experiences.
>> >> >>>
>> >> >>>Adding a new ID to qmi_wwan should be no problem if you are
>able to
>> >> >>>build GobiNet. It's also possible to test the modem by adding
>the ID
>> >> >>>dynamically, using the new_id attribute. But then you have to
>take
>> >> >>>special care to make sure only the QMI interface(s) are bound
>to the
>> >> >>>qmi_wwan driver.
>> >> >>>
>> >> >>>If you can do any testing in MBIM mode, then those results
>would
>> also be
>> >> >>>interesting. This should just work without any driver or
>userspace
>> >> >>>changes. In theory...
>> >> >>>
>> >> >>>
>> >> >>>Bjørn
>> >> >>>_______________________________________________
>> >> >>>libqmi-devel mailing list
>> >> >>>libqmi-devel at lists.freedesktop.org
>> >> >>>https://lists.freedesktop.org/mailman/listinfo/libqmi-devel
>> >> >_______________________________________________
>> >> >libqmi-devel mailing list
>> >> >libqmi-devel at lists.freedesktop.org
>> >> >https://lists.freedesktop.org/mailman/listinfo/libqmi-devel
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> _______________________________________________
>> >> libqmi-devel mailing list
>> >> libqmi-devel at lists.freedesktop.org
>> >> https://lists.freedesktop.org/mailman/listinfo/libqmi-devel
>> >>
>> >>
>>
More information about the libqmi-devel
mailing list