fprime/Svc/ComStub/ComStub.fpp
Thomas Boyer-Chammard c3b2e04880
Use data return pattern on Uplink and standardize port names (#3546)
* First pass at Svc + TcpClient implementation

* Revert FileUplink changes

* Add copy (with allocation/deallocation) to FprimeRouter to simplify buffer management

* Update FprimeRouter UTs

* Update FprimeDeframer UTs

* Update FrameAccumulator UTs

* Update ComStub UTs

* Update missing Drv and UTs

* Update ComInterface to use ComDataWithContext on output

* Update Ref/RPI topology

* Fix spelling

* Fix test typo

* Update Udp component and UTs

* Rename data ports and standardize "Return" naming pattern

* Fix variable name

* Adapt UTs

* Update Communication Adapter Interface docs

* Full SDD updates

* Spelling &  nits and details

* Put formatting back to original

* Update Deframer interface to include bufferReturn

* Address review comments
2025-05-08 10:54:54 -07:00

27 lines
1.0 KiB
Fortran

module Svc {
@ Communication adapter interface implementing communication adapter interface via a Drv.ByteStreamDriverModel.
passive component ComStub {
include "../Interfaces/ComInterface.fppi"
# ----------------------------------------------------------------------
# Byte stream model
# ----------------------------------------------------------------------
@ Ready signal when driver is connected
sync input port drvConnected: Drv.ByteStreamReady
@ Receive (read) data from driver. This gets forwarded to dataOut
sync input port drvReceiveIn: Drv.ByteStreamData
@ Send (write) data to the driver. This gets invoked on dataIn invocation
output port drvSendOut: Fw.BufferSend
@ Callback from drvSendOut (retrieving status and ownership of sent buffer)
sync input port drvSendReturnIn: Drv.ByteStreamData
@ Returning ownership of buffer that came in on drvReceiveIn
output port drvReceiveReturnOut: Fw.BufferSend
}
}