Corey et al,
I pulled down the filesystem branch and have gotten it running on my LaunchPad with 2 512K MRAMs.
First, thanks for cleaning up the MRAM code. As you might have guessed, the read/write was originally to choose between the MRAM and Flash memory on the STM32L processor. On the RTIHU, I just cut out the stuff for the flash. Looks like you have used the same basic scheme between the two partitions in the MRAM. I like it!
I have had to make two (identical) changes to get it to compile, and one more to get it to run:
1) I'm not entirely sure why the "reliance-edge" and its "core" subfolder were setup with different properties than everything else (that's the little key badge means, I think, although I've never been able to get rid of it once it was there!). But in any case, the changed setup had a path that was specific to your machine so it could not find <string.h>. I changed it to ${CG_TOOL_ROOT) in both places. Now it compiles.
2) Formatting the file system failed with a not-very-useful error message (Invalid Argument). The problem is that REDCONF_ENDIAN_BIG needs to be defined to 1 in redconf.h.
So now it formats and mounts ok. I have not tried anything else.
I'll push what I have right now up on my own branch named "BFFileSystem". Then I want to see why there are some MRAM errors when it first boots. Probably some old code.
73,
Burns Fisher, WB1FJ
AMSAT(R) Engineering -- Flight Software