Difference: TrbNetFiles (1 vs. 5)

Revision 5
27 Nov 2007 - Main.JanMichel
Line: 1 to 1
 
META TOPICPARENT name="TrbNetEntities"

TRBNet Files

This is a list of files found in the cvs. The optical link is missing at the moment.
Line: 25 to 25
 
trb_net_sbuf
An output buffer using two buffers to be independent from the following part and don't have to take care whether it is reading the offered data or not.

Medium layer

Changed:
<
<
trb_net_med_8bit_fast
data transport over a 2 x 16 Bit wide bus, i.e. lvds. The data is transmitted with dual data rate and 8 bits in parallel. five lines are used for control signals, three are free for debugging purposes.
>
>
trb_net16_med_8bit_slow
data transport over a 2 x 16 Bit wide bus, i.e. lvds. The data is transmitted with 25 MHz and 8 bits in parallel. five lines are used for control signals, three are free for debugging purposes.
 

Network layer

Multiplexer

Changed:
<
<
trb_net_io_multiplexer
A demultiplexer that divides the incoming data to the different ibufs according to channel id and path. Plus a multiplexer that combines the data from the obufs to the single media output, taking care of the different priorities of the different channels.
>
>
trb_net16_io_multiplexer
A demultiplexer that divides the incoming data to the different ibufs according to channel id and path. Plus a multiplexer that combines the data from the obufs to the single media output, taking care of the different priorities of the different channels.
 
trb_net_pattern_gen
A combinatorial entity, takes a number and sets this bit in the output vector
trb_net_priority_arbiter
trb_net_priority_encoder
These entities take care of the priorities of the different channels and select the one with highest priority.

IOBUF

Changed:
<
<
trb_net_ibuf
The input buffer. Receiving data from the medium. Reads flow control packets and hands data to the api.
trb_net_obuf
The output buffer. Sending data from the application layer, adding network layer packets
trb_net_iobuf
The combination of ibuf and obuf, giving complete flow control for the network channel
trb_net_term_ibuf
Simple type of input buffer to be used to receive triggers.

Hub

trb_net_hub_base
base file for all hubs
trb_net_hub_logic
the logic used inside a hub for distributing and concentrating data
>
>
trb_net16_ibuf
The input buffer. Receiving data from the medium. Reads flow control packets and hands data to the api.
trb_net16_obuf
The output buffer. Sending data from the application layer, adding network layer packets
trb_net16_iobuf
The combination of ibuf and obuf, giving complete flow control for the network channel
trb_net16_term_ibuf
Simple type of input buffer to be used to receive triggers.
 
Changed:
<
<

Application interface

trb_net_base_api
The base application interface. It can act in two ways: As an active api, that can send data on its own and as a passive api that sends data only as reply on an incoming transfer
trb_net_active_api
trb_net_passive_api
A active resp. passive application interface. This is only a wrapper for trb_net_base_api, connecting the right channels together
trb_net_term
A simplified application interface. It only indicates if an trigger has been received and allows the application to set the errorbits and the time when den channel should be released.
>
>

Hub

trb_net16_hub_base
base file for all hubs
trb_net16_hub_logic
the logic used inside a hub for distributing and concentrating data
trb_net16_hub_func
some functions used in hub_base
 
Added:
>
>

Application interface

trb_net16_api_base
The base application interface. It can act in two ways: As an active api, that can send data on its own and as a passive api that sends data only as reply on an incoming transfer
trb_net16_api_active
trb_net_api_passive
A active resp. passive application interface. This is only a wrapper for trb_net_base_api, connecting the right channels together
trb_net16_term
A simplified application interface. It only indicates if an trigger has been received and allows the application to set the errorbits and the time when den channel should be released.
 

Deleted:
<
<

16Bit files

trb_net16_dummy_fifo
trb_net16_fifo
trb_net16_base_api
trb_net16_apimbuf
trb_net16_ibuf
trb_net16_iobuf
trb_net16_io_multiplexer
trb_net16_obuf
trb_net16_sbuf
trb_net16_term_ibuf
trb_net16_term
These files use a data bus width of only 16 Bit and have an additional port for the number of the current packet as an indicator for which part of the 64 bit packet is currently transmitted. The usage is the same as for the non-16-bit files, so I'll give no explicit explanation again.
The splitting into passive and active entities has been omitted - this can now be configured using generics.
 

"User convenience files"

trb_net16_endpoint_*
These are complete network entpoints with multiplexer, iobuf and api/trg interface. The number of trigger and application interfaces is given in the filename
Changed:
<
<
-- JanMichel - 16 Oct 2007
>
>
trb_net16_regIO
A passive application to read and write registers over the network. Maybe some DMA-like access will be implemented later.

-- JanMichel - 27 Nov 2007
 
Revision 4
06 Nov 2007 - Main.JanMichel
Line: 1 to 1
 
META TOPICPARENT name="TrbNetEntities"

TRBNet Files

This is a list of files found in the cvs. The optical link is missing at the moment.
Line: 38 to 38
 
