DOCSLIB.ORG

Lab 1 Document

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Lab 1 Document CPRE 488X LAB01 Lab Conventions The following conventions are used throughout the labs: Location of additional information or tips. An important error or step that you should be aware of. A reference to a chapter in the book. Lab Overview In this lab you will be introduced to the hardware and tools you will be using the rest of the semester. We will put together a basic system and run some demonstrations on the development board. There is A LOT of information in this lab. Please stick with it, as most of this lab is a step-by-step walkthrough with lots of screenshots and pictures. We hope that you will use this lab as a reference for later labs if your forget some steps, since some processes involve quite a few. During the semester you will be keeping a “lab notebook,” writing down important information from each of the labs. You can feel free to keep your own notes in the notebook as well. Some of your lab notebook entries will be required and graded. For this lab, make a list of the errors you may encounter while using the board and log them in your lab notebook. This will be graded. Hardware We will be using a development board from Digilent, Inc and Xilinx called the XUP Virtex-II Development System. This board has a Virtex-II Pro series FPGA, which consists of reconfigurable FPGA “fabric” and two PowerPC firm-cores. The FPGA fabric can be configured to represent any desired digital logic at the low level. When you combine many of these small FPGA pieces together, you can build very complex hardware. The two PowerPC cores connect to the reconfigurable fabric and provide a 1 powerful processor capable of running at up to 300 MHz. There are also several “off- chip” devices, meaning they are not included in the FPGA chip itself, but on the board and connected to the FPGA. These include some DDR RAM, an RS232 (serial) port, an ethernet port, a VGA port, a Compact Flash reader/writer, and several other peripherals. We will use most of these during the course of the labs. A diagram taken from Digilent’s reference manual for the board is shown below. You can refer to Digilent’s website, http://www.digilentinc.com , to get the user manual and look at example designs. Power connector and on/off switch USB programmer connection Programming source selection User-programmable / general-purpose LEDs, DIP switches, and push buttons Highlighted on the picture are the power connector and on/off switch in the upper-left, the general-purpose DIP switches and LEDs in the bottom-center, the programming source selection DIP switches in lower-right, and the programming USB connector in the upper-right. These are the basic items that will be used during this lab. 2 Take a second now to make sure that the programming source selection DIP switches (the GREEN circle above) are set in the following way: the upper set of three DIP switches should be all UP, and the lower set of two DIP switches should be all DOWN, using the orientation given in the picture. You may have trouble getting the board to program if this is not done – specifically the DONE LED, located just to the right of the DIP switches, will not light. The DONE LED lights only when the board has been programmed with a valid programming bitstream. Software The software we will be using during the labs comes from several vendors, but our main tools will be Xilinx tools. The IDE for developing systems with Virtex-II Pro devices (FPGA devices having both FPGA fabric and PowerPC cores) is called Xilinx Platform Studio (XPS) . This program shows your projects at the component-level. Processor cores are used to run the software portions of your design, while FPGA hardware cores create the hardware portion of your design. When intermixed, we create a fully- functioning hardware/software system. Several other tools, like XMD and the software debugger (GDB) will be mentioned below for completeness but discussed in more detail when it becomes necessary. A standard use-case for the tool set is given below. 1) Choose the hardware cores you will be using and add them to your design. 2) Write the software portions of the system using XPS. 3) Synthesize and compile the hardware and software portions of your system, respectively. 4) Download the hardware bitstream to the development board. 5) Download the software to the development board (if necessary) using XMD. 6) Run software 7) If design is not correct, debug using GDB or ChipScope, and possibly revisit steps 1 or 2 XPS Base System Builder Open Xilinx® Platform Studio (XPS) . Select the Base System Builder Wizard. 3 Click OK . Browse to a project path that you will use for your labs. Currently you cannot work from a network drive in XPS. Therefore you will have to work from a local directory and then transfer your files before you leave the lab. Some of the projects can be fairly large (60- 90MB) so it is recommended that you use your university account space, (which will be mapped automatically if your university password and your engineering password is the same), or a personal USB drive. The directory you need use is: “C:\temp\<your_username>\<the_lab_or_project>\system.xmp ”. 1. The path cannot contain spaces! 2. It is important to make sure you put all your files in the C:\temp\<your username> directory while using them and DELETE them when finished for the day (save them to your U: or V: drives). This will prevent you from creating files that other users cannot delete. 3. It is important to specify the name your project as “system.xmp”, otherwise some filenames may not match the labs - especially the simulation we will be doing later in this lab. 4 Then check “ User Peripheral Repository search…” and Browse to the library directory for the XUP V2Pro board “ C:\EDK\xup_2vp30 ”. Click OK . 5 In Base System Builder, choose “ I would like to create a new design ”. Click Next . 6 Choose “ I would like to create a system for the following development board ”. Board Vendor: Xilinx® Board Name: XUP Virtex-II Pro Development System Board Revision: C Click Next . 7 Choose “ PowerPC ” for our processor design. Click Next . 8 For the next screen, we set the processor clock frequency, bus frequency, and JTAG interface. We’ll use the default settings. Click Next . 9 The next window allows you to specify which hardware you will be using on the board. For future designs using base system builder you will want to decide all of the hardware you will need beforehand and add them using this screen. Everything added with these screens can be added manually later in the design, but it is much easier to specify the peripherals now. For this system we will be using: o RS232 UART at 9600 baud (** Don’t forget this!) o LEDs (4-bits because there are 4 user-programmable LEDs on the board) o Push Buttons (5-bits for up, down, left, right, and enter) o DDR RAM (256 MB) Select hardware to match the following screens: 10 11 12 Choose the amount of BRAM (Block RAM) you will be using in your design. This is a limited amount of very fast memory which is built into the FPGA (on-chip). For most of your systems this BRAM is not large enough to hold the actual program (max size is 128 kB), but instead it is used to boot the PowerPC processor and direct it to start executing the program stored in the DDR RAM. At least one BRAM is required by all designs using a PowerPC processor. Set the size of the included BRAM on the next screen to 64 kB. 13 In the next screen we set the device which will act as STDIN and STDOUT, the two standard interfaces in C/C++ to which all printf() commands write. We will also let Base System Builder generate a sample application. If you do not correctly associate STDIN and STDOUT with a device, you will receive errors when compiling code using printf() statements or any other statement which attempts to write or read from the input or output. This can be changed later from the “Software Settings Base System Builder will provide some test code for you if you want, however we will not be using this feature for our introductory lab. If your system is not working and you think that bad hardware is to blame, you can run the “golden configuration” which is built into each Digilent board. Set the two lower Programming Source DIP switches to the UP position, connect to the serial port using TeraTerm (described later in this lab) at 9600 baud, and reset the power on the board to run the golden configuration. 14 The next screen allows you to review the system being built. Click Generate . 15 Once finished, you should get the “Congratulations” screen. Click Finish to load the generated project into XPS. 16 Select “ Start Using Platform Studio ”. Click OK . 17 Now, you should have the system design loaded. Along the left side is a tree-list of your system. Each entry is a hardware element that is included in your design. We will learn how to add hardware cores in a later lab. On the left side of the screen Presentation Area - Source Code - System Information System HW and Application SW tabs Output - Compilation/Synthesis results - Project information For now, click the “ Applications ” tab (in RED ) to switch to the applications view.
Load more

