Cannot access MangOH Yellow wp7702

then how can you communicate on working board in case the ecm0 interface is not started?

Does it has UART console on MangOH yellow board?

Seems to be through this interface:
enp0s20f0u2i19: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether e2:d4:fc:b4:57:18 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

is this renamed from usb0 on Linux PC?
You can check in dmesg.

I believe from the problematic board, there should also be usb0 enumerated in PC as ECM interface has bee enabled in AT!USBCOMP

in dmesg

cdc_ether 1-2:1.19 enp0s20f0u2i19: renamed from usb0

Following by:
ADDRCONF(NETDEV_UP): enp0s20f0u2i19: link is not ready

And in the working one I have this, but not in the other:
ADDRCONF(NETDEV_CHANGE): enp0s20f0u2i19: link becomes ready

ifconfig enp0s20f0u2i19

Problematic board:
enp0s20f0u2i19: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 6e:bc:30:04:a6:6f txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)

Working one:
enp0s20f0u2i19: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.2.3 netmask 255.255.255.0 broadcast 192.168.2.255
inet6 fe80::552:4bc8:eb00:da74 prefixlen 64 scopeid 0x20
ether 92:d9:1c:7d:2e:93 txqueuelen 1000 (Ethernet)
RX packets 11 bytes 1220 (1.2 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 47 bytes 7438 (7.4 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

how about “sudo ifconfig enp0s20f0u2i19 192.168.2.3” ?
and then try to ping module by “ping 192.168.2.2” ?

BTW is there any UART console on your MangOH yellow board?

PING 192.168.2.2 (192.168.2.2) 56(84) bytes of data.
From 192.168.2.3 icmp_seq=1 Destination Host Unreachable

I get the logs from USB on the other port, I do not really understand your UART question

seems the module’s ecm0 is not yet ready for IP 192.168.2.2.

there is a USB port in the mangoh yellow board, I believe that is UART console

Therfore what’s your advice?

Of course connect usb cable to see if you can enter console

Yes it is the USB port I used to retrieve all the logs I put in here
You mean write commands through this port ?

This is the uart console, you can check " ifconfig ecm0"

For the working one, I can enter commands through cutecom, and ifconfig ecm0 responds correctly
Otherwise, with the other I cannot enter any command
just this line loop:

swi-mdm9x28-wp user.err kernel: [ 49.040354] wait_for_irsc_completion: waiting for IPC Security Conf.

Like the boot steps are not finished and give me no access to the board

Suggest you downgrade to fw R9, and then use “swiflash -m wp77xx -r” to erase user app partition.

Please see here

I can’t download the R9 version:
https://source.sierrawireless.com/resources/airprime/software/wp77xx/wp77xx-firmware-release-9/#sthash.Z2l3OrCm.dpbs

Seems the whole source website has problem.
I cannot even download r12.


I also found these logs on the broken one:

Jan 6 00:49:23 swi-mdm9x28-wp user.err kernel: [ 83.821012] usb 1-1: device not accepting address 5, error -110
Jan 6 00:49:23 swi-mdm9x28-wp user.err kernel: [ 83.826015] usb usb1-port1: unable to enumerate USB device
Jan 6 00:49:23 swi-mdm9x28-wp user.info kernel: [ 83.832360] msm_hsic_host 7c00000.hsic_host: HSIC-USB in low power mode

No idea what it means, probably first try to erase user partiton

I found the R11, downgrade my board, and I managed to use the swiflash -r command which erased the board
After that I can connect by ssh :slight_smile:

Mangoh should correct swiflash -r option for the new release

Thank you for your time @jyijyi !!!