| ??? 06/30/06 17:58 Modified: 06/30/06 18:00 Read: times |
#119474 - i told you how Responding to: ???'s previous message |
Can it be done using the 24c04 or not?
from my previous post: "You 'can' make the chips you use work for you, but it will take quite some coding of the driver to detect that eg 17 bytes at 0xff will take write 16, set address, write 1." if your 'driver' ( write and read routines' keep track of which address to be written (last address byte + number of writes) it can detect when it need insert a new write command. Erik |
| Topic | Author | Date |
| eeprom word addressing | 01/01/70 00:00 | |
| do not confuse bits and bytes | 01/01/70 00:00 | |
| maximum seerial memory chip available? | 01/01/70 00:00 | |
| yes, you do | 01/01/70 00:00 | |
| code not working | 01/01/70 00:00 | |
| How to post code | 01/01/70 00:00 | |
| formatted code. | 01/01/70 00:00 | |
| I searched for a comment stating "write | 01/01/70 00:00 | |
| "write device address"-i2c subroutine | 01/01/70 00:00 | |
| you reply with an uncommented sub | 01/01/70 00:00 | |
| formatted code with comments. | 01/01/70 00:00 | |
| ORL a,HighAddressBit; | 01/01/70 00:00 | |
| Solution | 01/01/70 00:00 | |
| You 'can' make the chips you use work fo | 01/01/70 00:00 | |
| Question still remains unanswred | 01/01/70 00:00 | |
| i told you how | 01/01/70 00:00 | |
| One more time | 01/01/70 00:00 | |
| code written for that but not working | 01/01/70 00:00 | |
| rather than trying to figure your code o | 01/01/70 00:00 | |
| Corrections please, urgent. | 01/01/70 00:00 | |
| It is in the data sheet | 01/01/70 00:00 | |
datasheet | 01/01/70 00:00 |