If this is a sku 0000 module, then pinmux setting by default is using tegra234-mb1-bct-pinmux-p3701-0000.dtsi.
If this is sku 0004 module, then it should be tegra234-mb1-bct-pinmux-p3701-0000-a04.dtsi.
And again, it is just default setting, if you changed anything on your side, I won’t know.
I changed nothing just flashing with command ./flashing jetson-agx-orin-devkit mmcblk0p1
In flash log it shows Board ID(3701) version(500) sku(0000) revision(J.0)
so, I changed to pinmux in tegra234-mb1-bct-pinmux-p3701-0000.dtsi also.
just confirm once my dtsi modification are correct or not.why i am asking means if dtsi files are correct.
In hardware TX of RGMII interface are connected with Tx of KSZ swtich.
in schematic Straight cable connection there i will cross check with that part also.
tegra234-base-overlay.dtsi.txt (19.3 KB)
tegra234-mb1-bct-gpio-p3701-0000.dtsi.txt (4.9 KB)
tegra234-mb1-bct-gpio-p3701-0000-a04.dtsi.txt (4.8 KB)
tegra234-mb1-bct-pinmux-p3701-0000.dtsi.txt (63.6 KB)
tegra234-mb1-bct-pinmux-p3701-0000-a04.dtsi.txt (63.6 KB)
Could you stop doing this “because you told me the pinmux might be wrong so I just changed it” thing?
Your flash log will tell which pinmux file got flashed. If you really cannot read, you could post out the log and we can tell you which file is in use.
Also, if this is a switch case, then your RGMII setting in the device tree is wrong.
There are other users sharing their expereince which you could check.
Flash_log.txt (154.2 KB)
This i attached flash log
In this flash log i understand i need to change in this file tegra234-mb1-bct-pinmux-p3701-0000-a04.
what ever the modification in nvidia adaption document is there i did all.
that why i am asking confirmation from you.
I asked about why MDIO address not found.what the possibilities to get MDIO address not found.
I will looks towards that.
I shared flash log ,dtsi files,bootlog and dmesg everything.
@WayneWWW why i am asking confirmation of dtsi files means.
eth1 is showing in ifconfig -a
eth1 is now showing in ifconfig there might be hardware problem also.
@WayneWWW
In boot log
[ 10.045611] nvethernet 2310000.ethernet: Ethernet MAC index missing
[ 12.904157] mdio_bus 6800000.ethernet: MDIO device at address 0 is missing.
[ 12.904187] nvethernet 6800000.ethernet: failed to connect PHY
[ 12.904195] net eno1: ether_open: Cannot attach to PHY (error: -19)
[ 13.170365] mdio_bus 2310000.ethernet: MDIO device at address 1 is missing.
[ 13.170422] nvethernet 2310000.ethernet: failed to connect PHY
Ethernet MAC index is missing it mean.
boot-log.txt (68.8 KB)
in dmesg : MDIO bus registered is now showing
@WayneWWW I looked into hardware also i found Ethernet switch configured in SPI mode,We make changed into MIIM.
Now we are getting
[ 16.160535] nvethernet 2310000.ethernet: [poll_check][42][type:0x4][loga-0x0] poll_check: timeout
[ 16.160548] nvethernet 2310000.ethernet: ether_open: failed to initialize MAC HW core with reason -1
dmesg log.txt (6.6 KB)
we need to configure gpio,pinmux and dts file is correct
there is issue with reset pin issue hardware.
now i am able see the eth0 in ifconfig.
I checked with ethtool eth0 link status is ok.
Thank @WayneWWW but ping is not happens.if you have any idea on it please let me know
MAC index is missing,is this affect pinging.
@WayneWWW can you refer any document i need to follow for pinging issue.
I configure the eth0 with ifconfig tool
ifconfig 192.168.1.90 netmask 255:255:255:0.
we are using jet-pack 6 version ubuntu 22.04