system generator for dsp

8/21/2019 System Generator for DSP

1/349

R

SystemGenerator forDSP

User Guide

Release 10.1 March, 2008


2/349

System Generator for DSP www.xilinx.com Release 10.1 March, 2008

Xilinx is disclosing this Document and Intellectual Property (hereinafter “the Design”) to you for use in the development of designs to operateon, or interface with Xilinx FPGAs. Except as stated herein, none of the Design may be copied, reproduced, distributed, republished,downloaded, displayed, posted, or transmitted in any form or by any means including, but not limited to, electronic, mechanical,photocopying, recording, or otherwise, without the prior written consent of Xilinx. Any unauthorized use of the Design may violate copyrightlaws, trademark laws, the laws of privacy and publicity, and communications regulations and statutes.

Xilinx does not assume any liability arising out of the application or use of the Design; nor does Xilinx convey any license under its patents,copyrights, or any rights of others. You are responsible for obtaining any rights you may require for your use or implementation of theDesign. Xilinx reserves the right to make changes, at any time, to the Design as deemed desirable in the sole discretion of Xilinx. Xilinxassumes no obligation to correct any errors contained herein or to advise you of any correction if such be made. Xilinx will not assume anyliability for the accuracy or correctness of any engineering or technical support or assistance provided to you in connection with the Design.

THE DESIGN IS PROVIDED “AS IS” WITH ALL FAULTS, AND THE ENTIRE RISK AS TO ITS FUNCTION AND IMPLEMENTATION ISWITH YOU. YOU ACKNOWLEDGE AND AGREE THAT YOU HAVE NOT RELIED ON ANY ORAL OR WRITTEN INFORMATION ORADVICE, WHETHER GIVEN BY XILINX, OR ITS AGENTS OR EMPLOYEES. XILINX MAKES NO OTHER WARRANTIES, WHETHEREXPRESS, IMPLIED, OR STATUTORY, REGARDING THE DESIGN, INCLUDING ANY WARRANTIES OF MERCHANTABILITY,FITNESS FOR A PARTICULAR PURPOSE, TITLE, AND NONINFRINGEMENT OF THIRD-PARTY RIGHTS.

IN NO EVENT WILL XILINX BE LIABLE FOR ANY CONSEQUENTIAL, INDIRECT, EXEMPLARY, SPECIAL, OR INCIDENTAL

DAMAGES, INCLUDING ANY LOST DATA AND LOST PROFITS, ARISING FROM OR RELATING TO YOUR USE OF THE DESIGN,EVEN IF YOU HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. THE TOTAL CUMULATIVE LIABILITY OF XILINX INCONNECTION WITH YOUR USE OF THE DESIGN, WHETHER IN CONTRACT OR TORT OR OTHERWISE, WILL IN NO EVENTEXCEED THE AMOUNT OF FEES PAID BY YOU TO XILINX HEREUNDER FOR USE OF THE DESIGN. YOU ACKNOWLEDGE THATTHE FEES, IF ANY, REFLECT THE ALLOCATION OF RISK SET FORTH IN THIS AGREEMENT AND THAT XILINX WOULD NOT MAKEAVAILABLE THE DESIGN TO YOU WITHOUT THESE LIMITATIONS OF LIABILITY.

The Design is not designed or intended for use in the development of on-line control equipment in hazardous environments requiring fail-safe controls, such as in the operation of nuclear facilities, aircraft navigation or communications systems, air traffic control, life support, orweapons systems (“High-Risk Applications”). Xilinx specifically disclaims any express or implied warranties of fitness for such High-RiskApplications. You represent that use of the Design in such High-Risk Applications is fully at your risk.

© 2002-2008 Xilinx, Inc. All rights reserved. XILINX, the Xilinx logo, and other designated brands included herein are trademarks of Xilinx,Inc. PowerPC is a trademark of IBM, Inc. All other trademarks are the property of their respective owners.

R

http://www.xilinx.com/http://www.xilinx.com/


3/349

Release 10.1 March, 2008 www.xilinx.com System Generator for DSP

Preface: About This Guide

Guide Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

System Generator PDF Doc Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Typographical . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Online Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Chapter 1: Hardware Design Using System Generator

A Brief Introduction to FPGAs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Note to the DSP Engineer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Note to the Hardware Engineer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Design Flows using System Generator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Algorithm Exploration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Implementing Part of a Larger Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Implementing a Complete Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

System-Level Modeling in System Generator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19System Generator Blocksets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Signal Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Bit-True and Cycle-True Modeling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Timing and Clocking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Synchronization Mechanisms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Block Masks and Parameter Passing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Resource Estimation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Automatic Code Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Compiling and Simulating Using the System Generator Block . . . . . . . . . . . . . . . . . . 39Compilation Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42HDL Testbench . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Compiling MATLAB into an FPGA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Simple Selector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Simple Arithmetic Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Complex Multiplier with Latency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Shift Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Passing Parameters into the MCode Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Optional Input Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Finite State Machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60Parameterizable Accumulator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61FIR Example and System Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64RPN Calculator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Example of disp Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Importing a System Generator Design into a Bigger System . . . . . . . . . . . . . . . . . . 71

HDL Netlist Compilation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71Integration Design Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71New Integration Flow between System Generator & Project Navigator. . . . . . . . . . . 72A Step-by-Step Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Configurable Subsystems and System Generator . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80Defining a Configurable Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80Using a Configurable Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Deleting a Block from a Configurable Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Adding a Block to a Configurable Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Table of Contents



4/349


Generating Hardware from Configurable Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . 84

Notes for Higher Performance FPGA Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86Review the Hardware Notes Included in Block Dialog Boxes . . . . . . . . . . . . . . . . . . . 86Register the Inputs and Outputs of Your Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86Insert Pipeline Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86Use Saturation Arithmetic and Rounding Only When Necessary . . . . . . . . . . . . . . . . 86

Use the System Generator Timing Analysis Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86Set the Data Rate Option on All Gateway Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86Reduce the Clock Enable (CE) Fanout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Processing a System Generator Design with FPGA Physical Design Tools . . . . 87HDL Simulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87Generating an FPGA Bitstream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Resetting Auto-Generated Clock Enable Logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94ce_clr and Rate Changing Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94ce_clr Usage Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Design Styles for the DSP48 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97About the DSP48 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97Designs Using Standard Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Designs Using Synthesizable Mult, Mux and AddSub Blocks . . . . . . . . . . . . . . . . . . . 98Designs that Use DSP48 and DSP48 Macro Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99DSP48 Design Techniques . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Using FDATool in Digital Filter Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105Design Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105Open and Generate the Coefficients for this FIR Filter . . . . . . . . . . . . . . . . . . . . . . . . 106Parameterize the MAC-Based FIR Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107Generate and Assign Coefficients for the FIR Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . 108Browse Through and Understand the Xilinx Filter Block . . . . . . . . . . . . . . . . . . . . . . 109Run the Simulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Generating Multiple Cycle-True Islands for Distinct Clocks . . . . . . . . . . . . . . . . 113Multiple Clock Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Clock Domain Partitioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114Crossing Clock Domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115Netlisting Multiple Clock Designs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116Step-by-Step Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117Creating a Top-Level Wrapper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Using ChipScope Pro Analyzer for Real-Time Hardware Debugging . . . . . . . . 125ChipScope Pro Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125ChipScope in System Generator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125Real-Time Debug . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132Importing Data Into MATLAB Workspace From ChipScope . . . . . . . . . . . . . . . . . . . 135

