You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Feb 5, 2025. It is now read-only.
Currently, there's no API abstractions for non-volatile storage access. As is done in the read_nand.py example, it's up to the user to manually invoke available commands (e.g. nand) to perform NV storage accesses.
I would like to introduce an NV storage API, similar to that of the RAM-based MemoryReader and MemoryWriter.
However, the important differences (e.g. bad blocks, SoC-specific error correction) between different NV storage technologies (e.g., NOR, NAND, eMMC) and interfaces (e.g. parallel, SPI) will need to be taken into account. It may be more worth than is actually valuable to try to abstract that all away from the user -- I haven't decided.
Opening this issue tracker item to mull this over and happily accept feedback.
Currently, there's no API abstractions for non-volatile storage access. As is done in the read_nand.py example, it's up to the user to manually invoke available commands (e.g.
nand) to perform NV storage accesses.I would like to introduce an NV storage API, similar to that of the RAM-based MemoryReader and MemoryWriter.
However, the important differences (e.g. bad blocks, SoC-specific error correction) between different NV storage technologies (e.g., NOR, NAND, eMMC) and interfaces (e.g. parallel, SPI) will need to be taken into account. It may be more worth than is actually valuable to try to abstract that all away from the user -- I haven't decided.
Opening this issue tracker item to mull this over and happily accept feedback.