- pacsat-dev - mailman.amsat.org

Re: MRAM Layout has changed
by Chris Thompson 12 Oct '23

12 Oct '23

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 < pacsat-dev(a)amsat.org> 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 < > pacsat-dev(a)amsat.org> 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 < >> pacsat-dev(a)amsat.org> 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 < >>> pacsat-dev(a)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(a)gmail.com >>>> g0kla(a)arrl.net >>>> >>>> ----------------------------------------------------------- >>>> >>>> pacsat-dev mailing list -- pacsat-dev(a)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(a)amsat.org >>>> Manage all of your AMSAT-NA mailing list preferences at >>>> https://mailman.amsat.org >>>> >>> >>> ----------------------------------------------------------- >>> >>> pacsat-dev mailing list -- pacsat-dev(a)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(a)amsat.org >>> Manage all of your AMSAT-NA mailing list preferences at >>> https://mailman.amsat.org >>> >> >> ----------------------------------------------------------- >> >> pacsat-dev mailing list -- pacsat-dev(a)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(a)amsat.org >> Manage all of your AMSAT-NA mailing list preferences at >> https://mailman.amsat.org >> > > ----------------------------------------------------------- > > pacsat-dev mailing list -- pacsat-dev(a)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(a)amsat.org > Manage all of your AMSAT-NA mailing list preferences at > https://mailman.amsat.org >

1 0

Re: MRAM Layout has changed
by Burns Fisher (AMSAT) 12 Oct '23

12 Oct '23

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 < pacsat-dev(a)amsat.org> 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 < > pacsat-dev(a)amsat.org> 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 < >> pacsat-dev(a)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(a)gmail.com >>> g0kla(a)arrl.net >>> >>> ----------------------------------------------------------- >>> >>> pacsat-dev mailing list -- pacsat-dev(a)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(a)amsat.org >>> Manage all of your AMSAT-NA mailing list preferences at >>> https://mailman.amsat.org >>> >> >> ----------------------------------------------------------- >> >> pacsat-dev mailing list -- pacsat-dev(a)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(a)amsat.org >> Manage all of your AMSAT-NA mailing list preferences at >> https://mailman.amsat.org >> > > ----------------------------------------------------------- > > pacsat-dev mailing list -- pacsat-dev(a)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(a)amsat.org > Manage all of your AMSAT-NA mailing list preferences at > https://mailman.amsat.org >

1 0

Re: MRAM Layout has changed
by Chris Thompson 12 Oct '23

12 Oct '23

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 < pacsat-dev(a)amsat.org> 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 < > pacsat-dev(a)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(a)gmail.com >> g0kla(a)arrl.net >> >> ----------------------------------------------------------- >> >> pacsat-dev mailing list -- pacsat-dev(a)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(a)amsat.org >> Manage all of your AMSAT-NA mailing list preferences at >> https://mailman.amsat.org >> > > ----------------------------------------------------------- > > pacsat-dev mailing list -- pacsat-dev(a)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(a)amsat.org > Manage all of your AMSAT-NA mailing list preferences at > https://mailman.amsat.org >

1 0

Re: MRAM Layout has changed
by Burns Fisher (AMSAT) 12 Oct '23

12 Oct '23

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(a)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(a)gmail.com > g0kla(a)arrl.net > > ----------------------------------------------------------- > > pacsat-dev mailing list -- pacsat-dev(a)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(a)amsat.org > Manage all of your AMSAT-NA mailing list preferences at > https://mailman.amsat.org >

1 0

MRAM Layout has changed
by Chris Thompson 12 Oct '23

12 Oct '23

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(a)gmail.com g0kla(a)arrl.net

1 0

Demo files uploaded
by Chris Thompson 12 Oct '23

12 Oct '23

I have checked in the demo files. They are in the Demo folder in AMSAT-NA/PacSatDocs/Demo This consists of the Demo script and the two folders for the setup and operation on the demo. 73 Chris -- Chris E. Thompson chrisethompson(a)gmail.com g0kla(a)arrl.net

1 0

Re: "Mostly paused" for a couple weeks
by Chris Thompson 12 Oct '23

12 Oct '23

I don't know what to say, but our thoughts are with you and your family. Chris On Thu, Oct 12, 2023, 08:17 Jonathan Brandenburg via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > Some of y'all know but not all... I'm in the midst of addressing a > family tragedy (my sister took her life this past weekend). As a result, > I'm mostly pausing my AMSAT responsibilities to shed some load for a > couple weeks. > > Please understand if I'm not particularly responsive to AMSAT emails. I > anticipate having things wrangled into submission by the time Symposium > rolls around. > > Jonathan > > -- > Jonathan Brandenburg, KF5IDY > > > ----------------------------------------------------------- > > pacsat-dev mailing list -- pacsat-dev(a)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(a)amsat.org > Manage all of your AMSAT-NA mailing list preferences at > https://mailman.amsat.org >

