The FM main task has an internal queue to pass commands to the FM child task. Most command are executed by the child task since the command execution time is unknown or variable.
A stakeholder has experience two cases where an FM command somehow broke the FM main task and FM child task communication. The FM main task says the internal queue is full and the child task says it's waiting for the next command.
In flight, this problem seemed to go away after 20 minutes and the FM child task reported the 3 queued commands had warnings. When it happened on the ground we didn't wait long enough to see if it would clear up.
It appears the sem give/take got confused. Not sure how this can happen.
Observed on system using Vxworks 6.7, CFE 6.4.2, FM 2.4.2.
The FM main task has an internal queue to pass commands to the FM child task. Most command are executed by the child task since the command execution time is unknown or variable.
A stakeholder has experience two cases where an FM command somehow broke the FM main task and FM child task communication. The FM main task says the internal queue is full and the child task says it's waiting for the next command.
In flight, this problem seemed to go away after 20 minutes and the FM child task reported the 3 queued commands had warnings. When it happened on the ground we didn't wait long enough to see if it would clear up.
It appears the sem give/take got confused. Not sure how this can happen.
Observed on system using Vxworks 6.7, CFE 6.4.2, FM 2.4.2.
Imported from GSFCCFS-941