Fix issues with wrong context switching and global lock calls #1567
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.
Description
Enabling the debug checks showed, that some functions are called in the wrong context. We have to use methods with the correct postfix depending whether in ISR context or not. There are also functions which can be called from both contexts so we have to handle that.
We also have to make sure that GLOBAL_LOCK uses the correct SysLock depending whether in ISR or not.
How Has This Been Tested?
This has been tested on a custom STM32F427 based MCU board.
Screenshots
Types of changes
Checklist:
Signed-off-by: Martin Kuhn martin.kuhn@csa.ch