1 0

"Mostly paused" for a couple weeks
by Jonathan Brandenburg 12 Oct '23

12 Oct '23

Some of y'all know but not all... I'm in the midst of addressing a family tragedy (my sister took her life this past weekend). As a result, I'm mostly pausing my AMSAT responsibilities to shed some load for a couple weeks. Please understand if I'm not particularly responsive to AMSAT emails. I anticipate having things wrangled into submission by the time Symposium rolls around. Jonathan -- Jonathan Brandenburg, KF5IDY

1 0

Re: Annual Meeting proceedings
by Bill Reed 09 Oct '23

09 Oct '23

Revised docs have been submitted for publication. 🙂 Bill On 10/7/2023 12:41 PM, Chris Thompson via pacsat-dev wrote: > I reviewed the two documents and made some minor changes. I also > generated pdfs as we are publishing these and they are also checked > back into git. > > 73 > Chris > > On Fri, Oct 6, 2023 at 4:31 PM Burns Fisher (AMSAT) <wb1fj(a)fisher.cc> > wrote: > > Sure, ok with me. > 73, > > Burns Fisher, WB1FJ > /AMSAT(R) Engineering -- Flight Software/ > > > On Fri, Oct 6, 2023 at 4:30 PM Chris Thompson via pacsat-dev > <pacsat-dev(a)amsat.org> wrote: > > I am good with that assuming Burns is. I can read through them > this weekend and see if they need any changes. > > > 73 > Chris > > On Fri, Oct 6, 2023, 14:58 Bill Reed via pacsat-dev > <pacsat-dev(a)amsat.org> wrote: > > We discussed this briefly last night. > > Why don't we publish these docs in the proceedings? > > "PACSAT BBS Operations", 10 Nov 2022, by Chris > > and > > "PACSAT Software Architecture", 19 Mar 2023 by Chris and Burns > > Bill > > > ----------------------------------------------------------- > > pacsat-dev mailing list -- pacsat-dev(a)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(a)amsat.org > Manage all of your AMSAT-NA mailing list preferences at > https://mailman.amsat.org > > > ----------------------------------------------------------- > > pacsat-dev mailing list -- pacsat-dev(a)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(a)amsat.org > Manage all of your AMSAT-NA mailing list preferences at > https://mailman.amsat.org > > > > -- > Chris E. Thompson > chrisethompson(a)gmail.com > g0kla(a)arrl.net > > ----------------------------------------------------------- > > pacsat-dev mailing list --pacsat-dev(a)amsat.org > View archives of this mailing list athttps://mailman.amsat.org/hyperkitty/list/pacsat-dev@amsat.org > To unsubscribe send an email topacsat-dev-leave(a)amsat.org > Manage all of your AMSAT-NA mailing list preferences athttps://mailman.amsat.org

1 0

Re: Annual Meeting proceedings
by Chris Thompson 07 Oct '23

07 Oct '23

I reviewed the two documents and made some minor changes. I also generated pdfs as we are publishing these and they are also checked back into git. 73 Chris On Fri, Oct 6, 2023 at 4:31 PM Burns Fisher (AMSAT) <wb1fj(a)fisher.cc> wrote: > Sure, ok with me. > 73, > > Burns Fisher, WB1FJ > *AMSAT(R) Engineering -- Flight Software* > > > On Fri, Oct 6, 2023 at 4:30 PM Chris Thompson via pacsat-dev < > pacsat-dev(a)amsat.org> wrote: > >> I am good with that assuming Burns is. I can read through them this >> weekend and see if they need any changes. >> >> >> 73 >> Chris >> >> On Fri, Oct 6, 2023, 14:58 Bill Reed via pacsat-dev <pacsat-dev(a)amsat.org> >> wrote: >> >>> We discussed this briefly last night. >>> >>> Why don't we publish these docs in the proceedings? >>> >>> "PACSAT BBS Operations", 10 Nov 2022, by Chris >>> >>> and >>> >>> "PACSAT Software Architecture", 19 Mar 2023 by Chris and Burns >>> >>> Bill >>> >>> >>> ----------------------------------------------------------- >>> >>> pacsat-dev mailing list -- pacsat-dev(a)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(a)amsat.org >>> Manage all of your AMSAT-NA mailing list preferences at >>> https://mailman.amsat.org >>> >> >> ----------------------------------------------------------- >> >> pacsat-dev mailing list -- pacsat-dev(a)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(a)amsat.org >> Manage all of your AMSAT-NA mailing list preferences at >> https://mailman.amsat.org >> > -- Chris E. Thompson chrisethompson(a)gmail.com g0kla(a)arrl.net

1 0