Hello,
And i have flashed linux kernel version 4.9 (L4T 32.4.4) Ubuntu 18.04 , in my Jetson NX SOM module custom carrier board.
Here,
Internal EEPROM is connected to SoM via Bus I2C2 at address 0x57.
Connected External EEPROM to my carrier board by pin-27/pin-28 for I2C bus1 of 40 pin header…
It is really not good to share any log and code as a photo when your photo is not clear.
Also, share the board schematic since this is a custom board.
I am not sure why we have a “internal eeprom” here, what does that mean? The module eeprom? Why did you customize the module eeprom? This stuff is inside SOM and cannot be changed.
In my custom carrier board , If i want to connect EEPROM to I2C2 Device Address: 1010111 = 0x57H , What changes are required to be made in DTS file or any other file?
First one is on the SOM. i2c bus 0 address 0x50H. This one is needed and cannot be removed.
Second one is on the devkit, i2c bus 0 address 0x57H. This one is not required for booting. Which means if you have any problem in booting on custom board, this EEPROM has nothing to do with it.
But , i have an issue with my custom carrier board , its not booting up… and i am getting continous unstopable logs, and their i am getting error in EEPROM…
[0001.520] I> Reading eeprom i2c=1 address=0x50
[0001.521] E> I2C: slave not found in slaves.
[0001.522] E> I2C: Could not write 0 bytes to slave: 0x00a0 with repeat start true.
[0001.523] E> I2C_DEV: Failed to send register address 0x00000000.
[0001.523] E> I2C_DEV: Could not read 256 registers of size 1 from slave 0xa0 at 0x00000000 via instance 1.
[0001.532] E> eeprom: Retry to read I2C slave device.
[0001.537] E> I2C: slave not found in slaves.
[0001.541] E> I2C: Could not write 0 bytes to slave: 0x00a0 with repeat start true.
[0001.549] E> I2C_DEV: Failed to send register address 0x00000000.
[0001.554] E> I2C_DEV: Could not read 256 registers of size 1 from slave 0xa0 at 0x00000000 via instance 1. [0001.564] E> eeprom: Failed to read I2C slave device [0001.569] I> Eeprom read failed 0x3526070d
[0001.573] I> create_pm_ids: id: 3668-0000-200-J, len: 15
But sir, if it would have been a hardware issue,
then how Nano SoM is working in same custom board , whereas NX SoM is not working in that carrier board.
Hardware issue would have been resulted the same for both the SoM’s.