??? 12/09/09 06:14 Modified: 12/09/09 07:48 Read: times |
#171520 - I2C_0.1.zip released! Responding to: ???'s previous message |
Hi,
In response to Akhil's brave decision to found his 24C256 2-wire serial eeprom code on my low-level I2C protocol offering, and in gratitude for David's kind comments and efforts to assist Akhil, I've been inspired to take another look at the I2C code. The new version of code is free and may be downloaded via the following link: http://members.iinet.net.au/~vanluynm/click.php?Down/I2C_0.1.zip_NO_ROBOTS Please remove '_NO_ROBOTS' to download the code via your browser. Should the code link then still fail, please look for an updated version on my homepage at: http://members.iinet.net.au/~vanluynm/ Amongst other improvements, the new code makes possible polling of a serial eeprom for byte or page, scheduled write completion status, thereby obviating the need to call 5ms+ delays after each write request. It appears that some serial eeprom devices may complete write operations faster that others, so by employing an 'ack polling' technique, throughput might be optimised for all serial eeprom variants. I hope the improved code will be useful to someone, and any civil feedback would be greatly appreciated. Regards, Murray R. Van Luyn. |
Topic | Author | Date |
AT24C256 | 01/01/70 00:00 | |
help | 01/01/70 00:00 | |
BitBang's Amost Always.... | 01/01/70 00:00 | |
Why use void functions | 01/01/70 00:00 | |
thanks | 01/01/70 00:00 | |
Writing to specific address | 01/01/70 00:00 | |
Send sensible address values. | 01/01/70 00:00 | |
I2C_0.0.zip | 01/01/70 00:00 | |
no luck, | 01/01/70 00:00 | |
You have more pins to mis-wire. | 01/01/70 00:00 | |
i2c used, What should be the address | 01/01/70 00:00 | |
Read Murray's excellent Help Files | 01/01/70 00:00 | |
Incorrect reply | 01/01/70 00:00 | |
Please take some time to READ the Help | 01/01/70 00:00 | |
single byte read write working | 01/01/70 00:00 | |
I2C_0.1.zip released!![]() | 01/01/70 00:00 |