| ??? 09/12/02 09:46 Read: times |
#29059 - RE: Making 8751 I2C compliant |
Hi Kunal,
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. So if you use a FPGA to realize the I2C bus, you need nevertheless something like a busy polling to detect, if the I2C read or write was completed. But I have never seen, that a FPGA or CPLD implement a complete I2C bus transfer cycle. Only the I2C basic functions (start, write or read byte, acknowledge, stop) are implemented. Peter |
| 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 |