Chapter 2: Hardware/Software Co-Design

Hardware/Software Co-Design in System Generator . . . . . . . . . . . . . . . . . . . . . . . . 138Black Box Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138PicoBlaze Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138EDK Processor Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

Integrating a Processor with Custom Logic. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138Memory Map Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139Hardware Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140Hardware Co-Simulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141Generating Software Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141



5/349


Writing Software for EDK Processors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142Asynchronous Support for EDK Processors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

EDK Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145Importing an EDK Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145Exposing Processor Ports to System Generator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147Exporting a pcore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

Designing with Embedded Processors and Microcontrollers . . . . . . . . . . . . . . . . 148Designing PicoBlaze Microcontroller Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . 148Designing and Exporting MicroBlaze Processor Peripherals . . . . . . . . . . . . . . . . . . . 155Tutorial Example - Designing and Simulating MicroBlaze Processor Systems . . . . 160Using XPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

Chapter 3: Using Hardware Co-Simulation

Installing Your Hardware Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175Ethernet-Based Hardware Co-Simulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175 JTAG-Based Hardware Co-Simulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175Third-Party Hardware Co-Simulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

Compiling a Model for Hardware Co-Simulation . . . . . . . . . . . . . . . . . . . . . . . . . . . 176Choosing a Compilation Target . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176Invoking the Code Generator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

Hardware Co-Simulation Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

Hardware Co-Simulation Clocking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180Selecting the Target Clock Frequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180Clocking Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181Selecting the Clock Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

Board-Specific I/O Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182I/O Ports in Hardware Co-simulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

Ethernet Hardware Co-Simulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183Point-to-Point Ethernet Hardware Co-Simulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184

Network-Based Ethernet Hardware Co-Simulation . . . . . . . . . . . . . . . . . . . . . . . . . . . 188Shared Memory Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

Compiling Shared Memories for Hardware Co-Simulation . . . . . . . . . . . . . . . . . . . . 190Co-Simulating Unprotected Shared Memories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192Co-Simulating Lockable Shared Memories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193Co-Simulating Shared Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195Co-Simulating Shared FIFOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196Restrictions on Shared Memories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

Specifying Xilinx Tool Flow Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

Frame-Based Acceleration using Hardware Co-Simulation . . . . . . . . . . . . . . . . . . 201Shared Memories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202Adding Buffers to a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203

Compiling for Hardware Co-simulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207Using Vector Transfers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209

Real-Time Signal Processing using Hardware Co-Simulation . . . . . . . . . . . . . . . 214Applying a 5x5 Filter Kernel Data Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2165x5 Filter Kernel Test Bench . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219Reloading the Kernel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223

Installing Your Hardware Co-Simulation Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224Installing an ML402 Board for Ethernet Hardware Co-Simulation . . . . . . . . . . . . . . 224Installing an ML506 Board for Ethernet Hardware Co-Simulation . . . . . . . . . . . . . . 233



6/349


Installing a Spartan-3A DSP 1800A Starter Platform for Ethernet Hardware Co-Simulation242Installing a Spartan-3A DSP 3400A Development Platform for Ethernet Hardware Co-

Simulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245Installing an ML402 Board for JTAG Hardware Co-Simulation . . . . . . . . . . . . . . . . . 254

Supporting New Platforms through JTAG Hardware Co-Simulation . . . . . . . . 255Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255

Supporting New Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255

Chapter 4: Importing HDL Modules

Black Box HDL Requirements and Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270

Black Box Configuration Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270

Black Box Configuration M-Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272

HDL Co-Simulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283Configuring the HDL Simulator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283Co-Simulating Multiple Black Boxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285

Black Box Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286

Importing a Xilinx Core Generator Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286Importing a VHDL Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300Importing a Verilog Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307Dynamic Black Boxes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309Simulating Several Black Boxes Simultaneously . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311Advanced Black Box Example Using ModelSim. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313

Chapter 5: System Generator Compilation Types

HDL Netlist Compilation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320

NGC Netlist Compilation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320

Bitstream Compilation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321

XFLOW Option Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322Additional Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323Re-Compiling EDK Processor Block Software Programs in Bitstreams . . . . . . . . . . 324

EDK Export Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325Creating a Custom Bus Interface for Pcore Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326Export as Pcore to EDK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327System Generator Ports as Top-Level Ports in EDK . . . . . . . . . . . . . . . . . . . . . . . . . . . 328Supported Processors and Current Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328See Also: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328

Hardware Co-Simulation Compilation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329

Timing Analysis Compilation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329Timing Analysis Concepts Review . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330

Timing Analyzer Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332Creating Compilation Targets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342

Defining New Compilation Targets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347



7/349

System Generator for DSP www.xilinx.com 7Release 10.1 March, 2008

R

Preface

About This Guide

This User Guide provides in-depth discussions on topics that are key to understandingand using System Generator. In addition, examples and turorials are also provided thatextend beyond the scope of the System Generator Getting Started Guide.

Guide Contents

This User Guide contains information the following topics:

• Hardware Design using System Generator

• Hardware Software Co-Design

• Hardware Co-Simulation

• Importing HDL Modules

• System Generator Compilation Types

System Generator PDF Doc Set

This User Guide can be found in the System Generator Help system and is also part of theSystem Generator Doc Set that is provided in PDF format. The content of the doc set is as

follows:• System Generator for DSP Getting Started Guide

• System Generator for DSP User Guide

• System Generator for DSP Reference Guide

Note: Hyperlinks across these PDF documents work only when the PDF files reside in the samefolder. After clicking a Hyperlink in the Adobe Reader, you can return to the previous page by pressingthe Alt key and the left arrow key (←) at the same time.

Additional Resources

To find additional documentation, see the Xilinx website at:

http://www.xilinx.com/literature.

To search the Answer Database of silicon, software, and IP questions and answers, or tocreate a technical support WebCase, see the Xilinx website at:

http://www.xilinx.com/support.

http://www.xilinx.com/http://www.xilinx.com/literaturehttp://www.xilinx.com/supporthttp://www.xilinx.com/supporthttp://www.xilinx.com/literaturehttp://www.xilinx.com/


8/349

8 www.xilinx.com System Generator for DSPRelease 10.1 March, 2008

Preface: About This Guide R

Conventions

This document uses the following conventions. An example illustrates each convention.

Typographical

The following typographical conventions are used in this document:

Online Document

The following conventions are used in this document:

Convention Meaning or Use Example

Courier font Messages, prompts, andprogram files that the systemdisplays

speed grade: - 100

Courier bold Literal commands that youenter in a syntactical statement

ngdbuild design_name

Helvetica bold Commands that you select froma menu

File →Open

Keyboard shortcuts Ctrl+C

Italic font Variables in a syntax statementfor which you must supplyvalues

ngdbuild design_name

