TDES954: Connecting with TSER953 with STP mode for ar1044CS camera module.

Other Parts Discussed in Thread: TSER953, TDES954, ALP

Tool/software:

Trying to connect the TDES954 to TSER953 with STP mode to interface the AR1044CS Camera module.

These are the registers used to initialize the de serializer:

        add_write(&core, 0x01, 0x01, 0);
        add_delay(&core, delay_reset_assert_ms);
        add_write(&core, 0x1F, 0x03, 0);
        add_write(&core, 0x33, 0x23, 0);
        add_write(&core, 0x4c, 0x03, 0);
        add_write(&core, 0x6D, 0x78, 0);
        add_write(&core, 0x0c, 0x47, 0);
        add_write(&core, 0x58, 0x5e, 0);
        add_write(&core, 0x5c, 0x12, 0);
        add_write(&core, 0x5d, 0x20, 0);
        add_write(&core, 0x65, 0x20, 0);
        add_write(&core, 0x20, 0x10, 0);

Then we wrote

0x02 0x52

to the serializer to switch it to CSI 2 lanes.

We tried enabling BIST mode by setting register 

0xB3 to 0x81, is there anything else we need to change to run through bist and if we can see the errors in 0x57 immediately as it appears as 0x00 for us.

serializer lane with bist:

deserializer lane with bist:

  • Hello Anthony,

    First off, are you able to get stable LOCK when the 954 and 953 devices are connected and powered-up? LOCK should happen automatically after power-up. If LOCK is not up, then there may be an issue with the MODE settings on either the serializer or deserializer.

    You can check if LOCK is stable by performing these steps on the TDES954 device:

    1) Set 954 reg 0x4C = 0x01 # This select RX Port 0 as the receiver port. Set this to 0x12 if your serializer is connected to RX Port 1 instead.

    2) Read 954 reg 0x4D # Make sure this register reads 0x03. You can read this register multiple times to get an accurate reading, since these registers are cleared on read.

    ...

    You can also provide a register dump of the 954 and 953 if you would like us to check the registers.

    ...

    For the BIST script, we provide an example script to run BIST between the 954 and 953 devices. If you install ALP (https://www.ti.com/tool/ALP) there will be a folder on your computer with pre-defined example scripts. See example directory path below:

    C:\Program Files (x86)\Texas Instruments\Analog LaunchPAD v1.57.0010\PreDefScripts\DS90UB954\ub954_margin_analysis_script

    Best,

    Justin Phan

  • It does seem to lock we are able to see the serializer i2c id and the camera i2c id from the de-serializer's link.

    Below are the dumps while trying to get the AR0144CS camera to work through the deser and ser.

    Deser i2c dump:

    ser i2cDump:

  • Hello Anthony,

    Okay, it seems you have LOCK now. If you have established LOCK and are able to send I2C commands to the remote camera module, then you should be able to bring-up the system. Are you able to send I2C commands to the imager and confirm video is sent?

    ...

    If you do not have video, then you can use BIST and MAP to check the quality of the link.

    Once you enter BIST mode, you need to manually inject errors onto the link. Once you exit BIST mode, then the BIST error counters will update. If there are more errors than the number of errors you manually injected, then there may be issues with your link.

    For the BIST script, we provide an example script to run BIST between the 954 and 953 devices. If you install ALP (https://www.ti.com/tool/ALP) there will be a folder on your computer with pre-defined example scripts. See example directory path below:

    C:\Program Files (x86)\Texas Instruments\Analog LaunchPAD v1.57.0010\PreDefScripts\DS90UB954\ub954_margin_analysis_script

    Were you able to find the example scripts that TI provides for running BIST?

    You can also run the MAP tool to check the margin of the link.

    C:\Program Files (x86)\Texas Instruments\Analog LaunchPAD v1.57.0010\PreDefScripts\DS90UB954\953_954_BIST.py

    Best,

    Justin Phan