can you please find the newly updated changes in the tegra234-base-overlay.dtsi
tegra234-base-overlay.dtsi.txt (19.6 KB)
After the changes i have made and below logs are coming
Can you please confirm me where i’m missing.
eth_boot_log5th.txt (81.9 KB)
I guess your pinmux didn’t get into it at all.
Please check your flash config and make sure your pinmux dts really gets flashed into it.
tegra234-base-overlay.dtsi.txt (19.6 KB)
tegra234-p3737-0000+p3701-0000.dts.txt (10.3 KB)
tegra234-mb1-bct-pinmux-p3701-0000.dtsi (63.6 KB)
tegra234-mb1-bct-gpio-p3701-0000.dtsi.txt (4.8 KB)
Can you please confirm me gpio,pinmux,dts files are correct or not ?
and also can confirm me how to verify the pinmux is get into the flash config
Read your flash log… if you don’t know what to check ,share your log here…
flash_log.txt (101.1 KB)
eth_boot_log5th.txt (81.9 KB)
Can you please find the both flash and boot log files
Search “pinmux” in your log and tell me what do you see…
it is trying to copy the tegra234-mb1-bct-pinmux-p3701-0000-a04.dtsi file
should i need to modify the pinmux into tegra234-mb1-bct-pinmux-p3701-0000-a04.dtsi file?
yes… that one is the right one.
tegra234-mb1-bct-pinmux-p3701-0000-a04.dtsi.txt (63.6 KB)
custom board is not booting after made the changes of pinmux into file
please find the boot log
Boot_log.txt (35.1 KB)
Then go back and search what change did you make to cause this situation…
when changes made in the egra234-mb1-bct-pinmux-p3701-0000-a04.dtsi board is not booting completely.
Thank you Wayne for your Support,
issue was ressolved now we are able to detect eth1 when the command run ifconfig.
can you please tell me the process to make the phy lines up so that eth1 bring up for ethernet connectivity
sharing the boot log along with the commands.
eth1_bootlog.txt (79.9 KB)
Hii WayneWWW
1.can you please confirm the all gpio,pinmux,dts files correct or not
2. we configured the reset pin as output low and interrupt pin as input.
after your confirmation we will look toward the hardware.
tegra234-mb1-bct-pinmux-p3701-0000-a04.dtsi.txt (63.6 KB)
tegra234-mb1-bct-gpio-p3701-0000-a04.dtsi.txt (4.8 KB)
tegra234-base-overlay.dtsi.txt (19.3 KB)
ethernetBootLog.txt (88.1 KB)
Why are you setting GPIO G5 to output low? Anyone suggested you to do that?
Could you dump /proc/interrupts when you enable the interface?
this is given in the document as the changes that we have to do
soc_gpio17_pg4 {
nvidia,pins = “soc_gpio17_pg4”;
nvidia,function = “rsvd0”;
nvidia,pull = <TEGRA_PIN_PULL_UP>;
nvidia,tristate = <TEGRA_PIN_ENABLE>;
nvidia,enable-input = <TEGRA_PIN_ENABLE>;
nvidia,lpdr = <TEGRA_PIN_DISABLE>;
};
soc_gpio18_pg5 {
nvidia,pins = “soc_gpio18_pg5”;
nvidia,function = “rsvd0”;
nvidia,pull = <TEGRA_PIN_PULL_NONE>;
nvidia,tristate = <TEGRA_PIN_DISABLE>;
nvidia,enable-input = <TEGRA_PIN_DISABLE>;
nvidia,lpdr = <TEGRA_PIN_DISABLE>;
};
as per the document it is mentioned like pg5 is reset and pg4 is interrupt and our custom board also has the same .so we made it low .
And we are considering interrupt as input ,reset as output
There is no update from you for a period, assuming this is not an issue anymore.
Hence, we are closing this topic. If need further support, please open a new one.
Thanks ~0409
Is this still an issue to support? Any result can be shared?