Add support for external flash chips and improve mass storage. #31
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
storage to use micropython's VFS interface. This makes mass storage work with any VFS implementation rather than a single one.
This uses a scratch flash sector to save data before writing a full sector.
The code will fallback to the flash scratch space when the GC cannot allocate us enough memory.
This prevents file system corruption due to two systems mutating it at once.
same. Also switch the max size back to 512 for atmel-samd to save ram.
to the same sector. This fixes #20, the issue where a listdir or import won't work without a reset when it was run before the file was copied.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a whole host of changes that add support for external flash chips rather than internal flash.
Flash chips tend to have erase sectors larger than the 512 byte sector size. These commits add two ways to temporarily save the information next to the sector being written. The first added is a slower, low ram solution that uses a spare sector at the end of the flash as scratch space. This is slow and wears that last spare sector a lot so theres a ram cache also added that grabs a sector's worth of memory from the MicroPython heap and uses it to cache the data. This is used most often and falls back to the scratch sector method when low on memory.
Lastly, there are a few odds and ends: