Strictly necessary cookies are on by default and cannot be turned off. Functional, Performance and Tracking/targeting/sharing cookies can be turned on below based on your preferences (this banner will remain available for you to accept cookies). You may change your cookie settings by deleting cookies from your browser. Then this banner will appear again. You can learn more details about cookies HERE.
Strictly necessary (always on)
Functional, Performance and Tracking/targeting/sharing (default off)
Hello, I'm interfacing a PSoc5 MCU with a MAX6581 Temperature Sensor. The Sensor has a SMBUS/I2C Compatible interface. I'm using I2C Master module to interface with the device. I have been playing with a PSoc5 Dev Kit to learn how I2C works. The problem I see is that I don't see the I2C Read/Write on the Dev Kit match the datasheet page 10 and 11. I've attached pages 10 and 11 for anyone to look over and maybe see if it is even possible to implement an I2C link with this temperature sensor.
When I look at the I2C traffic is a logic analyzer and say I'm doing an I2C_MasterReadByte I only see the address followed by the Bytes I'm reading.
Hello, I went back and looked at an I2C MasterRead example that I did a few days ago and looked at the I2C signals and I believe things working correctly.
This shows the MasterWrite command first that passes the Device Address and the "Command" or "Sub-address". The second group is a MasterRead. The time between the MasterWrite and MasterRead is about 3.038ms.
Here is the MasterWrite passing the Device Address and the "Command" word. I use the "Command" to match the SMBus protocol wording.
Here is the MasterRead. What bothers me is the 3.03msec between the two functions. I thought it would be back to back transactions.