- pacsat-dev - mailman.amsat.org

Re: Ok, auto-sizing is merged to main
by Chris Thompson 23 Apr '23

23 Apr '23

Great to hear. I ifdef'ed out the MRAM code. We can completely remove it in the next edit. I just left it there temporarily in case I had trouble with the file system. But it seems to work really well so all that code is no longer needed. 73 Chris On Sat, Apr 22, 2023, 17:06 Burns Fisher (AMSAT) via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > Chris, I removed your change for the address size since it should no > longer be needed. I also left in the change that someone made to ifdef out > "NumberOfFiles and MRAMFiles in the configuration partition of the MRAM > (that leaves a lot more space!) > > 73, > > Burns Fisher, WB1FJ > *AMSAT(R) Engineering -- Flight Software* > > ----------------------------------------------------------- > > 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

Ok, auto-sizing is merged to main
by Burns Fisher (AMSAT) 23 Apr '23

23 Apr '23

Chris, I removed your change for the address size since it should no longer be needed. I also left in the change that someone made to ifdef out "NumberOfFiles and MRAMFiles in the configuration partition of the MRAM (that leaves a lot more space!) 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software*

1 0

Updates to software for MRAM
by Burns Fisher (AMSAT) 23 Apr '23

23 Apr '23

Hi, I've spent a couple days trying to figure out how to determine automatically whether the MRAM needs an address size of 2 or 3. I think I have finally done it, although I am not very happy. This is really only when we have multiple MRAM sizes flying around developers. The size should be coded permanently for flight. I've also started using the MRAM config data version number. This should be changed if you change anything in the config storage. That will force users to re-init the MRAM. Believe me, before I put this into Fox I spent ages trying to figure out what was wrong when a new software release was placed on an IHU that had been using an older version. I've also updated the version number for the software. I think it is important to do this. It was 0.0a. I've changed it to 0.1a. The first number refers to the satellite it is being built for (0 is nothing special yet), the second number is a somewhat major change, the letter is a minor change. All this code is currently in my branch: BFLaunchPadBoard. I'll do more testing and then move it to 'main'. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software*

1 0

Serial port on Launchpad?
by Corey Minyard 22 Apr '23

22 Apr '23

I have the current Pacsat software loaded and running, but how do I hook the serial port to the board. The "normal" serial port on the USB interface doesn't seem to work, and IIRC the serial port used by the Pacsat software goes through some other interface. How do you hook it up? Thanks, -corey

1 0

Pacsat dev mtg 4/20/2023
by Bill 21 Apr '23

21 Apr '23

Pacsat dev mtg 4/20/2023 Thu, Apr 20, 2023 7:00 PM - 9:00 PM (CDT) Please join my meeting from your computer, tablet or smartphone. https://meet.goto.com/294997261 You can also dial in using your phone. (For supported devices, tap a one-touch number below to join instantly.) United States: +1 (224) 501-3412 - One-touch: tel:+12245013412,,294997261# Access Code: 294-997-261 Join from a video-conferencing room or system. Dial in or type: 67.217.95.2 or inroomlink.goto.com Meeting ID: 294 997 261 Or dial directly: 294997261(a)67.217.95.2 or 67.217.95.2##294997261 Get the app now and be ready when your first meeting starts: https://meet.goto.com/install

1 0

Re: My status
by Jim McCullers 21 Apr '23

21 Apr '23

Enjoy the game and thanks for everything. Green wire clashes with the OSH-Park purple. Now I see the need for white! Since you will not be at the meeting tonight, do we need larger MRAM’s, at least on some of the boards. Next series up is about $12 per chip then it goes to $26 for the largest. We can discuss later. I chose this size due to the overall cost on a 1st gen test board for everyone. 73, Jim McCullers WA4CWI I may not me on the call tonight. Going to a Red Sox game. As Chris and Jim will report I got did a couple white wires (yes really white!) and then got the software fixed up to use smaller MRAMs so that now works great! The board is a huge improvement !! -- 73, Burns Fisher, WB1FJ AMSAT(R) Engineering -- Flight Software

1 0

My status
by Burns Fisher (AMSAT) 20 Apr '23

20 Apr '23

I may not me on the call tonight. Going to a Red Sox game. As Chris and Jim will report I got did a couple white wires (yes really white!) and then got the software fixed up to use smaller MRAMs so that now works great! The board is a huge improvement !! -- 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software*

1 0

Re: Task names
by Chris Thompson 20 Apr '23

20 Apr '23

