• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 2 answers
  • Subscribers 33 subscribers
  • Views 1047 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

DS90UB954-Q1: Using Serializer and De serializer in custom board

sai jyothi
Prodigy 205 points

Part Number: DS90UB954-Q1
Other Parts Discussed in Thread: DS90UB953-Q1

Tool/software:

Hello team,

I am planning to use Serializer DS90UB953-Q1 & Deserializer DS90UB954-Q1 and the camera sensor AR0341AT in my custom board.

Camera Module has Camera sensor with 4-lane MIPI CSI is connected to Serializer IC.

2 Camera modules are planning to connect with Deserializer (DS90UB954-Q1---dual channel) through FPD-Link III interface and the O/P of Deserializer shall connect to IMX8MPlus Processor through MIPI-CSI interface, here i have a doubt, do i need to connect 4-Lane MIPI-CSI single channel or 2-Lane MIPI-CSI dual channel from processor to communicate with 2 camera modules.

  • 0
    TI__Mastermind 33030 points

    Hello Saj,

    If you want to communicate to the 2 camera modules, you can use the I2C bus. The 954-953 devices can map the I2C commands from the processor to the image sensors.

    For the CSI traces, the 954 device has only 1 CSI Port, so you must route that to a single MIPI D-PHY receiver port on the IMX8MPlus processor. You can configure the MIPI D-PHY transmitter port on the 954 to output CSI data in 1, 2, 3, or 4 lanes and at CSI speeds up to 1.6Gbps per lane, but all of these traces must be routed to a single CSI Port on the processor. CSI video data from 2 cameras will be aggregated into a single video stream. We typically expect the processor to sort out where each CSI packet is from, since each CSI packet will have its own unique VC-ID.

    Please review registers 0x1F and 0x33 in the 954 datasheet for more details.

    Best,

    Justin Phan

  • 0 in reply to Justin Phan
    Prodigy 205 points

    Hello Justin,

    Thank you for your response.

    I have a doubt on I2C connection. Please clarify.

    What i understood from the datasheets of DS90UB953 (serializer) and DS90UB954 (De serializer), the I2C from Camera sensor will connect to the Serializer and I2C from the IMX8MP will connect to the Deserializer.

    As per your comment, how the communication will happen between Serializer & deserializer through I2C.

    Also please confirm which is master and which is slave along with the I2C address in this circuit flow. Please provide more description on this.

    Regards,

    Jyothi.

  • 0 in reply to sai jyothi
    TI__Mastermind 33030 points

    Hello Jyothi,

    You are correct about the connection. If you want to send I2C commands to the serializer or the camera sensor from the IMX8MP, then the IMX8MP is the Master and the 954 will act as the proxy Slave on the same PCB. The IMX8MP can send I2C commands to the proxy slave (954). The 954 will send it to the 953. The 953 acts as a proxy Master on its PCB and convey that I2C command to the real slave, which is the camera sensor.

    The 954/953 act to bridge the I2C communication between the IMX8MP and the camera sensor. You just need to program the 954 to map the correct I2C addresses from the IMX8MP to the camera sensor.

    In order to achieve this, please make sure the IMX8MP supports I2C clock stretching. This is needed since there will b a delay when the ACK bit is sent from the camera sensor back to the IMX8MP.

    See the video below for more details

    https://www.ti.com/video/5503353885001

    Best,

    Justin Phan