Manuals / Xilinx / Power Tools / Welder

Xilinx UG181 manual Core Architecture, System Overview

Models: UG181

1 136

Download 136 pages 34.17 Kb

Page 17

R

Chapter 2

Core Architecture

This chapter describes the SPI-4.2 Lite core architecture and interface signals.

System Overview

The SPI-4.2 Lite core is comprised of two separate cores that enable the transmission (Source core) and reception (Sink core) of data.

•Sink Core. Receives data from the SPI-4.2 interface. It takes the 16-bit interface and maps it to a 32-bit or 64-bit interface enabling the internal logic to run at a quarter of the line rate.

•Source Core. Transmits data on the SPI-4.2 interface. Payload data written into the core as 32-bit or 64-bit words (two or four 16-bit SPI-4.2 Lite words, respectively) is mapped onto the 16-bit SPI-4.2 interface.

Figure 2-1illustrates the interfaces of the SPI-4.2 Lite core and shows it in a typical link- layer application.

In the link layer example, the SPI-4.2 interface connects an external physical-layer device to

alink-layer implemented in a Virtex™-4 FPGA. The user logic reads data from the Sink core and writes data into the Source core. A standard FIFO interface is provided for this

SPI-4.2 Lite v4.3 User Guide

www.xilinx.com

17

UG181 June 27, 2008

Image 17

Xilinx UG181 manual Core Architecture, System Overview

Contents

