Enabling RGMII for AGX Orin

[sumin.lee1]

Hello,
We are trying to use RGMII for AGX Orin.
I followed the refer as below.
https://docs.nvidia.com/jetson/archives/r35.3.1/DeveloperGuide/text/HR/JetsonModuleAdaptationAndBringUp/JetsonAgxOrinSeries.html#for-rgmii

tegra234-ethernet-3737-0000.dtsi (2.1 KB)
tegra234-mb1-bct-pinmux-p3701-0000-a04.dtsi (63.6 KB)

The result are as below:

And It looks the interrupt pin doesn’t work.
Is it related?

Could I try anyting on BSP??

[WayneWWW]

If interrupt does not come in /proc/interrupts it means your pinmux is still wrong.

[sumin.lee1]

There is no interrupt for RGMII.

I checked a lot matching values between “guide” and “tegra234-mb1-bct-pinmux-p3701-0000-a04.dtsi”
And I can’t find any more different.

Futhermore, I add the gpio on the “tegra234-mb1-bct-gpio.dtsi”

tegra234-mb1-bct-gpio-p3701-0000-a04.dtsi (4.9 KB)
tegra234-mb1-bct-pinmux-p3701-0000-a04.dtsi (63.7 KB)

Do you have any idea for pinmux setting???

[WayneWWW]

Are you still using MGBE ethernet or not? If not, please disable it

[sumin.lee1]

It was using MGBE before.
And then MGBE is disabled in now.
But it doesn’t work as same.

[WayneWWW]

please share the interrupt result again.

[sumin.lee1]

There is no result for eth.

[WayneWWW]

please share me the whole result. No need to grep anything by yourself. Even the dmesg does not need grep.

Just share any kind of full log to NV moderator in future. We don’t need to you parse log unless we tell you to do that.

[sumin.lee1]

OK, I see.
Here it is for full result.
interrupt_without_MGBE.txt (21.1 KB)

[WayneWWW]

Could you check /proc/deivce-tree node on your jetson to make sure everything you add in device tree is really present there?

[sumin.lee1]

I already extracted the dts file from /proc/device-tree with device-tree-compiler.
extract.dts (523.5 KB)
I can see about eqos.
But, I’m not sure those hex data what are meaning.

And I don’t kwon well how to ckeck pinmux status on this file.

[WayneWWW]

Please share the full dmesg…

[sumin.lee1]

Here it is.
dmesg.txt (65.3 KB)

[WayneWWW]

Does this carrier board ever got validated on other modules like xavier AGX before?

[sumin.lee1]

The board is newly developed for AGX Orin.
And the schematic is refered to AGX Xavier board what we develped before.
So, this board wasn’t verified for AGX Xavier.

Anyway, I try to install and boot for AGX Xavier.
These are status of AGX Xavier.
dmesg_xavier.txt (76.1 KB)
interrupt_xavier.txt (11.3 KB)

[sumin.lee1]

Dear, @WayneWWW

Could you give us any tip or test to forward for this issue?

Do you think we need to check hardware signal ?
Or we can do any other test on the linux?

[WayneWWW]

Hi,

You can check the flash log to make sure your pinmux really got flashed.

If it really got flashed, then I think it could be hardware issue.

[WayneWWW]

We have patches here and maybe you can directly give a try. In case there is something wrong.
eqos-2310000-ether-DTB.patch (2.3 KB)
eqos-2310000-ether.patch (7.6 KB)

[sumin.lee1]

Thanks for the patch file. ^^

I tried the patch file ald bsp and new bsp.
But the RGMII still isn’t enabled for our board.

I think I would try to check hardware signals.