Open LeStarch opened 5 months ago
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.
.fppi
Interfaces are expected to live in a folder Interfaces under a given package (e.g. Drv/Interfaces or Svc/Sinterfaces).
Interfaces
Drv/Interfaces
Svc/Sinterfaces
New interfaces should use the filename pattern *.interface.fppi and not just .fppi. This is a change since the example was created.
*.interface.fppi
Here is a list of interfaces that should be created:
Svc::ComInterface
Drv::I2cDriver
Drv::GpioDriver
Drv::SpiDriver
Drv::TickDriver
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.
*UserInterface.fppi
Feature Description
Many F´ concepts can be reworked as F´ interfaces. These are specialized
.fppifiles 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
Interfacesunder a given package (e.g.Drv/InterfacesorSvc/Sinterfaces).Here is a list of interfaces that should be created:
Svc::ComInterface: https://github.com/nasa/fprime/issues/2257Drv::I2cDriver: https://github.com/nasa/fprime/issues/2580Drv::GpioDriver: https://github.com/nasa/fprime/issues/2581Drv::SpiDriver: https://github.com/nasa/fprime/issues/2582Drv::TickDriver: https://github.com/nasa/fprime/issues/2583