we want to connect a switch chip to replace PHY with xavier, working at MAC to MAC mode.
hardware/nvidia/platform/t19x/common/kernel-dts/t19x-common-platforms/tegra194-platforms-eqos.dtsi
when in MAC to MAC mode, i add fixed-link to tegra194-platforms-eqos.dtsi, like this:
fixed-link {
speed = <1000>;
full-duplex;
};
do i need to change parameters of tegra186-soc-eqos.dtsi, or keep default in
hardware/nvidia/soc/t18x/kernel-dts/tegra186-soc/tegra186-soc-eqos.dtsi
the problem i faced is: switch(MV88E6321) port registers works well (checked over the registers), but it can not ping with other computer. so i want to know how to set EQOS work in MAC to MAC, maybe it need some configurations.
Hi,
Only need to configure the t194 one. T186 is for TX2.
Also, the parameters you could configure in DT could be refer to this document.
kernel/nvidia/Documentation/devicetree/bindings/platform/tegra/tegra-eqos.txt
sorry for my fault, it should be tegra194-soc-eqos.dtsi, and
hardware/nvidia/soc/t19x/kernel-dts/tegra194-soc/tegra194-soc-eqos.dtsi
thanks for reply, i had read the doc:
kernel/nvidia/Documentation/devicetree/bindings/platform/tegra/tegra-eqos.txt
and there isnât anything about MAC to MAC.
Hi,
In case of MAC to MAC configuration - no other parameters need to be modified except adding fix-link node in corresponding platform DT.
One point to be noted is other end of MAC should provide the Rx Clock to EQOS HW. In your case, this clock need to be provided by switch MV88E6321.
In normal cases PHY will give Rx clock to EQOS.
Also please help us in getting the below logs
Dmesg logs
Ifconfig output
âethtool -S eth0â output
eth0 in DHCP mode.
sudo modprobe eqos
$ dmesg
$ ifconfig
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
rndis0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
usb0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
$ ethtool -S eth0
Hi,
$ ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::4c2b:543d:93b4:2b9b prefixlen 64 scopeid 0x20
ether 00:04:4b:e5:79:bb txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 21 bytes 3776 (3.7 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 40
Based on the above log, we see that EQOS is able to send the packets, but it doesnât received any packets. No other suspicious logs from our side.
Further questions we need to ask are
Does other end (i.e Switch) received the packets?
Check on the counters from the switch side and see if tx and rx counters are getting incremented.
Check if you can validate switch port loopback at the switch side to confirm on both tx and rx side working.
kayccc
June 11, 2020, 2:05am
9
Hi liu,jaliu,
Have you managed to get issue resolved? Any result can be shared?
according to the 88E6321 datasheet, set xavier eqos to ârgmiiâ, and 6321 to be ârgmii-idâ, it works at last.
1 Like
efio
November 29, 2020, 8:00pm
12
Hi,
I saw this thread and itâs exactly the problem I have. Can you please give more details about the solution?@liu.jialu Iâm using also the Marvell 88E6321, and I canât make the ethernet work. Can you please share the schematics connection between the ethernet switch and jetson xavier? I attached mine.
When I connect the xavier to my carrier board, I can see on scope that the 125MHz clock out from the switch is distorted, and the clock from the jetson to the switch is degraded - about half 0.8Vp-p, but it looks reasonable comparing to the other clock.
Can you help me please? could it be a software issue?
Thank you,
Efi
Hi @efio ,
This thread is over 5 months old. I suggest you start a new topic for your issue. Someone from the Jetson team should be able to assist.
Best,
