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
When deep sleep is being executed the interpreter seems to be stuck in schedule threads and doesn't exit so that power level can be changed.
It looked like the Schedule threads continues to run after executing the managed Deep sleep command, probably just finishing its quantum.
Added a return code of CLR_E_THREAD_WAITING in the Deep sleep call to force thread to stop running. This now seems to reliably exit the scheduler and run the deep sleep. Not sure why it was working when last tested.
May need similar change on STM32
Motivation and Context
Broken
Types of changes
Checklist:
Signed-off-by: adriansoundy adriansoundy@gmail.com