• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 35 subscribers
  • Views 280 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.

DS90UB960-Q1: DS90UB935-Q1 Serdes setup getting LINE_LEN_CHG error

Parveen Bansal
Prodigy 10 points
Part Number: DS90UB960-Q1

Hi Team,

We are getting following values on status registers:

UB960 Status Register dump:

Reg          Value
0x4d          0x43
0x4e          0x44
0x55          0x00
0x56          0x00
0x7a          0x00
0x7b          0x00
0x73          0x08 (LINE_COUNT_HI)
0x74          0x70 (LINE_COUNT_LO)
0x75          0x0b (LINE_LEN_HI)
0x76          0x40 ( LINE_LEN_LO)
0x70          0x6b
0x71          0x6c
0x72          0xe4


UB935 Reg Dump:

Reg          Value
0x52         0x45
0x55         0x00
0x56         0x00
0x5c         0x00
0x5d         0x00
0x5e         0x00
0x5f          0x00
0x60         0x00
0x61         0x2c
0x62         0x40
0x63         0x0b
0x64         0x07

There is no error at serializer side, but Line Length changed error occurring at des side.

OV OX3A2S Sensor Output format : 2x12bit Raw data, (It means 12bit HCG (Higher compression ) transmitted over VC0 and 12bit LCG transmitted over VC1) so 1080 will transmit consecutively one after another for each 12bit transmitted data. So the line count recevied at des is 2160 (1080x2).

Serializer is connected to RX1 port of des. Below are setting for Serdes:

Des register setting:

0x4c 0x12
0x32 0x12
0x33 0x03
0x21 0x50
0x20 0xd2  

Ser register setting:

0x02 0x72
0x0d 0x1c
0x0e 0xd0
0x33 0x01

Basically we need to map VC0 & VC1 from sensor to Des VC0 & VC1 channel on RX1, Is there any extra register need to write for virtual channel mapping.

What is the reason for Line Length changed error, Please help us to debug this issue.

Thanks

  • 0
    TI__Guru 66810 points

    Hi Praveen, 

    Thanks for reaching out. Our team is reviewing this information and will have preliminary feedback/questions for you shortly. 

    Regards, 

    Logan

  • 0 in reply to Logan Cummins
    TI__Mastermind 28160 points

    Hello Parveen,

    Based on the value in register 0x4D on the deserializer, it seems you are reading register statuses from RX Port 1. Can you confirm if only RX Port 1 is the only port that is having issues?

    I also see in register 0x4D that LOCK and PASS are HIGH. Can you read register 0x4D multiple times and verify that a stable LOCK is present? By stable LOCK, I mean that after multiple reads to register 0x4D, the LOCK_STS bit is consistently set to b'1 and the LOCK_STS_CHG bit is consistently set to b'0.

    Can you also run the MAP script tool on the 960, to get a higher-level overview of the quality of your link?

    If there are no issues detected on the serializer, but there are errors detected on the data received by the deserializer, then my first suspicion would be that there are issues in the channel link between the SER/DES that is introducing errors to the transported video data. I recommend trying the steps listed above as a first step.

    Best,

    Justin Phan