| ??? 09/12/02 11:31 Read: times |
#29066 - RE: Making 8751 I2C compliant - Peter |
"its impossible to access I2C memory like any external memory."
That's what I thought initially; but the man from Keil he say, "Yes! - it can be done!" "Because I2C was much slower than a MOVX instruction. So you need always a subroutine to write or read a single byte." Of course, you still have to implement the underlying functions to support the XDATA Banking, and timing will still be an issue. See http://www.8052.com/forum/read.phtml?id=27291&top= |
| Topic | Author | Date |
| Making 8751 I2C compliant | 01/01/70 00:00 | |
| RE: Making 8751 I2C compliant | 01/01/70 00:00 | |
| Why not... | 01/01/70 00:00 | |
| RE: Why not... | 01/01/70 00:00 | |
| RE: how about.. | 01/01/70 00:00 | |
| RE: how about.. | 01/01/70 00:00 | |
| RE: how about.. | 01/01/70 00:00 | |
| RE: Making 8751 I2C compliant | 01/01/70 00:00 | |
| RE: Making 8751 I2C compliant | 01/01/70 00:00 | |
| RE: Making 8751 I2C compliant | 01/01/70 00:00 | |
| RE: Making 8751 I2C compliant | 01/01/70 00:00 | |
| Software *is* an option | 01/01/70 00:00 | |
| RE: Making 8751 I2C compliant | 01/01/70 00:00 | |
| RE: Making 8751 I2C compliant | 01/01/70 00:00 | |
| RE: Making 8751 I2C compliant | 01/01/70 00:00 | |
| RE: Making 8751 I2C compliant - Peter | 01/01/70 00:00 | |
| RE: Making 8751 I2C compliant | 01/01/70 00:00 | |
RE: Making 8751 I2C compliant | 01/01/70 00:00 |



