We are currently working with a TX2 that has 6 cameras attached, there are two cameras per i2c bus on the following buses:
We are unable to communicate with the cameras randomly, getting the following message on kernel ring buffer :
[ 144.693153] tegra-i2c c250000.i2c: no acknowledge from address 0x10
To be a little bit more specific, the TX2 is mounted on a carrier board were we could use the TX1 and it work properly with the same 6 cameras; we switched to the TX2 using the version of Jetpack that is intended for that use and we updated it to include the driver. We also updated the device tree and are able to capture frames, however there seems to exhibit a random I2c communication issue. Currently we suspect that is a software issue, since this is what we checked so far:
1- We tried changing the pull up registers to optimize the waveform on the i2c bus and it didn’t made any difference. So it seems like is not a hardware issue ( also ,it was working on TX1).
2 - The issue seems related to the amount of devices on the i2c bus. When more than one cam is connected, the error occurs most of the time (two cameras on the same bus don’t share the same address, and as I said it was working on the TX1).
3 - The issue seems related to the i2c port. At some combinations of cams the error occurs more, than on others .
We are now guessing that this issue might be related to:
- i2c speed
- i2c settings
- OS i2c resource Management
Is there any difference to the i2c bus configuration on TX2 from TX1? any pointer will be gladly appreciated.