I am trying to get AGX Orin to boot on our custom board. We have EEPROM (AT24C02 with address: 0x56) on it. When booting up, the following error appears:
W> Skip ratchet update - OPTIN fuse not set
I> Task: Prepare eeprom data
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: Retry to read I2C slave device.
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.
Hi,
If the device cannot be flashed/booted, please refer to the page to get uart log from the device: Jetson/General debug - eLinux.org
And get logs of host PC and Jetson device for reference. If you are using custom board, you can compare uart log of developer kit and custom board to get more information.
Also please check FAQs: Jetson AGX Orin FAQ
If possible, we would suggest follow quick start in developer guide to re-flash the system: Quick Start — NVIDIA Jetson Linux Developer Guide 1 documentation
And see if the issue still persists on a clean-flashed system.
Thanks!
From the log you shared, it seems the issue relating to failed reading EEPROM through I2C.
Is there any custom design in EEPROM different from the devkit?
Hi KevinFFF
I using JetPack version 6.1
The design of the custom board is similar to the devkit in the eeprom part, it both uses i2c1: I2C_GP1_CLK and I2C_GP1_DAT.
This is the log when booting:
If you have similar design about EEPROM as the devkit, then you should not hit this issue.
Please get a devkit board and compare the difference from serial console log and also the signal on this I2C bus.
Or you can refer to Modifying the EEPROM with the modification to check if it would still hit that error.