fprime/Svc/Interfaces/RouterInterface.fppi
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

24 lines
955 B
Plaintext

# ---------------------------------------------
# Router <-> Deframers
# ---------------------------------------------
@ Receiving data (Fw::Buffer) to be routed with optional context to help with routing
sync input port dataIn: Svc.ComDataWithContext
@ Port for returning ownership of data (includes Fw.Buffer) received on dataIn
output port dataReturnOut: Svc.ComDataWithContext
# ---------------------------------------------
# Router <-> CmdDispatch/FileUplink
# ---------------------------------------------
@ Port for sending file packets as Fw::Buffer (ownership passed to receiver)
output port fileOut: Fw.BufferSend
@ Port for receiving ownership back of buffers sent on fileOut
sync input port fileBufferReturnIn: Fw.BufferSend
@ Port for sending command packets as Fw::ComBuffers
output port commandOut: Fw.Com
@ Port for receiving command responses from a command dispatcher (can be a no-op)
sync input port cmdResponseIn: Fw.CmdResponse