RTOS/TDA3XEVM: SENSOR ERROR

Hi Blessy,

on which usecase you see this issue? Also can you show the log of assertion failure?

Thanks,
Yordan

Hi Stan,

Thank you for your time. In the code I2C0 is referred to I2C1 and I2C1 is referred to I2C2, this is what i found.

I see now. Could it be a wrong address then? Is it 0x40 set in the sensor itself? I don't have sensor diagram by hand.

Hi Stan,

The address of the sensor is 0x62, as we are using 4 sensors of the same I2C address, alias address is set for the four. 0x40, 0x42, 0x44, 0x46 are the alias addresses of the sensors.

Hi Stan

Do you have any other suggestions for solving this error? I couldn't solve it yet.

Hi, Blessy Abraham,

Happy New Year!

Your question is forwarded to another expert.
Just to let you know that yet some vacations are on-going and the responses will delay.

Regards,
Mariya

Hi Blessy,

Were you able to resolve this?

If not can you please clarify, post removal of the assert, you were able to capture the video stream and display. Can we infer that sensor could be programmed after the assert was removed?

Regards, Sujith

Hi Blessy,

Can you share the UB913 & UB914 configurations that you are using?

24 MHz pixel clock could be one of the issue, please check UB913/UB914 technical reference manual, the valid range starts from 25 MHz.

Regards, Sujith

Hi Sujith, Please see the below configs.

BspUtils_Ub960I2cParams gUb960Cfg_IMI[] = {
{0x01, 0x01, 0xFFF}, /* Digital Reset 0 */
{0x1F, 0x05, 0x4FF},

/* IMI OV10640 1 */
{0x4C, 0x01, 0x0},//RX0
{0x58, 0x58, 0x0},//BC FREQ SELECT: 2.5 Mbps
{0x6D, 0x7D, 0x0},
{0x5D, 0xB0, 0x0},//slaveID[0] = 0XB0 (SERIALIZER = 0XB0?)
{0x65, ((UInt8) (IMI_PORT_0_SER_ADDR << 1U)), 0x0},
{0x5E, 0x62,0}, //slaveID[1] = 0x62 (SENSOR = 0X62)
{0x66, ((UInt8) (IMI_PORT_0_SENSOR_ADDR << 1U)), 0x0},
{0x7C, 0x00, 0x0},
{0x6E, 0x99, 0x0},//GPIO
{0x70, 0x2B, 0x0},//RAW10
{0x71, 0x2C, 0x0},//RAW12


/* IMI OV10640 2 */
{0x4C, 0x12, 0x0},//RX1
{0x58, 0x58, 0x0},
{0x6D, 0x7D, 0x0},
{0x5D, 0xB0, 0x0},//slaveID[0] = 0XB0 (SERIALIZER = 0XB0?)
{0x65, ((UInt8) (IMI_PORT_1_SER_ADDR << 1U)), 0x0},
{0x5E, 0x62,0}, //slaveID[1] = 0x62 (SENSOR = 0X62)
{0x66, ((UInt8) (IMI_PORT_1_SENSOR_ADDR << 1U)), 0x0},
{0x7C, 0x00, 0x0},
{0x6E, 0x99, 0x0},
{0x70, 0x6B, 0x0},
{0x71, 0x6C, 0x0},


/* IMI OV10640 3 */
{0x4C, 0x24, 0x0},
{0x58, 0x58, 0x0},
{0x6D, 0x7D, 0x0},
{0x5D, 0xB0, 0x0},//slaveID[0] = 0XB0 (SERIALIZER = 0XB0?)
{0x65, ((UInt8) (IMI_PORT_2_SER_ADDR << 1U)), 0x0},
{0x5E, 0x62,0}, //slaveID[1] = 0x62 (SENSOR = 0X62)
{0x66, ((UInt8) (IMI_PORT_2_SENSOR_ADDR << 1U)), 0x0},
{0x7C, 0x00, 0x0},
{0x6E, 0x99, 0x0},
{0x70, 0xAB, 0x0},
{0x71, 0xAC, 0x0},


/* IMI OV10640 4 */
{0x4C, 0x38, 0x0},
{0x58, 0x58, 0x0},
{0x6D, 0x7D, 0x0},
{0x5D, 0xB0, 0x0},//slaveID[0] = 0XB0 (SERIALIZER = 0XB0?)
{0x65, ((UInt8) (IMI_PORT_3_SER_ADDR << 1U)), 0x0},
{0x5E, 0x62,0}, //slaveID[1] = 0x62 (SENSOR = 0X62)
{0x66, ((UInt8) (IMI_PORT_3_SENSOR_ADDR << 1U)), 0x0},
{0x7C, 0x00, 0x0},
{0x6E, 0x99, 0x0},
{0x70, 0xEB, 0x0},
{0x71, 0xEC, 0x0},

{0xB0, 0x1C, 0xFFF},//CSI2 reserved regs
{0xB1, 0x13, 0xFFF},
{0xB2, 0x1F, 0xFFF},

{0x32, 0x01, 0x0},//CSI0 select
#ifdef BOARD_TYPE_TDA3XX_RVP
{0x33, 0x03, 0x0}, /* Enable CSI2 continous clock */
#else
{0x33, 0x01, 0x0}, //CSI_EN & CSI0 4L
#endif
{0x20, 0x00, 0x0},//forwarding of all RX to CSI0

{0x10, 0x81, 0x0},//GPIO0 Output Enabled, Framesync signal selected
{0x11, 0xa1, 0x0},//GPIO1 Output Enabled, RX port pass indication
{0x12, 0xc1, 0x0},//GPIO2 Output Enabled,
};


