| ??? 09/13/02 09:23 Read: times |
#29111 - RE: Making 8751 I2C compliant |
Peter Dannegger wrote: ------------------------------- its impossible to access I2C memory like any external memory. Because I2C was much slower than a MOVX instruction. So you need always a subroutine to write or read a single byte. Also since reading and writing a couple of bytes on the I2C bus can be done much faster, it would suggest to have routines for block read and write. ;---------------------------------- hi peter; why not map i2c registers for data and status in xram?change in status can be notified by using one of the external interrupts. regards pranav |
| 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 |



