hello, our custom carrier board have no eeprom and i2c,so we can’t get mac address from it ,so when drive probe ,it report an error,how can i give a mac in uefi , i need some help ,such as for more details code .Thanks
MAC address is read from module eeprom. Not your carrier board.
Please check if you disable RGMII node in UEFI dtb. That will cause MAC addr not appeared in DT.
you mean mac address in module eeprom ,and it is defined in factory. we change the tegra234-mb2-bct-common.dtsi epprom readsize both to zero, is it right?

We only asked you to disable cvb eeprom… not cvm eeprom…
Checked with the document.
does ethernet 6800000matter ? i have disabled it in tegra234-p3737-0000+p3701-0000.dts,but dmesg i still can see it .
It means you didn’t disable it correctly…
Check your pinmux file is really same as the document and whether it got flashed to the board correctly.
I won’t do that for you. You have to check by yourself.
i want to know how can configur rx node eqos_td0_pe6
Check the pinmux dtsi directly.
only lack of eqos_td0_pe6 this node my dtsi
Looks like a document typo. No such pin is needed. Please just focus on
![]()
we have check it carefully , change RX to pull up ,now it is all the same ,but it still can not link detected . what should i dow now ,please give some sugesstions . thankyou.
tegra234-mb1-bct-pinmux-p3701-0000.dtsi.txt (65.7 KB)
- Please always share the full dmesg as text file… I don’t want to see any parse by you or any screenshot.
- Please dump cat /etc/nv_boot_control.conf result from your board.
thanks for your support ,here are our dmesg info and nv_boot_control
cat etcnv_boot_control.conf.txt (285 Bytes)
dmesg.txt (59.4 KB)
This is Orin industrial module. The default pinmux file is not tegra234-mb1-bct-pinmux-p3701-0000.dtsi.txt …
Are you sure the file got flashed to your board is correct?
i guess it has effect ,because i rename and replace it in Linux_for_Tegra/bootloader/generic/BCT/tegra234-mb1-bct-pinmux-p3701-0000-a04.dtsi and Linux_for_Tegra/bootloader/generic/BCT/tegra234-mb1-bct-pinmux-p3701-0000.dtsi both , our pcie pinmux, can all take effect
interrupt.txt (1005 Bytes)
and our interrupt can not increase , it keep the status .
our H5 J5 pin do not acess to phy soc in hardware ,does it matter ?


