Hi All,
In my custom board RGMII interface was not pinging.
with ifconfig it shows eth1,I assigned address to it but it is not pinging.
Can you please verify my dts files. let me correct if i am wrong.
ethernetBootLog7th.txt (103.1 KB)
tegra234-base-overlay.dtsi.txt (19.4 KB)
tegra234-mb1-bct-gpio-p3701-0000-a04.dtsi.txt (4.8 KB)
tegra234-mb1-bct-pinmux-p3701-0000-a04.dtsi.txt (63.6 KB)
Hi,
If you are designing a custom base board, then it means some adaptation configurations are needed.
Otherwise, your board may not work fine.
For Orin AGX series, you could refer to below document
(please be aware that above link is for rel-36.3/jetpack6.0)
This document includes below configuration
Thanks!
The pinmux file looks correct but the interrupt result from the board looks not.
Are you sure the file got flashed into the board?
yes, pinmux is flashing into the board, but i am not sure about tegra234-mb1-bct-gpio-p3701-0000-a04 is flash or not here i am sharing flashing log with you ,can you have a look.
i observed include “tegra234-mb1-bct-gpio-p3701-0000-a04.dtsi” in tegra234-mb1-bct-pinmux-p3701-0000-a04.dtsi
I need to configure Reset pin (PG5) as input or output
I configure interrupt pin(PG4) as input.
flash_log.txt (99.2 KB)
@WayneWWW @carolyuu can you please respond on my uploaded file.
did i mistake let know.
I followed adaptation document.
Let mw know which is right one.
H5 and J5 are just pin name… It is not GPIO pin #.
H5 and J5 do not mean they are GPIO H5 and GPIO J5…
GPIO pin G4 and G5 are pin H5 and J5… they are same…
tegra234-base-overlay.dtsi.txt (19.3 KB)
tegra234-mb1-bct-gpio-p3701-0000-a04.dtsi.txt (4.8 KB)
tegra234-mb1-bct-pinmux-p3701-0000-a04.dtsi.txt (63.6 KB)
I did the change as per the adaptation document for RGMII interface.
eth1 is not show in ifconfig.
Can have a look in dtsi file which i uploaded.confirm my dtsi files as correct or not.
Please check Linux_for_Tegra/bootloader and see if that pinmux file result is matching to your change.
There is a copy and real pinmux in Linux_for_Tegra/bootloader and Linux_for_Tegra/bootloader/generic/BCT.
The copy one will always get flashed first so you have to make sure you modify to correct one and that one got flashed.
Flash_log.txt (154.2 KB)
I uploaded the flash log.
We change in Bootloader/generic/BCT /tegra234-mb1-bct-pinmux-p3701-0000-a04.dtsi
it get reflected to Bootloader/tegra234-mb1-bct-pinmux-p3701-0000-a04.dtsi both are same.
I configured G4 as input and G5 as Output low.
will ODM data will effect:
Please find ODMDATA=“gbe-uphy-config-0,hsstp-lane-map-3,nvhs-uphy-config-0,hsio-uphy-config-0”;
@WayneWWW Board ID(3701) version(500) sku(0000) revision(J.0)
i am changing in the tegra234-mb1-bct-pinmux-p3701-0000-a04.dtsi.
is this correct or wrong file.
In p3701.conf.common file
PINMUX_CONFIG=“tegra234-mb1-bct-pinmux-p3701-0000-a04.dtsi”;
PMIC_CONFIG=“tegra234-mb1-bct-pmic-p3701-0000.dts”;
If i am changing correct file please verify the my dtsi file confirm once either it is correct or any modification is required.
Checking your flash log. It will tell.
by looking into flash log tegra234-mb1-bct-pinmux-p3701-0000-a04.dtsi is right one.
i did correct changes
i did correct modification as for adaptation document.
only i suspect on gpio pin configuration.
G4 we make as input and G5 we make as output low in tegra234-mb1-bct-gpio-p3701-0000-a04.dtsi file is it right ,with design document i confirm this configuration.
boot-log.txt (68.8 KB)
dmeag_log.txt (1.1 KB)
let me i am missing anything.i sent all file.
Board ID(3701) version(500) sku(0000) revision(J.0)
Are you sure this is the correct module you are using? This one actually should not use tegra234-mb1-bct-pinmux-p3701-0000-a04.dts
[ 13.170365] mdio_bus 2310000.ethernet: MDIO device at address 1 is missing.
Also, what did you change here? Your situation is worse than the first log you shared before. I think you messed up the kernel DT again.
1.change in pinmux tegra234-mb1-bct-pinmux-p3701-0000-a04.dtsi
2.change in tegra234-mb1-bct-gpio-p3701-0000-a04.dtsi
3.change in nv-soc/tegra234-base-overlay.dtsi
Is there any hardware issue.let me know i will confirm with my hardware person.
eth1 is showing if i type ifconfig -a.
@WayneWWW actually we flashing on evk board by making eeprom zero and plug out the module and plug into custom board.
in custom board we are unable to flash.
instead of tegra234-mb1-bct-pinmux-p3701-0000-a04.dts in need to change in tegra234-mb1-bct-pinmux-p3701-0000.dtsi correct.
What does that mean “making eeprom zero”? You should not modify anything for the module EEPROM.
EEPROM is an optional component for a customized carrier board. When the carrier board is designed without an EEPROM, in the Linux_for_Tegra/bootloader/tegra234-mb2-bct-common.dtsi (the MB2 BCT file), make the following modification:
- cvb_eeprom_read_size = <0x100>
cvb_eeprom_read_size = <0x0>
In schematic Orin Tx is connected to Tx of Ksz9896 switch and Rx of orin is connected to Rx of switch is it right connection.
why MDIO address not found.
what the possibilities to get MDIO address not found.
Is this connecting to a switch or phy…? They are different cases in the device tree…
