Tool/software: Code Composer Studio
Does it have the The internal block diagram about I2C-EEPROM ?
If I2CRXBUF is not read, what happens to I2CRXBUF next time it is read?
thanks
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Tool/software: Code Composer Studio
Does it have the The internal block diagram about I2C-EEPROM ?
If I2CRXBUF is not read, what happens to I2CRXBUF next time it is read?
thanks
I'll assume you're talking about using the I2C in master mode, since we just discussed it that way.
In master mode, reading from I2CRXBUF is what triggers the hardware to read the next byte.
So after you get a DATA_READY high, indicating that data has been read, the hardware will stretch the clock until you read from I2CRXBUF, or until it hits the 35 millisecond timeout, whichever comes first.
Just in general, the I2C/PMBus interface logic can't be shown very well in a block diagram. The requirement and the design are pretty complicated.