NVIDIA Jetson AGX Orin Custom Carrier Board RGMII Ethernet is unable to receive data

[idealong]

Software Environment: R35.6.0
Hardware Environment: Jetson AGX Orin connected to YT8521 PHY via RGMII. The PC and Orin are on the same network segment, directly connected via an Ethernet cable.

Issue:
When pinging the PC from Orin, Wireshark on the PC can capture the ARP request packets sent by Orin. However, the ARP reply packets from the PC are not received by Orin. Using an oscilloscope to monitor the RGMII Rx signal shows that data is being transmitted.

Troubleshooting Steps:

1. Checked the statistics of eth0 using ethtool -S eth0, and found that the counters related to reception (rx) did not increase.
2. After executing ifconfig eth0 up/down, checked the interrupt count using cat /proc/interrupts | grep eth0, and observed that the interrupt count increased. When the Ethernet status changes, the corresponding Ethernet interrupt count will increase.

Consistent with the phenomenon described in the following post：

RGMII PHY KSZ9131 no transfer data

Please go back to previous post and use similar method to check things again… Your flash log gives this: copying pinmux_config(/home/jetson/Jetson_RT/Linux_for_Tegra/bootloader/generic/BCT/tegra234-mb1-bct-pinmux-p3701-0000-a04.dtsi Which means your pinmux is not tegra234-mb1-bct-pinmux-p3701-0000.dtsi…

Orin RGMII RX[0:3] → PHY RX[0:3],Is this connection incorrect?

[WayneWWW]

You could check pinmux setting by directly reading register for each pin.

If they are all correct, please review hardware or check with PHY vendor.

[idealong]

EQOS_TXC sudo busybox devmem 0x02445058 0x00002400
EQOS_TD0 sudo busybox devmem 0x02445018 0x00002400
EQOS_TD1 sudo busybox devmem 0x02445010 0x00002400
EQOS_TD2 sudo busybox devmem 0x02445008 0x00002400
EQOS_TD3 sudo busybox devmem 0x02445000 0x00002400
EQOS_TX_CTL sudo busybox devmem 0x02445068 0x00002400

EQOS_RXC sudo busybox devmem 0x02445060 0x00002458
EQOS_RD0 sudo busybox devmem 0x02445040 0x00002458
EQOS_RD1 sudo busybox devmem 0x02445030 0x00002458
EQOS_RD2 sudo busybox devmem 0x02445028 0x00002458
EQOS_RD3 sudo busybox devmem 0x02445020 0x00002458
EQOS_RX_CTL sudo busybox devmem 0x02445070 0x00002458

EQOS_SMA_MDIO sudo busybox devmem 0x02445038 0x00002440
EQOS_SMA_MDC sudo busybox devmem 0x02445048 0x00002400

ENET_RST_N sudo busybox devmem 0x02434078 0x00000000
ENET_INT_N sudo busybox devmem 0x02434078 0x00000058

管脚配置没问题

[idealong]

The image above shows the result of my command cat /proc/interrupts | grep eth , which is printed by me. Compared to the results printed by other developers, the output is missing the part highlighted in red as shown below.

[WayneWWW]

Then you forgot to set the interrupt pin to GPIO input.

[idealong]

The PHY interrupt pin uses GPIO3_PG.04, as shown in the image below:

The modifications related to the device tree are shown in the image below:

Is there something missing that still needs to be modified?

[WayneWWW]

Are you sure the pinmux file is the one your board is using?

[idealong]

Yes, I directly used the command sudo ./flash.sh jetson-agx-orin-devkit internal to flash the device.

pinmux register values are as follows:
EQOS_TXC sudo busybox devmem 0x02445058 0x00002400
EQOS_TD0 sudo busybox devmem 0x02445018 0x00002400
EQOS_TD1 sudo busybox devmem 0x02445010 0x00002400
EQOS_TD2 sudo busybox devmem 0x02445008 0x00002400
EQOS_TD3 sudo busybox devmem 0x02445000 0x00002400
EQOS_TX_CTL sudo busybox devmem 0x02445068 0x00002400

EQOS_RXC sudo busybox devmem 0x02445060 0x00002458
EQOS_RD0 sudo busybox devmem 0x02445040 0x00002458
EQOS_RD1 sudo busybox devmem 0x02445030 0x00002458
EQOS_RD2 sudo busybox devmem 0x02445028 0x00002458
EQOS_RD3 sudo busybox devmem 0x02445020 0x00002458
EQOS_RX_CTL sudo busybox devmem 0x02445070 0x00002458

EQOS_SMA_MDIO sudo busybox devmem 0x02445038 0x00002440
EQOS_SMA_MDC sudo busybox devmem 0x02445048 0x00002400

ENET_RST_N sudo busybox devmem 0x02434078 0x00000000
ENET_INT_N sudo busybox devmem 0x02434078 0x00000058

[WayneWWW]

pinmux and gpio setting are separate register. You should check gpio register too.

[idealong]

I understand. I modified the following two files, and the detailed modifications can be found in the previous reply.
tegra234-mb1-bct-gpio-p3701-0000-a04.dtsi
tegra234-mb1-bct-pinmux-p3701-0000-a04.dtsi

[WayneWWW]

I mean did you read the gpio register on the board or not…

[idealong]

I don’t have the board with me right now, so I’ll try it out tomorrow. Thanks for the reply.

[reduslewar]

Thanks for provide answer.

[idealong]

Is the register address and value read for soc_gpio17_pg4 as ENET_INT_N correct? As shown in the figure below, according to the TRM manual, only the input function is enabled?

[WayneWWW]

Are you sure your device tree change for kernel really takes effect ?

[idealong]

Viewing the flashing log, the file used is tegra234-mb1-bct-pinmux-p3701-0000-a04.dtsi . Previously, the wrong file tegra234-mb1-bct-pinmux-p3701-0000.dtsi was modified, which resulted in an error as shown in the image below.

NVIDIA Jetson AGX Orin Custom Carrier Board RGMII Ethernet Not Working

NVIDIA Jetson AGX Orin Custom Carrier Board RGMII Ethernet Not Working Hello, I have designed a custom carrier board hardware based on the NVIDIA Jetson Orin Developer Kit Carrier Board schematic. The abnormal print log is as follows： ![XFI and RGMII ethernet error inf print] [XFI and RGMII ethernet error inf print] For detailed prints, please refer to the attached log.txt. AGX Orin Developer Kit _20241205_130448.txt (74.1 KB) custom carry board USB and Ethernet Error.txt (71.4 KB) The h…

[WayneWWW]

Could you just stop sharing everything here in screenshot?

If you want to share log, give out full text file. Those partial screenshot really cannot clarify your situation well.

[idealong]

I’m sorry, I thought using screenshots to highlight the issue would help you quickly locate the problem.

The following three files have been modified:

• Linux_for_Tegra/bootloader/tegra234-mb1-bct-gpio-p3701-0000-a04.dtsi
  tegra234-mb1-bct-gpio-p3701-0000-a04.dtsi.txt (4.8 KB)

• Linux_for_Tegra/bootloader/t186ref/BCT/tegra234-mb1-bct-pinmux-p3701-0000-a04.dtsi
  tegra234-mb1-bct-pinmux-p3701-0000-a04.dtsi.txt (63.6 KB)

• Linux_for_Tegra/source/public/hardware/nvidia/platform/t23x/concord/kernel-dts/cvb/tegra234-ethernet-3737-0000.dtsi
  tegra234-ethernet-3737-0000.dtsi.txt (1.7 KB)

flash log:
flash_log.txt (493.2 KB)

dmesg log:
dmesg.txt (69.5 KB)

PG.04 pinmux:
sudo busybox devmem 0x02434070
0x00000058

PG.04 gpio config:
sudo busybox devmem 0x02214080
0x00000001

sudo cat /sys/kernel/debug/gpio | grep PG
gpio-347 (PGG.00 )
gpio-383 (PG.00 |force-recovery ) in hi IRQ ACTIVE LOW
gpio-384 (PG.01 |temp-alert ) in hi IRQ
gpio-385 (PG.02 |sleep ) in hi IRQ ACTIVE LOW
gpio-386 (PG.03 )
gpio-387 (PG.04 )
gpio-388 (PG.05 |phy_reset ) out hi
gpio-389 (PG.06 )
gpio-390 (PG.07 |cd ) in hi IRQ

The PG.04 pin interrupt function is not enabled.

[WayneWWW]

Your error log does not have this thing as screenshot mentioned.

Which log is correct? That is why you should stop sharing screenshot, because they are lacking of context and not clear at all.

Also, are you sure the device tree running on the board matches to what you flashed? I don’t care about how the original file looks like now. Check the dts file converted from dtb file and also check /proc/device-tree on your device.

[idealong]

The previous modification was made to the file tegra234-mb1-bct-pinmux-p3701-0000.dtsi, which led to the error shown in the screenshot. After synchronizing the changes to the file tegra234-mb1-bct-pinmux-p3701-0000-a04.dtsi, the error disappeared, indicating that the actual file in use is tegra234-mb1-bct-pinmux-p3701-0000-a04.dtsi.

Below are the dts files and the devicetree compressed package:
sudo dtc -I dtb -O dts -o devicetree_gen.dts /boot/dtb/kernel_tegra234-p3701-005-p3737-000.dtb
devicetree_gen.dts.txt (552.1 KB)

sudo tar -cvf devicetree.tar /sys/firmware/devicetree
devicetree_2.zip (397.6 KB)