Recommended publications
  • Efficient Checker Processor Design
    Efficient Checker Processor Design Saugata Chatterjee, Chris Weaver, and Todd Austin Electrical Engineering and Computer Science Department University of Michigan {saugatac,chriswea,austin}@eecs.umich.edu Abstract system works to increase test space coverage by proving a design is correct, either through model equivalence or assertion. The approach is significantly more efficient The design and implementation of a modern micro- than simulation-based testing as a single proof can ver- processor creates many reliability challenges. Design- ify correctness over large portions of a design’s state ers must verify the correctness of large complex systems space. However, complex modern pipelines with impre- and construct implementations that work reliably in var- cise state management, out-of-order execution, and ied (and occasionally adverse) operating conditions. In aggressive speculation are too stateful or incomprehen- our previous work, we proposed a solution to these sible to permit complete formal verification. problems by adding a simple, easily verifiable checker To further complicate verification, new reliability processor at pipeline retirement. Performance analyses challenges are materializing in deep submicron fabrica- of our initial design were promising, overall slowdowns tion technologies (i.e. process technologies with mini- due to checker processor hazards were less than 3%. mum feature sizes below 0.25um). Finer feature sizes However, slowdowns for some outlier programs were are generally characterized by increased complexity, larger. more exposure to noise-related faults, and interference In this paper, we examine closely the operation of the from single event radiation (SER). It appears the current checker processor. We identify the specific reasons why advances in verification (e.g., formal verification, the initial design works well for some programs, but model-based test generation) are not keeping pace with slows others.
    [Show full text]
  • Three-Dimensional Integrated Circuit Design: EDA, Design And
    Integrated Circuits and Systems Series Editor Anantha Chandrakasan, Massachusetts Institute of Technology Cambridge, Massachusetts For other titles published in this series, go to http://www.springer.com/series/7236 Yuan Xie · Jason Cong · Sachin Sapatnekar Editors Three-Dimensional Integrated Circuit Design EDA, Design and Microarchitectures 123 Editors Yuan Xie Jason Cong Department of Computer Science and Department of Computer Science Engineering University of California, Los Angeles Pennsylvania State University [email protected] [email protected] Sachin Sapatnekar Department of Electrical and Computer Engineering University of Minnesota [email protected] ISBN 978-1-4419-0783-7 e-ISBN 978-1-4419-0784-4 DOI 10.1007/978-1-4419-0784-4 Springer New York Dordrecht Heidelberg London Library of Congress Control Number: 2009939282 © Springer Science+Business Media, LLC 2010 All rights reserved. This work may not be translated or copied in whole or in part without the written permission of the publisher (Springer Science+Business Media, LLC, 233 Spring Street, New York, NY 10013, USA), except for brief excerpts in connection with reviews or scholarly analysis. Use in connection with any form of information storage and retrieval, electronic adaptation, computer software, or by similar or dissimilar methodology now known or hereafter developed is forbidden. The use in this publication of trade names, trademarks, service marks, and similar terms, even if they are not identified as such, is not to be taken as an expression of opinion as to whether or not they are subject to proprietary rights. Printed on acid-free paper Springer is part of Springer Science+Business Media (www.springer.com) Foreword We live in a time of great change.
    [Show full text]
  • Understanding Performance Numbers in Integrated Circuit Design Oprecomp Summer School 2019, Perugia Italy 5 September 2019
    Understanding performance numbers in Integrated Circuit Design Oprecomp summer school 2019, Perugia Italy 5 September 2019 Frank K. G¨urkaynak [email protected] Integrated Systems Laboratory Introduction Cost Design Flow Area Speed Area/Speed Trade-offs Power Conclusions 2/74 Who Am I? Born in Istanbul, Turkey Studied and worked at: Istanbul Technical University, Istanbul, Turkey EPFL, Lausanne, Switzerland Worcester Polytechnic Institute, Worcester MA, USA Since 2008: Integrated Systems Laboratory, ETH Zurich Director, Microelectronics Design Center Senior Scientist, group of Prof. Luca Benini Interests: Digital Integrated Circuits Cryptographic Hardware Design Design Flows for Digital Design Processor Design Open Source Hardware Integrated Systems Laboratory Introduction Cost Design Flow Area Speed Area/Speed Trade-offs Power Conclusions 3/74 What Will We Discuss Today? Introduction Cost Structure of Integrated Circuits (ICs) Measuring performance of ICs Why is it difficult? EDA tools should give us a number Area How do people report area? Is that fair? Speed How fast does my circuit actually work? Power These days much more important, but also much harder to get right Integrated Systems Laboratory The performance establishes the solution space Finally the cost sets a limit to what is possible Introduction Cost Design Flow Area Speed Area/Speed Trade-offs Power Conclusions 4/74 System Design Requirements System Requirements Functionality Functionality determines what the system will do Integrated Systems Laboratory Finally the cost sets a limit
    [Show full text]
  • CSE 141L: Design Your Own Processor What You'll
    CSE 141L: Design your own processor What you’ll do: - learn Xilinx toolflow - learn Verilog language - propose new ISA - implement it - optimize it (for FPGA) - compete with other teams Grading 15% lab participation – webboard 85% various parts of the labs CSE 141L: Design your own processor Teams - two people - pick someone with similar goals - you keep them to the end of the class - more on the class website: http://www.cse.ucsd.edu/classes/sp08/cse141L/ Course Staff: 141L Instructor: Michael Taylor Email: [email protected] Office Hours: EBU 3b 4110 Tuesday 11:30-12:20 TA: Saturnino Email: [email protected] ebu 3b b260 Lab Hours: TBA (141 TA: Kwangyoon) Æ occasional cameos in 141L http://www-cse.ucsd.edu/classes/sp08/cse141L/ Class Introductions Stand up & tell us: -Name - How long until graduation - What you want to do when you “hit the big time” - What kind of thing you find intellectually interesting What is an FPGA? Next time: (Tuesday) Start working on Xilinx assignment (due next Tuesday) - should be posted Sat will give a tutorial on Verilog today Check the website regularly for updates: http://www.cse.ucsd.edu/classes/sp08/cse141L/ CSE 141: 0 Computer Architecture Professor: Michael Taylor UCSD Department of Computer Science & Engineering RF http://www.cse.ucsd.edu/classes/sp08/cse141/ Computer Architecture from 10,000 feet foo(int x) Class of { .. } application Physics Computer Architecture from 10,000 feet foo(int x) Class of { .. } application An impossibly large gap! In the olden days: “In 1942, just after the United States entered World War II, hundreds of women were employed around the country as Physics computers...” (source: IEEE) The Great Battles in Computer Architecture Are About How to Refine the Abstraction Layers foo(int x) { .
    [Show full text]
  • Processor Architecture Design Using 3D Integration Technology
    Processor Architecture Design Using 3D Integration Technology Yuan Xie Pennsylvania State University Computer Science and Engineering Department University Park, PA, 16802, USA [email protected] Abstract (4)Smaller form factor, which results in higher pack- ing density and smaller footprint due to the addition of The emerging three-dimensional (3D) chip architec- a third dimension to the conventional two dimensional tures, with their intrinsic capability of reducing the wire layout, and potentially results in a lower cost design. length, is one of the promising solutions to mitigate This tutorial paper first presents the background on the interconnect problem in modern microprocessor de- 3D integration technology, and then reviews various ap- signs. 3D memory stacking also enables much higher proaches to design future 3D microprocessors, which memory bandwidth for future chip-multiprocessor de- leverage the benefits of fast latency, higher bandwidth, sign, mitigating the “memory wall” problem. In addi- and heterogeneous integration capability that are offered tion, heterogenous integration enabled by 3D technol- by 3D technology. The challenges for future 3D archi- ogy can also result in innovation designs for future mi- tecture design are also discussed in the last section. croprocessors. This paper serves as a survey of various approaches to design future 3D microprocessors, lever- 2. 3D Integration Technology aging the benefits of fast latency, higher bandwidth, and The 3D integration technologies [25,26] can be clas- heterogeneous integration capability that are offered by sified into one of the two following categories. (1) 3D technology. 1 Monolithic approach. This approach involves sequen- tial device process. The frontend processing (to build the 1.
    [Show full text]
  • Processor Design：System-On-Chip Computing For
    Processor Design Processor Design System-on-Chip Computing for ASICs and FPGAs Edited by Jari Nurmi Tampere University of Technology Finland A C.I.P. Catalogue record for this book is available from the Library of Congress. ISBN 978-1-4020-5529-4 (HB) ISBN 978-1-4020-5530-0 (e-book) Published by Springer, P.O. Box 17, 3300 AA Dordrecht, The Netherlands. www.springer.com Printed on acid-free paper All Rights Reserved © 2007 Springer No part of this work may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, photocopying, microfilming, recording or otherwise, without written permission from the Publisher, with the exception of any material supplied specifically for the purpose of being entered and executed on a computer system, for exclusive use by the purchaser of the work. To Pirjo, Lauri, Eero, and Santeri Preface When I started my computing career by programming a PDP-11 computer as a freshman in the university in early 1980s, I could not have dreamed that one day I’d be able to design a processor. At that time, the freshmen were only allowed to use PDP. Next year I was given the permission to use the famous brand-new VAX-780 computer. Also, my new roommate at the dorm had got one of the first personal computers, a Commodore-64 which we started to explore together. Again, I could not have imagined that hundreds of times the processing power will be available in an everyday embedded device just a quarter of century later.
    [Show full text]
  • Design Software & Development Kit Selector Guide
    ® Design Software & Development Kit Selector Guide April 2004 Table of Contents Quartus II Design Software Leadership ................................ page 2 Selecting a Design Software Product ................................... page 5 System Design Technology Recommended System Configurations ................................. page 8 Altera’s Quartus II software is the industry’s only design Altera Programming Hardware........................................... page 8 environment that supports Intellectual Property (IP)-based Altera Development Kits................................................... page 10 system design—including complete and automated system definition and implementation—without requiring lower- Third-Party Solutions........................................................ page 10 level hardware description language (HDL) or schematics. This capability enables designers to turn their concepts into working systems in minutes. The Quartus II system design tools include: Quartus II Design Software SOPC Builder: A system development tool that automates Leadership adding, parameterizing, and linking IP cores—including Altera’s Quartus® II software leads the embedded processors, co-processors, peripherals, memories, industry as the most comprehensive and user-defined logic—without requiring lower-level HDL environment available for FPGA, CPLD, or schematics. (See Figure 1.) and structured ASIC designs, delivering DSP Builder: Shortens digital signal processing (DSP) design unmatched performance, efficiency, and ease-of-use.
    [Show full text]
  • Physical Design of a 3D-Stacked Heterogeneous Multi-Core Processor
    Physical Design of a 3D-Stacked Heterogeneous Multi-Core Processor Randy Widialaksono, Rangeen Basu Roy Chowdhury, Zhenqian Zhang, Joshua Schabel, Steve Lipa, Eric Rotenberg, W. Rhett Davis, Paul Franzon Department of Electrical and Computer Engineering North Carolina State University, Raleigh, NC, USA frhwidial, rbasuro, zzhang18, jcledfo3, slipa, ericro, wdavis, [email protected] Abstract—With the end of Dennard scaling, three dimensional TSV (I/O pads) stacking has emerged as a promising integration technique to Bulk improve microprocessor performance. In this paper we present Active First metal layer a 3D-SIC physical design methodology for a multi-core processor using commercial off-the-shelf tools. We explain the various Metal High-performance core flows involved and present the lessons learned during the design Last metal layer process. The logic dies were fabricated with GlobalFoundries Face-to-face micro-bumps 130 nm process and were stacked using the Ziptronix face-to- Metal Low-power core face (F2F) bonding technology. We also present a comparative analysis which highlights the benefits of 3D integration. Results indicate an order of magnitude decrease in wirelengths for critical Active inter-core components in the 3D implementation compared to 2D Bulk implementations. I. INTRODUCTION Fig. 1. Cross-section of the face-to-face bonded 3D-IC stack. As performance benefits from technology scaling slows The primary advantage of 3D-stacking comes from reduced down, computer architects are looking at various architectural wirelengths leading to an improvement in routability and signal techniques to maintain the trend of performance improvement, delays. On the other hand, going 3D also increases design while meeting the power budget.
    [Show full text]
  • Modern Processor Design: Fundamentals of Superscalar
    Fundamentals of Superscalar Processors John Paul Shen Intel Corporation Mikko H. Lipasti University of Wisconsin WAVELAND PRESS, INC. Long Grove, Illinois To Our parents: Paul and Sue Shen Tarja and Simo Lipasti Our spouses: Amy C. Shen Erica Ann Lipasti Our children: Priscilla S. Shen, Rachael S. Shen, and Valentia C. Shen Emma Kristiina Lipasti and Elias Joel Lipasti For information about this book, contact: Waveland Press, Inc. 4180 IL Route 83, Suite 101 Long Grove, IL 60047-9580 (847) 634-0081 info @ waveland.com www.waveland.com Copyright © 2005 by John Paul Shen and Mikko H. Lipasti 2013 reissued by Waveland Press, Inc. 10-digit ISBN 1-4786-0783-1 13-digit ISBN 978-1-4786-0783-0 All rights reserved. No part of this book may be reproduced, stored in a retrieval system, or transmitted in any form or by any means without permission in writing from the publisher. Printed in the United States of America 7 6 5 4 3 2 1 Table of Contents PrefaceAbout the Authors x ix 1 Processor Design 1 1.1 The Evolution of Microprocessors 2 1.21.2.1 Instruction Digital Set Systems Processor Design Design 44 1.2.2 Architecture,Realization Implementation, and 5 1.2.3 Instruction Set Architecture 6 1.2.4 Dynamic-Static Interface 8 1.3 Principles of Processor Performance 10 1.3.1 Processor Performance Equation 10 1.3.2 Processor Performance Optimizations 11 1.3.3 Performance Evaluation Method 13 1.4 Instruction-Level Parallel Processing 16 1.4.1 From Scalar to Superscalar 16 1.4.2 Limits of Instruction-Level Parallelism 24 1.51.4.3 Machines Summary for Instruction-Level
    [Show full text]
  • Designing Digital Circuits a Modern Approach
    Designing Digital Circuits a modern approach Jonathan Turner 2 Contents I First Half 5 1 Introduction to Designing Digital Circuits 7 1.1 Getting Started . .7 1.2 Gates and Flip Flops . .9 1.3 How are Digital Circuits Designed? . 10 1.4 Programmable Processors . 12 1.5 Prototyping Digital Circuits . 15 2 First Steps 17 2.1 A Simple Binary Calculator . 17 2.2 Representing Numbers in Digital Circuits . 21 2.3 Logic Equations and Circuits . 24 3 Designing Combinational Circuits With VHDL 33 3.1 The entity and architecture . 34 3.2 Signal Assignments . 39 3.3 Processes and if-then-else . 43 4 Computer-Aided Design 51 4.1 Overview of CAD Design Flow . 51 4.2 Starting a New Project . 54 4.3 Simulating a Circuit Module . 61 4.4 Preparing to Test on a Prototype Board . 66 4.5 Simulating the Prototype Circuit . 69 3 4 CONTENTS 4.6 Testing the Prototype Circuit . 70 5 More VHDL Language Features 77 5.1 Symbolic constants . 78 5.2 For and case statements . 81 5.3 Synchronous and Asynchronous Assignments . 86 5.4 Structural VHDL . 89 6 Building Blocks of Digital Circuits 93 6.1 Logic Gates as Electronic Components . 93 6.2 Storage Elements . 98 6.3 Larger Building Blocks . 100 6.4 Lookup Tables and FPGAs . 105 7 Sequential Circuits 109 7.1 A Fair Arbiter Circuit . 110 7.2 Garage Door Opener . 118 8 State Machines with Data 127 8.1 Pulse Counter . 127 8.2 Debouncer . 134 8.3 Knob Interface . 137 8.4 Two Speed Garage Door Opener .
    [Show full text]
  • Academic Definitions
    School of Graduate studies calendar Fall 2009 ACADEMIC DEFINITIONS Prerequisite: Student must pass Course A before taking Course B. Corequisite: Student must take Course A prior to or concurrently with Course B. Course Credits: One course credit is equivalent to a one-term course taken for one term. It has a course weight of 1.00 for the purpose of GPA calculations. One module is equivalent to half of a one-term course and is normally taught in a 6 week session. Antirequisite: Students may not enrol in a course which lists, as an Antirequisite, one which they are also taking or in which they have already obtained standing. Pass/Fail Courses: Are not included in GPA calculations, but are included in promotion status. Milestone: a Milestone is a component of a program which is required for graduation, but is not offered in a traditional in-class course framework. Examples are theses, major research papers, major projects, comprehensive and candidacy examinations, dissertations, and WHIMIS certification. _________________________________________________________________________________________________ The following course descriptions are a guide to courses offered through the program from time to time. Not all courses will be offered every year. Courses are offered subject to faculty availability and are subject to change without notice. Courses followed by a second course number in brackets indicate that the course is offered through a joint program with another university. For example: CC8900 (CMCT 6000 3.0) Core Issues in Cultural Studies, indicates that the bracketed number is used at York University in the joint Ryerson/York Communication and Culture Program. Graduate Calendar Fall 2009 AEROSPACE ENGINEERING CURRICULUM Master of Applied Science DEGREE REQUIREMENTS Master's Thesis Five Elective credits 5 Master of Engineering DEGREE REQUIREMENTS Master's Project* Eight Elective credits 8 *students may apply to substitute 2 courses for the project.
    [Show full text]
  • Ultrafast Design Methodology Guide for the Vivado Design Suite
    See all versions of this document UltraFast Design Methodology Guide for the Vivado Design Suite UG949 (v2019.2) December 6, 2019 Revision History Revision History The following table shows the revision history for this document. Section Revision Summary 12/06/2019 Version 2019.2 Thermal Solution Considerations Added new section. Performance/Power Trade-Off for Block RAMs Updated examples. Using the CLOCK_LOW_FANOUT Constraint Updated examples. Using Incremental Implementation Flows Added information about automatic incremental implementation mode. Incremental Directives and Target WNS Added new section. Compile Time Considerations Added new section. Assessing the Maximum Frequency of the Design Added new section. Reducing Clock Delay in UltraScale and UltraScale+ Devices Added new section. Disable LUT Combining Updated example. ML Strategies Added new section. Using Incremental Implementation Added information about automatic incremental implementation mode. Using VIO Cores Added new section. 06/26/2019 Version 2019.1 About the UltraFast Design Methodology Added reference to UltraFast Design Methodology Timing Closure Quick Reference Guide (UG1292). SLR Utilization Considerations Updated example. Auto-Pipelining Considerations Added new section. Using Auto-Pipelining on Custom Interfaces Updated to show the hierarchy recommendation and USER_SLR_ASSIGNMENT constraints. Synchronous CDC Added note about safe timing between BUFGCE_DIV clocks. Incremental Synthesis Flows Added new section. Using Incremental Implementation Flows Added information on automatic incremental implementation. Optimization Analysis Added -debug_log option. Methodology DRCs with Impact on Timing Closure Added Severity column and TIMING-44 and TIMING-45 checks. Methodology DRCs with Impact on Signoff Quality Added Severity column and TIMING-46 check. Optimizing Paths with Dedicated Blocks and Macro Added optimization options. Primitives Interconnect Congestion Level in the Device Window Added enhanced reporting information.
    [Show full text]