2013年Quartus II脚本编程指南：解决命令行与Tcl错误详解

需积分: 5 93 浏览量更新于2024-07-16 收藏 3.59MB PDF 举报

身份认证购VIP最低享 7 折!

30元优惠券

资源详情

资源推荐

xvi Contents

Quartus II Scripting Reference Manual © July 2013 Altera Corporation

remove_from_collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–425

report_advanced_io_timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–426

report_bottleneck . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–427

report_clock_fmax_summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–429

report_clock_transfers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–430

report_clocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–431

report_datasheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–432

report_ddr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–433

report_exceptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–434

report_max_skew . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–438

report_metastability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–441

report_min_pulse_width . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–444

report_net_delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–446

report_net_timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–447

report_partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–448

report_path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–449

report_rskm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–451

report_sdc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–452

report_skew . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–453

report_tccs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–456

report_timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–457

report_ucp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–461

set_operating_conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–462

timing_netlist_exist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–463

update_timing_netlist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–464

use_timequest_style_escaping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–465

write_sdc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–466

stp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–467

close_session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–468

open_session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–469

run . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–470

run_multiple_end . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–471

run_multiple_start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–472

stop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–473

timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–474

compute_slack_on_edges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–475

create_timing_netlist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–476

delete_timing_netlist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–478

remove_timing_tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–479

report_timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–480

timing_assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–484

create_base_clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–485

create_relative_clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–487

get_clocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–489

set_clock_latency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–490

set_clock_uncertainty . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–492

set_input_delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–494

set_multicycle_assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–496

set_output_delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–498

set_timing_cut_assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–500

timing_report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–502

list_path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–503

xviii About this Reference Manual

Typographic Conventions

Quartus II Scripting Reference Manual © July 2013 Altera Corporation

Typographic Conventions

The following table shows the typographic conventions that this document uses.

Visual Cue Meaning

Bold Type with Initial Capital

Letters

Command names, dialog box titles, checkbox options, and dialog box options are

shown in bold, initial capital letters. Example: Save As dialog box.

bold type

External timing parameters, directory names, project names, disk drive names, file

names, file name extensions, and software utility names are shown in bold type.

Examples: f

MAX

, \qdesigns directory, d: drive, chiptrip.gdf file.

Italic Type with Initial Capital Letters

Document titles are shown in italic type with initial capital letters. Example: AN 75:

High-Speed Board Design.

Italic type

Internal timing parameters and variables are shown in italic type.

Examples: t

PIA

, n + 1.

Variable names are enclosed in angle brackets (< >) and shown in italic type.

Example: <file name>, <project name>.pof file.

Initial Capital Letters

Keyboard keys and menu names are shown with initial capital letters. Examples:

Delete key, the Options menu.

“Subheading Title”

References to sections within a document and titles of on-line help topics are shown

in quotation marks. Example: “Typographic Conventions.”

Courier type

Signal and port names are shown in lowercase Courier type. Examples:

data1, tdi,

input. Active-low signals are denoted by suffix n, e.g., resetn.

Anything that must be typed exactly as it appears is shown in Courier type. For exam-

ple:

c:\qdesigns\tutorial\chiptrip.gdf. Also, sections of an actual file,

such as a Report File, references to parts of files (e.g., the AHDL keyword

SUBDE-

SIGN

), as well as logic function names (e.g., TRI) are shown in Courier.

1., 2., 3., and

a., b., c., etc.

Numbered steps are used in a list of items when the sequence of the items is impor-

tant, such as the steps listed in a procedure.

■ ■ Bullets are used in a list of items when the sequence of the items is not important.

v The checkmark indicates a procedure that consists of one step only.

1 The hand points to information that requires special attention.

A caution calls attention to a condition or possible situation that can damage or

destroy the product or the user’s work.

A warning calls attention to a condition or possible situation that can cause injury to

the user.

r The angled arrow indicates you should press the Enter key.

f The feet direct you to more information on a particular topic.

1. Introduction to the Quartus II Scripting

Reference Manual

Introduction

The Quartus

II design software provides the FPGA industry’s easiest-to-use and

most powerful scripting environment available for command-line operation and tool

command language (Tcl) scripting. This scripting environment is offered in addition

to the Quartus II development software rich graphical user interface (GUI).

