Create F´ Interfaces From Existing Concepts

[LeStarch]

F´ Version
Affected Component

---

Feature Description

Many F´ concepts can be reworked as F´ interfaces. These are specialized .fppi files that define a set of ports. An example would be: https://github.com/nasa/fprime/blob/devel/Drv/Interfaces/ByteStreamDriverInterface.fppi.

Interfaces are expected to live in a folder Interfaces under a given package (e.g. Drv/Interfaces or Svc/Sinterfaces).

New interfaces should use the filename pattern *.interface.fppi and not just .fppi. This is a change since the example was created.

Here is a list of interfaces that should be created:

• Event Ports: Create Events Interface #2584
• Telemetry Ports: Create Telemetry/Channel Interface #2585
• Command Ports: Create Command Interface #2586
• Svc::ComInterface: Create Svc::ComInterface from Svc::ComStub #2257
• Drv::I2cDriver: Create Drv::I2cDriver Interface #2580
• Drv::GpioDriver: Create Interface from LinuxGpioDriver #2581
• Drv::SpiDriver: Create Interface from LinuxSpiDriver #2582
• Drv::TickDriver: Create TickDriver Interface #2583
• UART and TCP Driver: Establish FPP Interfaces for ByteSteamDriverModel #2255
• Time: Rename Time Interface File #2579, Svc::Time Interface #2256

I2c, Gpio, Spi, and ByteStreamDriver items should also have a *UserInterface.fppi for callers/managers using these inferaces. These issues have not been created. These are the same ports with the directions reversed.