I should say that I rewrote the mram and nonvol code quite a bit to improve the abstraction. All the code dealing directly with the MRAMs is in the mram.c file, all the mram test interfaces now use the mram number, not the SPI device, the partitions are handled in the mram.c file, and I renamed the type enums because the statistics code shouldn't care about where the data is stored.

The mram test code now runs on the filesystem partition, so if you run that test you need to unmount the filesystem first and format it after.

It's not perfect, but I think it's better than it was.

-corey

On Fri, Apr 7, 2023 at 11:30 AM Corey Minyard minyard@acm.org wrote:

I have the filesystem code mostly ready. I changed the configuration to use 256 byte block. It's available in the filesystem branch.

So I will need a launchpad and a board with MRAM. My address is:

7406 Wheatfield Rd, Garland, TX 75044

Chris, you can test it if you like, too. I haven't written any tests for anything yet, that needs to be added.

There is code to automatically mount the filesystem on startup and format the filesystem if it detects corruption.

There are three new console commands: mount fs, unmount fs, and format fs.

The commands are the normal POSIX commands with "red_" prefixed, red_open(), red_close(), read_read(), etc.

I need to write a README about how this is all set up.

-corey