FlyPi/crazyflie-firmware-2021.06/docs/functional-areas/memory-subsystem/MEM_TYPE_TESTER.md

+---
+title: Test - MEM_TYPE_TESTER
+page_id: mem_type_tester
+---
+
+TBD

FlyPi/crazyflie-firmware-2021.06/docs/functional-areas/memory-subsystem/MEM_TYPE_TRAJ.md

+---
+title: Trajectory - MEM_TYPE_TRAJ
+page_id: mem_type_traj
+---
+
+TBD

FlyPi/crazyflie-firmware-2021.06/docs/functional-areas/memory-subsystem/MEM_TYPE_USD.md

+---
+title: uSD card - MEM_TYPE_USD
+page_id: mem_type_usd
+---
+
+TBD

FlyPi/crazyflie-firmware-2021.06/docs/functional-areas/memory-subsystem/index.md

+---
+title: The memory subsystem
+page_id: memory_subsystem
+---
+
+The memory subsystem is intended to be used for transfering larger chunks of data
+between a Crazyflie and a client where real time characteristics are not important.
+
+The memory subsystem uses the ```CRTP_PORT_MEM``` port for communication and supports basic read and write functionality of raw binary data. One packet on the CRTP level contains data for one read or write operation with information on address, size and type. A larger read or write is split up in multiple operations, where each sub-operation fits into one
+CRTP packet. The sub-operations should be done in order (from lower address to higher) and
+some read handlers may rely on this to update caches or similar when receiving the last part of a block.
+
+The type can be seen as the highest level of abstraction and indicates which memory
+the read/write operation will act on. There are a number of memory types (defined in ```MemoryType_t```) which each implements a read and/or write paradigm of selected parts of a virtual memory space, for a functional area of the system. A read/write
+implementation may be mapped directly to a block of RAM in the Crazyflie, but it can
+also be connected to other data structures through function calls where the
+virtual memory map is simply a means of organaizing data for transfer.
+
+A module in the Crazyflie firmware registeres handlers for read and/or write operations
+and the framwork calls the handlers with appropriate values when memory operations are
+initiated from a client.
+
+## Memory types and mappings
+
+* [EEPROM - MEM_TYPE_EEPROM](./MEM_TYPE_EEPROM.md)
+* [One wire memory - MEM_TYPE_OW](MEM_TYPE_OW.md)
+* [LED ring - MEM_TYPE_LED12](MEM_TYPE_LED12.md)
+* [Loco Positioning System 1 - MEM_TYPE_LOCO](MEM_TYPE_LOCO.md)
+* [Trajectory - MEM_TYPE_TRAJ](MEM_TYPE_TRAJ.md)
+* [Loco Positioning System 2 - MEM_TYPE_LOCO2](MEM_TYPE_LOCO2.md)
+* [Lighthouse - MEM_TYPE_LH](MEM_TYPE_LH.md)
+* [Test - MEM_TYPE_TESTER](MEM_TYPE_TESTER.md)
+* [uSD card - MEM_TYPE_USD](MEM_TYPE_USD.md)
+* [LED ring timing - MEM_TYPE_LEDMEM](MEM_TYPE_LEDMEM.md)
+* [Generic application memory - MEM_TYPE_APP](MEM_TYPE_APP.md)
+* [Deck memory - MEM_TYPE_DECK_MEM](MEM_TYPE_DECK_MEM.md)