|
|
| F´ Version |
3.6.4 |
| Affected Component |
Drv/LinuxUartDriver |
Feature Description
The LinuxUartDriver provides BytesSent and BytesRecv telemetry channels, but doesn't write to them. This was fixed in F Prime v4, see #3918 and #3948, but it would be nice to backport this to v3.6.
I have cherry-picked the fix on top of v3.6.4 and done some light testing. That work is available here, and I can open a PR soon. It seems like FwSizeType does not work for telemetry channel types in v3, but if I revert the channels to U32 type, the test deployment compiles and functions as expected.
Rationale
Users of the LinuxUartDriver expect the BytesSent and BytesRecv telemetry channels to have relevant data written to them. Bytes sent/received are useful metrics for debugging and understanding the state of the system.
3.6.4Drv/LinuxUartDriverFeature Description
The LinuxUartDriver provides
BytesSentandBytesRecvtelemetry channels, but doesn't write to them. This was fixed in F Prime v4, see #3918 and #3948, but it would be nice to backport this to v3.6.I have cherry-picked the fix on top of v3.6.4 and done some light testing. That work is available here, and I can open a PR soon. It seems like
FwSizeTypedoes not work for telemetry channel types in v3, but if I revert the channels toU32type, the test deployment compiles and functions as expected.Rationale
Users of the LinuxUartDriver expect the
BytesSentandBytesRecvtelemetry channels to have relevant data written to them. Bytes sent/received are useful metrics for debugging and understanding the state of the system.