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.

TSER953: Technology support for TSER953 & TDES954

Part Number: TSER953
Other Parts Discussed in Thread: TDES954

Hi,

Please advise the below support need:

1. We use the TSER953 & TDES954 for camera signal  Serializer and Deserializer, we wants to know there are any test equipment promote to measure v3-link signal accuracy, 

    and please advise if there are any standard V3 link signal model for our evaluation;

2. How to check the V3 LINK signal is noraml in the mass production;

3. How the test the image signal is normal or not, like as the Stability/ Frame loss rate/ Delay and so on?

  • Hello,

    Thank you for your questions. There are many diagnostic tools and registers available to check and verify the signal of these devices. I believe you are asking about ways that you can ensure no errors are occurring or being transmitted. For that the registers below will be helpful.

    On the 954 register 0x04 (Device_STS) can indicate if pass or lock status has been attained. This means that the 954 has locked onto the 953 and is receiving/transmitting valid data. In registers 0x4d (RX_PORT_STS1) and 0x4E (RX_PORT_STS2) contain bits that can flag when there is a change in lock status, detect errors on the forward channel, detect parity and CRC errors, along with stability of the signal based on the line length and lines per video frame. The exact amount of parity errors can also be found in the registers 0x55 (RX_PAR_ERR_HI) and 0x56 (RX_PAR_ERR_LO). Lastly, if you know the correct line length and line length of the data being sent you can compare that value to the values stored in registers 0x73 and 0x74 (LINE_COUNT) and 0x75 and 0x76 (LINE_LEN).

    The pass and lock status can also be found by probing the corresponding pins instead of reading the registers. On the 954 this is pins 47 and 48. I'd recommend reviewing section 7.4.7 of the datasheet for more details on the lock and pass status features. In addition to registers, for when the device is in operation, BIST mode is also able to test the link between the two devices without any input data needed. For more information on this please see section 7.5.12 of the 954 datasheet.

    The 953 is similar, but it also has CSI status and error registers in register 0x5D (CSI_ERR_STATUS), 0x5C (CSI_ERR_CNT), 0x5E and 0x5F (CSI_ERR_DLANE), and 0x60 (CSI_ERR_CLK_LANE)

    Regards,

    Darrah

  • Hi Darrah,

    Thanks for your detail comment for this issue. Our software engineer will test the register bese on your suggestion soon;

    Now we have some other issue:

    1) The maximum output power for the POC, we get the data from the data is 1.8V/150mA, pleaes advise if this can support the 10W output;

    2) The MIPI signal is raw8 data format, and we transfer this MIPI data from TSER953/ TDES954 to CPU, but we can't get the whole MIPI signal

        based on raw8 format, and we need to change to raw10 data format, so we consider the TSER953/ TDES954 don't suppor the raw8 data transfer, right?

  • 1) TI recommends using one of the provided POC network examples. You can find one in section 8.1.1 of the 953 datasheet. This example has been validated to work with the devices. If you'd like to use a custom made POC network, you'll need to validate that the network works with the devices and follows the guidelines/specs documented in the datasheet. In addition to section 8.1.1 of the datasheet this app note also explains some helpful design guidelines. 

    2) Can you explain what you mean by not getting the whole MIPI signal? Raw8 data type is supported by the TSER953/TDES954. Are you using CSI mode?

  • Hi Darrah,

    Thanks for your reply;

    Now, we consider to use the Raw8 signal to CPU processor and there are any reference software for the date transfer from image SOC to CPU, thanks.

  • I'm not sure I'm understanding your question. Could you try to rephrase the issue?