Imx7 ethernet stopped working

Technical Support
, ,
1

I’m using the Colibri imx7D 1gb with the Aster Rev1.1
The Ethernet port has been working fine for a week but has suddenly stopped functioning.
The LED’s on the port no longer light up and it cannot connect to the network.

I have re-flashed the board with the latest Torizon Core image using the latest Toradex Easy Installer and tried different cables but this has not fixed the issue.

Could you please recommend how to resolve this issue?

colibri-imx7-emmc-07027016:~$ ifconfig
br-deef2fc3bd43: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500  metric 1
        inet 172.18.0.1  netmask 255.255.0.0  broadcast 172.18.255.255
        inet6 fe80::42:daff:fe9c:f470  prefixlen 64  scopeid 0x20<link>
        ether 02:42:da:9c:f4:70  txqueuelen 0  (Ethernet)
        RX packets 322  bytes 23888 (23.3 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 185  bytes 18475 (18.0 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

docker0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500  metric 1
        inet 172.17.0.1  netmask 255.255.0.0  broadcast 172.17.255.255
        ether 02:42:28:3e:26:2b  txqueuelen 0  (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

ethernet0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500  metric 1
        ether 00:14:2d:6b:39:48  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

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536  metric 1
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 80  bytes 6128 (5.9 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 80  bytes 6128 (5.9 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

veth90f24f6: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500  metric 1
        inet6 fe80::18b7:4eff:fedd:10e  prefixlen 64  scopeid 0x20<link>
        ether 1a:b7:4e:dd:01:0e  txqueuelen 0  (Ethernet)
        RX packets 360  bytes 31016 (30.2 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 128  bytes 11985 (11.7 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

dmesg.txt (47.9 KB)

2

Hi @jamesxors !

Could you please answer the following questions?

  • Which version is your Colibri iMX7D module?

  • Can you share the output of the following command:

ip -4 a
  • Also, could you perform the following test:
  1. turn the system off,
  2. remove the module,
  3. insert it back,
  4. turn on the system,
  5. check if the internet is accessible,
  • And, when you reinstalled the OS, could the module access the internet to download the OS? Or you use a USB stick with the OS loaded in it?

Best regards,

3

It’s the Colibri iMX7D 1GB, V1.1 EMMC, PN:0039

Output from ‘ip -4 a’

colibri-imx7-emmc-07027016:~$ ip -4 a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
4: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default 
    inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
       valid_lft forever preferred_lft forever
colibri-imx7-emmc-07027016:~$

I performed the test you suggested, however Ethernet port is still not functioning.

When I reinstalled the OS the module could not access the internet so I had to use a USB with the OS on it.

Many Thanks,
James

4

Hi, @jamesxors !

Can you check if the DHCP server of your network is working? Its failure can be the cause of your issue.

Best regards,

5

I have checked and the DHCP server is working correctly I have restated just to be sure, but still the device cannot connect.

I tried to renew the DHCP lease on the device and it was unable to find the server.
(The same commands work fine on the development Linux machine that is on the same network)
image

6

Hi @jamesxors !

Thanks for the test results.

Do you have another carrier board that you could test the same module?

This way we can isolate the ethernet problem.

Best regards,

7

@henrique.tx Unfortunately we do not, this is the only carrier board and SoC we have at the moment.
Do you reckon this is a hardware issue rather than software?
Is it possible to get a replacement carrier board if you think this is the issue?

Many Thanks,
James

8

Hi @jamesxors ,

Yes indeed, our current estimation suggests that this could be a hardware-related issue.

Please fill out the form for a RMA. They will get in touch with you about possible replacements.

RMA

Best Regards
Kevin

9

@kevin.tx Thank you!