Ethernet via RGMII on custom board

Autonomous Machines Jetson & Embedded Systems Jetson AGX Orin
,
1

Hi.
I’m having trouble getting some functionality to work on my own carrier board for NVIDIA 900-13701-0040-000. One of them is RGMII. Hardware-wise it is actually a copy of the solution from Jetson Xavier. The PHY chip is a Marvell 88e1512.

Schemat:

image
image1565×589 10.6 KB

image
image1722×737 29.1 KB

The problem is that I can’t establish communication with the chip.

image
image1263×178 96.9 KB

image
image1263×224 152 KB

I prepared the .dtsi files by myself: pinmux, padvolage and gpio. I attach the files below.

Orin-orin_full_config-pinmux.dtsi.txt (65.7 KB)
Orin-orin_full_config-gpio-default.dtsi.txt (4.6 KB)
Orin-orin_full_config-padvoltage-default.dtsi.txt (2.4 KB)

Next, I build and uploaded the software. I am attaching the logs.

  1. booting:
    putty_log_29_10_boot.txt (65.3 KB)

  2. dmsg:
    putty_log_29_10_dmesg.txt (39.7 KB)

  3. devicetree:
    putty_log_29_10_devicetree_nowe.txt (543.9 KB)

  4. tests eth:
    putty_log_29_10_ethtest.txt (1.8 KB)

Can I ask for guidance to determine what I haven’t done yet or have done wrong?

2

Hi,
If the device cannot be flashed/booted, please refer to the page to get uart log from the device:
Jetson/General debug - eLinux.org
And get logs of host PC and Jetson device for reference. If you are using custom board, you can compare uart log of developer kit and custom board to get more information.
Also please check FAQs:
Jetson AGX Orin FAQ
If possible, we would suggest follow quick start in developer guide to re-flash the system:
Quick Start — NVIDIA Jetson Linux Developer Guide 1 documentation
And see if the issue still persists on a clean-flashed system.
Thanks!

4

I saw that the interrupt is not connected.

And you didn’t share the kernel dt which should be as this

https://docs.nvidia.com/jetson/archives/r35.6.0/DeveloperGuide/HR/JetsonModuleAdaptationAndBringUp/JetsonAgxOrinSeries.html?highlight=rgmii#for-rgmii

5

WayneWWW
I suppose that an unconnected interrupt pin should not interfere with the proper operation of Marvel, but we are currently verifying this theory by connecting it. Also, MDIO support seems to be independent.
Regarding the link you’ve provided - we’ve compared our device tree with the entries from “Porting the Universal Serial Bus” documentation section, “For RGMII” subsection. The question is - is there exists a sample devicetree configuration file for RGMII ethernet that we could quickly attach and modify? There are a few parameters to change, we don’t want to break something in the process.

Hi,
If the device cannot be flashed/booted, please refer to the page to get uart log from the device:

carolyuu It is possible to flash/boot the device. I’ve posted the logs above from the enabled device.

6

I don’t know what you are reading here as my post directly links to the RGMII section with device tree example.

8

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.