We designed the carrier board based on the AGX Orin core module. When a set of 20+power is applied, the system fails to start once. The message is printed through the serial port and prompts the following message:
[0001.000] E> I2C: slave not found in slaves.
[0001.004] E> I2C: Could not write 0 bytes to slave: 0x0040 with repeat start false.
[0001.012] C> NONE: Failed to update reg address 0x4b of slave 0x40 in i2c block :0 in pad voltage config table.
[0001.022] C> Task 0x3a failed (err: 0xf573d02)
[0001.026] E> Top caller module: CPUINIT, error module: PMIC_CONFIG, reason: 0x02, aux_info: 0x3d
[0001.035] C> Boot Info Table status dump :
0111111100111000111111111111111111111111111110111011111101
*** Please note that this reply is generated by LLM automatically ***
The error messages you’re seeing suggest that there’s an issue with the I2C communication between the Jetson AGX Orin module and the carrier board. Specifically, it seems that the module is unable to communicate with the PMIC (Power Management IC) on the carrier board.
Here are some potential causes and troubleshooting steps:
I2C bus issues: The error messages indicate that the I2C slave is not found, and there are issues with writing to the slave device. Check the I2C bus connections between the Jetson AGX Orin module and the carrier board. Ensure that the I2C bus is properly connected, and there are no shorts or opens on the bus.
PMIC configuration: The error messages mention the PMICCONFIG module and an error code 0x02. This could indicate a configuration issue with the PMIC. Check the PMIC configuration on the carrier board and ensure that it matches the expected configuration for the Jetson AGX Orin module.
Voltage regulator issues: The error messages also mention a pad voltage config table error. This could indicate an issue with the voltage regulators on the carrier board. Check the voltage regulator settings and ensure that they are correct for the Jetson AGX Orin module.
Boot configuration: The error messages mention a Boot Info Table status dump. This could indicate an issue with the boot configuration. Check the boot configuration on the carrier board and ensure that it is correct for the Jetson AGX Orin module.
To troubleshoot and resolve this issue, you can try the following steps:
Check the carrier board design: Review the carrier board design and ensure that it matches the recommended design for the Jetson AGX Orin module.
Verify the I2C bus connections: Use a multimeter to verify that the I2C bus connections between the Jetson AGX Orin module and the carrier board are correct.
Check the PMIC configuration: Use a PMIC configuration tool to verify that the PMIC configuration on the carrier board matches the expected configuration for the Jetson AGX Orin module.
Verify the voltage regulator settings: Use a multimeter to verify that the voltage regulator settings on the carrier board are correct for the Jetson AGX Orin module.
Try a different boot configuration: Try changing the boot configuration on the carrier board to see if it resolves the issue.
If none of these steps resolve the issue, it may be helpful to consult the Jetson AGX Orin module documentation and the carrier board design documentation for further troubleshooting guidance.
In comparison to other similar issues, this issue seems to be related to the I2C communication between the Jetson AGX Orin module and the carrier board, which is a common issue in many embedded systems. The error messages and troubleshooting steps are similar to those seen in other I2C-related issues. However, the specific cause and solution may vary depending on the carrier board design and the Jetson AGX Orin module configuration.
*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***
Have you made any hardware or software modifications, or modified any BSP files?
From the file Linux_for_Tegra/bootloader/tegra234-mb2-bct-common.dtsi, it appears that the EEPROM address is not set to 0x40.
The cann’t to boot is occasional, occurring only once every few dozen times. After boot ok, the I2C address configuration can be seen as 0x40 through the reverse device tree.
May I ask what else can be investigated? May I ask which I2C channel corresponds to the hardware of this I2C bus? I2C1 (pin-K5/L8) or I2C2 (pin-J61/K61)
From the serial port information, it is not indicated that there was an error reading eeprom, but rather an error accessing the device with address 0x40 by i2c. The device with address 0x40 can be seen as a power monitoring chip through the device tree. Will this affect the startup? Or was it supposed to read eeprom, but got it wrong?What other places can be look?
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 ~1105
Is this still an issue to support? Any result can be shared?
