DOCSLIB.ORG

Vivado Design Suite User Guide:Logic Simulation

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Vivado Design Suite User Guide:Logic Simulation See all versions of this document Vivado Design Suite User Guide: Logic Simulation UG900 (v2020.1) June 3, 2020 Revision History Revision History The following table shows the revision history for this document. Section Revision Summary 06/03/2020 Version 2020.1 Chapter 3: Simulating with Third-Party Simulators Added table 8 and table 9 General Updates Updated Using Simulation Settings in chapter 2 General Updates Updated Object Windows in chapter 4 UG900 (v2020.1) June 3, 2020Send Feedback www.xilinx.com Vivado Design Suite User Guide: Logic Simulation 2 Table of Contents Revision History...............................................................................................................2 Chapter 1: Logic Simulation Overview............................................................... 7 Supported Simulators.................................................................................................................7 Simulation Flow .......................................................................................................................... 8 Language and Encryption Support ........................................................................................ 11 Chapter 2: Preparing for Simulation..................................................................12 Using Test Benches and Stimulus Files.................................................................................. 12 Pointing to the Simulator Install Location............................................................................. 13 Compiling Simulation Libraries............................................................................................... 14 Using Xilinx Simulation Libraries.............................................................................................19 Using Simulation Settings........................................................................................................ 28 Adding or Creating Simulation Source Files.......................................................................... 32 Generating a Netlist..................................................................................................................34 Chapter 3: Simulating with Third-Party Simulators................................. 37 Running Simulation Using Third Party Simulators with Vivado IDE................................... 39 Dumping SAIF for Power Analysis...........................................................................................42 Dumping VCD............................................................................................................................ 44 Simulating IP..............................................................................................................................45 Using a Custom DO File During an Integrated Simulation Run.......................................... 45 Running Third-Party Simulators in Batch Mode....................................................................48 Chapter 4: Simulating with Vivado Simulator..............................................49 Running the Vivado Simulator.................................................................................................49 Running Functional and Timing Simulation...........................................................................67 Saving Simulation Results........................................................................................................ 69 Distinguishing Between Multiple Simulation Runs...............................................................70 Closing a Simulation................................................................................................................. 70 Adding a Simulation Start-up Script File.................................................................................71 Viewing Simulation Messages................................................................................................. 72 Using the launch_simulation Command................................................................................ 73 UG900 (v2020.1) June 3, 2020Send Feedback www.xilinx.com Vivado Design Suite User Guide: Logic Simulation 3 Re-running the Simulation After Design Changes (relaunch).............................................74 Using the Saved Simulator User Interface Settings..............................................................75 Chapter 5: Analyzing Simulation Waveforms with Vivado Simulator...................................................................................................................... 77 Using Wave Configurations and Windows.............................................................................77 Opening a Previously Saved Simulation Run.........................................................................78 Understanding HDL Objects in Waveform Configurations .................................................79 Customizing the Waveform..................................................................................................... 82 Controlling the Waveform Display ......................................................................................... 88 Organizing Waveforms.............................................................................................................92 Analyzing Waveforms............................................................................................................... 94 Analyzing AXI Interface Transactions..................................................................................... 99 Chapter 6: Debugging a Design with Vivado Simulator....................... 114 Debugging at the Source Level............................................................................................. 114 Forcing Objects to Specific Values.........................................................................................118 Power Analysis Using Vivado Simulator............................................................................... 126 Using the report_drivers Tcl Command................................................................................128 Using the Value Change Dump Feature...............................................................................128 Using the log_wave Tcl Command........................................................................................ 129 Cross Probing Signals in the Object, Wave, and Text Editor Windows.............................131 Chapter 7: Simulating in Batch or Scripted Mode in Vivado Simulator.....................................................................................................................137 Exporting Simulation Files and Scripts................................................................................. 137 Running the Vivado Simulator in Batch Mode.....................................................................143 Elaborating and Generating a Design Snapshot, xelab......................................................145 Simulating the Design Snapshot, xsim.................................................................................156 Example of Running Vivado Simulator in Standalone Mode............................................. 159 Project File (.prj) Syntax..........................................................................................................160 Predefined Macros.................................................................................................................. 161 Library Mapping File (xsim.ini).............................................................................................. 161 Running Simulation Modes....................................................................................................162 Using Tcl Commands and Scripts .........................................................................................165 export_simulation ...................................................................................................................166 export_ip_user_files.................................................................................................................169 UG900 (v2020.1) June 3, 2020Send Feedback www.xilinx.com Vivado Design Suite User Guide: Logic Simulation 4 Appendix A: Compilation, Elaboration, Simulation, Netlist, and Advanced Options..................................................................................................171 Compilation Options...............................................................................................................171 Elaboration Options................................................................................................................ 174 Simulation Options................................................................................................................. 175 Netlist Options.........................................................................................................................178 Advanced Simulation Options............................................................................................... 178 Appendix B: SystemVerilog Support in Vivado Simulator................... 180 Targeting SystemVerilog for a Specific File..........................................................................180 Testbench Feature...................................................................................................................187 Appendix C: Universal Verification Methodology Support................. 196 Appendix D: VHDL
Load more

