2019-12-18 12:14 AM
Hello team,
I refer to a former posting from
MVoge, June 4, 2019 at 10:16 AM
As far as I can see from that thread, the timing question have bee cleared.
Nevertheless, our problem persists (I'm continuing Marcel's work).
This is, reading back values after writing often results in readings
like 0xFFFF, 0xC7FF or 0x1FFF (most bits set!). From this, I conclude (or presume) that
writing goes wrong rather than reading.
All I can do now is sending the code of our R/W routines - I can't find anything
wrong in that code - perhaps you can... Please note that
the granularity of eeprom AND our µC is 16 bit. Please find the code attached here.
The attached file contains the implementation of the eeprom operating commands.
BR
Goetz