Hmm. There is a place in the MRAM (maybe one at the beginning and one at the end?) with a version number. When you init the MRAM, the version number in the code (I think it is in the header file that defines the contents of the MRAM) is written into that/those spot/s. Then it compares, I think in the console code every command (it is really easy to miss otherwise). I don't think I compare it anywhere else.
Assuming you did not change the layout, my first thought would be that when we put the file system into the MRAM, the version number is somehow overlayed so it gets changed when some particular thing happens in the file system. Or maybe the file system overflows? If it is that latter (an overflow) that could end up corrupting the file system. Would that explain why the receiver is not working? Of course you can clear mram..I suppose that means you have to re-init the file system too?
73,
Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software*
On Thu, Oct 12, 2023 at 10:41 AM Chris Thompson via pacsat-dev < pacsat-dev@amsat.org> wrote:
Burns (and others),
I think there is a bug that corrupts MRAM. From time to time I get the message "*****MRAM layout has changed. You must issue clear mram******" even though I have not changed the layout. What causes that? It looks like it may then cause an issue where the receiver does not work.
73 Chris
-- Chris E. Thompson chrisethompson@gmail.com g0kla@arrl.net
pacsat-dev mailing list -- pacsat-dev@amsat.org View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/pacsat-dev@amsat.org To unsubscribe send an email to pacsat-dev-leave@amsat.org Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org