That' stuff I wrote to the memory in post three (3) months ago...
This also proves that it is pretty resilient: I had the FRAM for a long time wired and did many other things... and countless power cycles, and more, and the stuff is still there.
Have to find out if I can recreate the initial case,...
Yes, can be recreated: the first time after a power cycle reads just 0xFF...
...all the times. So it has to do with power up. May be I go too quickly after the FRAM...
It is not a timing issue... it has to do with the first power cycle...
Definitly, it has to do with power cycle: reading just one byte upfront clears the issue and all subsequent reads read what they are supposed to.
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
read() works - with somehow a hick-up:
subsequent uploads with runs delivers real data.
This is the console output:
data read as string:
That' stuff I wrote to the memory in post three (3) months ago...
This also proves that it is pretty resilient: I had the FRAM for a long time wired and did many other things... and countless power cycles, and more, and the stuff is still there.
Have to find out if I can recreate the initial case,...
Yes, can be recreated: the first time after a power cycle reads just 0xFF...
...all the times. So it has to do with power up. May be I go too quickly after the FRAM...
It is not a timing issue... it has to do with the first power cycle...
Definitly, it has to do with power cycle: reading just one byte upfront clears the issue and all subsequent reads read what they are supposed to.
Btw, my 256KBits / 32KBytes FRAM was $4 only... not that bad.