Fix linking error on FreeRTOS when using portYIELD_FROM_ISR #413
Conversation
This file contains 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
Thom747
force-pushed
the
fix-freertos-port
branch
from
f35233b to
8fc7a47
Compare
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.
Pull request
Choose Correct
Describe the pull request
The
portYIELD_FROM_ISR()macro declares a variable calledulPortYieldRequired.FreeRTOS assumes
ulPortYieldRequiredis in the global namespace.To prevent linking errors, this PR introduces a function in the global namespace called
ErpcPortYieldFromISRthat then callsportYIELD_FROM_ISR().To Reproduce
Build eRPC with FreeRTOS.
Expected behavior
eRPC builds as normal.
Desktop (please complete the following information):
Steps you didn't forgot to do