• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 569 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.

RTOS/TDA3XEVM: Deserializer Lock status

Blessy Abraham
Intellectual 585 points

Part Number: TDA3XEVM

Tool/software: TI-RTOS

HI,

We are using TDA3X , rear view panorama usecase in VisionSDK3.1. We are observing the following error.

[IPU1-0]     20.490117 s:  i2cMdSubmitChan: i2c1 transfer to slave address 0x40 failed
[IPU1-0]     20.490209 s: src/bsp_deviceI2c.c @ Line 667:
[IPU1-0]     20.490300 s:  I2C1: DEV 0x40: ERROR !!!
[IPU1-0]     20.490392 s: src/bsp_deviceI2c.c @ Line 689:
[IPU1-0]     20.490483 s:  I2C1: Error timeout 255 ms!!!

This is also in regard with the query i had posted in the below link. Unfortunately it got locked.

https://e2e.ti.com/support/arm/automotive_processors/f/1021/t/647542?tisearch=e2e-sitesearch&keymatch=RTOS%2FTDA3XEVM%3A%20SENSOR%20ERROR#pi320098=2

We tried reading the 0X4D register of deserializer to ensure whether the data is getting locked. We observed the below reads.

The 0th bit is getting set. Following were the observed values.
0x4D = 0x13
0x4D = 0x53
0x4D = 0x93
0x4D = 0xd3

But the LOCK_STS_CHG bit is getting set indicating that there is a change in LOCK_STS. Is that because we are getting this error?

  • 0
    TI__Genius 12455 points

    Hi Blessy,

    0x13: This seems ok, assuming this is first read of 0x4D for port 0. 0x53: same as 0x13 but for port 1, 0x93: same as 0x13 but for port 2, 0xD3: same as 0x13 but for port 3

    Also, from your previous thread. The bit 4 is reset when read for the second time. Indicating a, stable lock.

    Can you please tell us little bit more about the sensor+UB913 module? Do you have a crystal connected to sensor/UB913?

     

    Regards, Sujith

  • 0 in reply to Sujith
    Intellectual 585 points
    Hi, Sujith

    Yes. we have a 24MHz crystal connected to the sensor. Serializer is operated with the PCLK from the image sensor.

    In the datasheet of serializer it is mentioned that it is recommended to use external oscillator(48MHz) as reference clock for serializer, which we have not followed. I doubt this is the thing that is causing the issue.

    Is there any software side code change to be applied in order to select this mode of operation, i.e DS90UB91xQ-Q1 Operation With Pixel Clock from Imager as Reference Clock?
  • 0 in reply to Blessy Abraham
    TI__Genius 12455 points

    Hi Blessy,

    Thanks for the explanation. With pixel clock as reference clock for UB913x, internal clock will be used to establish Link.

    Are you programming the sensor? or sensor starts streaming without any software intervention?

    Regards, Sujith

  • 0 in reply to Sujith
    TI__Genius 12455 points
    Also, you could try and figure out at which point sensor would be accessible.
    Assuming that you CCS could be connected to the board that is being used, I2C utility provided as part of PDK could be used.

    1. Compile ti_components\drivers\pdk\packages\ti\drv\bsp_lld\i2c\examples\i2c_utility
    1.1. Refer the PDK user guide to compile this utility
    2. Load & run this utility on IPU1_0
    3. In the CCS console, you can enter command to perform I2C read/writes.
    e.g. to reset UB964 (first entry in {0x01, 0x01, 0xFFF}, /* Digital Reset 0 */ )
    command would wr 0x3D 0x01 0x01 (i.e. wr = write, 0x3D = address of UB964, first 0x01 = register offset, second 0x01 = value to be written.

    4. After programming first port (i.e. after {0x71, 0x2C, 0x0},//RAW12)
    5. type command "probe"

    Check if sensor is responding.

    Regards,
    Sujith