fs_atlantic - Altera Corporation 1 June 2002, ver. 3.0...

Info iconThis preview shows pages 1–4. Sign up to view the full content.

View Full Document Right Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: Altera Corporation 1 June 2002, ver. 3.0 Functional Specification 13 A-FS-13-3.0 Features ■ Flexible interface for packet-oriented data of arbitrary length ■ Interfaces all Altera ® cell and packet MegaCore ® functions ■ Synchronous point-to-point connection ■ High throughput with flexible flow control ■ Master source/slave sink or master sink/slave source relationships ■ Scalable clock frequency and data path width ■ Fixed start of packet (SOP) alignment simplifies packet handling Functional Description The direction of data flow on the Atlantic TM interface can be either from master to slave (master source) or slave to master (slave source). Figure 1 shows a block diagram of the Atlantic interface, transmitting from master source to slave sink. Figure 1. Master Source to Slave Sink Block Diagram Figure 2 on page 2 shows a block diagram of the Atlantic interface, transmitting from slave source to master sink. Atlantic Interface Master Source Atlantic Interface Slave Sink dat ena dav sop eop err mty Atlantic Interface 2 Altera Corporation Atlantic Interface Functional Specification Figure 2. Slave Source to Master Sink Block Diagram Figure 3 shows an example data packet in either master source or slave source configurations. In this case, ena and val are continuously asserted. Figure 3. Example Data Packet Notes: (1) sop marks the start of the data packet. (2) eop marks the end of the data packet, and mty indicates the number of invalid bytes. Master Source A slave sink interface responds to write commands from a master source interface. Atlantic Interface Master Sink Atlantic Interface Slave Source dat ena val dav sop eop err mty clk sop eop mty dat (1) (2) Valid Valid Valid Valid Valid Valid Valid Valid Valid Valid Valid Altera Corporation 3 Atlantic Interface Functional Specification The master asserts ena and drives new data on dat . On the following rising edge of clk , the slave observes dat and ena . If ena is asserted, the slave accepts and processes data; if not, it discards dat . No val is required in this direction because ena indicates when dat contains new, valid data. If ena is deasserted, dat is undefined. The slave sink has no cycle-by-cycle flow control; it uses dav to request the master to stop data transfer. However, the master may take several clock cycles to stop transferring data, depending on the application. dav indicates that the slave can accept a significant amount of data. The amount of data is application dependent. If the master continues to assert ena for an extended period of time after dav is deasserted, the slave may overflow. For a master source, there is no delay after ena is asserted or deasserted and dataflow on dat (and associated data interface signals) starts or stops....
View Full Document

Page1 / 10

fs_atlantic - Altera Corporation 1 June 2002, ver. 3.0...

This preview shows document pages 1 - 4. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online