TDA4VP-Q1: Query on I2C wave fomat.

hi team,

Logic analyzer settings was kept on to read with 2.5MHz and 3.3Volts to read the pulses present in above graph.

thanks and regards,

M Prashannaa ravi

Hi,

Does this occur on read and write transactions? Additionally, does it occur on all transactions or only some?

Prashannaa ravi M said:

We can able to write and read. But on looking wave form we are seeing 2 stop condition.

Kindly let me know if it is fine to have the I2C wave as below.

 

The rest of the bytes of data in the transaction look correct, can you confirm you do not see any loss of data?

Thanks,

Neehar

hi Neehar ,

>>Does this occur on read and write transactions?

Currently it is occuring on Write transaction.

>>Additionally, does it occur on all transactions or only some?

Hi,

Prashannaa ravi M said:

on the read data , we are having counter based field ( as in the marked pulses on response data from slave)

And from AD end they are doubting that because of 2 stop signals , it is causing in their API end to behave on the other way.

Are you using the I2C driver from the PDK?

Prashannaa ravi M said:

But from my end on the 1st stop signal since the clock is low . so, it should not be considered as I2c stop.

On the second stop , we can notice clock changed from low to high. And on the same we can see stop occurred.

So, Kindly confirm if there is any issues in the above graph.

Let me look deeper into the transaction and get back to you.

Thanks,

Neehar

Hi,

->Are you using the I2C driver from the PDK?

Hi,

I will run some tests and follow up in the next two days with my findings.

Thanks,

Neehar

Ok sure.

Thanks,

M Prashannaa ravi.

Hi,

Thanks for your patience!

Thanks,

Neehar