Telit LE910-NVG
Randy Yates
yates at digitalsignallabs.com
Sat Feb 6 04:17:41 CET 2016
Hi Sebastian,
Thank you for your assistance.
> Hi,
>
> Check the USBCFG of the LE910 that it is the wanted one (command
> AT#USBCFG), I have had some issues with HE910/LE920 regarding wrong
> USB configuration in the shipping configuration and needed to change
> it get the interfaces I need.
That AT command doesn't work for me. I get (from minicom terminal)
AT#USBCFG
ERROR
AT+GSN
359019050001202
OK
AT+USBCFG
ERROR
I did a GSN just to show it's working, and I also tried USBCFG with the
"+" just to try something.
--Randy
>
> Regards,
> Sebastian
>
> > On Feb 4, 2016, at 19:44 , Bjørn Mork <bjorn at mork.no> wrote:
> >
> > Randy Yates <yates at digitalsignallabs.com> writes:
> >
> >> After running this code, the 910 enumerates on the USB bus. I see
> >> /dev/ttyUSB0 through /dev/ttyUSB4. I can also connect to /dev/ttyUSB2
> >> and issue AT commands successfully, e.g., "AT+GSN" and receive the
> >> IMEI number back.
> >>
> >> Also the result of lsusb looks right:
> >>
> >> root at arm:~# lsusb
> >> Bus 001 Device 002: ID 1bc7:1201 Telit
> >> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> > ..
> >> The qmi_wwan kernel module also appears to be loaded as evidenced
> >> from the lsmod:
> >
> > qmi_wwan is supposed to bind to interface #2 on that device. I don't
> > know why it hasn't. dmesg output would be good. Maybe there is some
> > error? Or maybe some other driver has bound to that interface already?
> > It is blacklisted in the option driver, but if you (or some script) has
> > messed with dynamic IDs then it could still be taken.
> >
> > A few commands to try debug this further:
> >
> > lsusb -vd 1bc7:1201
> > ls -ld /sys/bus/usb/devices/*/driver
> > dmesg
> > cat /sys/bus/usb-serial/drivers/option1/new_id
> >
> >
> >
> > Bjørn
--
Randy Yates, DSP/Embedded Firmware Developer
Digital Signal Labs
http://www.digitalsignallabs.com
More information about the libqmi-devel
mailing list