Ok, I will take a stab at this and see if I can come up with a list for tasks and for the notifications. 73 Chris On Wed, Apr 19, 2023 at 2:55 PM Burns Fisher (AMSAT) via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > No, they are not the same. The WD has an enum value for each task that is > monitored by the watchdog (essentially all of them). The destination task > list only has the tasks that we send messages to via the message facility. > This typically allows one task or an interrupt to start up another task. > But not all tasks need it. > 73, > > Burns Fisher, WB1FJ > *AMSAT(R) Engineering -- Flight Software* > > > On Wed, Apr 19, 2023 at 2:25 PM Chris Thompson via pacsat-dev < > pacsat-dev(a)amsat.org> wrote: > >> Also note there is a second enum for InterTask notifications, which >> currently has this: >> >> typedef enum { >> ToNone=-1, >> ToDownlinkControl=0, >> ToCommand, >> ToRxTask, >> ToTxTask, >> ToTelemetry, >> // New message destinations go above here >> ToCAN, >> ToCoordinate, >> NumberOfDestinations >> } DestinationTask; >> >> Should this contain the same list as the WD Reports? >> >> 73 >> Chris >> >> On Wed, Apr 19, 2023 at 2:19 PM Chris Thompson via pacsat-dev < >> pacsat-dev(a)amsat.org> wrote: >> >>> This is probably a question just for Burns but I will copy to the list >>> so it is logged for posterity. >>> >>> We need to update the task names. From the architecture design I have >>> the following: >>> RxTask >>> TxTask >>> Ax25Task >>> UplinkTask >>> PbTask >>> CommandTask >>> ConsoleTask >>> TelemCollectionTask >>> >>> In the code today we define the names here, I think: >>> typedef enum { >>> CurrentTaskWD=0, >>> CANSupportWD, >>> TelemetryWD, >>> ControlWD, >>> RadioWD, >>> CommandWD, >>> IdleWD, // Note used in RT >>> ExperimentWD, >>> CoordinateWD, >>> /* Add any new tasks to watch in here. Maximum number of tasks is >>> 9. */ >>> /* The nine limit is the number of bits available in the downlink */ >>> LastWD, >>> InterruptThd = LastWD, >>> ConsoleTsk >>> }WdReporters_t; >>> >>> I have listed 8 tasks. We probably want the Experiment to be the 9th. >>> But what about idle, coordinate, Interrupt, CAN? How do we fit it into 9? >>> Or should we just assume 4 bits and have 16? >>> >>> 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 >>> >> >> >> -- >> 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 > -- Chris E. Thompson chrisethompson(a)gmail.com g0kla(a)arrl.net

1 0

Re: Task names
by Burns Fisher (AMSAT) 20 Apr '23

20 Apr '23

No, they are not the same. The WD has an enum value for each task that is monitored by the watchdog (essentially all of them). The destination task list only has the tasks that we send messages to via the message facility. This typically allows one task or an interrupt to start up another task. But not all tasks need it. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software* On Wed, Apr 19, 2023 at 2:25 PM Chris Thompson via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > Also note there is a second enum for InterTask notifications, which > currently has this: > > typedef enum { > ToNone=-1, > ToDownlinkControl=0, > ToCommand, > ToRxTask, > ToTxTask, > ToTelemetry, > // New message destinations go above here > ToCAN, > ToCoordinate, > NumberOfDestinations > } DestinationTask; > > Should this contain the same list as the WD Reports? > > 73 > Chris > > On Wed, Apr 19, 2023 at 2:19 PM Chris Thompson via pacsat-dev < > pacsat-dev(a)amsat.org> wrote: > >> This is probably a question just for Burns but I will copy to the list so >> it is logged for posterity. >> >> We need to update the task names. From the architecture design I have >> the following: >> RxTask >> TxTask >> Ax25Task >> UplinkTask >> PbTask >> CommandTask >> ConsoleTask >> TelemCollectionTask >> >> In the code today we define the names here, I think: >> typedef enum { >> CurrentTaskWD=0, >> CANSupportWD, >> TelemetryWD, >> ControlWD, >> RadioWD, >> CommandWD, >> IdleWD, // Note used in RT >> ExperimentWD, >> CoordinateWD, >> /* Add any new tasks to watch in here. Maximum number of tasks is 9. >> */ >> /* The nine limit is the number of bits available in the downlink */ >> LastWD, >> InterruptThd = LastWD, >> ConsoleTsk >> }WdReporters_t; >> >> I have listed 8 tasks. We probably want the Experiment to be the 9th. >> But what about idle, coordinate, Interrupt, CAN? How do we fit it into 9? >> Or should we just assume 4 bits and have 16? >> >> 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 >> > > > -- > 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

Re: Task names
by Burns Fisher (AMSAT) 20 Apr '23

20 Apr '23

See my thoughts below: 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software* On Wed, Apr 19, 2023 at 2:19 PM Chris Thompson via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > This is probably a question just for Burns but I will copy to the list so > it is logged for posterity. > > We need to update the task names. From the architecture design I have the > following: > RxTask > TxTask > Ax25Task > UplinkTask > PbTask > CommandTask > ConsoleTask > TelemCollectionTask > > In the code today we define the names here, I think: > typedef enum { > CurrentTaskWD=0, > CANSupportWD, > Not required. We are not using CAN in pacsat > > TelemetryWD, > Note: This task COLLECTS the telemetry every n seconds (4 in Fox and Golf I think) > ControlWD, > This may not be needed. In Fox and Golf it is the task that formats and downlinks (via Radio task) the telemetry. If the telemetry task just writes the telemetry into a file, then no one needs to format it differently. OTOH, if there are different modes etc like Golf and Fox, we might need something. RadioWD, > Is this going to be the same as Rx and Tx? Maybe not needed. > CommandWD, > This may still be needed. On Fox/Golf it is send command data to decode by the Radio task. Probably something like that still required? > IdleWD, // Note used in RT > I bet this is supposed to be "NOT" rather than "NOTE". But I'd have to check. FreeRTOS DOES have an idle task. In Fox, the idle task just whacks away at the watchdog so if there is no idle time, we reboot. On RT, we may use it to check memory, but I don't know why it does not need to pay attention to the WD. > ExperimentWD, > I'm not sure we need this. Pacsat IS a payload. CoordinateWD, > Not required. This is only for Golf where there are multiple processors. Unless we need something similar to coordinate the host and the pacsat payload. > /* Add any new tasks to watch in here. Maximum number of tasks is 9. > */ > /* The nine limit is the number of bits available in the downlink */ > LastWD, > InterruptThd = LastWD, > ConsoleTsk > }WdReporters_t; > > I have listed 8 tasks. We probably want the Experiment to be the 9th. > But what about idle, coordinate, Interrupt, CAN? How do we fit it into 9? > Or should we just assume 4 bits and have 16? > Worth a double check. THis comment (written by me no doubt) seems overly simplistic. But note that this is a bitmask, not a number. The bitmask shows which tasks have and have not kicked the watchdog. So to have 16, we need 16 bits. > > 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