Hi
1.We have a Jetson Orin module. I’ve flashed the module with Jetson Linux 35.4.1 and it boots successfully on the dev kit. However when we put it on our custom board, the module show “Busy Spin”
ERROR MESSAGE:
E> I2C: slave not found in slaves.
E> I2C: Could not write 0 bytes to slave: 0x00ac with repeat start true.
E> I2C_DEV: Failed to send register address 0x00000000.
E> I2C_DEV: Could not read 256 registers of size 1 from slave 0xac at 0x00000000 via instance 0.
E> eeprom: Failed to read I2C slave device
C> Task 0x0 failed (err: 0x1f1e050d)
E> Top caller module: I2C_DEV, error module: I2C, reason: 0x0d, aux_info: 0x05
I> Busy Spin
My custom board does not have AT24C02D-MAHM-T
What is the function of this EEPROM?
How can I avoid this problem?
Orin module + custom board NV_MY_D.log (19.5 KB) Orin module + dev kit NV_EVB_D.log (111.6 KB)
I refer to the following website to modify the EEPROM and it can boot successfully.
USE module
7023 for Jetson AGX Orin (P3701-0000 Developer Kit module)
https://docs.nvidia.com/jetson/archives/r36.2/DeveloperGuide/HR/JetsonModuleAdaptationAndBringUp/JetsonOrinNxNanoSeries.html#eeprom-modifications
Also modify Linux_for_Tegra/bootloader/tegra234-mb2-bct-misc-p3767-0000.dts.
But change use
7223 for Jetson AGX Orin (P3701-0004 with 32GB)
can’t boot successfully
7023 for Jetson AGX Orin (P3701-0000 Developer Kit module)
and
7223 for Jetson AGX Orin (P3701-0004 with 32GB)
Is there any difference in compilation or burning between the two???
