Change MessageQueueId to handle that internally #205

Closed
opened 2020-09-22 15:54:15 +02:00 by gaisser · 1 comment
Owner

The current FreeRTOS Version uses a QueueHandle_t pointer to handles its queues, but the FSFW does only support Numeric Queue Identifiers. This is handle by a dirty hack which casts the QueueHandle_t to a void pointer which is 32 bit on a 32 Bit System but brakes on any others.

To fix that, the FSFW should use a map internally to handle the conversion of numeric to OSAL Type.

The current FreeRTOS Version uses a QueueHandle_t pointer to handles its queues, but the FSFW does only support Numeric Queue Identifiers. This is handle by a dirty hack which casts the QueueHandle_t to a void pointer which is 32 bit on a 32 Bit System but brakes on any others. To fix that, the FSFW should use a map internally to handle the conversion of numeric to OSAL Type.
gaisser added the
feature
label 2020-09-22 15:54:15 +02:00
gaisser added this to the ASTP 1.0.0 Local pools milestone 2020-12-01 15:56:44 +01:00
Author
Owner

Currently, I would prefer a internal solution of the OSAL like the current Host OSAL:

auto result = QueueMapManager::instance()->addMessageQueue(this, &mqId);

Therefore, this only relevant for FreeRTOS.

Currently, I would prefer a internal solution of the OSAL like the current Host OSAL: https://egit.irs.uni-stuttgart.de/fsfw/fsfw/src/commit/c50796b785cbed04a0b30937f94870f5c2d28f52/osal/host/MessageQueue.cpp#L11 Therefore, this only relevant for FreeRTOS.
gaisser modified the milestone from ASTP 1.0.0 Local pools to ASTP 1.1.0 2021-04-20 18:14:01 +02:00
muellerr was assigned by gaisser 2021-05-11 14:46:01 +02:00
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: fsfw/fsfw#205
No description provided.