References to other manuals See the Development SystemReference Guide for moreinformation.

Emphasis in text If a wire is drawn so that itoverlaps the pin of a symbol,the two nets are not connected.

Square brackets [ ] An optional entry or parameter.However, in bus specifications,such as bus[7:0], they arerequired.

ngdbuild [option_name]design_name

Braces { } A list of items from which youmust choose one or more

lowpwr ={on|off}

Vertical bar | Separates items in a list ofchoices

lowpwr ={on|off}

Vertical ellipsis...

Repetitive material that has been omitted

IOB #1: Name = QOUT’IOB #2: Name = CLKIN’...

Horizontal ellipsis . . . Repetitive material that has been omitted

allow block block_name loc1loc2 ... locn;



9/349


ConventionsR

Convention Meaning or Use Example

Blue text Cross-reference link to alocation in the currentdocument

See the topic “AdditionalResources” for details.

Refer to “Title Formats” inChapter 1 for details.

Red text Cross-reference link to alocation in another document

See Figure 2-5 in the Virtex-IIPlatform FPGA User Guide.

Blue, underlined text Hyperlink to a website (URL) Go to http://www.xilinx.com for the latest speed files.



10/349


Preface: About This Guide R



11/349


R

Chapter 1

Hardware Design Using SystemGenerator

System Generator is a system-level modeling tool that facilitates FPGA hardware design. Itextends Simulink in many ways to provide a modeling environment that is well suited tohardware design. The tool provides high-level abstractions that are automaticallycompiled into an FPGA at the push of a button. The tool also provides access to underlyingFPGA resources through low-level abstractions, allowing the construction of highly

efficient FPGA designs.

A Brief Introduction to FPGAs Provides background on FPGAs, and discussescompilation, programming, and architecturalconsiderations in the context of System Generator.

Design Flows using SystemGenerator

Describes several settings in which constructingdesigns in System Generator is useful.

System-Level Modeling inSystem Generator

Discusses System Generator's ability to implementdevice-specific hardware designs directly from aflexible, high-level, system modeling environment.

Automatic Code Generation Discusses automatic code generation for SystemGenerator designs.

Compiling MATLAB into anFPGA

Describes how to use a subset of the MATLABprogramming language to write functions thatdescribe state machines and arithmetic operators.Functions written in this way can be attached to blocks in System Generator and can be automaticallycompiled into equivalent HDL.

Importing a System GeneratorDesign into a Bigger System

Discusses how to take the VHDL netlist from a SystemGenerator design and synthesize it in order to embedit into a larger design. Also shows how VHDL created by System Generator can be incorporated into asimulation model of the overall system.

Configurable Subsystems andSystem Generator

Explains how to use configurable subsystems inSystem Generator. Describes common tasks such asdefining configurable subsystems, deleting andadding blocks, and using configurable subsystems toimport compilation results into System Generatordesigns.



12/349


Chapter 1: Hardware Design Using System Generator R

A Brief Introduction to FPGAs

A field programmable gate array (FPGA) is a general-purpose integrated circuit that is“programmed” by the designer rather than the device manufacturer. Unlike anapplication-specific integrated circuit (ASIC), which can perform a similar function in anelectronic system, an FPGA can be reprogrammed, even after it has been deployed into asystem.

An FPGA is programmed by downloading a configuration program called a bitstream intostatic on-chip random-access memory. Much like the object code for a microprocessor, this bitstream is the product of compilation tools that translate the high-level abstractionsproduced by a designer into something equivalent but low-level and executable. XilinxSystem Generator pioneered the idea of compiling an FPGA program from a high-levelSimulink model.

An FPGA provides you with a two-dimensional array of configurable resources that canimplement a wide range of arithmetic and logic functions. These resources includededicated DSP blocks, multipliers, dual port memories, lookup tables (LUTs), registers, tri-state buffers, multiplexers, and digital clock managers. In addition, Xilinx FPGAs containsophisticated I/O mechanisms that can handle a wide range of bandwidth and voltagerequirements. The Virtex-4 and Virtex-II Pro family FPGAs include embeddedmicrocontrollers (IBM PowerPC 405), and multi-gigabit serial transceivers. The computeand I/O resources are linked under the control of the bitstream by a programmableinterconnect architecture that allows them to be wired together into systems.

FPGAs are high performance data processing devices. DSP performance is derived fromthe FPGA’s ability to construct highly parallel architectures for processing data. In contrastwith a microprocessor or DSP processor, where performance is tied to the clock rate atwhich the processor can run, FPGA performance is tied to the amount of parallelism thatcan be brought to bear in the algorithms that make up a signal processing system. Acombination of increasingly high system clock rates (current system frequencies of 100-200

Notes for Higher PerformanceFPGA Design

Suggests design practices in System Generator thatlead to an efficient and high-performanceimplementation in an FPGA.

Processing a System GeneratorDesign with FPGA PhysicalDesign Tools

Describes how to take the low-level HDL produced bySystem Generator and use it in tools like Xilinx'sProject Navigator, ModelSim, and Synplicity'sSynplify.

Resetting Auto-Generated ClockEnable Logic

Describes the behavior of rate changing blocks fromthe System Generator library when thece_clr signalis used for re-synchronization.

Design Styles for the DSP48 Describes three ways to implement and configure aDSP48 (Xtreme DSP Slice) in System Generator

Using FDATool in Digital FilterApplications

Demonstrates one way to specify, implement andsimulate a FIR filter using the FDATool block.

Generating Multiple Cycle-TrueIslands for Distinct Clocks

Describes how to implement multi-clock designs inSystem Generator

Using ChipScope Pro Analyzerfor Real-Time HardwareDebugging

Demonstrated how to connect and use the XilinxDebug Tool called ChipScope Pro within SystemGenerator



13/349


A Brief Introduction to FPGAsR

MHz are common today) and a highly-distributed memory architecture gives the systemdesigner an ability to exploit parallelism in DSP (and other) applications that operate ondata streams. For example, the raw memory bandwidth of a large FPGA running at a clockrate of 150 MHz can be hundreds of terabytes per second.

There are many DSP applications (e.g., digital up/down converters) that can beimplemented only in custom integrated circuits (ICs) or in an FPGA; a von Neumann

processor lacks both the compute capability and the memory bandwidth required.Advantages of using an FPGA include significantly lower non-recurring engineering coststhan those associated with a custom IC (FPGAs are commercial off-the-shelf devices),shorter time to market, and the configurability of an FPGA, which allows a design to bemodified, even after deployment in an end application.

When working in System Generator, it is important to keep in mind that an FPGA hasmany degrees of freedom in implementing signal processing functions. You have, forexample, the freedom to define data path widths throughout your system and to employmany individual data processors (e.g., multiply-accumulate engines), depending onsystem requirements. System Generator provides abstractions that allow you to design foran FPGA largely by thinking about the algorithm you want to implement. However, themore you know about the underlying FPGA, the more likely you are to exploit the unique

capabilities an FPGA provides in achieving high performance.

The remainder of this topic is a brief introduction to some of the logic resources available inthe FPGA, so that you gain some appreciation for the abstractions provided in SystemGenerator.

