Hello!
I've been having a nightmare getting I2C working on a 28X2, and I'm pretty much out of ideas. Perhaps someone here has some experience they could share...
I am trying to communicate with an MCP3421 ADC on its eval board with built-in pull up resistors. I am using:
The SlaveAdr_2 symbol is to b3 and contains the appropriate address.
I see nothing on the SCL or SDA pins on my scope. Both are perpetually high. No clock pulses. No data. Nothing. Even if I was sending junk to the MCP3421, I should be able to see clock pulses on the SCL and data on the SDA.
This is being prototyped on the AXE091 dev board. I'm going straight to pin 14 and 15 on the 28X2.
I had the exact same problem trying to communicate with my I2C LCD and finally set it to RS232 serial mode instead, but no such solution exists for the MCP3421 so now I'm stuck with getting I2C working.
Since I'm not seeing any activity on SCL or SDA at all, I suspect the problem is software related.
Has anyone experienced this sort of pain with I2C before? Any help would be appreciated!''
Regards,
-Robert
I've been having a nightmare getting I2C working on a 28X2, and I'm pretty much out of ideas. Perhaps someone here has some experience they could share...
I am trying to communicate with an MCP3421 ADC on its eval board with built-in pull up resistors. I am using:
Code:
Hi2cSetup I2CMaster, SlaveAdr_2, I2CSlow, I2CByte
Hi2cout [SlaveAdr_2], ( $88 ) ' Configure the MCP3421
Hi2cin [SlaveAdr_2], ( Hi, Lo, Config ) ' Retrieve hi byte, lo byte and Config byte
I see nothing on the SCL or SDA pins on my scope. Both are perpetually high. No clock pulses. No data. Nothing. Even if I was sending junk to the MCP3421, I should be able to see clock pulses on the SCL and data on the SDA.
This is being prototyped on the AXE091 dev board. I'm going straight to pin 14 and 15 on the 28X2.
I had the exact same problem trying to communicate with my I2C LCD and finally set it to RS232 serial mode instead, but no such solution exists for the MCP3421 so now I'm stuck with getting I2C working.
Since I'm not seeing any activity on SCL or SDA at all, I suspect the problem is software related.
Has anyone experienced this sort of pain with I2C before? Any help would be appreciated!''
Regards,
-Robert