UG181 June 27 LogiCORE IP SPI-4.2 LiteDate Version Revision SPI-4.2 Lite v4.3 User Guide UG181 June 27Table of Contents Designing with the Core Appendix C SPI-4.2 Lite Core Verification SPI-4.2 Lite v4.3 User Guide 1SPI-4.2 Lite Core in a Typical Link Layer Application Schedule of Figures30Addressable Status Fifo Interface 4-Channel Configuration Generating the Core Designing with the Core Schedule of TablesAppendix a SPI-4.2 Lite Control Word About This Guide ContentsTypographical ConventionsConventions Online DocumentPreface About This Guide About the Core IntroductionRecommended Design Experience Additional Core ResourcesFeedback Technical SupportSPI-4.2 Lite Core DocumentSystem Overview Core ArchitectureCore Architecture Sink CoreSource Core Sink Core Interfaces Sink Core InterfacesSink Core Block Diagram RCtlN Sink SPI-4.2 InterfaceSink Control and Status Interface Sink User InterfaceSink Fifo Interface 3Sink Fifo Signals NameCore Architecture 3Sink Fifo Signals Name Sink Core Interfaces Sink Static Configuration Interface Number of Complete Training Sequences a Sink Almost Full Threshold Negate RDClk0 General Purpose Sink Clocking InterfaceRDClk0USER This clock Source Core InterfacesSource Core Interfaces Source SPI-4.2 InterfaceDomain Source User InterfaceSource Control and Status Interface 16 bytes with no EOP Name Direction Clock Description Domain Source Fifo Interface14 Source Status Fifo Signals Source Status Address Source Static Configuration InterfaceSource Almost Full Threshold Assert Source Calendar Period The SrcCalendarM Source Clocking InterfaceSysClk0 General Purpose Domain Core Architecture Core Generator Graphical User Interface Generating the CoreSink Status Options Screen Main ScreenComponent Name Core OptionsStatus Interface CalendarFlow Control Fifo Threshold Sink Other Options ScreenSynchronization Source Status Options Screen Clock ModeClocking Clock DistributionBursting Source Other Options ScreenBurst Size in Credits Burst ModeSysClk Distribution TSClk DistributionCalendar COE File Format Designing with the Core Understand Signal PipeliningGeneral Design Guidelines Know the Degree of DifficultyInitializing the SPI-4.2 Lite Core Recognize Timing Critical SignalsKeep it Registered Use Supported Design FlowsBasic Operation Sink CoreSPI-4.2 Interface Sink Data Path Example1SPI-4.2 Interface to the 64-Bit User Interface SnkFFSOP SnkFFEOP Sink Fifo RCtlSPI-4.2 Control Word Mapping to 32-bit User Interface Sink Control and Status Signals Sink Fifo Almost Empty Sink Fifo Interface SignalsSink Almost Full Sink Fifo EmptySink Overflow Sink Status and Flow Control SignalsInitializing the Calendar In-Circuit Sink Calendar Initialization7Sink Calendar Initialization Sink Flow Control8Typical Flow Control Implementation for 4-Channel System 2,3 None CH 1,2 CH 0,3 CH 0,1,2,3 Sink Status Fifo Interface ExampleSink Status Fifo Status Interface Example Insertion of DIP2 Errors Sink Static Configuration SignalsFifo Almost Full Mode FifoAFMode and Sink Almost Full12FIFO Almost Full Mode Sink Data Capture Implementation Fifo Almost Full Mode 10 orStatic Alignment DCM Alignment Implementation ConsiderationsSynchronization and Start-up Sync Wait ResetHunt Sync Data Error HandlingSync Train In-Frame and Out-of-Frame BehaviorSink SPI-4.2 Bus Error and Sink Bus Error Status70 Sink Fifo Burst ErrorEOP Abort Handling Loss of RDClkSequential End-of-Burst Control Words Sink DIP-4 Error HandlingSequential Payload Control Words 18Example of Error Flag SnkFFDIP4Err Reserved Control Words Source CoreSource Core Source Data Path Example22Source Data Path Minimum SOP Spacing Enforced SrcFFData630 TDat SPI-4.2 Lite v4.3 User Guide Transmitting Training Patterns Transmitting Idle Cycles Inserting DIP4 ErrorsSource Control and Status Signals Source Fifo Almost Full Source Fifo Interface Signals24Source Fifo Almost-full Condition Source Fifo OverflowWriting to the Source Fifo Source Status and Flow Control SignalsInsertion of DIP-4 Errors 27Typical User Design Example Source Calendar Initialization28Source Calendar Initialization Source Flow Control Addressable Status Interface29Addressable Status Fifo Interface Addressable Status Fifo Interface Example30Addressable Status Fifo Interface 4-Channel Configuration Bank None Source Flow Control Transparent Status Interface 33Transparent Status Fifo Interface Block Diagram Source Burst Mode Source Static Configuration Signals35Example Of Source Burst Mode = Source Burst Mode ExampleReset Source Behavior After Synchronization Source Behavior Before SynchronizationEOP Abort Insertion Source Out of FrameSource Pattern Error Handling Source DIP-2 Error HandlingSource Status Frame Word Handling Incorrect Burst TerminationDesigning with the Core Overview Constraining the CoreSink Core Required Constraints Timing ConstraintsTime Names for Clocks Maxdelay for ResetTimespecs for Clocks Constraining the CoreClock Delay in Iserdes Phase Shift for DCMDCM and Static Alignment Constraints Sink Core Required ConstraintsPlacement Placement ConstraintsSink Core Optional Constraints IDelayCtrlStandards Constraints IOB Register PackingArea Group Constraints Source Core Required ConstraintsTiming Ignore Constraints Timenames for ClocksSource Core Required Constraints Inst SysClk LOC = Bank9 Source Core Optional Constraints Source Core Optional ConstraintsNew Target Region or Device Package User ConstraintsConstraints Migration Target Device Modifying the UCF FileSink Core Source CoreInst TSClk LOC = Bank3 Embedded Clocking Special Design ConsiderationsSink Clocking Options Special Design Considerations User Clocking2Sink Core User Clocking Resources Clocking Option Global ClockingSink Clocking Options 3Sink User Clocking Global Clocking Regional ClockingSource Clocking Options Source Clocking Options5Source Clocking Master and Slave Implementation Master ClockingIOB 8Source Clocking Regional Clocking for SysClk TSClk Clocking Resources Clocking Option Slave Clocking3SysClk Clocking Resources Clocking Option Instantiating Multiple Cores Multiple Core ImplementationsMultiple Core Implementations Generating the CoresCreating Top-Level UCF File Clocking Considerations SPI-4.2 Lite v4.3 User Guide 123 124 Functional Simulation Simulating and Implementing the CoreGenerating a Simulation Model Generating a Simulation Model with Initialized CalendarSimulating and Implementing the Core Timing SimulationSynthesis of Example Design SynthesisSynplify SynthesisExample Design Script Xilinx Tool FlowNGDBuild Mapping the DesignXilinx Tool Flow Static Timing AnalysisGenerating a Bitstream 130 Eops SPI-4.2 Lite Control WordDIP-4 Example SPI-4.2 Lite Calendar ProgrammingAppendix B SPI-4.2 Lite Calendar Programming SPI-4.2 Lite Core Verification Appendix C SPI-4.2 Lite Core Verification