The figure above shows a physical view of a Virtex-4 FPGA. To a signal DSP engineer, an

FPGA can be thought of as a 2-D array of logic slices striped with columns of hard macro blocks (block memory and arithmetic blocks) suitable for implementing DSP functions,embedded within a configurable interconnect mesh. In a Virtex-4 FPGA, the DSP blocks(shown in the next figure) can run in excess of 450 MHz, and are pitch-matched to dualport memory blocks (BRAMs) whose ports can be configured to a wide range of word sizes(18 Kb total per BRAM). The Virtex-4 SX55 device contains 512 such DSP blocks andBRAMs. In System Generator, you can access all of these resources through arithmetic and



14/349



logic abstractions to build very high performance digital filters, FFTs, and other arithmeticand signal processing functions.

While the multiply-accumulate function supported by a Virtex-4 DSP block is familiar to aDSP engineer, it is instructive to take a closer look at the Virtex family logic slice (shown below), which is the fundamental unit of the logic fabric array.

Each logic slice contains two 4-input lookup tables (LUTs), two configurable D-flip flops,multiplexers, dedicated carry logic, and gates used for creating slice-based multipliers.

Each LUT can implement an arbitrary 4-input Boolean function. Coupled with dedicatedlogic for implementing fast carry circuits, the LUTs can also be used to build fastadder/subtractors and multipliers of essentially any word size. In addition toimplementing Boolean functions, each LUT can also be configured as a 16x1 bit RAM or asa shift register (SRL16). An SRL16 shift register is a synchronously clocked 16x1 bit delayline with a dynamically addressable tap point.

In System Generator, these different memory options are represented with higher-levelabstractions. Instead of providing a D-flip flop primitive, System Generator provides aregister of arbitrary size. There are two blocks that provide abstractions of arbitrary



15/349


A Brief Introduction to FPGAsR

width, arbitrary depth delay lines that map directly onto the SRL16 configuration. Thedelay block can be used for pipeline balancing, and can also be used as storage for time-division multiplexed (TDM) data streams. The addressable shift register (ASR) block,with a function depicted in the figure below, provides an arbitrary width, arbitrary depthtapped delay line. This block is of particular interest to the DSP engineer, since it can beused to implement tapped delay lines as well as sweeping through TDM data streams.

Although random access memories can be constructed either out of the BRAM or LUT(RAM16x1) primitives, doing so can require considerable care to ensure most efficientmappings, and considerable clerical attention to detail to correctly assemble the primitivesinto larger structures. System Generator removes the need for such tasks.

For example, the dual port RAM (DPRAM) block shown in the figure below mapsefficiently onto as many BRAM or RAM16x1 components on the device as are necessary toimplement the desired memory. As can be seen from the mask dialog box for the DPRAM,the interface allows you to specify a type of memory (BRAM or RAM16x1), depth (datawidth is inferred from the Simulink signal driving a particular input port), initial memorycontents, and other characteristics.



16/349



In general, System Generator maps abstractions onto device primitives efficiently, freeingyou from worrying about interconnections between the primitives. System Generatoremploys libraries of intellectual property (IP) when appropriate to provide efficientimplementations of functions in the block libraries. In this way, you don’t always have tohave detailed knowledge of the underlying FPGA details. However, when it makes senseto implement an algorithm using basic functions (e.g., adder, register, memory), System

Generator allows you to exploit your FPGA knowledge while reducing the clerical tasks ofmanaging all signals explicitly.

System Generator library blocks and the mapping from Simulink to hardware aredescribed in detail in subsequent topics of this documentation. There is a wealth ofdetailed information about FPGAs that can be found online at http://support.xilinx.com,including data books, application notes, white papers, and technical articles.

Note to the DSP Engineer

System Generator extends Simulink to enable hardware design, providing high-levelabstractions that can be automatically compiled into an FPGA. Although the arithmeticabstractions are suitable to Simulink (discrete time and space dynamical systemsimulation), System Generator also provides access to features in the underlying FPGA.

The more you know about a hardware realization (e.g., how to exploit parallelism andpipelining), the better the implementation you’ll obtain. Using IP cores makes it possible tohave efficient FPGA designs that including complex functions like FFTs. System Generatoralso makes it possible to refine a model to more accurately fit the application.

Scattered throughout the System Generator documentation are notes that explain ways inwhich system parameters can be used to exploit hardware capabilities.

Note to the Hardware Engineer

System Generator does not replace hardware description language (HDL)-based design, but does makes it possible to focus your attention only on the critical parts. By analogy,

most DSP programmers do not program exclusively in assembler; they start in a higher-level language like C, and write assembly code only where it is required to meetperformance requirements.

A good rule of thumb is this: in the parts of the design where you must manage internalhardware clocks (e.g., using the DDR or phased clocking), you should implement usingHDL. The less critical portions of the design can be implemented in System Generator, andthen the HDL and System Generator portions can be connected. Usually, most portions ofa signal processing system do not need this level of control, except at external interfaces.System Generator provides mechanisms to import HDL code into a design (see ImportingHDL Modules) that are of particular interest to the HDL designer.

Another aspect of System Generator that is of interest to the engineer who designs usingHDL is its ability automatically generate an HDL testbench, including test vectors. This

aspect is described in the topic HDL Testbench.

Finally, the hardware co-simulation interfaces described in the topic Using Hardware Co-Simulation allow you to run a design in hardware under the control of Simulink, bringingthe full power of MATLAB and Simulink to bear for data analysis and visualization.

http://www.xilinx.com/http://support.xilinx.com/http://support.xilinx.com/http://www.xilinx.com/


17/349


Design Flows using System GeneratorR

Design Flows using System Generator

System Generator can be useful in many settings. Sometimes you may want to explore analgorithm without translating the design into hardware. Other times you might plan to usea System Generator design as part of something bigger. A third possibility is that a SystemGenerator design is complete in its own right, and is to be used in FPGA hardware. This

topic describes all three possibilities.

Algorithm Exploration

System Generator is particularly useful for algorithm exploration, design prototyping, andmodel analysis. When these are the goals, you can use the tool to flesh out an algorithm inorder to get a feel for the design problems that are likely to be faced, and perhaps toestimate the cost and performance of an implementation in hardware. The work ispreparatory, and there is little need to translate the design into hardware.

In this setting, you assemble key portions of the design without worrying about fine pointsor detailed implementation. Simulink blocks and MATLAB M-code provide stimuli forsimulations, and for analyzing results. Resource estimation gives a rough idea of the costof the design in hardware. Experiments using hardware generation can suggest thehardware speeds that are possible.

Once a promising approach has been identified, the design can be fleshed out. SystemGenerator allows refinements to be done in steps, so some portions of the design can bemade ready for implementation in hardware, while others remain high-level and abstract.System Generator's facilities for hardware co-simulation are particularly useful whenportions of a design are being refined.

Implementing Part of a Larger Design

