The memory layout of the FRAM with its persistent variables, EDU program queue, EDU program status history, and Telemetry Memory needs to be managed/determined in a central location. It would also be nice to have a small memory region that we can use for studying radiation effects. This memory region should be read- and writable by GS commands and should not be used for anything else.
The sizes of the different regions/memories of the FRAM are static. Currently, we estimate something like the following:
Persistent variables: ~100 B × 3 = 300 B
EDU program queue: 10 B / entry × 20 entries = 200 B
EDU program status history: 7 B / entry × 50 entries = 350 B
Test memory: 1000 B
--------------------------------------------------------------
Subtotal 1850 B
Telemetry Memory = FRAM size - subtotal = 8 Mib - 1850 B = 8,386,758 B = 7 MiB 1022 kiB 198 B
Description
The memory layout of the FRAM with its persistent variables, EDU program queue, EDU program status history, and Telemetry Memory needs to be managed/determined in a central location. It would also be nice to have a small memory region that we can use for studying radiation effects. This memory region should be read- and writable by GS commands and should not be used for anything else.
The sizes of the different regions/memories of the FRAM are static. Currently, we estimate something like the following:
Telemetry Memory = FRAM size - subtotal = 8 Mib - 1850 B = 8,386,758 B = 7 MiB 1022 kiB 198 B