Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Handle devices whose flash implementations cannot copy flash to flash #190

Open
multiplemonomials opened this issue Sep 30, 2023 · 0 comments
Labels
New Feature Usability This makes Mbed harder to use, and needs to be cleaned up.

Comments

@multiplemonomials
Copy link
Collaborator

Currently, it seems like most Mbed devices are not capable of copying one location in flash memory to another in FlashIAP. This means that it has to get buffered, and the logical place to do this is in the FlashIAP class itself. This class should detect if a source region of memory falls inside the flash and, if so, buffer it in RAM.

Optional extra credit: adding a some sort of capability which indicates whether a device can copy flash to flash natively, so that the new code is only activated when actually needed.

@multiplemonomials multiplemonomials added Usability This makes Mbed harder to use, and needs to be cleaned up. New Feature labels Sep 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
New Feature Usability This makes Mbed harder to use, and needs to be cleaned up.
Projects
None yet
Development

No branches or pull requests

1 participant