Hi team,
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Hi team,
Hi Shinji,
For the SOC in the ECU unit to send commands via I2C to the CMOS censor in the Camera Unit, please enable I2C passthrough mode and use slave aliases for each of the FPD link III portions of the signal chain.
Letst first work backwards logically to determine address mappings from the CMOS sensor:
Ensure the slave address used for the CMOS Sensor for the 953 and 954 in the Camera Unit / Video splitter unit map to the i2c address of the CMOS sensor.
Ensure the slave address for used for the CMOS sensor for the 953 and 954 in the Video Splitter Unit / ECU map to slave address used for the CMOS Sensor for the 953 and 954 in the Camera Unit / Video splitter unit.
Sincerely,
Bryan Kahler
Hi Bryan,
I'm little confused between Slave address and Slave Alias address.
First of all, the image in Jiashow's reply is correct or not?
regards,
?Hi Brian,
I would like to monitor register value in CMOS image sensor chip through I2C between UB954_1 and UB953_1 by SoC in Video Splitter Unit.
Isn't it possible to connect I2C pins of the SoC to this I2C bus?
regards,
Hi Tsuji-san,
The way you have connected the I2C buses in the block diagram is correct. The difference between the slaveID and slaveAlias is that when the host sends a command to the slaveAlias, the device will look up this slaveAlias and see if it has a slaveID associated to it. If so, then the device sends it to the device with the slaveID.
If you follow my diagram to set the slave ID and aliases you should be able to communicate to all the devices. Only communicate using the slave alias addresses.
Best,
Jiashow
Hi Shinji,
Yes, the addressing example given by Jiashow is correct.
SLAVE_ID_N (where n is a value 0-7) refers to the actual i2c address of the device.
SLAVE_ID_ALIAS_N refers to the new address mapping.
Let's refer to the i2c network between the CMOS sensor and 953_2 as camera unit i2c network.
Let's refer to the i2c network between the 954_2 (shown as 954_1 in the image above) and 953_1 as video splitter unit i2c network.
So for example (we will use N=3 for this device in this example), if the CMOS sensor has an i2c address of 0x20, set its SLAVE_ID_3 = 0x20 and set the corresponding SLAVE_ID_ALIAS_3 = 0x34. These settings will be performed on the 954_2 via commands sent on the video splitter unit i2c network.
This mapping will now cause i2c commands with an address of 0x20 on the camera unit i2c network to appear on the video splitter unit i2c network as 0x34.
This describes the mapping of the CMOS sensor between these two aforementioned i2c networks. Mapping may also be performed for commands between the video splitter unit i2c network and the ECU i2c network.
It is possible to connect a SOC to the video splitter unit i2c network. Multi master is possible, but it will be up to your devices to properly handle the multi master arbitration across the 3 i2c nets.
Sincerely,
Bryan Kahler
Hi Bryan,
Could you advise how long should I take the latency into account for FPD-Link video signals and I2C signals
by UB953-1/954-1 in video splitter Unit?
regards,
Hi Tsuji-san,
Local I2C communication latency is negligible compared to back channel latency. The I2C latency through the back channel is ~1us. So if there are two back channels, it'll be ~2us.
Best,
Jiashow
Hi Jiashow,
Thank you.
How long is the FPD-Link High speed signal's latency between them?
BR
Shinji
Hi Jiashow,
Do you mean the latency between 954 input to 953 output is ~225ns?
regards,