TDA4VH-Q1: i2c timeout occasionally

muqun.yun

Part Number: TDA4VH-Q1

Tool/software:

Hi,

TI Experts,

We are using SDK 9.0 on our customer board. There are three deserializers on the board, which use I2C1, I2C5, and I2C6 respectively , and correspond to three CSIs.

We now use MCU2_0 to configure these three deserializers and the three I2C insts are all initialized at 400KHZ POLLING MODE.

However, we have now found occasional I2C timeouts when using Board_i2c16BitRegRd. This problem currently only occurs about ten seconds after power on, with approximately one occurrences in 1000 power-on-and-off cycles each I2C, and all the three I2Cs may occur. Once it occurs, then both reading and writing registers on this I2C will timeout.

We found that the issue on this case is very similar to our problem：TDA4VM: i2c timeout issue (occationally 1/1000) on SDK0703 - Processors forum - Processors - TI E2E support forums

And the modification in this case has improved this issue: TDA4VM: The HwiP_disable() function does not work - Processors forum - Processors - TI E2E support forums

Is there any progress on this issue now？

Regards,

Muqun

over 2 years ago

0 Neehar Sawant over 2 years ago

TI__Mastermind 22680 points

Hi Muqun,

What timeout value are you using?
Are you aware if the SCL or SDA lines are stuck low?
Thanks,

Neehar

0 muqun.yun over 2 years ago in reply to Neehar Sawant

Prodigy 160 points

Hi, Neehar,

Neehar Sawant said:
What timeout value are you using?

Timeout value is the default value: #define SENSOR_I2C_TIMEOUT (5000U) , but the actual timeout time is about 16 seconds

Then I tried to decrease the value, and the actual timeout did indeed decrease.

Neehar Sawant said:
Are you aware if the SCL or SDA lines are stuck low?

The probability of reproducing this problem is very low and requires a lot of time and resources for testing. Do you have any effective solutions at present?

Thanks,

Muqun

0 Neehar Sawant over 2 years ago in reply to muqun.yun

TI__Mastermind 22680 points

Hi Muqun,

Can you test with using I2C_WAIT_FOREVER as the timeout value?

muqun.yun said:
The probability of reproducing this problem is very low and requires a lot of time and resources for testing. Do you have any effective solutions at present?

Without much information about the SCL and SDA lines, I cannot give an exact solution. Can you test calling I2C_recoverBus() API after the timeout occurs?
Thanks,

Neehar

0 Neehar Sawant over 2 years ago in reply to Neehar Sawant

TI__Mastermind 22680 points

Hi Muqun,

Following up, is this issue still open?
Thanks,

Neehar