Jetpack 6.1 L4T 36.3 RGMII issue

Autonomous Machines Jetson & Embedded Systems Jetson AGX Orin
,
1

Hi,

I have an issue with RGMII configuration in L4T 36.4 on our custom board.
Previously on this board was run L4T 35.4.1 and after adaption according to Developer guide RGMII worked fine.
In L4T 36.4 was done same modification as in L4T 35.4.1 but i get next error on boot and don’t see any interface under ifconfig:

[    0.113350] OF: /bus@0/ethernet@2310000: could not get #gpio-cells for /bus@0/aconnect@2900000/ahub@2900800/ports/port@4d/endpoint

I’m never see in your DTS node/filed named gpio-cels and i don’t understand how eth device related to ahub.
Myabe i’m missing something in DTS configuration? ODM data set according to Developer guide. Dmesg,pinmux and last dtsi are attached.

Hope for your help,
Ronen.
tegra234-p3737-0000+p3701-0004-nv.dts.txt (310.9 KB)
dmesg.txt (39.1 KB)
flash_log.txt (525.2 KB)
tegra234-mb1-bct-pinmux-p3701-0000-a04.dtsi.txt (63.6 KB)

2

Hello,

Thanks for visiting the NVIDIA Developer forums! Your topic will be best served in the Jetson category.

I will move this post over for visibility.

Cheers,
Tom

5

I guess it is due to this one. 0x35 seems to be the phandle of other nodes but not related to GPIO.

		nvidia,phy-reset-gpio = <0x35 0x0>;
6

Was missing some definition in DT node:
Was:

nvidia,phy-reset-gpio = <TEGRA234_MAIN_GPIO(G, 5) 0>;

Now and correct one:(i think)

nvidia,phy-reset-gpio = <&gpio TEGRA234_MAIN_GPIO(G, 5) 0>;

In decompiled DTB this node look like:

nvidia,phy-reset-gpio = <0xf1 0x35 0x0>;

I don’t found any errors related to ethernet now in dmesg but it still not appear in ifconfig.
Dmesg and updated DT attached.
dmesg_new.txt (38.8 KB)
tegra234-p3737-0000+p3701-0004-nv_NEW.txt (310.9 KB)

BR,
Ronen.

7

What I saw here is it seems you still get into the same mistake I mentioned to you 3 months ago.

I don’t see other driver logs that should be there as well. I guess your nvethernet driver and other drivers are not appeared in your lsmod again?