Visible to Intel only — GUID: nik1412467989615
Ixiasoft
1. Introduction to the Avalon® Interface Specifications
2. Avalon® Clock and Reset Interfaces
3. Avalon® Memory-Mapped Interfaces
4. Avalon® Interrupt Interfaces
5. Avalon® Streaming Interfaces
6. Avalon® Streaming Credit Interfaces
7. Avalon® Conduit Interfaces
8. Avalon® Tristate Conduit Interface
A. Deprecated Signals
B. Document Revision History for the Avalon® Interface Specifications
2.1. Avalon® Clock Sink Signal Roles
2.2. Clock Sink Properties
2.3. Associated Clock Interfaces
2.4. Avalon® Clock Source Signal Roles
2.5. Clock Source Properties
2.6. Reset Sink
2.7. Reset Sink Interface Properties
2.8. Associated Reset Interfaces
2.9. Reset Source
2.10. Reset Source Interface Properties
5.1. Terms and Concepts
5.2. Avalon® Streaming Interface Signal Roles
5.3. Signal Sequencing and Timing
5.4. Avalon® -ST Interface Properties
5.5. Typical Data Transfers
5.6. Signal Details
5.7. Data Layout
5.8. Data Transfer without Backpressure
5.9. Data Transfer with Backpressure
5.10. Packet Data Transfers
5.11. Signal Details
5.12. Protocol Details
Visible to Intel only — GUID: nik1412467989615
Ixiasoft
8.3. Tristate Conduit Timing
The following illustrates arbitration timing for the Tristate Conduit Pin Sharer. Note that a device can drive or receive valid data in the granted cycle.
Figure 39. Tristate Conduit Arbitration TimingThis figure shows the following sequence of events:
- In cycle 1, the tristate conduit agent asserts grant. The agent drives valid data in cycles1 and 2.
- In cycle 4, the tristate conduit agent asserts grant. The agent drives valid data in cycles 5–8.
- In cycle 9, the tristate conduit agent asserts grant. The agent drives valid data in cycles 10–17.
- Cycles 3, 4 and 9 do not contain valid data.