TDA4VM: I2C Selftest Fail

Hello Yao,

Is this on the A72 side running QNX OS or on the R5F core running FreeRTOS?

Thanks.

Hi

R5 core, the log shows that both the deserializer and camera can be powered on normally, and the camera with the deserializer is configured normally. Failed to read camera internal parameters

Hi Yao,

Have you tested this with the 8.6 SDK?

Thanks,

Neehar

Our product has already been mass-produced using SDK 8.2 and cannot be tested using SDK 8.6

Hi Yao,

Did you implement these I2C_control commands yourself? Such as I2C_CMD_GET_PSC, I2C_CMD_SELFTEST etc.

If so, can you provide what they are doing?

Thanks,

Neehar

Yes, I manually executed the I2C_control command.
Firstly, run I2C_CMD_SLFTEST for I2C self-test, and the return value of I2C_control function is -1; Then run I2C_CMDVNet PSC, I2C_CMD_GET_SCLL,I2C_CMD_GET_SCLH, Their operational return values are normal

Hi Yao,

Are these I2C_control commands solely returning the values of the registers?

Thanks,

Neehar

I2C_control is a function interface provided by TI, and we did not change it. We only changed the parameters passed in. When using the I2C_CMD_SLFTEST parameter, the return value of I2C is -1. Through code analysis, we found that this may be caused by the inconsistency between the values of i2c TX and RX. We would like to know the possible reason for this error;

In addition, I2C_CMD_SLFTEST has set I2C to LOOPBACK mode. May I ask if LOOPBACK mode is an internal register loop or a loop related to peripherals;

Hi Yao,

I will look into this and get back to you.

Thanks,

Neehar

Hi Neehar,

do you have any new finding for this issue, customer is waiting for this for long time.

BR,

Biao 

Hi Yao,

Can you provide what I2C_CMD_SELFTEST command is doing with the driver? As well as the other added commands.

Thanks,

Neehar

static int32_t I2C_v1_selfTest(I2C_Handle handle)
{
int32_t retVal = I2C_STATUS_SUCCESS;
I2C_HwAttrs const *hwAttrs = NULL;
uint32_t sysTest = 0;
const uint8_t dataTx = 0xff;
uint8_t dataRx = 0xff;

/* Input parameter validation */
if(NULL != handle)
{
/* Get the pointer to the object and hwAttrs */
hwAttrs = (I2C_HwAttrs const *)handle->hwAttrs;
}

sysTest = I2CMasterGetSysTest(hwAttrs->baseAddr);
I2C_v1_udelay(I2C_DELAY_USEC);

/* switch to system test mode */
HW_SET_FIELD32(sysTest, I2C_SYSTEST_ST_EN, I2C_SYSTEST_ST_EN_ENABLE);
HW_SET_FIELD32(sysTest, I2C_SYSTEST_TMODE, I2C_SYSTEST_TMODE_LOOPBACK);
I2CMasterSetSysTest(hwAttrs->baseAddr, sysTest);
I2C_v1_udelay(I2C_DELAY_USEC);

I2CMasterDataPut(hwAttrs->baseAddr, dataTx);
I2C_v1_udelay(I2C_DELAY_USEC);
dataRx = (uint8_t)I2CMasterDataGet(hwAttrs->baseAddr);
I2C_v1_udelay(I2C_DELAY_USEC);

if (dataRx == dataTx)
{
retVal = I2C_STATUS_SUCCESS;
}
else
{
retVal = I2C_STATUS_ERROR;
}

/* Switch back to functional mode */
HW_SET_FIELD32(sysTest, I2C_SYSTEST_ST_EN, I2C_SYSTEST_ST_EN_DISABLE);
HW_SET_FIELD32(sysTest, I2C_SYSTEST_TMODE, I2C_SYSTEST_TMODE_FUNCTIONAL);
I2CMasterSetSysTest(hwAttrs->baseAddr, sysTest);
I2C_v1_udelay(I2C_DELAY_USEC);

return retVal;
}

May I ask if the I2C_SYSTEST TMODE.LOPBACK mode depends on external devices

Hi Yao,

Yao Zhang said:

May I ask if the I2C_SYSTEST TMODE.LOPBACK mode depends on external devices

It should not depend on external devices as the loopback is an internal path through the FIFO buffers.

Thanks,

Neehar

Hi all,

we have a meeting with customer today:

1. Linjun feedback this self-test function is located in recovery mode, this may should not call when the system is normal. Linjun will help double check the proper self-test function should be called for the FuSa.

2. Linjun will feedback some patch to help customer recovery from the I2C stuck status. 

3. Customers find they are calling this function three times in a short period (ms), customer are afraid is there any risk for this? because of this issue is difficult to reproduce. they want TI to give some general analysis for this based on the self-test logic.  Neehar Sawant this need you help check.

BR,

Biao 

Hi Yao,

Could you please add the bold code here to make sure the I2C bus signal is correct? 

HW_SET_FIELD32(sysTest, I2C_SYSTEST_ST_EN, I2C_SYSTEST_ST_EN_ENABLE);

HW_SET_FIELD32(sysTest, I2C_SYSTEST_TMODE,

I2C_SYSTEST_TMODE_LOOPBACK);

/* make sure the SDA to High */

HW_SET_FIELD32(sysTest, I2C_SYSTEST_SDA_O, I2C_SYSTEST_SCL_O_SCLOH);

I2CMasterSetSysTest(hwAttrs->baseAddr, sysTest);

And I suggust add this code to the funciton I2C_v1_recoverBus also .

Thanks.

Linjun

hi expert 

thanks for your replay 

i will add this code at once

Hi YAO,

  It is important to clarify here that ST_EN is "system test enable" .

 To my understanding that if the purpose of checking the master I2C IP status, such as I2C_IRQSTATUS_RAW, I2C_BUFSTAT need readback firstly. Even if the purpose is to check the status of the board I2C system, such as the bus electronic signal is a necessary part to check.

  Thanks.

Linjun

we are still testing that we can close it first