FreeRTOS Improvements #82
No reviewers
Labels
No Label
API Change
Breaking API Change
bug
build
cosmetics
Documentation
duplicate
feature
help wanted
hotfix
invalid
question
Refactor
Tests
wontfix
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: fsfw/fsfw#82
Loading…
Reference in New Issue
No description provided.
Delete Branch "KSat:mueller_FreeRTOS_improvements"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
fixes #55
I might split the semaphore parts which can be used by all OSes, for now everything is in this branch though.
Some details:
SemaphoreFactory (All OSes):
semaphores from FreeRTOS, so the interface to return a Semaphore instance is similar
SemaphoreIF (All OSes):
MessageQueue:
BinarySemaphore:
CoutingSemaphore:
TaskManagement:
There should not be any API changes: the default call context of a message queue is stil the task context, so everything should work as before.
mueller_FreeRTOS_improvementsto FreeRTOS ImprovementsBinary and Counting Semaphores were tested for FreeRTOS and are working. I think there is an incosistency between FreeRTOS and Linux: NO_TIMEOUT does not have the same meaning..
I will split this up. I wrote Semaphore implementations for FreeRTOS which use the new task notifications, but I'd like to keep those separate because they are bound to the task (because they use the tasks' notification value).
I also adapted the factory interface a bit, additional parameters can be passed too (required to create different kind of semaphores).
Pull request closed