Useful Links

Description

Standing alongside the other subsystems, this component may seem insignificant. However, the OBC Flash Memory device is a critical component to daily flight operations. It is where we will be storing our system data, telemetry packages, and our operations log files. The particular device we will be using is the S25FL127SABMFI101, a flash non-volatile memory product that will communicate with OBC via SPI. The task is simple, create a a driver that can read and write data to memory. The driver should expect to receive data from a CSP thread thread if it is told to write something to memory, or it will receive a request for a certain piece of data to read from memory.

Tasks

[x] Develop a test plan to validate that the functionality of this thread validates the corresponding requirement
[ ] Create functions that can read and write data to the memory chip. Keep in mind that we need to store various types of data (telemetry, log files), hence the functions should be able to accommodate all of these
- [ ] Optimize the program as much as possible. Memory transfer operations are typically very expensive, and we do not want several threads blocked as they wait for one operation to finish
[ ] Write the unit test that you described earlier in the test plan, and validate that your drivers pass all test cases
[ ] Ensure that the code you write adheres to the Firmware Design Guidelines, and create a pull request

→ Please post a link to the project’s GitHub branch in the Artifacts section, as well as any relevant documentation and deliverables.

→ Use the Notes section for all meeting notes and relevant research findings!

Notes

Old

@Rocklen Utilizing EEPROM Emulation in Flash Memory for optimizing the storage and reducing data loss without utilizing the current method with linked lists seeing as it is inefficient. Because STM32 does not come with EEPROM, emulating it would be beneficial for the overall data storage.

Reserve storage for EEPROM emulation