Synopsys Identify User manual

https://solvnet.synopsys.com
Identify Debugger
User Guide
March 2015

LO
Preface
© 2015 Synopsys, Inc. Identify Debugger User Guide
2March 2015
Copyright Notice and Proprietary Information
© 2015 Synopsys, Inc. All rights reserved. This software and documentation
contain confidential and proprietary information that is the property of
Synopsys, Inc. The software and documentation are furnished under a
license agreement and may be used or copied only in accordance with the
terms of the license agreement. No part of the software and documentation
may be reproduced, transmitted, or translated, in any form or by any means,
electronic, mechanical, manual, optical, or otherwise, without prior written
permission of Synopsys, Inc., or as expressly provided by the license
agreement.
Right to Copy Documentation
The license agreement with Synopsys permits licensee to make copies of the
documentation for its internal use only.
Each copy shall include all copyrights, trademarks, service marks, and
proprietary rights notices, if any. Licensee must assign sequential numbers
to all copies. These copies shall contain the following legend on the cover
page:
“This document is duplicated with the permission of Synopsys, Inc., for the
exclusive use of __________________________________________ and its
employees. This is copy number __________.”
Destination Control Statement
All technical data contained in this publication is subject to the export
control laws of the United States of America. Disclosure to nationals of other
countries contrary to United States law is prohibited. It is the reader’s
responsibility to determine the applicable regulations and to comply with
them.

Preface
Identify Debugger User Guide © 2015 Synopsys, Inc.
March 2015 3
Disclaimer
SYNOPSYS, INC., AND ITS LICENSORS MAKE NO WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, WITH REGARD TO THIS MATERIAL, INCLUDING,
BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY
AND FITNESS FOR A PARTICULAR PURPOSE.
Registered Trademarks (®)
Synopsys, AEON, AMPS, Astro, Behavior Extracting Synthesis Technology,
Cadabra, CATS, Certify, CHIPit, CoMET, CODE V, Design Compiler,
DesignWare, EMBED-IT!, Formality, Galaxy Custom Designer, Global
Synthesis, HAPS, HapsTrak, HDL Analyst, HSIM, HSPICE, Identify, Leda,
LightTools, MAST, METeor, ModelTools, NanoSim, NOVeA, OpenVera, ORA,
PathMill, Physical Compiler, PrimeTime, SCOPE, Simply Better Results, SiVL,
SNUG, SolvNet, Sonic Focus, STAR Memory System, Syndicated, Synplicity,
the Synplicity logo, Synplify, Synplify Pro, Synthesis Constraints Optimization
Environment, TetraMAX, UMRBus, VCS, Vera, and YIELDirector are regis-
tered trademarks of Synopsys, Inc.
Trademarks (™)
AFGen, Apollo, ARC, ASAP, Astro-Rail, Astro-Xtalk, Aurora, AvanWaves,
BEST, Columbia, Columbia-CE, Cosmos, CosmosLE, CosmosScope, CRITIC,
CustomExplorer, CustomSim, DC Expert, DC Professional, DC Ultra, Design
Analyzer, Design Vision, DesignerHDL, DesignPower, DFTMAX, Direct Silicon
Access, Discovery, Eclypse, Encore, EPIC, Galaxy, HANEX, HDL Compiler,
Hercules, Hierarchical Optimization Technology, High-performance ASIC
Prototyping System, HSIMplus, i-Virtual Stepper, IICE, in-Sync, iN-Tandem,
Intelli, Jupiter, Jupiter-DP, JupiterXT, JupiterXT-ASIC, Liberty,
Libra-Passport, Library Compiler, Macro-PLUS, Magellan, Mars, Mars-Rail,
Mars-Xtalk, Milkyway, ModelSource, Module Compiler, MultiPoint, ORAengi-
neering, Physical Analyst, Planet, Planet-PL, Polaris, Power Compiler,
Raphael, RippledMixer, Saturn, Scirocco, Scirocco-i, SiWare, Star-RCXT,
Star-SimXT, StarRC, System Compiler, System Designer, Taurus, Total-
Recall, TSUPREM-4, VCSi, VHDL Compiler, VMC, and Worksheet Buffer are
trademarks of Synopsys, Inc.

LO
Preface
© 2015 Synopsys, Inc. Identify Debugger User Guide
4March 2015
Service Marks (sm)
MAP-in, SVP Café, and TAP-in are service marks of Synopsys, Inc.
SystemC is a trademark of the Open SystemC Initiative and is used under
license.
ARM and AMBA are registered trademarks of ARM Limited.
Saber is a registered trademark of SabreMark Limited Partnership and is
used under license.
All other product or company names may be trademarks of their respective
owners.
Printed in the U.S.A
March 2015