trb_net_obuf
The output buffer. Sending data from the application layer, adding network layer packets
trb_net_iobuf
The combination of ibuf and obuf, giving complete flow control for the network channel
trb_net_term_ibuf
Simple type of input buffer to be used to receive triggers.
Changed:
<
<
>
>

Hub

trb_net_hub_base
base file for all hubs
trb_net_hub_logic
the logic used inside a hub for distributing and concentrating data
 

Application interface

Line: 52 to 54
  The splitting into passive and active entities has been omitted - this can now be configured using generics.

"User convenience files"

Changed:
<
<
trb_net16_apimbuf
These entities consist of the api interface, the iobuf and a multiple channel multiplexer. This can be used for any simple endpoint where you don't want to take care about connecting the network and application layer together.
trb_net16_trigger_receiver_endpoint
A simple interface with an even simpler port to see and release triggers
trb_net16_trigger_receiver_apimbuf_endpoint
The combination of a data and a trigger channel
>
>
trb_net16_endpoint_*
These are complete network entpoints with multiplexer, iobuf and api/trg interface. The number of trigger and application interfaces is given in the filename
  -- JanMichel - 16 Oct 2007
Revision 3
16 Oct 2007 - Main.JanMichel
Line: 1 to 1
 
META TOPICPARENT name="TrbNetEntities"

TRBNet Files

This is a list of files found in the cvs. The optical link is missing at the moment.
Line: 46 to 46
 
trb_net_active_api
trb_net_passive_api
A active resp. passive application interface. This is only a wrapper for trb_net_base_api, connecting the right channels together
trb_net_term
A simplified application interface. It only indicates if an trigger has been received and allows the application to set the errorbits and the time when den channel should be released.
Deleted:
<
<

"User convenience files"

trb_net_active_apimbuf
trb_net_passive_apimbuf
These entities consist of the api interface, the iobuf and a single channel multiplexer. This can be used for any simple endpoint where you don't want to take care about connecting the network and application layer together.
trb_net_trigger_receiver_endpoint
A simple interface with an even simpler port to see and release triggers
 

16Bit files

Changed:
<
<
trb_net16_dummy_fifo
trb_net16_fifo
trb_net16_active_api
trb_net16_active_apimbuf
trb_net16_base_api
trb_net16_ibuf
trb_net16_iobuf
trb_net16_io_multiplexer
trb_net16_obuf
trb_net16_passive_api
trb_net16_passive_apimbuf
trb_net16_sbuf
trb_net16_term_ibuf
trb_net16_term
These files use a data bus width of only 16 Bit and have an additional port for the number of the current packet as an indicator for which part of the 64 bit packet is currently transmitted. The usage is the same as for the non-16-bit files, so I'll give no explicit explanation again.
>
>
trb_net16_dummy_fifo
trb_net16_fifo
trb_net16_base_api
trb_net16_apimbuf
trb_net16_ibuf
trb_net16_iobuf
trb_net16_io_multiplexer
trb_net16_obuf
trb_net16_sbuf
trb_net16_term_ibuf
trb_net16_term
These files use a data bus width of only 16 Bit and have an additional port for the number of the current packet as an indicator for which part of the 64 bit packet is currently transmitted. The usage is the same as for the non-16-bit files, so I'll give no explicit explanation again.
The splitting into passive and active entities has been omitted - this can now be configured using generics.
 
Changed:
<
<
-- JanMichel - 30 Sep 2007
>
>

"User convenience files"

trb_net16_apimbuf
These entities consist of the api interface, the iobuf and a multiple channel multiplexer. This can be used for any simple endpoint where you don't want to take care about connecting the network and application layer together.
trb_net16_trigger_receiver_endpoint
A simple interface with an even simpler port to see and release triggers
trb_net16_trigger_receiver_apimbuf_endpoint
The combination of a data and a trigger channel
-- JanMichel - 16 Oct 2007
 
Revision 2
04 Oct 2007 - Main.JanMichel
Line: 1 to 1
 
META TOPICPARENT name="TrbNetEntities"

TRBNet Files

This is a list of files found in the cvs. The optical link is missing at the moment.
Line: 48 to 48
 

"User convenience files"

trb_net_active_apimbuf
trb_net_passive_apimbuf
These entities consist of the api interface, the iobuf and a single channel multiplexer. This can be used for any simple endpoint where you don't want to take care about connecting the network and application layer together.
Added:
>
>
trb_net_trigger_receiver_endpoint
A simple interface with an even simpler port to see and release triggers
 

16Bit files

trb_net16_dummy_fifo
trb_net16_fifo
trb_net16_active_api
trb_net16_active_apimbuf
trb_net16_base_api
trb_net16_ibuf
trb_net16_iobuf
trb_net16_io_multiplexer
trb_net16_obuf
trb_net16_passive_api
trb_net16_passive_apimbuf
trb_net16_sbuf
trb_net16_term_ibuf
trb_net16_term
These files use a data bus width of only 16 Bit and have an additional port for the number of the current packet as an indicator for which part of the 64 bit packet is currently transmitted. The usage is the same as for the non-16-bit files, so I'll give no explicit explanation again.
 
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Hades Wiki? Send feedback
Imprint (in German)
Privacy Policy (in German)