Often System Generator is used to implement a portion of a larger design. For example,System Generator is a good setting in which to implement data paths and control, but isless well suited for sophisticated external interfaces that have strict timing requirements. Inthis case, it may be useful to implement parts of the design using System Generator,implement other parts outside, and then combine the parts into a working whole.

A typical approach to this flow is to create an HDL wrapper that represents the entiredesign, and to use the System Generator portion as a component. The non-SystemGenerator portions of the design can also be components in the wrapper, or can beinstantiated directly in the wrapper.

Implementing a Complete Design

Many times, everything needed for a design is available inside System Generator. For sucha design, pressing the Generate button instructs System Generator to translate the designinto HDL, and to write the files needed to process the HDL using downstream tools. Thefiles written include the following:

• HDL that implements the design itself;

• A clock wrapper that encloses the design. This clock wrapper produces the clock andclock enable signals that the design needs.

• A HDL testbench that encloses the clock wrapper. The testbench allows results fromSimulink simulations to be compared against ones produced by a logic simulator.



18/349



• Project files and scripts that allow various synthesis tools, such as XST and SynplifyPro to operate on System Generator HDL

• Files that allow the System Generator HDL to be used as a project in ProjectNavigator.

For details concerning the files that System Generator writes, see the topic CompilationResults.



19/349


System-Level Modeling in System GeneratorR

System-Level Modeling in System Generator

System Generator allows device-specific hardware designs to be constructed directly in aflexible high-level system modeling environment. In a System Generator design, signalsare not just bits. They can be signed and unsigned fixed-point numbers, and changes to thedesign automatically translate into appropriate changes in signal types. Blocks are not just

stand-ins for hardware. They respond to their surroundings, automatically adjusting theresults they produce and the hardware they become.

System Generator allows designs to be composed from a variety of ingredients. Data flowmodels, traditional hardware design languages (VHDL, Verilog, and EDIF), and functionsderived from the MATLAB programming language, can be used side-by-side, simulatedtogether, and synthesized into working hardware. System Generator simulation results are bit and cycle-accurate. This means results seen in simulation exactly match the results thatare seen in hardware. System Generator simulations are considerably faster than thosefrom traditional HDL simulators, and results are easier to analyze.

System Generator Blocksets Describes how System Generator's blocks areorganized in libraries, and how the blocks can beparameterized and used.

Signal Types Describes the data types used by System Generatorand ways in which data types can be automaticallyassigned by the tool.

Bit-True and Cycle-TrueModeling

Specifies the relationship between the Simulink-basedsimulation of a System Generator model and the behavior of the hardware that can be generated fromit.

Timing and Clocking Describes how clocks are implemented in hardware,and how their implementation is controlled insideSystem Generator. Explains how System Generatortranslates a multirate Simulink model into workingclock-synchronous hardware.

Synchronization Mechanisms Describes mechanisms that can be used tosynchronize data flow across the data path elementsin a high-level System Generator design, anddescribes how control path functions can beimplemented.

Block Masks and ParameterPassing

Explains how parameterized systems and subsystemsare created in Simulink.

Resource Estimation Describes how to generate estimates of the hardwareneeded to implement a System Generator design.



20/349



System Generator Blocksets

A Simulink blockset is a library of blocks that can be connected in the Simulink block editorto create functional models of a dynamical system. For system modeling, SystemGenerator blocksets are used like other Simulink blocksets. The blocks provideabstractions of mathematical, logic, memory, and DSP functions that can be used to buildsophisticated signal processing (and other) systems. There are also blocks that provideinterfaces to other software tools (e.g., FDATool, ModelSim) as well as the SystemGenerator code generation software.

System Generator blocks are bit-accurate and cycle-accurate. Bit-accurate blocks producevalues in Simulink that match corresponding values produced in hardware; cycle-accurate blocks produce corresponding values at corresponding times.



21/349



Xilinx Blockset

The Xilinx Blockset is a family of libraries that contain basic System Generator blocks.Some blocks are low-level, providing access to device-specific hardware. Others are high-level, implementing (for example) signal processing and advanced communicationsalgorithms. For convenience, blocks with broad applicability (e.g., the Gateway I/O blocks) are members of several libraries. Every block is contained in the Index library. Thelibraries are described below.

Note: More information concerning blocks can be found in the topic Xilinx Blockset.

Xilinx Reference BlocksetThe Xilinx Reference Blockset contains composite System Generator blocks that implementa wide range of functions. Blocks in this blockset are organized by function into differentlibraries. The libraries are described below.

Each block in this blockset is a composite, i.e., is implemented as a masked subsystem, withparameters that configure the block.

You can use blocks from the Reference Blockset libraries as is, or as starting points whenconstructing designs that have similar characteristics. Each reference block has a

Library Description

Index Every block in the Xilinx Blockset.

Basic Elements ElementsStandard building blocks for digital logic

Communication Forward error correction and modulator blocks, commonly used indigital communications systems

Control Logic Blocks for control circuitry and state machines

Data Types Blocks that convert data types (includes gateways)

DSP Digital signal processing (DSP) blocks

Math Blocks that implement mathematical functions

Memory Blocks that implement and access memories

Shared Memory Blocks that implement and access Xilinx shared memories

Tools “Utility” blocks, e.g., code generation (System Generator block),resource estimation, HDL co-simulation, etc

Library Description

Communication Blocks commonly used in digital communications systems

Control Logic LogicBlocks used for control circuitry and state machines

DSP Digital signal processing (DSP) blocks

Imaging Image processing blocks

Math Blocks that implement mathematical functions

http://www.xilinx.com/http://sysgen_ref.pdf/http://sysgen_ref.pdf/http://sysgen_ref.pdf/http://www.xilinx.com/


22/349



description of its implementation and hardware resource requirements. Individualdocumentation for each block is also provided in the topic Xilinx Reference Blockset.

Signal Types

In order to provide bit-accurate simulation of hardware, System Generator blocks operateon Boolean and arbitrary precision fixed-point values. By contrast, the fundamental scalarsignal type in Simulink is double precision floating point. The connection between Xilinx blocks and non-Xilinx blocks is provided by gateway blocks . The gateway in converts adouble precision signal into a Xilinx signal, and the gateway out converts a Xilinx signal intodouble precision. Simulink continuous time signals must be sampled by the Gateway In block.

Most Xilinx blocks are polymorphic, i.e., they are able to deduce appropriate output types based on their input types. When full precision is specified for a block in its parameters

dialog box, System Generator chooses the output type to ensure no precision is lost. Signextension and zero padding occur automatically as necessary. User-specified precision isusually also available. This allows you to set the output type for a block and to specify howquantization and overflow should be handled. Quantization possibilities include unbiasedrounding towards plus or minus infinity, depending on sign, or truncation. Overflowoptions include saturation, truncation, and reporting overflow as an error.

Note: System Generator data types can be displayed by selecting Format > Port Data Types inSimulink. Displaying data types makes it easy to determine precision throughout a model. If, forexample, the type for a port is Fix_11_9, then the signal is a two's complement signed 11-bit number

http://www.xilinx.com/http://sysgen_ref.pdf/http://sysgen_ref.pdf/http://www.xilinx.com/


