Error installing Telit LE910x using ECM

Cellular Modules Telit LE910C1/C4 LTE Module
1

I was following the steps listed here: https://docs.sixfab.com/page/internet-connection-with-twilio-super-sim-telit-le910x-and-sixfab-base-hat-using-ecm

When it asks to enter AT#USBCFG=4 I accidentally entered AT#USBCFG=3.

Now when I try to enter: minicom -D /dev/ttyUSB2 -b 115200
I get: minicom: cannot open /dev/ttyUSB2: No such file or directory.

Any help would be appreciated.

lsusb -t

/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
        |__ Port 3: Dev 3, If 0, Class=Communications, Driver=cdc_mbim, 480M
        |__ Port 3: Dev 3, If 1, Class=CDC Data, Driver=cdc_mbim, 480M

lsusb

Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 1bc7:1205 Telit Wireless Solutions 
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

dmesg | grep tty

[ 0.000000] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 video=HDMI-A-1:1920x1080M@60 smsc95xx.macaddr=DC:A6:32:A3:32:21 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 console= **tty** 1 root=/dev/mmcblk0p7 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait quiet splash plymouth.ignore-serial-consoles

[ 0.001081] printk: console [ **tty** 1] enabled

[ 1.145433] fe201000.serial: **tty** AMA0 at MMIO 0xfe201000 (irq = 29, base_baud = 0) is a PL011 rev2
2

Hi @adam.simms,

Send MBIM_OPEN message to the modem with the following command and wait 3 sec.

echo 01 00 00 00 10 00 00 00 01 00 00 00 00 10 00 00 | xxd -r -p >/dev/cdc-wdm0

Send USB composition with the following command:

echo 03 00 00 00 32 00 00 00 05 00 00 00 01 00 00 00 00 00 00 00 54 65 6c 69 74 4d 42 49 4d 45 78 74 65 6e 64 53 01 00 00 00 01 00 00 00 02 00 00 00 00 00 | xxd -r -p >/dev/cdc-wdm0

Note: You might need root permission to do this: sudo su

3

That worked perfectly. I’m up and running. Thanks!

4

@ensar same thing happened to me. attemped to apply this fix but i still cannot access ttyUSB2. please advise.

5

Hi @Salient ,

Could you share the following command outputs?

lsusb -t
lsusb
dmesg | grep tty
usb-devices
6

Hi @ensar thanks.

lsusb -t
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 3: Dev 3, If 0, Class=Communications, Driver=cdc_mbim, 480M
|__ Port 3: Dev 3, If 1, Class=CDC Data, Driver=cdc_mbim, 480M
|__ Port 4: Dev 4, If 0, Class=Vendor Specific Class, Driver=mt76x0u, 480M

lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 0b05:17d1 ASUSTek Computer, Inc. AC51 802.11a/b/g/n/ac Wireless Adapter [Mediatek MT7610U]
Bus 001 Device 003: ID 1bc7:1205 Telit Wireless Solutions LE910C4-NF
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

dmseg | grep tty
[ 0.000000] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_headphones=0 snd_bcm2835.enable_headphones=1 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_hdmi=0 smsc95xx.macaddr=DC:A6:32:EE:8C:47 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 console=ttyS0,115200 console=tty1 root=PARTUUID=24a0b1b9-02 rootfstype=ext4 fsck.repair=yes rootwait cfg80211.ieee80211_regdom=US
[ 0.000912] printk: console [tty1] enabled
[ 1.676396] fe201000.serial: ttyAMA1 at MMIO 0xfe201000 (irq = 36, base_baud = 0) is a PL011 rev2
[ 1.676683] serial serial0: tty port ttyAMA1 registered
[ 5.087153] systemd[1]: Created slice system-getty.slice - Slice /system/getty.

usb-devices
T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 1
D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=1d6b ProdID=0002 Rev=06.01
S: Manufacturer=Linux 6.1.0-rpi4-rpi-v8 xhci-hcd
S: Product=xHCI Host Controller
S: SerialNumber=0000:01:00.0
C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 4 Ivl=256ms

T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=480 MxCh= 4
D: Ver= 2.10 Cls=09(hub ) Sub=00 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=2109 ProdID=3431 Rev=04.21
S: Product=USB2.0 Hub
C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=100mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 1 Ivl=256ms

T: Bus=01 Lev=02 Prnt=02 Port=02 Cnt=01 Dev#= 3 Spd=480 MxCh= 0
D: Ver= 2.00 Cls=ef(misc ) Sub=02 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=1bc7 ProdID=1205 Rev=03.18
S: Manufacturer=Android
S: Product=LE910C4-NF
S: SerialNumber=0123456789ABCDEF
C: #Ifs= 2 Cfg#= 1 Atr=a0 MxPwr=500mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=02(commc) Sub=0e Prot=00 Driver=cdc_mbim
E: Ad=82(I) Atr=03(Int.) MxPS= 64 Ivl=32ms
I: If#= 1 Alt= 1 #EPs= 2 Cls=0a(data ) Sub=00 Prot=02 Driver=cdc_mbim
E: Ad=01(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E: Ad=81(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms

T: Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=5000 MxCh= 4
D: Ver= 3.00 Cls=09(hub ) Sub=00 Prot=03 MxPS= 9 #Cfgs= 1
P: Vendor=1d6b ProdID=0003 Rev=06.01
S: Manufacturer=Linux 6.1.0-rpi4-rpi-v8 xhci-hcd
S: Product=xHCI Host Controller
S: SerialNumber=0000:01:00.0
C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 4 Ivl=256ms

7

This didn’t work? Any errors, output? Is there a service etc. that keeps the module in this mode in the background?

8

You know. You guys are great just want to preface this reply with that. And F&(*#$king ModemManager was the culpret again (will never forget to check that before i request support). Held up the port. All good now. Thanks and have a great weekend.

@ensar

any idea what this is about?

AT+CGREG?
+CGREG: 2,1,“58E7”,“A79D0C”,7,D9

AT+CREG?
+CREG: 2,1,“58E7”,“A79D0C”,7

I’ve been scouring AT command manuals, but is there any way to clear NVM something like a factory reset?