Synchronisation module interface
See also: IPort
Author: Till Steinbach
The following diagram shows usage relationships between types. Unresolved types are missing from the diagram. Click here to see the full picture.
The following diagram shows inheritance relationships for this type. Unresolved types are missing from the diagram. Click here to see the full picture.
Name | Type | Description |
---|---|---|
IPort | module interface |
Interface of TTEthernet ports. A port is a virtual instance that can receive critical traffic through its gates. |
Name | Type | Description |
---|---|---|
TTEEtherHost | compound module |
Module for a TTEthernet Host. Contains a EtherLLC for best-effort traffic, a TTEPHYPort module as physical port, sync module (Sync) and a TTEScheduler module. The Host is configured by the provided TTEthernet XML network configuration (network_configuration parameter) and uses the device_name parameter to find its config. The configuration is done by the BufferManager that deletes itself at runtime. |
TTEEtherSwitch | compound module |
Module for a TTEthernet Switch with variable number of ports. Contains a configurable best-effort implementation (beRelayUnitType like IMACRelayUnit), TTEPHYPort modules for physical ports, sync module (Sync) and a TTEScheduler module. The switch is configured by the provided TTEthernet XML network configuration (network_configuration parameter) and uses the device_name parameter to find its config. The configuration is done by the BufferManager that deletes itself at runtime. |
Name | Value | Description |
---|---|---|
display | i=block/timer |
// // Synchronisation module interface // // @see IPort // // @author Till Steinbach moduleinterface ISync extends IPort { parameters: @display("i=block/timer"); gates: //Input for scheduler messages input schedulerIn @directIn; }