Yes. I've don't it. I will monitor to see when I get it again.
73 Chris
On Thu, Oct 12, 2023, 12:26 Burns Fisher (AMSAT) via pacsat-dev < [email protected]> wrote:
Have you done the clear mram to start again? How long before you get the error again? 73,
Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software*
On Thu, Oct 12, 2023 at 12:07 PM Chris Thompson via pacsat-dev < [email protected]> wrote:
I'm unsure if it really messes up the receiver or if that is just a coincidence. I made the receiver work by rebooting the windows laptop that controls the ground station. Go figure.
But the MRAM definitely sees this issue. I see the message at reboot.
73 Chris
On Thu, Oct 12, 2023, 11:00 Burns Fisher (AMSAT) via pacsat-dev < [email protected]> wrote:
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 < [email protected]> 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 [email protected] [email protected]
pacsat-dev mailing list -- [email protected] View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/[email protected] To unsubscribe send an email to [email protected] Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org
pacsat-dev mailing list -- [email protected] View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/[email protected] To unsubscribe send an email to [email protected] Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org
pacsat-dev mailing list -- [email protected] View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/[email protected] To unsubscribe send an email to [email protected] Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org
pacsat-dev mailing list -- [email protected] View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/[email protected] To unsubscribe send an email to [email protected] Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org