Refactor/mpu manager #537
Open
Refactor/mpu manager #537
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
…Alternate functions
…per MPU configuration
…egion outside defined ones
FoniksFox
changed the base branch from
compile-infrastructure
to
development
… refactor/MPUManager
…symbol, to ensure initialization order doesn't matter
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.
Refactor of the MPU so that it works with the new compile-infrastructure.
You can inscribe any type, on any memory domain, with any alignment (up to 32B, since there's no meaning in going any further) cacheable or non-cacheable. The MPU module will calculate and allocate on compile-time all the memory required with the required offsets and everything, such that it even fails if you request too much memory (well, the linker script is the one that actually fails).
It still gives support to the legacy MPUManager.
It has a greater range of protection of the memory, so that you cannot access any memory that is not explicitly defined as accessible.
It dinamycally (in compile-time) allocates the necessary memory with the minimum padding possible so as to not waste any unnecessary memory.
The linker script has been changed to adapt to this new structure.
You need to delete the MPUManager::start() call from Runes to maki this work (since this function no longer exists).