Timeline for EEPROM address definitions and delay
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 6, 2013 at 6:19 | comment | added | Ignacio Vazquez-Abrams | @Rookie91: Reading from EEPROM is a much faster operation than writing, so much so that I2C will be the bottleneck, not the EEPROM. | |
| Nov 6, 2013 at 6:15 | comment | added | Rookie91 | I have not found any docs regarding the read time from eeprom after it is written on to the chip.Certainly it must be lesser than 5ms i trust | |
| Nov 6, 2013 at 6:05 | comment | added | alex.forencich | No more time than however long it takes to perform the transaction. The data should be available immediately, it's just a question of how quickly you can get it out of the chip on the bus. | |
| Nov 6, 2013 at 6:03 | comment | added | Rookie91 | What would the time needed to read a byte from eeprom? | |
| Nov 6, 2013 at 5:54 | vote | accept | Rookie91 | ||
| Nov 6, 2013 at 5:04 | comment | added | Ignacio Vazquez-Abrams | Oh, is that what that was about? The compiler doesn't care what radix you use for your numbers. | |
| Nov 6, 2013 at 5:01 | comment | added | Rookie91 | So the first case would work i trust.By declaring address locations as numbers instead of hexadecimal | |
| Nov 6, 2013 at 4:53 | history | answered | Ignacio Vazquez-Abrams | CC BY-SA 3.0 |