@DrAzzy, yes, but only on a very low level: read and write bytes at a memory location. Basically, the serial FRAM/MRAM behaves like the serial EEPROM - except there are no wait states for write. No wait states for writes and unlimited write cycles would open up new application files: some memory segments in the whole memory space could be FRAM/MRAM and would serve as persistency with the simple option of having or moving data there.
For my own use I have started writing an (string) object store with garbage collect, but no file system yet. As I understand your intention is to have a file system with files on a (what ever) device that you can access serially. Correct?
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.
@DrAzzy, yes, but only on a very low level: read and write bytes at a memory location. Basically, the serial FRAM/MRAM behaves like the serial EEPROM - except there are no wait states for write. No wait states for writes and unlimited write cycles would open up new application files: some memory segments in the whole memory space could be FRAM/MRAM and would serve as persistency with the simple option of having or moving data there.
For my own use I have started writing an (string) object store with garbage collect, but no file system yet. As I understand your intention is to have a file system with files on a (what ever) device that you can access serially. Correct?