We tried to adapt the new JetPack 5.0 DP Release for our custom carrier board Xavier AGX and came across multiple issues. First we could not flash the carrier board. This was solved using the steps from the following thread (just for your information):
Now we tried to adapt the device tree for our PHY KSZ9031 as in previous JetPack Versions described in this other thread:
We see the following error messages in the “dmesg”:
[ 8.932207] nvethernet 2490000.ethernet: Adding to iommu group 31
[ 8.944695] nvethernet 2490000.ethernet: failed to read skip mac reset flag, default 0
[ 8.958930] nvethernet 2490000.ethernet: failed to read MDIO address
[ 8.976293] nvethernet 2490000.ethernet: setting to default DMA bit mask
[ 9.057539] nvethernet 2490000.ethernet: set default TXQ to TC mapping
[ 9.103367] nvethernet 2490000.ethernet: Setting default PTP RX queue
[ 9.109303] nvethernet 2490000.ethernet: failed to get eqos_rx_m clk
[ 9.117548] nvethernet 2490000.ethernet: failed to get eqos_rx_input clk
[ 9.130938] nvethernet 2490000.ethernet: failed to get eqos_tx_divider clk
[ 9.145819] nvethernet 2490000.ethernet: No MAC address in local DT!
[ 9.158666] nvethernet 2490000.ethernet: failed to get MAC address
[ 9.159490] nvethernet: probe of 2490000.ethernet failed with error -22
We are already using the new DT properties as we only adapted the “tegra194-platforms-eqos.dtsi” file in the source files. Even when we remove the added settings for the ksz9031 PHY, we get the same errors.
As we understand, normally the MAC Address is read from the EEPROM on the module, is that correct? Can the commenting out of the EEPROM lines for the flashing have an influence?
I think EEPROM plays an important role in r34.1(JP5.0); But some custom board (just like mine) maybe disable the EEPROM or in different connection. Comment out “EEPROM section” is just for flash.sh could work well temporaily, not a best solution.
I found my board ksz9896 switch and CAN ports could not adapt r34.1 using “old way” hardware dts, and I also want to know how to adapt ksz989X switch in r34.1(JP5.0)
According to offical eeprom docs, I tried “read_size” value: 150, 50, 20; all values hang at “tegrarcm_v2 --isapplet”, except 0.
When I use above minimal changes, more hardware vendor information was shown in kernel dmesg out.
Kernel 5.10 include ksz switch driver, but not compiled in default sample kernel; I think customize device tree and drivers in kernel config, rebuild kernel would bring ksz9896 switch up.
Little bug: “kernel/nvidia/drivers/misc/Kconfig:116:warning: multi-line strings not supported”
Missing ending quote of line 116;