Hi, it turned out that my problem is not wrong setting...it was the load method. i loaded barebox by uboot like it's documented here: https://www.barebox.org/doc/latest/user/barebox.html#starting-barebox except i have loaded files via fatload and not tftp. if i flash barebox and boot directly into it, network works (also with first version of dts with rx-delay/tx-delay and rgmii phy_mode). barebox@BPI R2PRO:/ dhcp eth1 eth1: 1000Mbps full duplex link detected WARNING: eth1: No MAC address set. Using random address 92:26:6a:9c:ec:d5 T T T eth1: DHCP client bound to address 192.168.0.104 barebox@BPI R2PRO:/ ping 192.168.0.10 PING 192.168.0.10 (192.168.0.10) host 192.168.0.10 is alive so imho there are 2 possible rootcauses - uboot has initialized anything (clocks/pinctrl/...) which barebox cannot change afterwards (due to missing reset) - barebox skips any initialization step if it is chainloaded i have now tested both configurations (rgmii+delays and rgmii-id without delay-properties, but delays set in driver). linux is already updated in next to the rgmii+delays part, so i would send this as update to barebox. regards Frank _______________________________________________ barebox mailing list barebox@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/barebox
