T2080RDB-PC Cannot ping

cancel
Showing results for 
Search instead for 
Did you mean: 

T2080RDB-PC Cannot ping

Jump to solution
636 Views
sandratrujillog
Contributor III

I have enabled the 1G RGMII (RTL8211E) ethernet ports (Port FM1@DTSEC3 in U-boot and port fm1-mac3 in linux) on the t2080 reference board, assigned IP address. However, I am unable to ping to the computer from the board attached to the network.

From U-boot if I try this connection (ping 192.168.1.2) I get a response. But since linux I configure the network but I do not get the answer.

In linux I follow the following steps to configure the network:

1) vi / etc / network / interfaces

2) I add the following lines in the interface file:

      auto fm1-mac9

      iface fm1-mac9 inet static

      address 192.168.1.3

      net mask 255.255.255.0

3) From the console I execute:

      ifup fm1-mac9

4) Then I try ‘ping 192.168.1.2’ but I can’t.

From U-boot if I do 'ping 192.168.1.2', I get the following response:

      Using FM1@DTSEC3 device

      host 192.168.1.2 is alive

PD: I think that the host network computer is correctly configured because I can ping from another terminal with linux.

Attached is the kernel boot up logs.

Labels (1)
Tags (1)
0 Kudos
1 Solution
322 Views
ufedor
NXP TechSupport
NXP TechSupport

On the T2080RDB:

ETH4 - FM1@DTSEC3 - fm1-mac3

Why you are configuring "fm1-mac9"?

View solution in original post

3 Replies
323 Views
ufedor
NXP TechSupport
NXP TechSupport

On the T2080RDB:

ETH4 - FM1@DTSEC3 - fm1-mac3

Why you are configuring "fm1-mac9"?

322 Views
sandratrujillog
Contributor III

I have solved the problem. I configured fm1-mac9 because in the login I read the following and thought that it was renamed. 

Starting udev
udevd[1357]: starting version 182
fsl_dpa fsl,dpaa:ethernet@1 fm1-mac2: renamed from eth1
udevd[1361]: renamed network interface eth1 to fm1-mac2
fsl_dpa fsl,dpaa:ethernet@2 fm1-mac3: renamed from eth2
fsl_dpa fsl,dpaa:ethernet@0 fm1-mac1: renamed from eth0
udevd[1365]: renamed network interface eth2 to fm1-mac3
fsl_dpa fsl,dpaa:ethernet@3 fm1-mac4: renamed from eth3
udevd[1360]: renamed network interface eth0 to fm1-mac1
fsl_dpa fsl,dpaa:ethernet@9 fm1-mac10: renamed from eth5
udevd[1363]: renamed network interface eth3 to fm1-mac4
fsl_dpa fsl,dpaa:ethernet@8 fm1-mac9: renamed from eth4
udevd[1366]: renamed network interface eth5 to fm1-mac10
udevd[1364]: renamed network interface eth4 to fm1-mac9
bootlogd: cannot allocate pseudo tty: No such file or directory
random: dd urandom read with 8 bits of entropy available
Populating dev cache
Running postinst /etc/rpm-postinsts/100-sysvinit-inittab...
update-rc.d: /etc/init.d/run-postinsts exists during rc.d purge (continuing)
INIT: Entering runlevel: 5
Configuring network interfaces... done.
Starting OpenBSD Secure Shell server: sshd
generating ssh RSA key...
generating ssh ECDSA key...
generating ssh DSA key...
generating ssh ED25519 key...
done.
Starting syslogd/klogd: done

QorIQ SDK (FSL Reference Distro) 2.0 t2080rdb /dev/ttyS0

Thank you very much for your answer. I have another question, Why every time that I start the T2080RDB-PC I have to configure the network (interface)? It is normal? I have the fsl-image-mfgtool installed.

0 Kudos
322 Views
ufedor
NXP TechSupport
NXP TechSupport

Please create new community question for your latest request.

0 Kudos