This overview covers the Quartus II design software support for command-line

operation and Tcl scripting.

Overview

Each stage of the Quartus II software design flow corresponds to a command-line

executable file. Many of these executable files also support industry-standard Tcl

scripting for custom functionality or processing beyond the GUI design flow.

Quartus II design software offers the following scripting support benefits, also known

as CAR:

■ Custom Analysis

■ Automation

■ Reproducibility

Custom analysis allows you to build test procedures into the script and change design

processing based on the test results. Scripts can automate design flows to perform on

multiple computers simultaneously and easily archive and restore projects.

Reproducibility ensures that scripts use the same project setup and assignments for

every compile, even when you transfer a project from one engineer to another. In

other words, you can use scripts as another level of design quality assurance.

The Quartus II Scripting Reference Manual is your reference guide to Quartus II

software command-line executables and Tcl commands, including command details,

usage, and examples.

All of the information included in the Quartus II Scripting Reference Manual, as well as

the most up-to-date list of commands, can also be found in the Quartus II software Tcl

API and command-line executable online help reference, Qhelp. To access this

information within Quartus II design software, type the following command at the

command prompt:

quartus_sh --qhelp r

Quartus II Software Command-Line Operation Support

Use command-line operation for:

■ Scripting simple design flows

■ Compiling existing projects

■ Making global project assignments

1–2 Introduction to the Quartus II Scripting Reference Manual

Overview

■ Incorporating third-party EDA executable files

■ Makefile operation

You can also group commands for Quartus II executable files into a script, batch file,

or in a makefile to automate design flows. The Quartus II software command-line

executables accept arguments to set project variables and access common settings.

Quartus II Software Tcl Scripting Support

Use Tcl scripting for:

■ Solving complex analysis

■ Making individual assignments

■ Generating custom reports

■ Creating custom solutions

Tcl is an EDA industry-standard scripting language used by Synopsys, Mentor

Graphics

, Synplicity, Altera, and others. The Tcl language supports control

structures, variables, procedures, network socket access, and application

programming interfaces (APIs). Altera's Tcl support is aligned with major EDA

vendor solutions. It has an API format similar to the Synopsys design constraint

(SDC) format used by the Synopsys PrimeTime and Design Compiler products.

Command-Line Executables

Quartus II software provides command-line executables for each stage in the design

flow. The software also provides additional executables for specific tasks.

Table 1 details the command-line executables and their respective descriptions.

Table 1. Quartus II Command-Line Executables and Descriptions (Part 1 of 3)

Executable Description

Analysis and Synthesis

quartus_map

Quartus II Analysis and Synthesis builds a single project database that integrates all the

design files in a design entity or project hierarchy, performs logic synthesis to minimize the

logic of the design, and performs technology mapping to implement the design logic using

device resources such as logic elements.

Fitter

quartus_fit

The Quartus II Fitter performs place-and-route by fitting the logic of a design into a device.

The Fitter selects appropriate interconnection paths, pin assignments, and logic cell

assignments.

Quartus II Analysis and Synthesis must be run successfully before running the Fitter.

Signal Integrity

quartus_si

The Quartus II SSN Analyzer estimates the simultaneous switching noise contributions to

voltage and timing noise.

Quartus II Analysis & Synthesis and the Fitter must be run successfully before running the

SSN Analyzer.

剩余633页未读，继续阅读

JAD7998

粉丝: 58
资源: 30

2013年Quartus II脚本编程指南：解决命令行与Tcl错误详解

Scripting Reference Manual for quartusII

Quartus II 13.0.0.156.qdz.zip

QuartusII软件安装与熟悉.pdf

quartus ii 13.0.0.156.器件库

如何安装Quartus II 13.0.0.156器件包？

quartus ii怎么打开.v文件

quartus器件库13.0.1.232

quartus prime programmer and tools 15.1.0.185

quartus ii安装教程

quartus ii13.0下载

quartus ii 13.1使用教程

quartus ii 11.0安装教程

Error: Quartus II Analysis & Synthesis was unsuccessful.怎么解决

quartus ii 13.0器件库安装

Quartus II 安装教程—FPGA入门教程

quartus ii13.0安装教程

quartus ii和vscode

quartusii 13.0 器件库下载 download.altera

quartusii 下载

quartus ii 13.0使用教程

最新资源