-
Notifications
You must be signed in to change notification settings - Fork 321
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
lib_manager: Set target memory flags after data loading from storage #8882
Conversation
98b6361
to
b200a01
Compare
@softwarecki I think this and others are blocked by the Zephyr upgrade. We should be able to fix this soon though. |
SOFCI TEST |
@softwarecki will mark this as blocked on Zephyr update (impacts other PRs too). @lyakh now looking at resolving Zephyr update. |
@softwarecki Zephyr is now updated, so this is unblocked now (but you do need to rebase). |
@softwarecki could you update this one, please? |
@softwarecki This adds a sparse warnings: can you check? |
Memory region must first be mapped as writable to allow data to be placed there. Then the target access flags are set, e.g. read-only and executable. Signed-off-by: Adrian Warecki <[email protected]>
Memory region must first be mapped as writable to allow data to be placed there. Then the target access flags are set, e.g. read-only and executable.
Updated zephyr to zephyrproject-rtos/zephyr@9cf3e08