23/349



having nine fractional bits. Similarly, if the type is Ufix_5_3, then the signal is an unsigned 5-bitnumber having three fractional bits.

In the System Generator portion of a Simulink model, every signal must be sampled.Sample times may be inherited using Simulink's propagation rules, or set explicitly in a block customization dialog box. When there are feedback loops, System Generator issometimes unable to deduce sample periods and/or signal types, in which case the tool

issues an error message. Assert blocks must be inserted into loops to address this problem.It is not necessary to add assert blocks at every point in a loop; usually it suffices to add anassert block at one point to “break” the loop.

Note: Simulink can display a model by shading blocks and signals that run at different rates withdifferent colors (Format > Sample Time Colors in the Simulink pulldown menus). This is often usefulin understanding multirate designs

Bit-True and Cycle-True Modeling

Simulations in System Generator are bit-true and cycle-true. To say a simulation is bit-truemeans that at the boundaries (i.e., interfaces between System Generator blocks and non-System Generator blocks), a value produced in simulation is bit-for-bit identical to the

corresponding value produced in hardware. To say a simulation is cycle-true means that atthe boundaries, corresponding values are produced at corresponding times. The boundaries of the design are the points at which System Generator gateway blocks exist.When a design is translated into hardware, Gateway In (respectively, Gateway Out) blocks become top-level input (resp., output) ports.

Timing and Clocking

Discrete Time Systems

Designs in System Generator are discrete time systems. In other words, the signals and the blocks that produce them have associated sample rates. A block’s sample rate determineshow often the block is awoken (allowing its state to be updated). System Generator setsmost sample rates automatically. A few blocks, however, set sample rates explicitly orimplicitly.

Note: For an in-depth explanation of Simulink discrete time systems and sample times, consult theUsing Simulink reference manual from the MathWorks, Inc.

A simple System Generator model illustrates the behavior of discrete time systems.Consider the model shown below. It contains a gateway that is driven by a Simulink source(Sine Wave), and a second gateway that drives a Simulink sink (Scope).

The Gateway In block is configured with a sample period of one second. The Gateway Out block converts the Xilinx fixed-point signal back to a double (so it can analyzed in the



24/349



Simulink scope), but does not alter sample rates. The scope output below shows theunaltered and sampled versions of the sine wave.

Multirate Models

System Generator supports multirate designs, i.e., designs having signals running atseveral sample rates. System Generator automatically compiles multirate models intohardware. This allows multirate designs to be implemented in a way that is both naturaland straightforward in Simulink.

Rate-Changing Blocks

System Generator includes blocks that change sample rates. The most basic rate changersare the Up Sample and Down Sample blocks. As shown in the figure below, these blocksexplicitly change the rate of a signal by a fixed multiple that is specified in the block’sdialog box.

Other blocks (e.g., the Parallel To Serial and Serial To Parallel converters) change ratesimplicitly in a way determined by block parameterization.

Consider the simple multirate example below. This model has two sample periods, SP1and SP2. The Gateway In dialog box defines the sample period SP1. The Down Sample block causes a rate change in the model, creating a new rate SP2 which is half as fast as SP1.



25/349



Hardware Oversampling

Some System Generator blocks are oversampled, i.e., their internal processing is done at arate that is faster than their data rates. In hardware, this means that the block requires morethan one clock cycle to process a data sample. In Simulink such blocks do not have anobservable effect on sample rates.

One block that can be oversampled is the DAFIR FIR filter. An oversampled DAFIRprocesses samples serially, thus running at a higher rate, but using less hardware.

Although blocks that are oversampled do not cause an explicit sample rate change inSimulink, System Generator considers the internal block rate along with all other samplerates when generating clocking logic for the hardware implementation. This means thatyou must consider the internal processing rates of oversampled blocks when you specifythe Simulink system period value in the System Generator block dialog box.

Asynchronous Clocking

System Generator focuses on the design of hardware that is synchronous to a single clock.It can, under some circumstances, be used to design systems that contain more than oneclock. This is possible provided the design can be partitioned into individual clockdomains with the exchange of information between domains being regulated by dual portmemories and FIFOs. System Generator fully supports such multi-clock designs, includingthe ability to simulate them in Simulink and to generate complete hardware descriptions.Details are discussed in the topic Generating Multiple Cycle-True Islands for DistinctClocks. The remainder of this topic focuses exclusively on the clock-synchronous aspectsof System Generator. This discussion is relevant to both single-clock and multiple-clockdesigns.

Synchronous Clocking

As shown in the figure below, when you use the System Generator token to compile adesign into hardware, there are three clocking options for Multirate implementation: (1)Clock Enables (the default), (2) Clock Generator(DCM), and (3) Expose Clock Ports.



26/349



The Clock Enables Option

When System Generator compiles a model into hardware with the Clock Enable optionselected, System Generator preserves the sample rate information of the design in such away that corresponding portions in hardware run at appropriate rates. In hardware,System Generator generates related rates by using a single clock in conjunction with clockenables, one enable per rate. The period of each clock enable is an integer multiple of the

period of the system clock.

Inside Simulink, neither clocks nor clock enables are required as explicit signals in aSystem Generator design. When System Generator compiles a design into hardware, ituses the sample rates in the design to deduce what clock enables are needed. To do this, itemploys two user-specified values from the System Generator block: the Simulink systemperiod and FPGA clock period. These numbers define the scaling factor between time in aSimulink simulation, and time in the actual hardware implementation. The Simulinksystem period must be the greatest common divisor (gcd) of the sample periods thatappear in the model, and the FPGA clock period is the period, in nanoseconds, of thesystem clock. If p represents the Simulink system period, and c represents the FPGAsystem clock period, then something that takes kp units of time in Simulink takes k ticks ofthe system clock (hence kc nanoseconds) in hardware.

To illustrate this point, consider a model that has three Simulink sample periods 2, 3, and4. The gcd of these sample periods is 1, and should be specified as such in the SimulinkSystem Period field for the model. Assume the FPGA Clock Period is specified to be 10ns.With this information, the corresponding clock enable periods can be determined inhardware.

In hardware, we refer to the clock enables corresponding to the Simulink sample periods 2,3, and 4 as CE2, CE3, and CE4, respectively. The relationship of each clock enable period tothe system clock period can be determined by dividing the corresponding Simulinksample period by the Simulink System Period value. Thus, the periods for CE2, CE3, andCE4 equal 2, 3, and 4 system clock periods, respectively. A timing diagram for the exampleclock enable signals is shown below:

The Clock Generator(DCM) Option

If the implementation target is an FPGA with a Digital Clock Manager (DCM), you canchoose to drive the clock tree with a DCM. The DCM option is desirable when high fanouton clock enable nets make it difficult to achieve timing closure.

System Generator instantiates the DCM in a top-level HDL clock wrapper and configuresthe DCM to provide up to three clock ports at different rates for Virtex-4 and Virtex-5 and upto two clock ports for Spartan-3A DSP. If this DCM option is selected and the set of rates inthe design cannot be supported using a single DCM, than an error will be issued. Themapping of rates to the DCM outputs is done according to the following priority scheme:CLK0 > CLK2x > CLKdv > CLKfx.

