You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed the TlmPacketizer's TlmRecv port is sync input (i.e. not guarded): https://github.com/nasa/fprime/blob/devel/Svc/TlmPacketizer/TlmPacketizer.fpp#L22-L23. I thought a similar implementation approach may be valid for both. Is there any specific reason why TlmChan's TlmRecv port can't be made sync input to allow telemetry reports in ISR context? Or is TlmPacketizer's TlmRecv input port being sync not suitable for multi-threaded use-case?
The text was updated successfully, but these errors were encountered:
TlmChan component's TlmRecv port is of type guarded input: https://github.com/nasa/fprime/blob/devel/Svc/TlmChan/TlmChan.fpp#L6-L7. As a result reporting telemetry values in ISR context leads to a crash for VxWorks.
I noticed the TlmPacketizer's TlmRecv port is sync input (i.e. not guarded): https://github.com/nasa/fprime/blob/devel/Svc/TlmPacketizer/TlmPacketizer.fpp#L22-L23. I thought a similar implementation approach may be valid for both. Is there any specific reason why TlmChan's TlmRecv port can't be made sync input to allow telemetry reports in ISR context? Or is TlmPacketizer's TlmRecv input port being sync not suitable for multi-threaded use-case?
The text was updated successfully, but these errors were encountered: