Skip to content

TlmChan TlmRecv Guarded Input Port #3459

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
arizvi786 opened this issue Apr 7, 2025 · 0 comments
Open

TlmChan TlmRecv Guarded Input Port #3459

arizvi786 opened this issue Apr 7, 2025 · 0 comments

Comments

@arizvi786
Copy link
Collaborator

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants