Hi,
As discussed last night, I have a HALCoGen configuration set up that is specifically designed for the LaunchPad. I've also added a command "test mram" and another called "mram wren". The former writes 10 bytes into the mram at a specified address and then reads them back. It prints what it was writing, and what the read-back results are. It does this twice with one pattern of data and once with a different one. You can specify an address following the command. For example "test mram 100". It will take 0xnnn" as well for hex
"mram wren" sends a write enable command to the mram. The existing command "get mram sr" should show this. If it returns "40" the chip is not write enabled. If it returns 42, it is write enabled.
There is also, in config.h, a #ifdef FRAM64K. If this is set, the address sent to the non-volatile RAM is 2 bytes. If it is not defined (just comment it out) it will be 3 bytes. I've left it set up for 3-byte addresses since that is what Chris is using.
Please let me know if you have tried this successfully, especially with a real MRAM (most of those tests were for my funky F-RAM). If so, I'll move it to the main branch.
73,
Burns Fisher, WB1FJ
AMSAT(R) Engineering -- Flight Software