Comparison of IIC data and logic diagram between the reference prototype and your own product

QWE4562009

Comparison of IIC data and logic diagram between the reference prototype and your own product [Copy link]

I grabbed the IIC data and logic diagram of my own product and the IIC data and logic diagram of the reference prototype. I found that my product is writing and reading, writing and reading... while the reference prototype only writes a 0X00 address at the beginning, and then all read operations until the data transmission is completed, and there is a 0X7A+NAK package. I feel that the reference prototype is more concise. I wonder if each has its pros and cons?

bobde163

If it supports continuous reading of multiple bytes, then the reference prototype will naturally have no problem processing, and it will be efficient and less prone to errors.

qwqwqw2088

One is the unit s catch

One is to use the unit

ms抓，这样对比有甚意义

w494143467

Multi-byte is of course better, it can save a lot of time.

QWE4562009

qwqwqw2088 发表于 2020-12-17 12:46 一个用是单位s抓 一个是用单位 ms抓，这样对比有甚意义

Mistake. Mistake. What I want to ask is whether reading and writing can set protocols and rules at will?

QWE4562009

bobde163 posted on 2020-12-17 11:50 If it supports continuous reading of multiple bytes, then the processing of the reference prototype will naturally have no problem at all, and it is highly efficient and less prone to errors

Yes, I found that my product IIC data has more than 600 rows...

Ejack1979

This problem is obvious. Continuous reading is to improve bus efficiency. Just pay attention to the starting address and page size.