A dmc_reset input port is exposed on the top-level wrapper to allow the external designto reset the DCM after bitstream configuration. A dcm_locked output port is also exposedto help the external design synchronize the input data with the single clk input port.



27/349



Known Limitations: The following System Generator blocks are not supported by theClock Generator(DCM) Option:

• Clock Enable Probe

• Clock Probe

• DAFIR

• Downsample - when the Sample option First value of the frame is selected• FIR Compiler - when the core rate is not equal to the input sample rate

• Parallel to Serial- when the Latency option is specified as 0 (zero)

• Time Division De-Multiplexer

• Time Division Multiplexer

• Upsample - when the Copy samples (otherwise zeros are inserted) option is not selected.

Note: For Release 10.1, the Clock Generator(DCM) option was tested in hardware using Virtex 4and Virtex 5 platforms at 400MHz and the Spartan-3A DSP platform at 190MHz.

The Expose Clock Ports Option

When you select this option, System Generator creates a top-level wrapper that exposes aclock port for each rate. You can then manually instantiate a clock generator outside thedesign to drive the clock ports.

Tutorial Example: Using the Clock Generator(DCM) Option

The following step-by-step example will show you how to select the Clock Generator(DCM) option, netlist the HDL design, implement the design in ISE, simulate the designand examine the files and reports to verify that the DCM is properly instantiated andconfigured.

The dcm_case1 design example is located at the following pathname/examples/clocking_options/dcm_case1/dcm_case1.mdl

1. Open the model in MATLAB and observe the following blocks:

• Addressable Shift Register (ASR): used to implement the input delay buffer. Theaddress port runs n times faster than the data port, where n is the number of the filtertaps (5 for this example)

• Coefficient ROM: used to store the filter coefficients

• Counter: used to generate addresses for the ROM and ASR

• Comparator: used to generate the reset and enable signals



28/349



• MAC Engine: used as a Multiply-Accumulator operator for the filter

2. Double-click on the System Generator token to bring up the following dialog box:

As shown above, select Clock Generator(DCM), then click Generate. After a fewmoments, a sub-directory named hdl_netlist is created in the current working directorycontaining the generated files.



29/349



3. In the MATLAB Current Directory window, double-click on the filedcm_case1_sysgen.log. As shown below, the clocks from the DCM are listed.

4. Launch ISE, then load the ISE project at pathname./hdl_netlist/dcm_case1_dcm_mcw.ise

5. Under the Project Navigator Processes tab, double-click on Implement Design.

6. From the Project Navigator Sources tab, do the following:

a. Double-click on the file dcm_case1_dcm_mcw.vhd, then scroll down to view theDCM component declaration as shown below by the VHDL code snippet:

b. Observe that System Generator automatically infers and instantiates the DCMinstance and its parameters according to the required clock outputs.

c. Close the VHDL file.

Next, you are going to examine the clock propagation by examining the ISE timing report.To be able to see the DCM clock outputs in the ISE timing report, you must first create asimple user constraint file (UCF).

7. Under the Processes tab > User Constraints, double-click on Create TimingConstraints. Constrain the design as shown in the figure below, then save the file.

8. Examine the DCM clock outputs: Under Processes tab > Implement Design > Place &Route > Generate Post-Place & Route Static Timing



30/349



9. Once finished, double -click on Analyze Post-Place & Route Static Timing and youshould see the information in the figure below:

The timing report validates the correct clock propagation by System Generator - 10 nsand 50 ns.

Next you want to perform a behavior simulation using the ModelSim.

10. As shown in the following figure, move to the Sources for dialog box in the Sources

window, then select Behavioral Simulation



31/349



Note: System Generator automatically creates the top-wrapper VHDL testbench, script file andinput/output stimulus data files. The Processes tab changes and displays according to theSources type being selected.

11. Simulate the design, as shown above, by double-click on Simulate Behavioral Modelin the Processes window

12. After the simulation is finished, you should be able to observe the simulationwaveforms as shown in the figure below:

2. Double Click

1. Select



32/349



Summary

When you select the Clock Generator(DCM) option, System Generator automaticallyinfers and instantiates a DCM without further manual intervention. You do not have to setattributes or specify DCM clock outputs. Clock rates are determined by the samemethodology when you use the Clock Enables option. You should expect minimal clockskew when selecting the Clock Generator (DCM) option compared to the Clock Enables

option.

Tutorial Example: Using the Expose Clock Ports Option

The following step-by-step example will show you how to select the Expose Clock Portsoption, netlist the HDL design, implement the design in ISE, simulate the design, thenexamine the files and reports to verify the design.

The expose_clock_ports_case1 design example is located at the following pathname/examples/clocking_options/expose_clock_ports_case1/expose_clock_ports_case1.mdl

1. Open the model in MATLAB and observe the following blocks:

• Addressable Shift Register (ASR): used to implement the input delay buffer. The

address port runs n times faster than the data port, where n is the number of the filtertaps (5 for this example)

• Coefficient ROM: used to store the filter coefficients

• Counter: used to generate addresses for the ROM and ASR

• Comparator: used to generate the reset and enable signals

• MAC Engine: used as a Multiply-Accumulator operator for the filter



33/349



2. Double-click on the System Generator token to bring up the following dialog box:

As shown above, select Expose Clock Ports, then click Generate. After a few moments, asub-directory named hdl_netlist is created in the current working directory containing thegenerated files.

3. Launch ISE, then load the ISE project at pathname./hdl_netlist/expose_clock_ports_case1_mcw.ise

4. Under the Project Navigator Processes tab, double-click on Implement Design.

5. From the Project Navigator Sources tab, do the following:

a. double-click on the file expost_clock_ports_case1_mcw.vhd , then scrolldown to view the entity named expose_clock_ports_mcw, as shown below:

b. Observe that System Generator infers the clocks based on the different rates in thedesign and brings the clock ports to the top-level wrapper. Since this designcontains two clock rates, clocks clk_1 and clk_5 are pulled to the top-levelwrapper. This will allow you to directly drive the multiple synchronous clocksfrom outside the System Generator design.

c. Close the VHDL file.

Next you want to perform a behavior simulation using the ModelSim.



34/349



6. As shown below, move to the Sources for dialog box in the Sources window, thenselect Behavioral Simulation

Note: System Generator automatically creates the top-wrapper VHDL testbench, script file andinput/output stimulus data files. The Processes tab changes and displays according to theSources type being selected.

7. Simulate the design, as shown above, by double-click on Simulate Behavioral Modelin the Processes window

8. After the simulation is finished, you should be able to observe the simulationwaveforms as shown in the figure below:

Summary

When you select the Expose Clock Ports option, System Generator automatically infers thecorrect clocks from the design rates and exposes the clock ports in the top-level wrapper.The clock rates are determined by the same methodology when you use the Clock Enables option. You can now drive the exposed clock ports from an external synchronous clocksource.

2. Double Click

1. Select



35/349



Synchronization Mechanisms