Recommended publications
  • A Full-System VM-HDL Co-Simulation Framework for Servers with Pcie
    A Full-System VM-HDL Co-Simulation Framework for Servers with PCIe-Connected FPGAs Shenghsun Cho, Mrunal Patel, Han Chen, Michael Ferdman, Peter Milder Stony Brook University ABSTRACT the most common connection choice, due to its wide availability in The need for high-performance and low-power acceleration tech- server systems. Today, the majority of FPGAs in data centers are nologies in servers is driving the adoption of PCIe-connected FPGAs communicating with the host system through PCIe [2, 12]. in datacenter environments. However, the co-development of the Unfortunately, developing applications for PCIe-connected application software, driver, and hardware HDL for server FPGA FPGAs is an extremely slow and painful process. It is challeng- platforms remains one of the fundamental challenges standing in ing to develop and debug the host software and the FPGA hardware the way of wide-scale adoption. The FPGA accelerator development designs at the same time. Moreover, the hardware designs running process is plagued by a lack of comprehensive full-system simu- on the FPGAs provide little to no visibility, and even small changes lation tools, unacceptably slow debug iteration times, and limited to the hardware require hours to go through FPGA synthesis and visibility into the software and hardware at the time of failure. place-and-route. The development process becomes even more diffi- In this work, we develop a framework that pairs a virtual ma- cult when operating system and device driver changes are required. chine and an HDL simulator to enable full-system co-simulation of Changes to any part of the system (the OS kernel, the loadable ker- a server system with a PCIe-connected FPGA.
    [Show full text]
  • Co-Emulation of Scan-Chain Based Designs Utilizing SCE-MI Infrastructure
    UNLV Theses, Dissertations, Professional Papers, and Capstones 5-1-2014 Co-Emulation of Scan-Chain Based Designs Utilizing SCE-MI Infrastructure Bill Jason Pidlaoan Tomas University of Nevada, Las Vegas Follow this and additional works at: https://digitalscholarship.unlv.edu/thesesdissertations Part of the Computer Engineering Commons, Computer Sciences Commons, and the Electrical and Computer Engineering Commons Repository Citation Tomas, Bill Jason Pidlaoan, "Co-Emulation of Scan-Chain Based Designs Utilizing SCE-MI Infrastructure" (2014). UNLV Theses, Dissertations, Professional Papers, and Capstones. 2152. http://dx.doi.org/10.34917/5836171 This Thesis is protected by copyright and/or related rights. It has been brought to you by Digital Scholarship@UNLV with permission from the rights-holder(s). You are free to use this Thesis in any way that is permitted by the copyright and related rights legislation that applies to your use. For other uses you need to obtain permission from the rights-holder(s) directly, unless additional rights are indicated by a Creative Commons license in the record and/ or on the work itself. This Thesis has been accepted for inclusion in UNLV Theses, Dissertations, Professional Papers, and Capstones by an authorized administrator of Digital Scholarship@UNLV. For more information, please contact [email protected]. CO-EMULATION OF SCAN-CHAIN BASED DESIGNS UTILIZING SCE-MI INFRASTRUCTURE By: Bill Jason Pidlaoan Tomas Bachelor‟s Degree of Electrical Engineering Auburn University 2011 A thesis submitted
    [Show full text]
  • Open Source Synthesis and Verification Tool for Fixed-To-Floating and Floating-To-Fixed Points Conversions
    Circuits and Systems, 2016, 7, 3874-3885 http://www.scirp.org/journal/cs ISSN Online: 2153-1293 ISSN Print: 2153-1285 Open Source Synthesis and Verification Tool for Fixed-to-Floating and Floating-to-Fixed Points Conversions Semih Aslan1, Ekram Mohammad1, Azim Hassan Salamy2 1Ingram School of Engineering, Electrical Engineering Texas State University, San Marcos, Texas, USA 2School of Engineering, Electrical Engineering University of St. Thomas, St. Paul, Minnesota, USA How to cite this paper: Aslan, S., Mo- Abstract hammad, E. and Salamy, A.H. (2016) Open Source Synthesis and Verification Tool for An open source high level synthesis fixed-to-floating and floating-to-fixed conver- Fixed-to-Floating and Floating-to-Fixed Points sion tool is presented for embedded design, communication systems, and signal Conversions. Circuits and Systems, 7, 3874- processing applications. Many systems use a fixed point number system. Fixed point 3885. http://dx.doi.org/10.4236/cs.2016.711323 numbers often need to be converted to floating point numbers for higher accuracy, dynamic range, fixed-length transmission limitations or end user requirements. A Received: May 18, 2016 similar conversion system is needed to convert floating point numbers to fixed point Accepted: May 30, 2016 numbers due to the advantages that fixed point numbers offer when compared with Published: September 23, 2016 floating point number systems, such as compact hardware, reduced verification time Copyright © 2016 by authors and and design effort. The latest embedded and SoC designs use both number systems Scientific Research Publishing Inc. together to improve accuracy or reduce required hardware in the same design.
    [Show full text]
  • Xilinx Vivado Design Suite User Guide: Release Notes, Installation, And
    Vivado Design Suite User Guide Release Notes, Installation, and Licensing UG973 (v2013.3) October 23, 2013 Notice of Disclaimer The information disclosed to you hereunder (the “Materials”) is provided solely for the selection and use of Xilinx products. To the maximum extent permitted by applicable law: (1) Materials are made available "AS IS" and with all faults, Xilinx hereby DISCLAIMS ALL WARRANTIES AND CONDITIONS, EXPRESS, IMPLIED, OR STATUTORY, INCLUDING BUT NOT LIMITED TO WARRANTIES OF MERCHANTABILITY, NON-INFRINGEMENT, OR FITNESS FOR ANY PARTICULAR PURPOSE; and (2) Xilinx shall not be liable (whether in contract or tort, including negligence, or under any other theory of liability) for any loss or damage of any kind or nature related to, arising under, or in connection with, the Materials (including your use of the Materials), including for any direct, indirect, special, incidental, or consequential loss or damage (including loss of data, profits, goodwill, or any type of loss or damage suffered as a result of any action brought by a third party) even if such damage or loss was reasonably foreseeable or Xilinx had been advised of the possibility of the same. Xilinx assumes no obligation to correct any errors contained in the Materials or to notify you of updates to the Materials or to product specifications. You may not reproduce, modify, distribute, or publicly display the Materials without prior written consent. Certain products are subject to the terms and conditions of the Limited Warranties which can be viewed at http://www.xilinx.com/warranty.htm; IP cores may be subject to warranty and support terms contained in a license issued to you by Xilinx.
    [Show full text]
  • Verification Methodology Minimum • Most Companies Can Justify at Most 1 Re-Spin for New Design Ming-Hwa Wang, Ph.D
    • Success on the first tapeout or reduce the number of re-spin to very Verification Methodology minimum • Most companies can justify at most 1 re-spin for new design Ming-Hwa Wang, Ph.D. (time-to-market/cost: 2 tapeouts) COEN 207 SoC (System-on-Chip) Verification • Most integrations of proven IPs can be done at the first tapeout Department of Computer Engineering • Shorten time to market Santa Clara University Responsibilities Topics Responsibilities and cooperation among 3 teams • Vision and goals • Architecture team responsibility • Strategy • has to make sure the model is a correct executable specification and • Verification environment covers all functionalities of the design • Verification plan and execution strategy • RTL design team responsibility • Automation • Doing RTL implementation according the model or the specifications • Resources • Verification team responsibility • Verify the RTL is the same as the model Vision and Goals model The definition of verification design verification • Verify the RTL implementation is the same as the intention (which is not the same as the golden model or the specifications) Level of Verification • Block-level verification, integration verification, chip-level verification, intension and system-level verification equivalent ? Design vs. Verification implementation • Separation of Design and Verification • Designers do verification on their own design tend to neglect/miss • Verification = infrastructure/methodology + product understanding + non-working cases, or misinterpret the specs monitoring
    [Show full text]
  • Vivado Design Suite User Guide: High-Level Synthesis (UG902)
    Vivado Design Suite User Guide High-Level Synthesis UG902 (v2018.3) December 20, 2018 Revision History Revision History The following table shows the revision history for this document. Section Revision Summary 12/20/2018 Version 2018.3 Schedule Viewer Updated information on the schedule viewer. Optimizing the Design Clarified information on dataflow and loops throughout section. C++ Arbitrary Precision Fixed-Point Types: Reference Added note on using header files. Information HLS Math Library Updated information on how hls_math.h is used. The HLS Math Library, Fixed-Point Math Functions Updated functions. HLS Video Library, HLS Video Functions Library Moved the HLS video library to the Xilinx GitHub (https:// github.com/Xilinx/xfopencv) HLS SQL Library, HLS SQL Library Functions Updated hls::db to hls::alg functions. System Calls Added information on using the __SYNTHESIS__ macro. Arrays Added information on array sizing behavior. Command Reference Updated commands. config_dataflow, config_rtl Added the option -disable_start_propagation Class Methods, Operators, and Data Members Added guidance on specifying data width. UG902 (v2018.3) December 20, 2018Send Feedback www.xilinx.com High-Level Synthesis 2 Table of Contents Revision History...............................................................................................................2 Chapter 1: High-Level Synthesis............................................................................ 5 High-Level Synthesis Benefits....................................................................................................5
    [Show full text]
  • Vivado Tutorial
    Lab Workbook Vivado Tutorial Vivado Tutorial Introduction This tutorial guides you through the design flow using Xilinx Vivado software to create a simple digital circuit using Verilog HDL. A typical design flow consists of creating model(s), creating user constraint file(s), creating a Vivado project, importing the created models, assigning created constraint file(s), optionally running behavioral simulation, synthesizing the design, implementing the design, generating the bitstream, and finally verifying the functionality in the hardware by downloading the generated bitstream file. You will go through the typical design flow targeting the Artix-100 based Nexys4 board. The typical design flow is shown below. The circled number indicates the corresponding step in this tutorial. Figure 1. A typical design flow Objectives After completing this tutorial, you will be able to: • Create a Vivado project sourcing HDL model(s) and targeting a specific FPGA device located on the Nexys4 board • Use the provided partially completed Xilinx Design Constraint (XDC) file to constrain some of the pin locations • Add additional constraints using the Tcl scripting feature of Vivado • Simulate the design using the XSim simulator • Synthesize and implement the design • Generate the bitstream • Configure the FPGA using the generated bitstream and verify the functionality • Go through the design flow in batch mode using the Tcl script Procedure This tutorial is broken into steps that consist of general overview statements providing information on the detailed instructions that follow. Follow these detailed instructions to progress through the tutorial. www.xilinx.com/university Nexys4 Vivado Tutorial-1 [email protected] © copyright 2013 Xilinx Vivado Tutorial Lab Workbook Design Description The design consists of some inputs directly connected to the corresponding output LEDs.
    [Show full text]
  • Xilinx Vivado Design Suite 7 Series FPGA and Zynq-7000 All Programmable Soc Libraries Guide (UG953)
    Vivado Design Suite 7 Series FPGA and Zynq-7000 All Programmable SoC Libraries Guide UG953 (v 2013.1) March 20, 2013 Notice of Disclaimer The information disclosed to you hereunder (the "Materials") is provided solely for the selection and use of Xilinx products. To the maximum extent permitted by applicable law: (1) Materials are made available "AS IS" and with all faults, Xilinx hereby DISCLAIMS ALL WARRANTIES AND CONDITIONS, EXPRESS, IMPLIED, OR STATUTORY, INCLUDING BUT NOT LIMITED TO WARRANTIES OF MERCHANTABILITY, NON-INFRINGEMENT, OR FITNESS FOR ANY PARTICULAR PURPOSE; and (2) Xilinx shall not be liable (whether in contract or tort, including negligence, or under any other theory of liability) for any loss or damage of any kind or nature related to, arising under, or in connection with, the Materials (including your use of the Materials), including for any direct, indirect, special, incidental, or consequential loss or damage (including loss of data, profits, goodwill, or any type of loss or damage suffered as a result of any action brought by a third party) even if such damage or loss was reasonably foreseeable or Xilinx had been advised of the possibility of the same. Xilinx assumes no obligation to correct any errors contained in the Materials or to notify you of updates to the Materials or to product specifications. You may not reproduce, modify, distribute, or publicly display the Materials without prior written consent. Certain products are subject to the terms and conditions of the Limited Warranties which can be viewed at http://www.xilinx.com/warranty.htm; IP cores may be subject to warranty and support terms contained in a license issued to you by Xilinx.
    [Show full text]
  • Vivado Design Suite User Guide: Implementation
    See all versions of this document Vivado Design Suite User Guide Implementation UG904 (v2021.1) August 30, 2021 Revision History Revision History The following table shows the revision history for this document. Section Revision Summary 08/30/2021 Version 2021.1 Sweep (Default) Added more information. Incremental Implementation Controls Corrected Block Memory and DSP placement example. Using Incremental Implementation in Project Mode Corrected steps and updated image. Using report_incremental_reuse Updated Reuse Summary example and Reference Run Comparison. Physical Optimization Reports Updated to clarify that report is not cumulative. Available Logic Optimizations Added -resynth_remap. Resynth Remap Added logic optimization. opt_design Added [-resynth_remap] to opt_design Syntax. Physical Synthesis Phase Added entry for Property-Based Retiming. 02/26/2021 Version 2020.2 General Updates General release updates. 08/25/2020 Version 2020.1 Appendix A: Using Remote Hosts and Compute Clusters Updated section. UG904 (v2021.1) August 30, 2021Send Feedback www.xilinx.com Implementation 2 Table of Contents Revision History...............................................................................................................2 Chapter 1: Preparing for Implementation....................................................... 5 About the Vivado Implementation Process............................................................................. 5 Navigating Content by Design Process...................................................................................
    [Show full text]
  • Open On-Chip Debugger: Openocd User's Guide
    Open On-Chip Debugger: OpenOCD User's Guide for release 0.11.0 7 March 2021 This User's Guide documents release 0.11.0, dated 7 March 2021, of the Open On-Chip Debugger (OpenOCD). • Copyright c 2008 The OpenOCD Project • Copyright c 2007-2008 Spencer Oliver [email protected] • Copyright c 2008-2010 Oyvind Harboe [email protected] • Copyright c 2008 Duane Ellis [email protected] • Copyright c 2009-2010 David Brownell Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled \GNU Free Documentation License". i Short Contents About :::::::::::::::::::::::::::::::::::::::::::::::::: 1 1 OpenOCD Developer Resources :::::::::::::::::::::::::: 3 2 Debug Adapter Hardware ::::::::::::::::::::::::::::::: 5 3 About Jim-Tcl ::::::::::::::::::::::::::::::::::::::: 11 4 Running :::::::::::::::::::::::::::::::::::::::::::: 12 5 OpenOCD Project Setup :::::::::::::::::::::::::::::: 14 6 Config File Guidelines ::::::::::::::::::::::::::::::::: 21 7 Server Configuration :::::::::::::::::::::::::::::::::: 32 8 Debug Adapter Configuration::::::::::::::::::::::::::: 36 9 Reset Configuration::::::::::::::::::::::::::::::::::: 54 10 TAP Declaration ::::::::::::::::::::::::::::::::::::: 59 11 CPU Configuration ::::::::::::::::::::::::::::::::::: 67 12 Flash Commands :::::::::::::::::::::::::::::::::::::
    [Show full text]
  • UG908 (V2019.2) October 30, 2019 Revision History
    See all versions of this document Vivado Design Suite User Guide Programming and Debugging UG908 (v2019.2) October 30, 2019 Revision History Revision History The following table shows the revision history for this document. Section Revision Summary 10/30/2019 Version 2019.2 General Updates Updated for Vivado 2019.2 release. 05/22/2019 Version 2019.1 Appendix E: Configuration Memory Support Replaced Configuration Memory Support Tables. Bus Plot Viewer Added new section on Bus Plot Viewer. High Bandwidth Memory (HBM) Monitor Added new section on High Bandwidth (HBM) Monitor. UG908 (v2019.2) October 30, 2019Send Feedback www.xilinx.com Vivado Programming and Debugging 2 Table of Contents Revision History...............................................................................................................2 Chapter 1: Introduction.............................................................................................. 8 Getting Started............................................................................................................................ 8 Debug Terminology.................................................................................................................... 9 Chapter 2: Vivado Lab Edition................................................................................13 Installation................................................................................................................................. 13 Using the Vivado Lab Edition .................................................................................................
    [Show full text]
  • CERN Radiation Monitoring Electronics (CROME) Project in Order to Develop a Replacement
    Contributions to the SIL 2 Radiation Monitoring System CROME (CERN RadiatiOn Monitoring Electronics) Master Thesis CERN-THESIS-2017-478 //2017 Author: Nicola Joel Gerber Supervisor CERN - HSE-RP/IL: Dr. Hamza Boukabache Supervisor EPFL - SEL j STI: Dr. Alain Vachoux March 2017 Abstract CERN is developing a new radiation monitoring system called CROME to replace the currently used system which is at the end of its life cycle. As radiation can pose a threat to people and the environment, CROME has to fulfill several requirements regarding functional safety (SIL 2 for safety-critical functionalities). This thesis makes several contributions to increase the functionality, reliability and availability of CROME. Floating point computations are needed for the signal processing stages of CROME to cope with the high dynamic range of the measured radiation. Therefore, several IEEE 754-2008 conforming floating point operation IP cores are developed and implemented in the system. In order to fulfill the requirements regarding functional safety, the IP cores are verified rigorously by using a custom OSVVM based floating point verification suite. A design methodology for functional safety in SRAM-based FPGA-SoCs is developed. Some parts of the methodology are applied to the newly developed IP cores and other parts were ported back to the existing system. In order to increase the reliability and availability of CROME, a new in-system communication IP core for decoupling the safety-critical from the non-safety-critical parts of the FPGA-SoC-based system is implemented. As the IP core contains mission critical configuration data and will have an uptime of several years, it is equipped with several single event upset mitigation techniques such as ECC for memory protection and fault-robust FSMs in order to increase the system's reliability and availability.
    [Show full text]