Interfaces
The TRB-Endpoints are all using the same interfaces. There is a media independent interface (MII) on the network side. On the application side of the endpoint two different interfaces are used: An application interface (API) for sending and receiving data and a trigger interface (TRG) that only receives and answers triggers.
The connection to the Media Interfaces is given by the Media Independent Interface (MII).
Transmitter port
These signals are used to transfer data from the endpoint to the media interface
Name |
Description |
MED_DATAREADY_OUT |
Data is offered by the endpoint |
MED_DATA_OUT(15 downto 0) |
Data |
MED_PACKET_NUM_OUT(1 downto 0) |
Packet number of the current data |
MED_READ_IN |
The media interface reads data from the endpoint |
Receiver port
The receiver port transports data from the media interface to the endpoint
Name |
Description |
MED_DATAREADY_IN |
Data is offered by the media interface |
MED_DATA_IN(15 downto 0) |
Data |
MED_PACKET_NUM_IN(1 downto 0) |
Packet number of the current data |
MED_READ_OUT |
The endpoint reads data from the media interface |
MED_ERROR_IN |
Current status of the network connection (e.g. transmission error or not connected cable) |
Application interface
The application interface is the main interface to the network. Data can be sent and received, either in active (can initiate a transfer) or in passive (can only reply on incoming transfers) mode.
Transmitter port
This is the port for sending data to the network
Name |
Description |
APL_DATA_IN |
Data from the application |
APL_PACKET_NUM_IN |
Packet number of current data |
APL_WRITE_IN |
Data is offered by the application for the API |
APL_FIFO_FULL_OUT |
Full signal of the API's FIFO |
APL_SHORT_TRANSFER_IN |
Activates a short transfer without data |
APL_DTYPE_IN |
Only on active apis: sets dtype |
APL_TARGET_ADDRESS_IN |
Only on active apis: target address |
APL_SEND_IN |
Start sending data to the network |
APL_ERROR_PATTERN_IN |
Errorpattern to be sent with trailer |
Receiver port
Name |
Description |
APL_DATA_OUT |
Data from the network |
APL_PACKET_NUM_OUT |
Packet number of current data |
APL_TYP_OUT |
Type of current data (DAT, HDR, TRM) |
APL_DATAREADY_OUT |
Data is offered for the application |
APL_READ_IN |
Application is reading offered data |
Control port
Name |
Description |
APL_RUN_OUT |
Transfer is running |
APL_MY_ADDRESS_IN |
My own network address |
APL_SEQNR_OUT |
Sequence numberof current transfer |
Trigger receiving interface
This interface can only be used to receive triggers (i.e. short transfers in terms of network definitions). The application connected to this trigger interface has to release the trigger when the necessary operations have been finished and give an errorcode back. With this interface it is not possible to send or receive any other kind of data. If one's reply has to contain data, the normal application interface must be used.
Name |
Description |
TRG_GOT_TRIGGER_OUT |
A trigger has been received |
TRG_ERROR_PATTERN_OUT |
Error pattern of the current trigger |
TRG_DTYPE_OUT |
Trigger type |
TRG_SEQNR_OUT |
Trigger number |
TRG_ERROR_PATTERN_IN |
Error pattern to be sent when releasing trigger |
TRG_RELEASE_IN |
Releases the trigger |