System Generator does not make implicit synchronization mechanisms available. Instead,synchronization is the responsibility of the designer, and must be done explicitly.

Valid Ports

System Generator provides several blocks (in particular, a FIFO) that can be used forsynchronization. Several blocks provide input (respectively, output) ports that specifywhen an input (resp., output) sample is valid. Such ports can be chained, affording aprimitive form of flow control. Blocks with such ports include the FFT, FIR, and Viterbi.

Indeterminate Data

Indeterminate values are common in many hardware simulation environments. Often theyare called “don’t cares” or “Xs”. In particular, values in System Generator simulations can be indeterminate. A dual port memory block, for example, can produce indeterminateresults if both ports of the memory attempt to write the same address simultaneously.What actually happens in hardware depends upon effectively random implementationdetails that determine which port sees the clock edge first. Allowing values to become

indeterminate gives the system designer greater flexibility. Continuing the example, thereis nothing wrong with writing to memory in an indeterminate fashion if subsequentprocessing does not rely on the indeterminate result.

HDL modules that are brought into the simulation through HDL co-simulation are acommon source for indeterminate data samples. System Generator presents indeterminatevalues to the inputs of an HDL co-simulating module as the standard logic vector 'XXX . .. XX'.

Indeterminate values that drive a Gateway Out become what are called NaNs. (NaNabbreviates “not a number”.) In a Simulink scope, NaN values are not plotted. Conversely,NaNs that drive a Gateway In become indeterminate values. System Generator providesan Indeterminate Probe block that allows for the detection of indeterminate values. Thisprobe cannot be translated into hardware.

In System Generator, any arithmetic signal can be indeterminate, but Boolean signalscannot be. If a simulation reaches a condition that would force a Boolean to becomeindeterminate, the simulation is halted and an error is reported. Many Xilinx blocks havecontrol ports that only allow Boolean signals as inputs. The rule concerning indeterminateBooleans means that such blocks never see an indeterminate on a control port

A UFix_1_0 is a type that is equivalent to Boolean except for the above restrictionconcerning indeterminate data.

Block Masks and Parameter Passing

The same scoping and parameter passing rules that apply to ordinary Simulink blocks

apply to System Generator blocks. Consequently, blocks in the Xilinx Blockset can beparameterized using MATLAB variables and expressions. This capability makes possiblehighly parametric designs that take advantage of the expressive and computational powerof the MATLAB language.

Block Masks

In Simulink, blocks are parameterized through a mechanism called masking. In essence, a block can be assigned mask variables whose values can be specified by a user through dialog



36/349



box prompts or can be calculated in mask initialization commands. Variables are stored ina mask workspace. A mask workspace is local to the blocks under the mask and cannot beaccessed by external blocks.

Note: It is possible for a mask to access global variables and variables in the base workspace. Toaccess a base workspace variable, use the MATLAB evalin function. For more information on theMATLAB and Simulink scoping rules, refer to the manuals titled Using MATLAB and Using Simulink

from The Mathworks, Inc .

Parameter Passing

It is often desirable to pass variables to blocks inside a masked subsystem. Doing so allowsthe block’s configuration to be determined by parameters on the enclosing subsystem. Thistechnique can be applied to parameters on blocks in the Xilinx blockset whose values areset using a listbox, radio button, or checkbox. For example, when building a subsystemthat consists of a multiply and accumulate block, you can create a parameter on thesubsystem that allows you to specify whether to truncate or round the result. Thisparameter will be called trunc_round as shown in the figure below.

As shown below, in the parameter editing dialog for the accumulator and multiplier blocks, there are radio buttons that allow either the truncate or round option to be selected.

In order to use a parameter rather than the radio button selection, right click on the radio button and select: “Define With Expression”. A MATLAB expression can then be used asthe parameter setting. In the example below, the trunc_round parameter from the



37/349



subsystem mask can be used in both the accumulator and multiply blocks so that each block will use the same setting from the mask variable on the subsystem.



38/349



Resource Estimation

System Generator supplies tools that estimate the FPGA hardware resources needed toimplement a design. Estimates include numbers of slices, lookup tables, flip-flops, blockmemories, embedded multipliers, I/O blocks and tristate buffers. These estimates make iteasy to determine how design choices affect hardware requirements. To estimate theresources needed for a subsystem, drag a Resource Estimator block into the subsystem,double-click on the estimator, and press the Estimate button.

Automatic Code Generation

System Generator automatically compiles designs into low-level representations. Theways in which System Generator compiles a model can vary, and depend on settings in theSystem Generator block. In addition to producing HDL descriptions of hardware, the toolgenerates auxiliary files. Some files (e.g., project files, constraints files) assist downstreamtools, while others (e.g., VHDL testbench) are used for design verification.

Compiling and Simulating Usingthe System Generator Block

Describes how to use the System Generator block tocompile designs into equivalent low-level HDL.

Compilation Results Describes the low-level files System Generatorproduces when HDL Netlist is selected on the SystemGenerator block and Generate is pushed.

HDL Testbench Describes the VHDL testbench that System Generatorcan produce.



39/349


Automatic Code GenerationR

Compiling and Simulating Using the System Generator Block

System Generator automatically compiles designs into low-level representations. Designsare compiled and simulated using the System Generator block. This topic describes how touse the block.

Before a System Generator design can be simulated or translated into hardware, the design

must include a System Generator block. When creating a new design, it is a good idea toadd a System Generator block immediately. The System Generator block is a member ofthe Xilinx Blockset’s Basic Elements and Tools libraries. As with all Xilinx blocks, theSystem Generator block can also be found in the Index library.

A design must contain at least one System Generator block, but can contain several SystemGenerator blocks on different levels (one per level). A System Generator block that isunderneath another in the hierarchy is a slave; one that is not a slave is a master. The scopeof a System Generator block consists of the level of hierarchy into which it is embeddedand all subsystems below that level. Certain parameters (e.g. Simulink System Period)can be specified only in a master.

Once a System Generator block is added, it is possible to specify how code generation andsimulation should be handled. The block’s dialog box is shown below:



40/349



Compilation Type and the Generate Button

Pressing the Generate button instructs System Generator to compile a portion of thedesign into equivalent low-level results. The portion that is compiled is the sub-tree whoseroot is the subsystem containing the block. (To compile the entire design, use a SystemGenerator block placed at the top of the design.) The compilation type (underCompilation) specifies the type of result that should be produced. The possible types are

• Two types of Netlists, HDL Netlist and NGC Netlist

• Bitstream - produces an FPGA configuration bitstream that is ready to run in ahardware FPGA platform

• EDK Export Tool - for exporting to the Xilinx Embedded Development Kit variousvarieties of hardware co-simulation, and

• Timing Analysis - a report on the timing of the design.

HDL Netlist is the type used most often. In this case, the result is a collection of HDL andEDIF files, and a few auxiliary files that simplify downstream processing. The collection isready to be processed by a synthesis tool (e.g., XST), and then fed to the Xilinx physicaldesign tools (i.e., ngdbuild, map, par, and bitgen)

system generator for dsp

Documents