what do you mean it is same log?
Can you enter anything in COM16 after reboot?
at!mapuart=16,1 and at!reset are just to set the UART1 to linux console and reboot the module, it should not change the USB part of module
1 Like
I was able to type ifconfig
root@swi-mdm9x28-wp:~# ifconfig
bridge0 Link encap:Ethernet HWaddr 5E:69:9C:7D:54:09
inet addr:192.168.225.1 Bcast:192.168.225.255 Mask:255.255.255.0
inet6 addr: fe80::5c69:9cff:fe7a:5106/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:1 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:76 (76.0 B)
ecm0 Link encap:Ethernet HWaddr 0A:79:01:40:5B:C6
inet addr:192.168.2.2 Bcast:192.168.2.255 Mask:255.255.255.0
inet6 addr: fe80::879:1ff:fe40:5bc6/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:280 errors:0 dropped:4 overruns:0 frame:0
TX packets:9 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:33959 (33.1 KiB) TX bytes:990 (990.0 B)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
rmnet0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
UP RUNNING MTU:2000 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Now I just need to turn off the firewall to be able to ssh into the module right?
ok, then that means your COM16 is linux console in UART1 now.
Problem is now your device manager did not enumerate any port by USB of module…
You need to fix that first.
I tried unplugging the power supply and plugging it back in and got all the ports.
Do you see the module’s ECM port in network interface in device manager?
is it this?
Control panel → Network and Sharing Center → change adpter setting → Double click the "Sierra Wireless LEGATO EthLink ECM → properties → internet protocol version 4 (TCP/IPv4) → properties →
IP address : 192.168.2.3
subnet mask: 255.255.255.0
default gateway: 192.168.2.2
Click OK.
You also need to disable the firewall of module:
iptables -I INPUT -j ACCEPT
After adjusting the ip and disabling the firewall as you indicated. I switch the module connection from window to ubuntu virtual machine, the ip of the module is 192.168.2.3?
Did I do it wrong?
Source code in ubuntu virtual machine, how to build and install on the device plugged in window. Sorry for asking too much, I’m a newbie so a lot of things are strange to me.
ens33 is the network interface of your ubuntu PC, not module…
Didn’t you already install leaf and vscode in linux at the beginning of this thread?
Yes, i installed leaf and vscode in linux up to step 7 in the tutorial: Install the Legato Plugin for VSCode - Legato Docs. You can see my first helloComponent.c file as shown.
If you compile the app successfully, there should be .update file.
You can transfer the .update file to windows and transfer to module /tmp folder by WINSCP.
To install the app, you can type “update xxx.update” in module’s console
I turned off the firewall but still Network error: Connection to “192.168.2.2” refused (transfer the .update file by WINSCP.)
Can you ssh to 192.168.2.2 through linux pc?
I assume you can ping 192.168.2.2 from the host PC.
have you disabled the firewall of module in the UART console:
iptables -I INPUT -j ACCEPT
you cannot even ping the module’s IP 192.168.2.2
how about “ping 192.168.2.2 -I ens33”
(lsh:wp76stable) ntram@ubuntu:~/space$ ping 192.168.2.2 -I ens33
PING 192.168.2.2 (192.168.2.2) from 192.168.2.3 ens33: 56(84) bytes of data.
^C
--- 192.168.2.2 ping statistics ---
27 packets transmitted, 0 received, 100% packet loss, time 26605ms
pipe 4
You can capture wireshark log and see if there is any clue.
BTW, if you remove the USB of module, does the interface ens33 disappear?
I am not sure if ens33 is really the interface to the module.
you should also check in dmesg and see if the ens33 is really the USB ECM interface from the module
I remove the module’s USB, the ens33 interface does not disappear.
ens35u1i19 is USB ECM interface from the module
(lsh:wp76stable) ntram@ubuntu:~/space$ ping 192.168.2.2 -I ens35u1i19
PING 192.168.2.2 (192.168.2.2) from 192.168.2.3 ens35u1i19: 56(84) bytes of data.
64 bytes from 192.168.2.2: icmp_seq=1 ttl=64 time=608 ms
64 bytes from 192.168.2.2: icmp_seq=2 ttl=64 time=2.82 ms
64 bytes from 192.168.2.2: icmp_seq=3 ttl=64 time=3.76 ms
64 bytes from 192.168.2.2: icmp_seq=4 ttl=64 time=3.95 ms
64 bytes from 192.168.2.2: icmp_seq=5 ttl=64 time=3.78 ms
64 bytes from 192.168.2.2: icmp_seq=6 ttl=64 time=3.33 ms
64 bytes from 192.168.2.2: icmp_seq=7 ttl=64 time=1.95 ms
64 bytes from 192.168.2.2: icmp_seq=8 ttl=64 time=1.55 ms
64 bytes from 192.168.2.2: icmp_seq=9 ttl=64 time=1.65 ms
^C
--- 192.168.2.2 ping statistics ---
9 packets transmitted, 9 received, 0% packet loss, time 8012ms
rtt min/avg/max/mdev = 1.550/70.125/608.303/190.276 ms
(lsh:wp76stable) ntram@ubuntu:~/space$