Identify Debugger User Guide © 2015 Synopsys, Inc.
March 2015 5
Contents
Chapter 1: Using the Debugger
Configuring and Invoking the Debugger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Reviewing the Instrumentation Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Changing the Communication Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Reviewing the JTAG Chain Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Saving the Debugged Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Invoking the Debugger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Debugger Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
IICE Instrumentation Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Console Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Project Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Commands and Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Opening and Saving Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Executing a Script File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Activating/Deactivating an Instrumentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Selecting Multiplexed Instrumentation Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Activating/Deactivating Folded Instrumentation . . . . . . . . . . . . . . . . . . . . . . . . . 24
Run Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Sampled Data Compression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Sample Buffer Trigger Position . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Sampled Data Display Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Saving and Loading Activations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Cross Triggering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Listing Watchpoints and Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
HAPS Deep Trace Debug . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Running Deep Trace Debug with DDR3 Memory . . . . . . . . . . . . . . . . . . . . . . . 40
Viewing Captured Deep Trace Debug Samples . . . . . . . . . . . . . . . . . . . . . . . . 41
Hardware Configuration Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Debugging on a Different Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Simultaneous Debugging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

LO
Contents
© 2015 Synopsys, Inc. Identify Debugger User Guide
6March 2015
Debugger-Analyst Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Waveform Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Generating the Fast Signal Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Logic Analyzer Interface Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Logic Analyzer Scan Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Logic Analyzer Properties Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Logic Analyzer Submit Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
IICE Assignments Report Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Chapter 2: Board Bring-up
Board Query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Board Bring-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Setting Initial Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
ConfPro GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Board Configuration Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Utility Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Chapter 3: Incremental Flow
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Setting up the Original Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Creating the Incremental Instrumentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Redefining the Instrumented Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Generating the Bit File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Incremental Implementation Support
with Distributed Instrumentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Debugging the Incremental Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Incremental Flow Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Chapter 4: IICE Hardware Description
JTAG Communication Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Breakpoint and Watchpoint Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Breakpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Watchpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Multiple Activated Breakpoints and Watchpoints . . . . . . . . . . . . . . . . . . . . . . . . 83
Sampling Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Complex Counter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Creating a Complex Counter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Debugging with the Complex Counter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Disabling the Counter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Contents
Identify Debugger User Guide © 2015 Synopsys, Inc.
March 2015 7
State Machine Triggering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Simple or Advanced Triggering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Advanced Triggering Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
State-Machine Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
State-Machine Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Chapter 5: Connecting to the Target System
Basic Communication Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Debugger Communications Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Debugger Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
JTAG Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
JTAG Hardware in Instrumented Designs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Using the Built-in JTAG Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Using the Synopsys Debug Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Boards Without Direct Built-in JTAG Connections . . . . . . . . . . . . . . . . . . . . . . 130
Setting the JTAG Chain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
JTAG Communication Debugging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Basic Communication Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
On-chip Identification Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
JTAG Chain Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
UMRBus Communications Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

LO
Contents
© 2015 Synopsys, Inc. Identify Debugger User Guide
8March 2015

Identify Debugger User Guide © 2015 Synopsys, Inc.
March 2015 9
CHAPTER 1
Using the Debugger
Before a design can be debugged, the instrumentor is first used to define the
specific signals to be monitored and then to generate an
instrumentation
design
constraints ( idc ) file containing the instrumented signals and break
points. The design is synthesized and the device is programmed with the
debuggable design. The debugger is then launched to analyze the design
while it is running in the target system
The debugger enables HDL designs to be analyzed by interacting with the
instrumented HDL design implemented in the target hardware system. You
can activate breakpoints and watchpoints to cause trigger events within the
IICE
™
on the target device. These triggers cause signal data to be captured in
the IICE. The data is then transferred to the debugger through a communica-
tions port where it can be displayed in a variety of formats. This chapter
describes:
•Configuring and Invoking the Debugger, on page 10
•Debugger Windows, on page 13
•Commands and Procedures, on page 18
•HAPS Deep Trace Debug, on page 40
•Debugging on a Different Machine, on page 44
•Simultaneous Debugging, on page 45
•Debugger-Analyst Integration, on page 46
•Waveform Display, on page 51
•Logic Analyzer Interface Parameters, on page 54

LO
Chapter 1: Using the Debugger Configuring and Invoking the Debugger
© 2015 Synopsys, Inc. Identify Debugger User Guide
10 March 2015
Configuring and Invoking the Debugger
To configure a design for debugging, click the project tab to reopen the project
window (reopening the project window shows the instrumentation and
communication settings). Configuring and invoking the debugger is described
in the following sections:
•Reviewing the Instrumentation Settings, on page 10
•Changing the Communication Settings, on page 10
•Reviewing the JTAG Chain Settings, on page 11
•Saving the Debugged Design, on page 12
•Invoking the Debugger, on page 12
Reviewing the Instrumentation Settings
The instrumentation settings are displayed in the Instrumentation settings
section of the project window. Because these configuration settings are inher-
ited from the instrumentor and used to construct the IICE, you cannot
change these settings in the debugger.
Changing the Communication Settings
The cable type and port specification communication settings can be set or
changed from the project window.
There is a list of possible vendor cable-type settings available from the
Cable
type
drop-down menu. A umrbus setting is also available to setup UMRBus
communications between the host and the HAPS
®
board system (see
UMRBus Communications Interface , on page 136). Set Cable type value
according to the type of cable you are using to connect to the programmable
device.
Adjust the port setting based on the port where the communication cable is
connected. Most often,
lpt1 is the correct setting for parallel ports.