2,008
edits
Changes
Jump to navigation
Jump to search
Line 12:
Line 12: − +
RaspberryPI I2C confilct problem (view source)
Revision as of 16:03, 20 January 2021
, 16:03, 20 January 2021→Hardware solution (recommended)
To be able to use this I2C interface on CPU, we use the ''camera_i2c_config'' script to expose VC-I2C to CPU which creates a problem:
To be able to use this I2C interface on CPU, we use the ''camera_i2c_config'' script to expose VC-I2C to CPU which creates a problem:
'''When using our CSI-2 camera module and screen of the DSI-2 interface at the same time, CPU controls the camera module through VC-I2C as the master, and GPUcontrols the LCD screen through VC-I2C as the master too. There is a certain probability that there will be I2C access conflicts, which will lead to possible I2C miscodes and misconfigurations.'''
'''When using our CSI-2 camera module and screen of the DSI-2 interface at the same time, the CPU controls the camera module through VC-I2C as the master, and the GPU controls the LCD screen through VC-I2C as the master too. There is a certain probability that there will be I2C access conflicts, which will lead to possible I2C miscodes and misconfigurations.'''
=== Solution ===
=== Solution ===