This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Hi TI team,
On both AM64x EVM and AM65x EVM I've noticed if I assign a static IP address to eth0 (by changing /etc/network/interfaces and rebooting), eth0 does not assign the static IP at boot. The NIC remains un-configured, but can be fixed by issuing "ifdown eth0 && ifup eth0" twice (one time doesn't seem to do it).
See AM64x EVM console log below showing eth0 is down until I issue ifdown/ifup two times in a row:
_____ _____ _ _ | _ |___ ___ ___ ___ | _ |___ ___ |_|___ ___| |_ | | _| .'| . | . | | __| _| . | | | -_| _| _| |__|__|_| |__,|_ |___| |__| |_| |___|_| |___|___|_| |___| |___| Arago Project http://arago-project.org am64xx-evm ttyS2 Arago 2020.09 am64xx-evm ttyS2 [ 16.478620] omap_rng 40910000.rng: Random Number Generator ver. 241b34c [ 16.611492] icssg-prueth icssg1-eth: TI PRU ethernet driver initialized: single EMAC mode [ 17.427651] usbcore: registered new interface driver usbfs [ 17.478077] usbcore: registered new interface driver hub [ 17.515878] usbcore: registered new device driver usb [ 17.936466] remoteproc remoteproc10: powering up 300b4000.pru [ 17.950552] remoteproc remoteproc10: Booting fw image ti-pruss/am65x-sr2-pru0-prueth-fw.elf, size 36316 [ 17.965024] remoteproc remoteproc10: unsupported resource 5 [ 17.976961] remoteproc remoteproc10: remote processor 300b4000.pru is now up [ 17.989697] remoteproc remoteproc11: powering up 30084000.rtu [ 18.005061] remoteproc remoteproc11: Booting fw image ti-pruss/am65x-sr2-rtu0-prueth-fw.elf, size 29944 [ 18.033018] remoteproc remoteproc11: remote processor 30084000.rtu is now up [ 18.052946] remoteproc remoteproc12: powering up 3008a000.txpru [ 18.068431] remoteproc remoteproc12: Booting fw image ti-pruss/am65x-sr2-txpru0-prueth-fw.elf, size 35916 [ 18.085055] remoteproc remoteproc12: remote processor 3008a000.txpru is now up [ 18.102406] pps pps1: new PPS source ptp2 [ 18.122100] TI DP83869 300b2400.mdio:0f: attached PHY driver [TI DP83869] (mii_bus:phy_addr=300b2400.mdio:0f, irq=POLL) [ 18.141192] net eth2: started am64xx-evm login: root Password: root@am64xx-evm:~# ifconfig eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 metric 1 inet6 fe80::f684:4cff:fef9:7d1a prefixlen 64 scopeid 0x20<link> ether f4:84:4c:f9:7d:1a txqueuelen 1000 (Ethernet) RX packets 86 bytes 7878 (7.6 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 25 bytes 4186 (4.0 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth1: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 metric 1 ether 70:ff:76:1e:29:1a 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 eth2: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 metric 1 ether 70:ff:76:1e:29:1b 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 82 bytes 6220 (6.0 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 82 bytes 6220 (6.0 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 root@am64xx-evm:~# ping 192.168.10.1 PING 192.168.10.1 (192.168.10.1): 56 data bytes ping: sendto: Network is unreachable root@am64xx-evm:~# ifdown eth0 && ifup eth0 && ifdown eth0 && ifup eth0 ifdown: interface eth0 not configured [ 64.606611] am65-cpsw-nuss 8000000.ethernet eth0: Link is Down [ 64.702978] TI DP83867 8000f00.mdio:00: attached PHY driver [TI DP83867] (mii_bus:phy_addr=8000f00.mdio:00, irq=POLL) [ 64.716307] am65-cpsw-nuss 8000000.ethernet eth0: Link is Down root@am64xx-evm:~# [ 67.802461] am65-cpsw-nuss 8000000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off [ 67.810979] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready root@am64xx-evm:~# ping 192.168.10.1 PING 192.168.10.1 (192.168.10.1): 56 data bytes 64 bytes from 192.168.10.1: seq=0 ttl=128 time=1.609 ms 64 bytes from 192.168.10.1: seq=1 ttl=128 time=1.423 ms 64 bytes from 192.168.10.1: seq=2 ttl=128 time=1.411 ms 64 bytes from 192.168.10.1: seq=3 ttl=128 time=1.179 ms ^C --- 192.168.10.1 ping statistics --- 4 packets transmitted, 4 packets received, 0% packet loss round-trip min/avg/max = 1.179/1.405/1.609 ms root@am64xx-evm:~# ifconfig eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 metric 1 inet 192.168.10.2 netmask 255.255.0.0 broadcast 192.168.255.255 inet6 fe80::f684:4cff:fef9:7d1a prefixlen 64 scopeid 0x20<link> ether f4:84:4c:f9:7d:1a txqueuelen 1000 (Ethernet) RX packets 268 bytes 28611 (27.9 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 75 bytes 11457 (11.1 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth1: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 metric 1 ether 70:ff:76:1e:29:1a 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 eth2: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 metric 1 ether 70:ff:76:1e:29:1b 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 82 bytes 6220 (6.0 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 82 bytes 6220 (6.0 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Hello Steven,
I have not tried to set a static IP on AM64x yet. In this post, I discuss options we have used for static IPs on previous devices:
https://e2e.ti.com/support/processors-group/processors/f/processors-forum/954816/tmdsice3359-lost-network-config-when-cable-is-disconnected
If you are still running into challenges after looking at that post, please provide exact steps for how you are trying to set static IP address.
Regards,
Nick
Hi Nick, that did it. I had to setup systemd in /etc/systemd/network instead of via /etc/network/interfaces. Thanks for the link.
Hello Steven,
Good to hear you got it working. Thanks for posting your solution!
Regards,
Nick