> Yes, now I have made that measurement. Cool! > So it happily accepts just one byte as an address (that is no NACK), but all > bytes read afterward will be 0xff (but the device will ACK all of them). I > have tried to fill up the eeprom with non-0xff data, so it does not appear > to be reading from any other address. Interesting. > > I am not sure if this is a behavior that is worth trying to mimic? Not yet. We can add this incrementally once we know most EERPOMs behave like this. It could be worth adding a comment, though, like: /* * FIXME: What to do if only 8 bits of a 16 bit address are sent? * The <your vendor & eeprom type> sends only 0xff then. Needs verification * with other EEPROMs, though. We currently use the 8 bit as a valid * address. */
Attachment:
signature.asc
Description: PGP signature