BspUtils_Ub960I2cParams gUB913SerCfg[] = {
{0x03, 0xC5, 0x0},
{0x0D, 0x99, 0x0},

/* Changing the default I2C clock rate to 100 KHz */
/* Default 0x82 = 74 kbits/sec
0x64 = 100 kbps
0x32 = 400 kbps */
{0x11, 0x32, 0x0}, /* SCL High period */
{0x12, 0x32, 0x0} /* SCL Low period */
};

Hi Blessy,

Can we check on the following 

1. Ensure the back-channel lock is detected
   1. This is required to ensure communication between UB964 and UB913
   2. Remove the assert (IMI modules that is supported by default operates with external clock mode and back-channel lock check is not required and hence the assert was needed)
   3. After UB964 and UB913 are programmed, check register 0x4D of UB964, bit 0 should be set.
      • Wait until lock is detected
   4. Ensure to check on all receive channels, a receive channel is selected by programming 0x4C with 0x01 for port 0 and 0x12 for port 1, etc...
2. Pixel Clock
   1. The minimum pixel clock is 25 MHz, recommend to operate with 25 MHz pixel clock
3. Check back-channel frequency reported at UB913
   1. After UB964 & UB913 are programmed, add a delay of 1 second
   2. Read contents of register 0x14 of UB913, for all the connected UB913's

Regards, Sujith

Hi Sujith,

Thankyou for your response. I checked with the above mentioned points.

1. Back-channel lock is detected. After UB964 and UB913 programming - 0X4D registers of each channels were checked. The 0th bit is getting set. Following were the observed values.
0x4D = 0x13
0x4D = 0x53
0x4D = 0x93
0x4D = 0xd3
2. Pixel clock obtained is 48MHz
3. Added a delay of 1 second after programming of UB964 and UB913
Content of register 0x14 = 0x00 for all the connected UB913's.

Still facing the same error.

Hi Blessy,

1. Can you please read 0x4D of UB964 for all ports multiple times (2 times) to ensure correct status is indicated.

2. Try reducing the I2C clock speed, i.e. in UB913 configurations, please comment out values being written into register 0x11 and 0x12. i.e. Let I2C operate at default speeds.

Interesting thing is that sensors is accessible after the UB964/UB913 are programmed and sensor programming is initiated. So it seems after some delay the sensors are indeed accessible.

Regards, Sujith

Hi Sujith,
1. I tried reading the register 0x4D of UB964 for all ports multiple times. Each time the last bit was getting set.
0x4D = 0x13
0x4D = 0x53
0x4D = 0x93
0x4D = 0xd3
0x4D = 0x03
0x4D = 0x43
0x4D = 0x83
0x4D = 0xc3
2. Made I2C to operate at default speeds by commenting out the two register values, 0x11 and 0x12

Got the same error but video is working fine as it was before.