Conformal Lec Training Basic Advance

CADENCE CONFIDENTIAL 1 CADENCE DESIGN SYSTEMS, INC.
Conformal
LEC
Logic Equivalence Checker
Basic Training Manual
Verplex
Systems, Inc.
2 CADENCE CONFIDENTIAL
Getting Help
You can get help with Cadence software
from the following sources:
Education Services training materials
SourceLink service on the Internet:
sourcelink.cadence.com
OR go to the Cadence home page
(http://www.cadence.com).
Select the Customer Support link.
You must have a maintenance contract to log in (authorization
number).
Customer Response Center (CRC) or send your
request to support@cadence.com
Agenda of Conformal LEC Basic
Training
Overview of Verplex formal verification tools
Conformal
LEC usage
Introduction to LEC
A typical session (flat compare)
Hierarchical compare
Overview of Verplex formal
verification tools
Formal verification
A systematic method that uses mathematical
proof to check the designs properties
Advantages of formal verification
Enable "White box" verification
No test vectors required
Exhaustive verification
Find bugs earlier
Speed
Functional Closure
Verplex enables you to obtain the Golden
RTL that meets the functional specifications
Verplex ensures that the functionality of the
final layout matches that of the Golden RTL
Final
Layout
Golden
RTL
RTL
Blocks
RTL
Blocks
Functional
Specification
RTL
Blocks
Property
Checking
Logical
consistency
Structural
consistency
Clock
synchronization
Structural
consistency
Semantic
consistency
Clock
synchronization
Implementation
Verification
Our formal technology enables you to catch bugs
Earlier Target a class of bugs typically found with
simulation late in the design cycle
Faster Formal is magnitudes faster than simulation
Easier No test vectors required, easy debugging
VERPLEX Conformal Solution Overview
Conformal Custom
Extends EC to Cust. Log &
memory
Extends EC to
custom logic
and memory
Conformal ASIC
Property Checking
Verifies
Clock domain
crossings
Semantic
consistency
Structural
consistency
Design it golden - keep it golden.
TM
Conformal Ultra
Extends EC to Datapath
RTL-gate
Equivalence Checking
(EC)
Conformal ASIC
Equivalence Checker
RTL-gate
Equivalence Checking
(EC)
Verifies
Clock domain
crossings
Structural
consistency
RTL GDSII Gate
Design
Implementation
Physical
Implementation RTL GDSII Gate
Design
Creation
Design Flow
Functional
Specification
Assertion Based Property Checker
Pre-Defined
Checks
(automatic)
Done Done
Pass
HDL
design
Fail Debug
Proof Proof
engine engine
Verplex Formal Verification Solution
Assertion Based Functional Checker
Pre-Defined Checks (PDC)
Automatically checks for
Asynchronous clock domain crossing
Clock domain analysis
Structural checks for metastability prevention
Functional checks for data stability
Semantic inconsistency
full_case/parallel_case
range-overflow conditions
X-assignment
Structural inconsistency
Tri-state enable stuck-at conditions
Simultaneous set-reset conflict
Conflicting values on multi-port latches
Bus contention and bus floating
Conformal LTX Logic Transistor
Extraction
Module xor(y, a, b)
input a,b;
output y;
y = (~a&b) | (a&~b);
endmodule
RTL
Abstract
transistor-level
circuitry into gate-
level
Enable
equivalence
checking
Conformal LEC
Conformal LTX
Gate-Level
SPICE
Verilog
or CDL
Conformal LEC Logic Equivalence
Checker
Largest designs with the highest
completion rate
Handles even complex logic
Verifies any step back to original
RTL
Accommodates any combination:
RTL and gate, flat or hierarchical
Easiest to use
Annotated error patterns
RTL-gate cross highlighting
Logic cone schematic display
Highest performance
Flat R2G compare: 1hr / 1M gates
Flat G2G compare: 20min / 1M
gates
Conformal LEC Usage
LEC usage
Introduction to LEC
Getting familiar with LEC
LEC modes of operation
LEC flow
Starting and exiting LEC
LEC GUI environment
LEC command conventions
3-2-1
Add/Delete/Report
Convenient features
Online help and documentation
Starting and exiting LEC
Starting LEC
GUI mode: UNIX% lec
Non-GUI mode: UNIX% lec -nogui
Switch GUI & non-GUI modes (anytime during LEC session)
LEC> set gui [on | off]
Batch mode:
UNIX % lec -dofile <batch_file> -nogui
LEC> dofile <batch_file>
Exiting LEC
LEC> exit -force
LEC automatically closes all windows upon exit
GUI environment
Mode Read lib Read design
Golden Revised
Design
hierarchy
Messages
Command Entry window
Read Design
window
File list area
Selected file area
Browser
File
filter
Design type
LEC
window
Transcript
window
Command: 3-2-1 convention
Most three-word commands can be abbreviated
Example:
SETUP> add pin constraint 0 scan_en
can be written as:
SETUP> add pi c 0 scan_en
If 3-2-1 convention does not produce unique
command, more letters may be added
add in c ADD INstance Constraint
add pi c ADD PIn Constraint
set lo f SET LOg File
3-2-1 convention Commands
Add/Delete/Report convention
For every ADD command, there is a corresponding
REPORT and DELETE command
For example, if you specify:
SETUP> ADD PIn Constraint 0 scan_en
To report all pin constraints:
SETUP> REPort PIn Constraint
To remove the added constraint:
SETUP> DELete PIn Constraint scan_en
Convenient features
Rerun previous command
Up and down arrow keys help avoid retyping previous
commands
Alias
Alias command usage: add alias <name> <string>
Example alias in .conformal_lec file:
add alias setup set system mode setup
Initial command file, .conformal_lec, executed in the following
order (3.4.0.a or later ):
a. Verplex install directory: $VERPLEX_HOME/lib/.conformal_lec
b. Home directory: ~/.conformal_lec
c. Current working directory: ./.conformal_lec
Online help and documentation
Access location of the PDF format manuals:
Commands: List of all command options, usage, examples,
and related commands
Reference Manual: PDF format file of command reference
with detailed command usage and definitions
User Manual: PDF format file with information related to the
product (for example; installation, process flow, and GUI)
Directory location of the PDF format manuals:
$VERPLEX_HOME/doc
LEC usage
Introduction to LEC
LEC flow
Modes of operation
SETUP mode
Saving LEC transcript to a log file
Specifying black boxes
Reading libraries and designs
Specifying design constraints
Specifying modeling directives
LEC mode
Mapping process
Resolving unmapped key points
Compare process
Debugging non-equivalent key points
Report run statistics
Switching modes of operation
GUI: click
Command: set system mode [lec | setup]
LEC usage
Introduction to LEC
LEC flow
No
Equivalence Equivalence
established established
Differences ? Differences ?
Yes
All mapped ? All mapped ?
Specify constraints Specify constraints
& other parameters & other parameters
Golden Golden
Analyze Analyze
Yes
Debug Debug
Fix design Fix design
No
Revised Revised
Map key points Map key points
Compare key points Compare key points
ASIC
Lib
ASIC ASIC
Lib Lib
LEC flow
Setup
mode
LEC
mode
LEC usage
Introduction to LEC
LEC flow
Switching to LEC mode
Mapping process
Compare process
LEC
SETUP
Example 1:
Specify the name of the log file where LEC session
transcript is to be written
set log file logfile -replace
...
set log file logfile -replace
...
Example 2:
Note: $LEC_VERSION is automatically set to the current LEC version
set log file logfile.$LEC_VERSION -replace
...
...
Mapping process
Compare process
LEC
SETUP
Black box
Module types
RAM, ROM, analog, behavioral, or
any module you dont want to verify
Allows wildcard(*) specification
Black box connections are verified
RAM
ALU CTRL
Execute black boxing command before module is
read in
For missing module, create one with just
input/output declaration
set log file logfile.$LEC_VERSION replace
setenv LIB /user1/lib/verilog/
add notranslate module *ram* hstm -full -both
read library $LIB/verilog/*.v -verilog both
...
add notranslate module *ram* hstm -full -both
read library $LIB/verilog/*.v -verilog both
...
module sram1(in1, in2, out2, out2);
input in1, in2;
output out1, out2;
//empty
endmodule
module sram1(in1, in2, out2, out2);
input in1, in2;
output out1, out2;
//empty
endmodule
Reporting black boxes
SETUP> report black box
Check for unbalanced black boxes in the
Golden and Revised
LEC window
SYSTEM: (G R) ram8x256
SYSTEM: (G R) hstm
SYSTEM: (G R) ram8x256
SYSTEM: (G R) hstm
Mapping process
Compare process
LEC
SETUP
Supported formats
Library
Verilog (standard simulation libraries)
Liberty
Design (Synthesizable RTL, gate, transistor)

Verilog
VHDL
SPICE
Reading Verilog library & design:
Syntax
Read library:
read library <filename >
[-verilog | -liberty]
[-replace | -append]
[-both | -golden | -revised]
Read design:
read design <filename >
[-file <verilog_command_file>]
[-verilog | -verilog2k]
[-golden | -revised]
Reading files via command line
Allows wildcard (*) specification
Allows path search specification
read design cpu_rtl.v -verilog -golden
read library $LIB/*.v -verilog -revised
read design cpu_gate.v -verilog -revised
...
read library $LIB/*.v -verilog -revised
read design cpu_gate.v -verilog -revised
...
add search path /user1/lib/verilog/ -lib -revised
read library *.v -verilog -revised
add search path /user1/lib/verilog/ -lib -revised
read library *.v -verilog -revised
Method 1
Reading files via Verilog command file
LEC reads only library cells being instantiated
Method 2
read design cpu_rtl.v -verilog golden
read design -file verilog.vc -verilog -revised
...
read design cpu_rtl.v -verilog golden
...
General syntax:
<File>... Design Data File
-v <File>... List of Library Files
-y <Directory>... Library Directory(s)
+incdir+<dir_name>... Include Directories
+libext+<extension>... File Extension e.g ".v"
-yd <Directory>... Design Directory(s)
<File>... Design Data File
-v <File>... List of Library Files
-y <Directory>... Library Directory(s)
+incdir+<dir_name>... Include Directories
+libext+<extension>... File Extension e.g ".v"
-yd <Directory>... Design Directory(s)
Syntax:
-y $LIB
cpu_gate.v
Content:
-y $LIB
cpu_gate.v
Reading VHDL design: Syntax
read design -vhdl <filename >
[-map <library_name> <library_path>]
[-mapfile <library_name> <filename >]
[-golden | -revised]
-map: read in library files from the specified
library_path for the specified
library_name
-mapfile: read in the specified library files
for the specified library_name
Multiple -map and -mapfile options are allowed
Reading VHDL design: Example
Content of mb_lock.vhd:
LIBRARY MB_LIB;
LIBRARY DP_LIB;
USE MB_LIB.ATTRIBUTES.ALL;
USE DP_LIB.MISC_PKG.ALL;
...
LIBRARY MB_LIB;
LIBRARY DP_LIB;
USE MB_LIB.ATTRIBUTES.ALL;
USE DP_LIB.MISC_PKG.ALL;
...
read design -vhdl RTL/mb_lock.vhd golden \
-map MB_LIB /user1/lib/vhdl/ \
-mapfile DP_LIB ./vhdl_lib/misc_pkg.vhd
...
read design -vhdl RTL/mb_lock.vhd golden \
-map MB_LIB /user1/lib/vhdl/ \
-mapfile DP_LIB ./vhdl_lib/misc_pkg.vhd
...
Reading mixed languages
Mixed-language: Libraries
setenv LIB /user1/lib/
read library $LIB/verilog/*.v -verilog -golden
read library $LIB/vhdl/*.lib -liberty -append -golden
...
read library $LIB/vhdl/*.lib -liberty -append -golden
...
Mixed-language: Designs
read design RTL/core.vhd -vhdl -noelab -golden
read design RTL/top.v -verilog -golden
...
read design RTL/core.vhd -vhdl -noelab -golden
read design RTL/top.v -verilog -golden
...
HDL rule checks
LEC displays HDL rule violations after parsing design
Non-GUI mode
SETUP> report rule check <rule_name> -verbose
GUI mode
Click to
open
// Command: read design src/idsctrl.v -gold
// Check out vlg 3.0 license
// Parsing file src/idsctrl.v ...
// Golden root module is set to idsctrl
// Warning: (RTL2.3) externally defined signal reference not supported
// Warning: (RTL5.1) overlapped case items in parallel case statement
...
// Command: read design src/idsctrl.v -gold
// Check out vlg 3.0 license
// Parsing file src/idsctrl.v ...
// Golden root module is set to idsctrl
// Warning: (RTL2.3) externally defined signal reference not supported
// Warning: (RTL5.1) overlapped case items in parallel case statement
...
Transcript window
HDL rule check categories
You can specify the severity level for each
category: "Error", "Warning", "Note", or "Ignore"
with command "SET RUle Handling"
Directives: Synthesis and Verplex directives
Hierarchy: Rules apply to hierarchical design
Ignored: Redundant constructs or statement not
supported, and thus ignored by LEC
RTL: RTL-level Verilog or VHDL rules
UDP: User-defined primitives
Verilog: Designs written in Verilog language
Mapping process
Compare process
LEC
SETUP
Design constraints
What are design constraints?
Users inputs to control part of a designs logic
Purpose of constraints
To disable test logic (for example; scan and JTAG)
To specify one-hot or one-cold conditions
To specify relationships between pins
To constrain undriven signals
Example of constraints
Pin constraint
Instance constraint
Pin equivalence
Tied signal
Undriven signal
Pin constraint
Specify the mode of circuit operation under which comparison
will take place (for example; functional vs. scan operation)
U1
DFF
D Q
CLK
scan_in
scan_en (0)
CLK
0
1
s
U1
DFF
D Q
Golden Revised
add notranslate module *sram* -library -both
add pin constraint 0 scan_en -revised
...
...
Instance constraint
Apply to any internal DFF or D-latch output to Logic-0
or logic-1 (for example; JTAG registers)
U1
DFF
D
Q
CLK
Ties U1 DFF
output to 0
0
U1
DFF
D Q
CLK
...
add instance constraint 0 U1 -revised
...
...
add instance constraint 0 U1 -revised
...
Pin equivalence
Specify the relationship (equivalent or inverted
equivalent) between two or more primary input pins
CLK_n
U1
DFF
D Q
CLK
U2
DFF
D Q
U1
DFF
D Q
CLK
U2
DFF
D Q
...
add pin equivalence CLK invert CLK_n -revised
...
...
add pin equivalence CLK invert CLK_n -revised
...
Tied signal
Specify floating nets or pins to be tied to Logic-0 or
Logic-1 (for example; equate GND to 0 or VDD to 1)
U1
DFF
D Q
CLK
SET
GND
U1
DFF
D Q
SET
CLK
...
add tied signal 0 GND -net -revised
...
...
add tied signal 0 GND -net -revised
...
Undriven signals
Specify the global behavior of floating signals in the designs
(for example; ties all floating signals to a constant)
U1
DFF
Z
CLK
D
U1
DFF
0
CLK
D
...
set undriven signal 0 -revised
...
...
set undriven signal 0 -revised
...
Mapping process
Compare process
LEC
SETUP
Modeling directives
In SETUP mode, user can specify directives to
influence the way LEC models the design
Modeling directives are needed to handle
modeling styles specific to vendors libraries or
synthesis tools
Modeling options:
Latch folding
Gated-clock
Sequential redundancy
Sequential constant
Latch transparent
Sequential merge (clock
and data logic cones )
Grounded clock
DFF direct feedback
Latch folding: Problem
Library cell uses 2 D-latches (master/slave) to
model a DFF
Causes mapping problem!
CLK
latch
D Q
latch
CLK
D Q
CLK
DFF
Golden Revised
Latch folding: Solution
Fold the 2 D-latches into a DFF:
CLK
latch
D Q
latch
D Q
CLK
DFF
D Q
CLK
DFF
Golden Revised
...
set flatten model -latch_fold
...
...
...
Latch folding (master): Problem
Library cell uses two D-latches (master/slave),
with only set/reset to the master D-latch
Causes mapping problem!
latch
D Q
latch
CLK
SET
D Q
CLK
DFF
SET
Golden Revised
Latch folding (master): Solution
Fold the two D-latches into a DFF:
latch
D Q
latch
CLK
SET
D Q
CLK
DFF
SET
D Q
CLK
DFF
SET
Golden Revised
...
set flatten model -latch_fold_master
...
...
set flatten model -latch_fold_master
...
Gated-clock: Problem
Power optimization tools create latch-based gated
clock circuit
Causes compare problem!
D
Q
CLK
DFF
en
latch
en
CLK
D
Q
DFF
Golden Revised
Gated-clock: Solution
Enable gated-clock learning:
D
Q
CLK
DFF
en
latch
en
CLK
D
Q
DFF
D
Q
CLK
DFF
en
Golden Revised
...
set flatten model gated_clock
...
...
set flatten model gated_clock
...
Sequential redundancy: Problem
Redundant AND gate is introduced so that the
reset signal takes effect right away
Causes comparing problem!
D
CLK
DFF
RST
PO
D
RST
DFF
CLK
PO
Golden Revised
Sequential redundancy: Solution
Remove sequential redundancies:
D
CLK
DFF
RST
PO
D
CLK
DFF
RST
D
RST
DFF
CLK
PO
PO
Golden Revised
...
set flatten model seq_redundant
...
...
set flatten model seq_redundant
...
Sequential constant: Problem
Occurs due to the way the circuit is designed
or a designers preference to constrain the
data port
1b1
in1
DFF
CLK
PO
in1
1b1
PO
Golden Revised
Sequential constant: Solution
Convert a DFF or a D-latch to a ZERO/ONE gate
if the data port is set to 0/1:
in1
1b1
PO
in1
1b1
1b1
in1
DFF
CLK
PO PO
Golden Revised
...
set flatten model seq_constant
...
...
set flatten model seq_constant
...
Latch transparent: Problem
Designers choice to have a D-latch with its
clock always enabled as a buffer (transparent
latch)
OUT
1b1
latch
IN
IN OUT
Golden
Revised
Latch transparent: Solution
Remodel D-latches whose clock ports are always
enabled into buffers (transparent latches):
IN OUT
OUT
1b1
Latch
IN
IN OUT
Golden Revised
...
set flatten model latch_transparent
...
...
set flatten model latch_transparent
...
Sequential merge (clock cone):
Problem
Duplicated register in the clock logic cone
Causes mapping/comparing problem!
CLK
DFF
DFF
D0
D1
DFF
CLK
DFF
D1
DFF
D0
Golden Revised
Merge a group of functionally equivalent sequential
elements into one:
Sequential merge (clock cone):
Solution
CLK
DFF
DFF
D0
D1
DFF
CLK
DFF
D1
DFF
D0
CLK
DFF
DFF
D0
D1
Golden Revised
...
set flatten model seq_merge
...
...
set flatten model seq_merge
...
Sequential merge: Problem
Duplicated register in the clock and/or data logic cone
CLK
DFF
D0
DFF
CLK
DFF
DFF
D0
DFF
Golden Revised
Sequential merge: Solution
Merge a group of functionally equivalent sequential
elements into one
This directive is more "expensive" than -seq_merge
Revised
CLK
DFF
DFF
D0
DFF
CLK
DFF DFF
D0
Golden
CLK
DFF DFF
D0
...
set flatten model all_seq_merge
...
...
set flatten model all_seq_merge
...
Grounded clock: Problem
By default, LEC converts a DFF with clock signal
disabled to a D-latch
Might cause mapping/comparing problem!
Actual designs After LEC default modeling
DFF
D
DFF
D
Golden
DFF
D D
DLAT
Revised
Grounded clock: Solution
Instruct LEC not to turn DFF with disabled clock into a D-latch:
After LEC default modeling Issued modeling directive
DFF
D
DFF
D
Golden
Revised
DFF
D
D
DLAT
...
set flatten model nodff_to_dlat_zero
...
...
set flatten model nodff_to_dlat_zero
...
DFF direct feedback: Problem
By default, LEC converts a DFF to a D-latch when
there is a direct feedback from the Q port to the D port
Causes mapping/comparing problem!
After LEC default modeling Designs with LEC constraint
CLK
B
A
DFF
D Q
CLK
B
A
DFF
D Q
Golden
CLK
DLAT
D Q
Revised
CLK
DFF
D Q
DFF direct feedback: Solution
Instruct LEC not to model a DFF with direct feedback into a D-latch:
After LEC default modeling Turned off default modeling
CLK
B
A
DFF
D Q
CLK
B
A
DFF
D Q
Golden
...
set flatten model nodff_to_dlat_feedback
...
...
set flatten model nodff_to_dlat_feedback
...
CLK
DFF
D Q
Revised
CLK
DLAT
D Q
Mapping process
Compare process
LEC
SETUP
Flatten golden and revised designs
Perform circuit modeling
Map key points (automatic by default)
Can turn off automatic mapping to read file containing
mapped key points
set system mode lec
...
set system mode lec
...
Modeling messages
LEC generates modeling messages after you
change mode to LEC
To get a list of modeling messages and their rule number
LEC> report message -model
To display a particular message with detail
LEC> report message -model -rule <rule#> -verbose
// Command: set system mode lec
// Processing golden ...
// Modeling golden ...
// Warning: converted 78 X assignment(s) as dont care(s)
// Processing revised ...
// Modeling revised ...
// Folded 340 dlat(s) into 170 dff(s)
// Processing golden ...
// Modeling golden ...
// Warning: converted 78 X assignment(s) as dont care(s)
// Processing revised ...
// Modeling revised ...
// Folded 340 dlat(s) into 170 dff(s)
Transcript window
LEC
SETUP
Mapping process
Compare process
Mapping process
Understanding mapping process
What are key points?
What is key point mapping?
Why is key point mapping necessary?
How is key point mapping done?
Resolve mapping issues
Mapping takes too long
Incomplete mapping
Logic cones
What are key points?
Key Points: primary inputs(PI), primary
outputs(PO), DFFs, D-latches, black boxes, Z
gates, cut gates
Design consists of combinational logic cones
bounded by key points
Key points
Pairing corresponding key points: PIs, POs,
DFFs, D-latches, black boxes, Z gates, cut gates
Golden Revised
Key points
Combinatorial logic
Why is mapping necessary?
So that corresponding combinational logic
cones are correctly paired
Golden Revised
Key points
Combinatorial logic
How is mapping done?
Name-based: Mapping based strictly on instance
pathnames (or net names) of key points
/core/fd0
Golden
DFF
D
CK
A
B
/core/fd0
Revised
DFF
D
CK
A
BB
Function-based: Mapping based on function and
structure of logic cones
/core/fd0
Golden
DFF
D
CK
A
B
/core_fd[0]
Revised
DFF
D
CK
A
B
Mapping options
LEC command to specify mapping options:
Syntax: set mapping method <mapping_option>
Can be applied in both SETUP and LEC modes
Available mapping options:
-noname
function-based -name guide
name-based
-name first (default)
-name only
name-based
function-based
function-based
name-based
Execute mapping method Followed by
Mapping options
Mapping messages
SETUP> set system mode lec
The following message is displayed during mapping:
...
// Processing Golden ...
// Modeling Golden ...
// Processing Revised ...
// Modeling Revised ...
// Mapping key points
// Warning: more than 1/3 of the key points have mis-matched names
// Warning: please use renaming rules if automatic mapping fails
// to finish
...
// Processing Golden ...
// Modeling Golden ...
// Processing Revised ...
// Modeling Revised ...
// Warning: please use renaming rules if automatic mapping fails
// to finish
Transcript window
Analyze mapping messages:
Problem: Mapping takes too long
Mapping seems to hang and LEC displays this message
Default mapping
Name-based followed by function-based mapping
Function-based mapping is taking a long time
...
...
...
...
Transcript window
Solution:
Interrupt the mapping process: Ctrl-C on UNIX terminal
Remap using the "name only method:
LEC> delete mapped points -all
LEC> set mapping method -name only
LEC> map key points
Mapping messages
The following message is displayed after mapping:
Transcript window
...
// Warning: Golden has 144 unmapped key points
// Warning: Revised has 144 unmapped key points
...
Unmapped points:
================================================================================
Golden:
--------------------------------------------------------------------------------
Unmapped points DFF Total
--------------------------------------------------------------------------------
Not-mapped 144 144
================================================================================
Revised:
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Not-mapped 144 144
================================================================================
// Warning: Key point mapping is incomplete
...
// Warning: Golden has 144 unmapped key points
// Warning: Revised has 144 unmapped key points
...
Unmapped points:
================================================================================
Golden:
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Not-mapped 144 144
================================================================================
Revised:
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Not-mapped 144 144
================================================================================
Incomplete mapping
Problem: Incomplete mapping
Mapping process ends with the message
Unmapped points must be resolved
Solution: Add renaming rule
Technique 1: Determine renaming rules from the Mapping
Manager
Technique 2: Write out unmapped points into files then
determine renaming rules from the files
Transcript window
...
...
...
...
Add renaming rule
Command usage:
add renaming rule <rule_id> <search_string> \
<replacement_string> [-golden | -revised]
Renaming rule structures
%d - matches 1 or more digits (0-9)
#(expr) - expr evaluates to a constant integer
%s - matches 1 or more alpha-numeric characters
Refer to the Reference Manual for more renaming structures
The escape character " \ "
You must prefix the following special characters with "\" if they
are used in the search_string as a normal character
% . * ^ $ | ( ) [ ] / \
Add renaming rule: Example
Unmapped points in Golden
/fifo_reg[0][0]
/fifo_reg[0][1]
/fifo_reg[0][2]
Unmapped points in Revised
/fifo_0__reg[0]
/fifo_0__reg[1]
/fifo_0__reg[2]
Matching the Revised key points to the Golden:
add renaming rule R1 "%d__reg\[%d\]" "reg[@1][@2]" \
-revised
Mapping Manager
Unmapped
Points
Mapped
Points
Compared
Points
Mapping
Manager
LEC
window
Categories of unmapped points
Extra: Key point that exists in only the Golden design or in
only the Revised design, but does not affect the circuit
functionality. Example: scan_in, scan_out
Unreachable: Key point that is not propagated to any
observable point. Example: spare flops
Not-mapped: Key point that has no correspondence on the
other side. May be resolved with renaming rules
(red-filled circle)
Note: To view a list of unmapped points, enter:
LEC> report unmapped points
Resolving incomplete mapping:
Technique 1
Using Mapping
Manager to
create
renaming rules
Tips
Preference Sort
by name
Class Disable All
Not-Mapped
Technique 2
Write out unmapped key points to files, then define
renaming rules based on the output files
Write out all unmapped key points as seen by LEC
LEC> test renaming rule -map
Transcript window
=========================================
Test name mapping results
----------------------------------------------
Golden-Revised pair: 25
PI: 21
PO: 2
DFF: 2
Golden-Revised group: 15 (280 key points)
Golden single: 10
Revised single: 12
=========================================
=========================================
Test name mapping results
----------------------------------------------
Golden-Revised pair: 25
PI: 21
PO: 2
DFF: 2
Golden-Revised group: 15 (280 key points)
Golden single: 10
Revised single: 12
=========================================
Technique 2 (cont'd)
LEC> test renaming rule -print group -file \
group.list -replace
Key point groups: 15
(G) 437 DFF /syndrm/macreg/q_reg[4]
(R) 383 DFF /syndrm/macreg/q_reg(4)/g2/i0
(G) 445 DFF /syndrm/macreg_1/q_reg[4]
(R) 463 DFF /syndrm/macreg_1/q_reg(4)/g2/i0
...
Key point groups: 15
...
Content of group.list:
LEC> test renaming rule -print single -file single.list \
-replace
Content of single.list:
Technique 2 (cont'd)
Golden un-grouped single key point: 10
(G) 2554 DFF /rtn_data/xramBO_reg_2_/U$1
(G) 2556 DFF /rtn_data/xramBR_reg_31_/U$1
...
Revised un-grouped single key point: 12
(R) 6993 DFF /array_byte_reg_7_/Vpx/U$1/i0
(R) 6994 DFF /base_addr1_reg_9_/Vpx/U$1/i0
(R) 6996 DFF /request_reg_16_/Vpx8/U$1/i0
...
Golden un-grouped single key point: 10
...
Revised un-grouped single key point: 12
(R) 6994 DFF /base_addr1_reg_9_/Vpx/U$1/i0
(R) 6996 DFF /request_reg_16_/Vpx8/U$1/i0
...
Based on "single.list" and "group.list", new renaming rules
can be created to make the mapping more name-based.
Mapping is an iterative process
Iterative process
Add rules incrementally
Continue the mapping process with command:
LEC> map key point
Note: LEC will skip the existing mapped points
Example:
LEC> add renaming rule rule1 ...
LEC> map key points
...
LEC> map key points
...
Notes on renaming rules
Rules are order dependent
To view rules:
report renaming rule
To delete a rule:
delete renaming rule <rule_id>
"test renaming rule" can test:
A rule before adding
All rules added
Built-in renaming rules
Renaming Rule GUI window can be used to edit rule(s)
Test renaming rule
Test a renaming rule before adding it
Syntax:
test renaming rule <test_string | -gate_id <gate_id>> \
-new_rule <search_string> <replace_string>
Example:
LEC> test re r abc -new "abc$" "xyz"
Add the rule when the intended result is achieved
LEC> add re r rule0 "abc$" "xyz" -revised
===================================
Transcript window
===================================================================
Original string Substituted string Result
-------------------------------------------------------------------
abc
abc$ xyz xyz
===================================================================
================================
-------------------------------------------------------------------
abc
abc$ xyz xyz
===================================================================
Test renaming rule (cont'd)
Test all added renaming rules
Renaming rules are order dependent
Syntax:
test renaming rule <test_string | -gate_id <gate_id>>
Example:
LEC> add re r rule1 "xyz$" "C" -map -revised
LEC> test re r abc -revised
Transcript window
============================================================================
----------------------------------------------------------------------------
abc
rule0 abc xyz xyz
rule1 xyz C C
============================================================================
============================================================================
----------------------------------------------------------------------------
abc
rule0 abc xyz xyz
rule1 xyz C C
============================================================================
Built-in renaming rules
Built-in renaming rules (version 3.4.0.a or later)
resolve the following renaming rule issues:
Array delimiters: [ ], _ _, < >, ( )
Hierarchical separator: _, /
Extraneous digits: reg%d_%d
Multiple always blocks
Renaming Rule GUI window
You can add, test, and edit rules in the
Renaming Rule GUI window
Exercise
Define renaming rules to match the following Golden/Revised key
points pairs
Golden
/u0/u1/c_reg[5]
Revised
/u0/c_reg(5)/I1/U$1
answer: add renaming rule r1 "u1\/" "" -golden
Note: Trailing characters for library cells are tripped automatically ( /I1/U$1 )
Golden
/u0/u1/c_reg[1]
Revised
/u0_u1_c_.ram1_reg
answer: add renaming rule _____________________________________________
Golden
/u0/b_reg[24]
Revised
/u0/b_2_reg[22]
answer: add renaming rule
Solutions are in the back of this manual
1
2
3
Add renaming rule: Module pins
Problem: Black box pins not mapped due to
name differences
Solution: Apply renaming rule to the pin
Syntax: add renaming rule name_name \
<search_string> <replace_string> -pin -bbox \
<module_name> [-golden|-revised]
Summary
Once you are satisfied with the mapping results,
you can incorporate all renaming rules into
your dofile
add renaming rule rule0 "abc" "xyz" -map -revised
add renaming rule rule1 "xyz" "C" -map -golden
set system mode lec
...
set system mode lec
...
Mapping process
Compare process
LEC
SETUP
Compare process
Understanding compare process
How is state element handled?
What are the compare points?
What is being compared?
How is state element handled?
No connection between input and output
Think of a D-latch or a DFF being cut in halves
Input and output are verified separately
D
Q
What are compare points?
Compare points are:
Sink points of logic cones
Primary outputs, cut gates, DFFs, D-latches, and black
boxes
D
Q
DFF
/fd0
IN_0
IN_1
OUT_0
OUT_1
BLACK BOX
/bb0
PO
What is being compared?
Corresponding combinational logic cones
Golden Revised
Two designs are equivalent when all corresponding
cones are equivalent
Comparing
Consider all successfully mapped points for comparison
Comparison is an iterative process
LEC remembers points already compared equiv/non-equiv
Can interrupt with "Ctrl-C" to change compare options
To continue the compare process, enter "compare"
set system mode lec
add compare points -all
compare
...
set system mode lec
compare
...
Comparison results
The following message is displayed after comparing:
Transcript window
...
// Command: compare
================================================================================
Compared points PO DFF DLAT BBOX Total
--------------------------------------------------------------------------------
Equivalent 2 146 2 1 151
--------------------------------------------------------------------------------
Non-equivalent 0 2 0 0 2
================================================================================
...
// Command: compare
================================================================================
Compared points PO DFF DLAT BBOX Total
--------------------------------------------------------------------------------
Equivalent 2 146 2 1 151
--------------------------------------------------------------------------------
Non-equivalent 0 2 0 0 2
================================================================================
Comparison results in GUI
Filtering comparison results on the Mapping Manager
Categories of comparison results
Equivalent: Key points proven to be equivalent (green-filled
circle)
Inverted-Equivalent: Key points proven to be
complementary (divided green-filled circle)
Non-Equivalent: Key points proven to be different (red-filled
circle)
Abort: Key points not yet proven equivalent or non-
equivalent due to timeout or other system parameters
(yellow-filled circle)
Not-Compared: Key points not yet compared
LEC> report compare data -class [...]
Diagnose smaller cone first
Using the Mapping Manager to sort key points by
supporting size
Concentrate on one logic cone at a time
Debugging tools
Diagnosis Manager
Schematic Viewer
Source Code Manager
Gate Manager
Sort key point by supporting size
Left-click to select
a compared point.
Then right-click to
select "Sort by
Support Size
from pull-down
menu
Invoking the Diagnosis Manager
Left-click to select
a non-equivalent
point (red-filled
circle).
Then right-click,
choose "Diagnose"
Diagnosis Manager
Non-corresponding,
and not mapped (red)
Non-corresponding, but
mapped (yellow with M)
M
Compared Point
Diagnosis Point (Active)
Diagnosis Points
Corresponding Support
Non-corresponding Support
Error Patterns Error Candidates
Diagnosis information
Compared Point: Non-equivalent compared point
Diagnosis Point (Active): Point at which diagnosis failed. Simulation
value shown in parenthesis ( )
Diagnosis Point (Inputs): Lists all the fanin diagnosis points for the
compare point
Corresponding Support: Displays the mapped points that are in the fanin
cone of the diagnosis point of both the Golden and Revised designs.
Simulation values of the corresponding support points are shown along with
the key point names
Non-corresponding Support: Displays the mapped or unmapped points
that are in the fanin cone of the diagnosis point for either the Golden or
Revised designs. Simulation values of the non-corresponding support points
are shown along with the key point names
Error Pattern: Test vector proving the diagnosis point to be non-equivalent
Error Candidate: Gates in the Revised with highest probability of causing
non-equivalence
Diagnosis information
0
0
seq0
Q
A
D
1
1
1
1
0 0
1
1
D
DFF
CP
D
Q
seq0
Q
A
1 1
1
1
DFF
CP
D
Q
1
seq1
1
Q D
1
GOLDEN
DFF
CP
Corresponding Support Diagnosis Input Compare Points
seq1
Q
DFF
REVISED
CP
Path to Error Candidate
(highlighted)
Non-corresponding
Support
B
Error Candidate
Diagnosis Manager: New features
Color coding for
corresponding support
points
Cross highlighting of
support key point and error
pattern
Note: These features are only
available to LEC 3.3.1.a or later
Schematic viewer
Diagnosis Manager
Can invoke the Source
Code Manager by double
clicking on any gate
Schematic Tool Bar
Last View : Return to the previous schematic view
Zoom to Full : Display all the contents of the schematic
Push View Up : Displays the parent level hierarchy
Push View Down : Displays the lower level of hierarchy
Trace Load : Highlight the load in red
Trace Driver : Highlight the driver in yellow
Trace 2 Points : Trace path between 2 points in the schematic
Prove : Prove equivalency between 2 points in the schematic
Find : Find and highlight the specified object
Note: Trace 2 Points and Prove are only available in the Flatten Schematics.
Source Code Manager
Corresponding
gates on
Golden and
Revised are
highlighted
Signal can be
traced across
modules
Gate Manager
Can be used to browse design connectivity
Mapping process
Compare process
LEC
SETUP
LEC run statistics
Report:
Total CPU runtime
Memory usage
add renaming rule rule0 "abc "xyz" -map -revised
set system mode lec
compare
usage
...
add renaming rule rule0 "abc "xyz" -map -revised
set system mode lec
compare
usage
...
LEC usage
Introduction to LEC
LEC flow
Introduction
What is Hierarchical Compare?
Flow of Hierarchical Compare
Setup for Hierarchical Compare
Skipped modules in Hierarchical Compare
Cross-boundary optimization
What is Hierarchical Compare?
TOP
U3
U1 U2
U4
A B
TOP
U3
U1 U2
U4
X
Golden Revised
A bottom-up, module-by-module comparison
Requirement: Designs must contain some hierarchy
Benefits: Shorter runtime, easier to debug
Automatic: Tool-generated script or dofile
Flow
TOP
U3
U1 U2
U4
A B
TOP
U3
U1 U2
U4
X
Golden Revised
1) Set root module to U1 Compare U1 Save U1 Result
Black Box U1
Black Box U2
Black Box U3
Black Box U4
5) Set root module to TOP Compare TOP Save TOP Result
Note: Modules U4 and their sub-modules will be compared flat
Setup for Hier Compare:
A typical dofile
set log file hier.log -replace
read design rtl.v -verilog -gold
read design -file verilog.vc gate.v -rev
add renaming rule rule0 "abc" "xyz" -map -rev
//
// --- running in flat comparison mode
//
// set system mode lec
// add compare points -all
// compare
// usage
//
// --- running in hierarchical mode ---
//
write hier dofile hier.dofile -replace
dofile hier.dofile
read design rtl.v -verilog -gold
read design -file verilog.vc gate.v -rev
add renaming rule rule0 "abc" "xyz" -map -rev
//
// --- running in flat comparison mode
//
// set system mode lec
// add compare points -all
// compare
// usage
//
// --- running in hierarchical mode ---
//
write hier dofile hier.dofile -replace
dofile hier.dofile
Tool-generated file: hier.dofile
...
// Comparing module U1
set root module U1 -golden
set root module U1 -revised
report black box -NOHidden
set system mode lec
compare
save hier_compare result
set system mode setup
add black box U1 -module -golden
add black box U1 -module -revised
set system mode lec
compare
...
...
set system mode lec
compare
set system mode lec
compare
...
Constraint propagation
Revised Golden
U1
TOP
U2 U2
U1
TOP
SE_0
SE_1
SE_2
SE_3
scan_en
Automatic propagation to all lower-level modules
Constraint values
Pin equivalence relationships
read design rtl.v -verilog -golden
read design -file verilog.vc gate.v -revised
write hier dofile hier.dofile -constraint -noexact -replace
dofile hier.dofile
dofile hier.dofile
Resulting hier.dofile
...
//
//
add pin equivalences SE_0 SE_1 -revised
add pin constraint 0 SE_0 -revised
set system mode lec
compare
save hier_compare lec result
...
...
//
//
add pin constraint 0 SE_0 -revised
set system mode lec
compare
save hier_compare lec result
...
Skipped modules
Hierarchical script generation may skip modules
due to:
Module name mismatch
Extra ports
Non-compatible instantiation
Unbalanced instantiation
Attempt to maximize hierarchical comparison by
reducing skipped modules to:
Minimize runtime
Isolate abort modules
Isolate non-equivalent points
Module mapping
Pairing modules with the same module names
Golden Revised
ABC ABC
XYZ XYZ
TOP TOP
Module name mismatch: Problem
Module names change due to uniquification during
synthesis or backend flow
Golden Revised
ABC
TOP
XYZ XYZ
ABC_scan
TOP
XYZ_0 XYZ_1
SETUP> write hier dofile hier.dofile -constraint -noexact
Transcript Window
// Warning: Module name XYZ exists in Golden design only
// Warning: Module name ABC exists in Golden design only
...
...
// Warning: Module name XYZ_0 exists in Revised design only
// Warning: Module name ABC_scan exists in Revised design only
// Warning: Module name XYZ exists in Golden design only
// Warning: Module name ABC exists in Golden design only
...
...
// Warning: Module name ABC_scan exists in Revised design only
Module name mismatch: Solution
Method 1:
Use module renaming rule to fix module name differences
add renaming rule m1 "%s_%d$" "@1" -module -revised
add renaming rule m2 "%s_scan$" "@1" -module -revised
dofile hier.dofile
add renaming rule m1 "%s_%d$" "@1" -module -revised
add renaming rule m2 "%s_scan$" "@1" -module -revised
dofile hier.dofile
Method 2:
Use uniquify command (explained later)
SETUP> uniquify XYZ -golden
Extra ports
If you use the constraint option and this removes
extra ports, module may be compared
Most common examples are scan ports and CT insertion
Bit Blasting - Array ports changed to single ports
d_in[7:0] => d_in_7, d_in_6, ...
read design -file verilog.vc gate.v -ver -rev
add renaming rule m1 %s_%d$ @1 -module -revised
add renaming rule m2 %s_scan$ @1 -module -revised
add renaming rule r1 "d_in\[%d\]" "d_in_@1" -pin -bbox <module_name>
write hier dofile hier.dofile -constraint -replace
dofile hier.dofile
add renaming rule m1 %s_%d$ @1 -module -revised
add renaming rule m2 %s_scan$ @1 -module -revised
add renaming rule r1 "d_in\[%d\]" "d_in_@1" -pin -bbox <module_name>
dofile hier.dofile
Conflicting instantiation: will skip module foo
Non-compatible instantiation:
Problem
Golden Revised
foo: i_0
foo: i_1
foo_0: i_0
foo_1: i_1
Transcript Window
...
// Warning: Module foo and foo_0 have non-compatible instantiations
...
Use uniquify command
Module foo is replaced by foo_0 and foo_1
Determine names by looking at the other design
Non-compatible instantiation:
Solution
Golden Revised
foo: i_0
foo: i_1
foo_0: i_0
foo_1: i_1
foo_0: i_0
foo_1: i_1
uniquify foo -golden
dofile hier.dofile
uniquify foo -golden
dofile hier.dofile
Transcript Window
Unbalanced instantiation: Problem
Hierarchical script will skip module B
A
B
B
C
A
B
B
Golden Revised
// Warning: Module B used in Golden module A 1 times, but in Revised
module A 2 times (non-balance). Skip B
...
1 modules are not output for hierarchical compare due to non-balanced
instantiations
...
// Warning: Module B used in Golden module A 1 times, but in Revised
module A 2 times (non-balance). Skip B
...
1 modules are not output for hierarchical compare due to non-balanced
instantiations
...
Transcript Window
Unbalanced instantiation: Solution
A
B
B
C
A
B
B
Revised
B
B
A
Golden
resolve C -golden
dofile hier.dofile
resolve C -golden
dofile hier.dofile
Cross-boundary optimization
Golden
U2
U1
Revised
A
B
TOP
U1
A
U2
TOP
User might allow logic to move across module
boundary during synthesis optimization
False negative during LEC hierarchical compare
Miscompare U2 at point A and U1 at point B
Two forms of logic rearrangement:
Simple inverter
All other cases
U2
U1
Golden
A
Revised
U2
U1
A_BAR
TOP TOP
Logic rearrangement - Case 1: Simple
inverter
Inverters moved across module boundary
Must set naming rule before read library/design
LEC maintains inversion relationship
set naming rule _BAR -inverted_pin -golden
dofile hier.dofile
set naming rule _BAR -inverted_pin -golden
dofile hier.dofile
TOP
U2
U1
Golden
Revised
TOP
A
A
U2
U1
Logic rearrangement - Case 2: General
logic
Block of logic moved across module boundary
User specifies no compare at U2 level
Logic of U2 is considered at U1 level
add noblack box U2 both
dofile hier.dofile
add noblack box U2 both
dofile hier.dofile
Hierarchical Compare
Exercise answer
1. Add re r r1 "u1\/" "" -gold /u0/c_reg[5]
2. Add re r r2 "c_\.ram%d_reg" "c_reg[@1]" -rev /u0_u1_c_reg[1]
3. Add re r r3 "b_%d_reg\[%d\]" "b_reg[#(@1+@2)]" -rev /u0/b_reg[24]
Final names Renaming rules
Lab 1
Objective: Read VHDL and Verilog designs, and libraries
1. UNIX % cd ~/lec_labs/setup/single_language
2. Type "lec" to start GUI LEC
3. Read VHDL design (./RTL/mult_sign_oper.vhd) along with its pkg
libraries all in one command. mult_sign_oper.vhd uses DPAK_LIB,
FCTN_LIB, and IEEE libraries.
Use the mapfile option to map the file
./vhdl_lib/dpak_unit/minimum_pkg.vhd for DPAK_LIB library
Use the map option to map the whole directory ./vhdl_lib/common/ for
FCTN_LIB library.
4. Read the library ./verilog_lib/lib.v for the revised design
5. Read the revised design ./synthesis/multiplier_oper.gate.v
6. Click LEC icon to switch to LEC mode
7. Compare design from Run Menu
8. Use File Menu to save the commands you entered into a dofile. Exit LEC
from File Menu
Note: Solution is in the back of the manual and current working directory
Lab 2
Objective: Black box library modules; read libraries
and design using Verilog command file
1. UNIX% cd ~/lec_labs/setup/vcfile_bbox
2. Create Verilog command files to:
a. Read in Golden design (./RTL/golden.v) and its library elements in
./lib/std/ and ./lib/mem/ directories
b. Read in Revised design (./GATES/revised.v) and its library
elements in ./lib/std/ and ./lib/mem/ directories
3. Start LEC
4. Issue commands to black box library modules that have "rom" and "ram" in
their names (for both Golden and Revised)
5. Read Golden design and libraries via Verilog command file format
6. Read Revised design and libraries via Verilog command file format
7. Exit LEC
Lab 3
OBJECTIVE: Add renaming rule(s) to complete
mapping key points
1. Unix % cd ~/lec_labs/mapping/renaming1, start LEC
2. Execute the dofile init.dofile
4. Open the Mapping Manager to examine the unmapped points.
I w Main GU indow
Lab 3 (cont'd)
Sort key points by name to help determine the renaming rules (Preference
Sort by name)
5. Create renaming rules to resolve unmapped key points. After rule(s) are
specified, continue mapping with the command "map key point"
6. Make sure all key points are mapped
7. Exit LEC
Mapping Manager
Lab 4
OBJECTIVE: Debugging non-equivalent key points
1. Unix % cd ~/lec_labs/compare/compare1/, start LEC.
2. Execute the dofile init.dofile.
3. Invoke the Mapping Manager.
4. On the Mapping Manager, use "Class" pull-down menu to display only the non-
equivalent key points.
Mapping Manager
Lab 4 (cont'd)
5. Invoke the Diagnosis Manager for a non-equivalent key point.
6. Invoke the Schematic Viewer from the Diagnosis Manager.
Mapping Manager
Diagnosis Manager
Lab 4 (cont'd)
7. On the schematic you should see a simulation mismatch for the compare point.
Compare point is located at the right hand side of the schematics. Examine
the schematics to find the gate that causes the mismatch. That gate causing
the the mismatch is the three-input NOR gate on the Revised schematic.
8. Double click the NOR gate in the Revised design to go back to netlist.
6. Do the same to the Golden design on any gate.
7. Exit LEC and close all views.
Note: Solution is in the back of the manual and current working directory.
Lab 5
OBJECTIVE: Write dofile for hierarchical compare
1. Unix % cd ~/lec_labs/hier_compare/hier1, start LEC.
2. Read in golden.v for the Golden design.
3. Read in revised.v for the Revised design. The library lib.v is needed for the
Revised design.
4. Generate hierarchical compare script.
5. Execute hierarchical compare script.
Lab 6
OBJECTIVE: Module Mapping
1. Unix% cd ~/lec_labs/hier_compare/hier2, start LEC.
2. Read in golden.v for the Golden design.
3. Read revised.v for the Revised design. The library lib.v is needed for the
Revised design.
5. Fix module mapping problem with add renaming rule.
6. Re-generate hierarchical compare script.
Note: Make sure 5 modules are included in the generated script.
Lab solutions
Lab1
read design -vhdl ./RTL/mult_sign_oper.vhd -gold -map FCTN_LIB \
./vhdl_lib/common -mapfile DPAK_LIB \
./vhdl_lib/dpak_unit/minimum_pkg.vhd
read library verilog_lib/lib.v -revised
read design synthesis/multiplier_oper.gate.v -verilog -revise
set system mode lec
add compare point all
compare
Lab1
read design -vhdl ./RTL/mult_sign_oper.vhd -gold -map FCTN_LIB \
./vhdl_lib/common -mapfile DPAK_LIB \
./vhdl_lib/dpak_unit/minimum_pkg.vhd
read library verilog_lib/lib.v -revised
read design synthesis/multiplier_oper.gate.v -verilog -revise
set system mode lec
compare
Lab 2
add notranslate modules *rom* -library both
add notranslate modules *ram* -library both
read design golden.vc f golden.vc verilog -golden
read design revised.vc f revised.vc verilog -revised
set system mode lec
compare
Lab 2
add notranslate modules *rom* -library both
add notranslate modules *ram* -library both
read design golden.vc f golden.vc verilog -golden
read design revised.vc f revised.vc verilog -revised
set system mode lec
compare
Lab solutions
Lab3
read design golden_rtl.v verilog golden
read library lib.v verilog
read design revised_gate.v verilog revised
set mapping method name only
set system mode lec
add renaming rule R1 macreg_0%d macreg_@1 -revised
add renaming rule R2 hcount del_hcount -revised
add renaming rule R3 synvalid1\/regout synvalid1/del_regout -revised
map key points
Lab3
read design golden_rtl.v verilog golden
read library lib.v verilog
read design revised_gate.v verilog revised
set mapping method name only
set system mode lec
add renaming rule R1 macreg_0%d macreg_@1 -revised
add renaming rule R2 hcount del_hcount -revised
add renaming rule R3 synvalid1\/regout synvalid1/del_regout -revised
map key points
Lab4
Non-equivalent occurs in revised_gate.v when an "OR" gate is purposely replaced by a
"NOR" gate.
Lab4
Non-equivalent occurs in revised_gate.v when an "OR" gate is purposely replaced by a
"NOR" gate.
Lab solutions
Lab5
read design -golden golden.v -verilog
read library lib.v -verilog
read design -revised revised.v -verilog
write hier dofile hr.do -replace
dofile hr.do
Lab5
dofile hr.do
Lab6
// These renaming rules will fix module mapping problems
//add renaming rule rule1 %s_scan$ @1 -module -revised
//add renaming rule rule2 %s_%d$ @1 -module -revised
dofile hr.do
Lab6
// These renaming rules will fix module mapping problems
//add renaming rule rule1 %s_scan$ @1 -module -revised
//add renaming rule rule2 %s_%d$ @1 -module -revised
dofile hr.do
Sample flat compare dofile
Set log file logfile.$LEC_VERSION -replace
Add notranslate module *sram* -library -both
Read design cpu_rtl.v -verilog -golden
Read design -file verilog.vc -verilog revised
// Note: The read design above can be replaced by
// Any of the examples explained in this manual
Add pin constraint 0 scan_en -revised
Set flatten model -latch_fold
Set flatten model seq_redundant
Report floating signals -undriven -full both
Set mapping method -name only
//The above commands are the same for both flat and hier dofiles
Add renaming rule rule0 "abc" "xyz" -revised
Add renaming rule rule1 "xyz" "C" golden
// Note: The renaming rules above are for a particular case only
Set system mode lec
// Test renaming rule -design -all
// Test renaming rule -print group -file group.list
// Test renaming rule -print single -file single.list
Report mapped points > mapped.log
Report unmapped points -notmapped > unmapped.log
Add compare points -all
Compare
Report compare data noneq > noneq.log
Usage
// Note: The read design above can be replaced by
// Any of the examples explained in this manual
Add renaming rule rule0 "abc" "xyz" -revised
Add renaming rule rule1 "xyz" "C" golden
// Note: The renaming rules above are for a particular case only
Set system mode lec
// Test renaming rule -design -all
// Test renaming rule -print group -file group.list
// Test renaming rule -print single -file single.list
Report mapped points > mapped.log
Report unmapped points -notmapped > unmapped.log
Add compare points -all
Compare
Report compare data noneq > noneq.log
Usage
Sample Hier Compare dofile
//Note: The read design above can be replaced by
//Any of the examples explained in this manual
Add black box U2 -both
Write hier dofile hier.dofile constraint noexact -replace
dofile hier.dofile
Usage
//Note: The read design above can be replaced by
//Any of the examples explained in this manual
Add black box U2 -both
Write hier dofile hier.dofile constraint noexact -replace
dofile hier.dofile
Usage
Command overview
Add / Delete / Report Commands
General Commands
Add black box
Add compared points
Add instance constraints
Add noblack box
Add notranslate modules
Add pin constraints
Add pin equivalences
Add instance equivalences
Add renaming rule
Add tied signals
Report black box
Report compare data
Report compared points
Report design data
Report environment
Report floating signals
Report instance constraints
Report instance equivalences
Report library data
Report messages
Report modules
Report notranslate modules
Report noblack box
Report pin constraints
Report pin equivalences
Report rule check
Report renaming rule
Report statistics
Report tied signals
Report unmapped points
Compare
Dofile
Exit
Help
Map key points
Read design
Read library
Set flatten model
Set gui
Set log file
Set mapping method
Set system mode
Set undefined cell
Set undriven signal
Uniquify
Version
Test renaming rule
Usage
Delete black box
Delete compared points
Delete instance constraints
Delete mapped points
Delete noblack box
Delete notranslate modules
Delete pin equivalences
Delete pin constraints
Delete renaming rule
Delete tied signals
CADENCE CONFIDENTIAL 162 CADENCE DESIGN SYSTEMS, INC.
Conformal
LEC
Logic Equivalence Checker
Advanced Training Manual
Verplex
Systems, Inc.
Agenda
1. LEC-1 review
2. Mapping Problems
3. Debugging & Diagnosis Tips
4. Multipliers
5. Resolving abort key points
6. RTL coding guidelines
7. Labs
1. LEC-1 review
LEC-1 review
LEC flow
A typical LEC session (flat comparison)
Hierarchical comparison session
SETUP mode
LEC mode
Mapping process
Compare process
LEC flow
No
Equivalence Equivalence
established established
Differences ? Differences ?
Yes
All mapped ? All mapped ?
Specify constraints Specify constraints
& other parameters & other parameters
Golden Golden
Analyze Analyze
Yes
Debug Debug
Fix design Fix design
No
Revised Revised
Map key points Map key points
Compare key points Compare key points
ASIC
Lib
ASIC ASIC
Lib Lib
Setup
mode
LEC
mode
A typical LEC session (flat compare)
Executing mapping process
Executing comparison process
Reporting run statistics
LEC
SETUP
Hierarchical Comparison session
Generating a hierarchical compare script
Executing the hierarchical compare script
Analyzing comparison result
Reporting run statistics
LEC
SETUP
2. Problem of Mapping key points
Pairing corresponding key points: PIs, POs,
DFFs, D-latches, black boxes, Z gates, cut gates
Key points
Combinatorial logic
Mapping problem: Special cases
Black boxes
Module pins
Phase inversion
Mapping black boxes
Problem:
Module names are different (e.g, parameterized modules)
By default, LEC doesnt map black boxes of different module
names, even though instance names are the same
Solutions:
Manual mapping
Add mapping point <golden_bbox> <rev_bbox>
Turn off default mode:
set mapping method -nobbox_name_match
Match module names with renaming rule
add renaming rule <rule_id> <> <> -module
Mapping module pins
Problem:
Black box pins not mapped due to name differences
To see how the pins are mapped:
report map point <black_box> -input -output
Solution:
Apply renaming rule to the pin
Syntax: add renaming rule name_name \
<search_string> <replace_string> -pin -bbox \
<module_name> [-golden|-revised]
Phase inverted mapping: Problem
DFF/DLAT implemented with phase inverted library
cells (inverted data, set/reset swapping)
RST
D Q
R
S
IN OUT
CLK
U1_reg
RST
D Q
R
S
IN OUT
CLK
U1_reg
Golden
Revised
U1_reg must be phase-mapped
Phase inverted mapping: Solution
Enable phase map method
read design cpu_netlist.vg -verilog -revised
set mapping method -phase
set system mode lec
...
set system mode lec
...
Faster if phase map only applies on phase-inverted cells
add mapping model <cell_name* > -invert revised
set system mode lec
...
add mapping model <cell_name* > -invert revised
set system mode lec
...
Note: add mapping model command is not documented
3. Debugging & Diagnosis
Debugging non-equivalent key
points
Diagnosis tips
Diagnose smaller cone first
Using the Mapping Manager to sort key points
by supporting size
Concentrate on one logic cone at a time
Diagnosis tools
Diagnosis Manager
Schematic Viewer
Source Code Manager
Gate Manager
Diagnosis Manager
Compared Point
Diagnosis Point (Active)
Diagnosis Points
Corresponding Support
Non-corresponding Support
Non-corresponding,
and not mapped (red)
Non-corresponding, but
mapped (yellow with M)
M
Error Patterns Error Candidates
How do I debug from the Diagnosis
Manager?
Non-corresponding support points hint at setup or mapping
problems
Shows unconstrained signals (e.g., scan_en, undriven signals)
shows incomplete mapping, possible sequential optimization, merging,
and replication
Invoke the Schematic Viewer to view logic cones
Examine the simulation patterns in the corresponding supports
Look for common values in all reported test vectors
Examine non-equivalence support points (red color code)
need phase mapping?
incorrect mapping?
Invoke Schematic Viewer & Source Code Viewer to debug
Typical false non-equivalence: Setup
problems
Missing constraints
Need to disable scan-chain and JTAG test logic when
verifying normal mode of operation
Tie off undriven signals
Missing modeling directives
Modeling options are specific to synthesis tools and ASIC
library vendors. User must turn on appropriate modeling
directives
Example: Folding D-latch that models a DFF
More typical causes of false non-
equivalence
Unbalanced black-boxes
Use LEC commands :
report design data
report black box
Port order inverted for black-boxes (undefined cell)
set undef cell black -noascend
Not phase mapped
Phase map method is off by default for optimal runtime
Symptom shows non-equivalence on Data, Set, and Reset
cones
Can try prove <golden_ID> <revised_ID> -invert
Debug non-equivalence: Hierarchical
compare
Isolate problem module
Reduce cone size for easier debugging
Refer to Hierarchical Comparison section for how
to set up
4. Multipliers
Introduction
Multipliers can take a long time to compare due to
Unmatched architectures
Operand swapping
Solution:
Match multiplier architectures
Swap operands
DC synthesized multipliers
DesignCompiler
TM
uses DesignWare
TM
components
to implement arithmetic operators, comparators, etc.
assign z = a * b;
<mod>_DW02_mult U1 (.A(a), .B(b), .TC(1b0),
.PRODUCT(z));
Three DW multiplier architectures
Carry Save Adder (CSA): DW Basic
Wallace Tree (WALL): DW Foundation required
Non-Booth Wallace Tree (NBW): DW Foundation required
(new in DC 99.05)
Report architectures from DC command
dc_shell>report_resources
Explicit control of DC implementation
module foo (in1, in2, out);
input [9:0] in1, in2;
output [19:0] out;
// synopsys dc_script_begin
// set_implementation wall
// synopsys dc_script_end
assign out = in1 * in2;
endmodule
LEC understands this embedded script and will
create specified architecture
LEC also understands analogous VHDL syntax
Instantiated multiplier or divider
Multiplier or divider instantiated in RTL
DW02_mult #(A_width, B_width) U1 (.A(a),
.B(b), .TC(1b1), .PRODUCT(z);
DW02_divide #(A_width, B_width, TC_mode)U2
(.A(a), .B(b), .TC(tc),
.DIVIDE_BY_0(div_by_0),
.QUOTIENT(result));
LEC has a built-in representation for DW02_mult
and DW02_divide
Do not read in the simulation models (for example:
DW02_mult.v)
Long runtime due to multipliers?
Check to see if there are any multipliers in the design
LEC> report design data
Matched architecture will be compared faster
...
------ word-level --------------------------
ADD * 55 0
MULT * 3 0
BBOX 2 2
--------------------------------------------
Total
Transcript window
...
------ word-level --------------------------
ADD * 55 0
MULT * 3 0
BBOX 2 2
--------------------------------------------
Total 1058 1058
1058 1058
Matching multiplier architecture
Method 1: LEC commands
Automatic (recommended)
set multiplier option
Manual
set multiplier implementation
Method 2: Verplex directive
Hard-coded in RTL
LEC automatically
chooses best matching architecture
swaps the operand order if necessary
Requirement:
specify command: set multiplier option auto
version 4.0.1.a or later
multiplier module must have boundary
Advantage:
User doesnt need to know the revised architecture
Push-button solution
Disadvantage:
Doesnt work on multiplier with no module boundary
Matching multiplier architecture:
Automatic
User manually specifies
Which type of architecture to set
Operand swapping
Requirement:
Specify command:
set multiplier implementation <auto | CSA |
WALL | NBW | RCA | BKA>
auto default, choose NBW if combined input width < 52, WALL
otherwise
CSA, WALL, & NBW correspond to DC architectures
RCA Ripple Carry Adder
BKA BuildGate
TM
architecture
Command must be executed before the read design
command
Manual
Manual (contd)
Advantage
Doesnt require module boundary for multiplier modules
Disadvantage
Users knowledge of the Revised architecture
Verplex directive
module foo (a, b, c, d, out1, out2);
input [7:0] a, b, c, d;
output [7:0] out1, out2;
// verplex multiplier wall
assign out1 = a * b;
assign out2 = c * d;
endmodule
Only the next statement is affected by directive
Implement out1 with WALL architecture
out2 will use the default implementation
Operand swapping
Multiplier structures are not symmetric
Comparing multipliers with different operand order can also
take a long time
Synthesis tools might swap the operand order (usually
happens in VHDL)
set multiplier implementation [-noswap |
-swap | -autoswap]
noswap - do not swap operands
swap - swap operands
autoswap - first operand is the largest
Dont have to specify swapping if set multiplier
option auto command is used
May have to re-code RTL to control operand ordering
Isolating multiplier modules
Multiplier logic is complex and hard to
compare
Isolating to compare multiplier modules and
compare them separately can help the
compare process
Two ways to isolate multiplier modules
Flat compare: Black box multiplier modules and
compare separately
Hierarchical compare: Please refer to the
Hierarchical Compare section
5. Resolving abort key points
Introduction
What are abort points?
Investigate RTL causing abort
Dont Cares
Data Path
What to do if compare aborts:
Increase compare effort (first resort)
Partition large logic cones
Key point partition -automatic
Key point partition -manual
What are abort points?
Key points that have neither been proven
equivalent nor non-equivalent, based on the
current compare effort algorithms
Abort points can be attributed to large logic cone
sizes with large numbers of support points
Abort points can also be attributed to different
structures with dont care conditions (RTL-gate)
Investigating RTL dont cares
Please see RTL coding guideline section
Dont cares
Use LEC to report dont cares in logic cone:
report map point <abort_point> -property
Note: -property option is not documented
full case/parallel case/x-assignments are common source of
dont cares
re-coding RTL to get rid of dont cares might help
Investigating RTL data path
Operator ordering
Multiplier - refer to the Multiplier section
Operator ordering
LEC operator tree implementation
z = a * b * c * d; z = (a * b) * (c * d);
a b c d
z
a b c d
z
Operator ordering
Different logical structures can exacerbate situation
RTL ordering Netlist ordering
z = a * b * c * d; (a * b) * (c * d);
a b c d
z
a b c d
z
Changing RTL to match the netlist ordering can
make comparison faster
Identifying abort points in LEC
GUI: yellow-filled circle on Mapping Manager
Non-GUI: LEC> rep compare data -class abort
Abort key points
are shown with
yellow-filled circle
Resolving abort points:
Increase compare effort
Default compare effort: low
Can be changed to high or super
Should be used after low-effort run is completed (to avoid
"expensive" methods used on easy compare points)
read design -f verilog.vc -verilog -revised
set system mode lec
compare
//set compare effort auto will automatically switch to super compare
effort to aborted key points
report compare data -abort
set compare effort high
compare
...
set system mode lec
compare
//set compare effort auto will automatically switch to super compare
effort to aborted key points
compare
...
Resolving abort points:
Partition large logic cone
Key point partition - Automatic
Key point partition - Manual
Narrows down abort modules
Reduces logic cone size
Please refer to the Hierarchical Compare section
Key point partitioning
Divide-and-conquer approach to verifying large logic cones
0
Iteration 1
AB = 00
0
0
1
Key points are selected by LEC or users
LEC automatically generates a dofile that executes the
above iterations
Iteration 2
AB = 01
0
1
1
Iteration 3
AB = 10
1
Iteration 4
AB = 11
Key point partitioning: Automatic
set system mode lec
compare
compare
report compare data -abort > aborts.high
set compare option -partition key //This command is not documented
compare
set system mode lec
compare
compare
report compare data -abort > aborts.high
set compare option -partition key //This command is not documented
compare
LEC can select partition key points automatically
set compare option -partition <flow | key>
flow allows LEC to select points inside the cloud of logic
key will limit partition points to inputs to logic cone
Note: This command is not documented
...
...
Key point partitioning: Manual
set system mode lec
compare
add partition key_point -pin a b
write partition dofile partition.dofile -replace
dofile partition.dofile
...
set system mode lec
compare
add partition key_point -pin a b
write partition dofile partition.dofile -replace
dofile partition.dofile
...
When should I manually partition the key points?
When automatic selection does not work to your satisfaction
Criteria in selecting key points:
Support points of aborted cones
Key points that are already proven equivalent
Contents of partition.dofile
// Iteration 1
//
delete pin constraint a -golden
delete pin constraint a -revised
delete pin constraint b -golden
delete pin constraint b -revised
add pin constraint 0 a -golden
add pin constraint 0 a -revised
add pin constraint 0 b -golden
add pin constraint 0 b -revised
set system mode lec
compare
//
// Iteration 2
//
set system mode lec
compare
// Iteration 1
//
set system mode lec
compare
//
// Iteration 2
//
set system mode lec
compare
// Iteration 3
//
set system mode lec
compare
//
// Iteration 4
//
set system mode lec
compare
// Iteration 3
//
set system mode lec
compare
//
// Iteration 4
//
set system mode lec
compare
6. RTL coding guidelines to
optimize equivalence checking
Introduction
The following RTL coding guidelines can be used to
improve the performance of the equivalence
checking process
Keep difficult arithmetic blocks separate
Assign known values to all cases in case statement
Use more assign statements
Avoid combinatorial feedback loops
Following the guidelines helps reduce problems
described in sections:
Multipliers
Comparison: Debugging non-equivalent compare points
Resolving abort key points
Keep difficult arithmetic blocks separate
Arithmetic blocks such as multipliers tend to
produce longer runtime, more difficult mapping,
abort points (more than random logic blocks)
Complexity dramatically increases when these
multipliers are buried within a flattened design
When kept in their own hierarchy, verification
stands a much better chance of completion through
module-based (hierarchical) comparison mode
Assign known value to all cases in
case statement: Problem
Applying synthesis full_case directive or X assignments on
incompletely specified case statements creates "dont care" (DC)
conditions in LEC
LEC creates DC circuitry to ignore comparison of unspecified states
DC circuitry grows with greater numbers of unspecified states
Bigger DC circuitry leads to longer LEC runtime
Module xyz (sm, out);
input [1:0] sm;
output out;
reg out;
always @(sm)
case (sm) //synopsys full_case
2b00: out = 2b01;
2b01: out = 2b10;
2b11: out = 2b00;
endcase
endmodule
01
10
00
11
DC
Assign known value to all cases in
case statement: Solution
Use "default" with known value to catch all unspecified
conditions
Using default with known value does not necessarily
impact synthesis performance in area/speed optimization
Note: Refer to an Esnug paper on "full_case parallel_case", the Evil Twins of Verilog Synthesis by Cliff
Cummings, Sunburst Design, Inc.
Module xyz (sm, out);
input [1:0] sm;
output out;
reg out;
always @(sm)
case (sm)
2b00: out = 2b01;
2b01: out = 2b10;
2b11: out = 2b00;
default = 2b00;
endcase
endmodule
01
10
00
11
0 0
Using more assign statements
Break down the size of logic cones
Improve compare performance with smaller intermediate
cones
Easier to diagnose with more intermediate similarity points
assign pmo = (((x * y) & mask) + offset);
assign p = (x * y);
assign pm = (p & mask);
assign pmo = (pm + offset);
Golden Revised
Golden Revised
Before
After
Avoid combinatorial feedback
Combination feedback loops can hinder
verification process
LEC must insert cut gate to break the loops
Hard to match point of cut in the Golden and the
Revised loops
For difficult cases, user has to specify where to
insert cut gate
7. Labs
Lab 1
OBJECTIVE: Add renaming rule(s) to complete
mapping key points
1. Unix % cd ~/lec2_labs/mapping/key_point_mapping, start
LEC.
2. Execute the dofile init.do.
4. Open the Mapping Manager to examine the unmapped points.
Main GUI window

8. Labs
Lab 1 (contd)
Sort key points by name to help determine the renaming rules (Preference
Sort by name)
5. Create renaming rules to resolve unmapped key points. After you
specify rules, continue mapping with the command map key point
6. Make sure all key points are mapped
7. Exit LEC
Note: Solution is at the end of this section and current working directory
Mapping Manager
8. Labs
Lab 2
OBJECTIVE: Mapping black box pins
1. Unix % cd ~/lec2_labs/mapping/pin_mapping, start LEC.
4. Specify rep compare data -class nonequivalent and check the
report to see that the black box
bridge/pci_target_unit/fifos/pcir_ram is non-equivalent due to non-
corresponding inputs (input pins not being mapped).
5. Report black box pin mapping with the command rep mapped point
<black_box> -input -output. Input pins that have no correspondence need
to be mapped
6. Delete the mapped black box with the command delete mapped point
<black_box>. Pins are only mapped while the black box is being mapped, so
we need to re-map the black box so that the unmapped pins can be mapped.
7. Specify renaming rules to map the pins that werent mapped, and then re-
map the black box with the command map key point.
8. Labs
Lab 2 (contd)
8. Specify rep mapped point <black_box> -input -output
again to verify that the pins indeed mapped (paired) after you specified
renaming rules.
9. Compare to verify the problem is fixed:
a) LEC> add compare point -all
b) LEC> compare
c) LEC> report compare data -class nonequivalent
10. Exit LEC.
Note: Solution is at the end of this section and current working directory.
8. Labs
Lab 3
OBJECTIVE: Debug non-equivalent key points
through the Diagnosis
Manager
1. Unix % cd ~/lec2_labs/debug_neq/neq_mapping, start LEC.
4. On the Mapping Manager, use "Class" pull-down menu to display only
the non-equivalent key points.
Mapping Manager
8. Labs
Lab 3 (contd)
5. Invoke the Diagnosis Manager for a non-equivalent key point and try to
figure out what the problem is. (Hint: Non-corresponding points . . . possible
mapping problem?)
6. Fix the problem:
a) Delete mapped points with the command delete mapped points.
b) Specify renaming rules.
c) Run the compare process again. Verify that the design is 100% equivalent.
7. Exit LEC.
Note: Solution is at the end of this section and current working directory.
Mapping Manager
8. Labs
Lab 4
1. Unix % cd ~/lec2_labs/debug_neq/cone_partition, start
LEC.
4. On the Mapping Manager, use "Class" pull-down menu on the Mapping
Manager to display only the non-equivalent key points.
Mapping Manager
8. Labs
Lab 4 (contd)
5. a) Invoke the Diagnosis Manager to diagnose the non-equivalent key
point:
bridge/configuration/pci_err_data_reg[31].
b) In the Non-corresponding Support section, toggle the simulation value for
each non-corresponding support point (OUT and Z). OUT is the output
pin
of a BBOX.
Look for any simulation value changes at the
Diagnosis Point (active) after toggling.
Mapping Manager
Diagnosis Manager
8. Labs
Lab 4 (contd)
6. Invoke logic cones schematic from the Diagnosis Manager.
7. Starting from the compare point (dark blue DFF), trace the fan-in logic
to find the source of the logic difference. LEC (3.4.0.a or later) trims the
similar logic for easier debugging, but it might be hard to see the logic
connection at first. To have LEC open more gates to get a better picture of
the circuit, click to highlight the compare point then right click Fan-in Cone
Close Right click again Fan-in Cone Open to EQ/Key Points. Do
this for both the Golden and the Revised schematics.
Diagnosis Manager
8. Labs
Lab 4 (contd)
8. Exit LEC when done debugging.
Note: Solution is at the end of this section and current working directory
8. Labs
Lab 5
OBJECTIVE: Map modules with renaming rules
1. Start LEC: Unix% cd
~/lec2_labs/hier_compare/mod_map_renaming
2. Read golden.v for the Golden design.
3. Read the Revised library lib.v.
4. Read revised.v as the Revised design.
6. Use add renaming rule to map all modules (5 modules).
7. Regenerate the hierarchical compare script.
Verify that the generated script includes 5 modules for hierarchical
compare.
Note: The solution is at the end of this section and current working
directory.
8. Labs
Lab 6
OBJECTIVE: Map modules with uniquify
command
1. Start LEC :
Unix% cd ~/lec2_labs/hier_compare/mod_map_uniquify
2. Read golden.v for the Golden design.
3. Read the Revised library lib.vpx.v.
4. Read revised.v as the Revised design
6. Instead of using add renaming rule, use uniquify command to
fix mapping problem for the modules being instantiated more than once (7
modules).
7. Re-generate hierarchical compare script.
Verify that the generated script includes 7 modules for hierarchical
compare.
Note: The solution is at the end of this section and current working
directory.
8. Labs
Lab 7
using
hierarchical compare
technique
1. Unix % cd ~/lec2_labs/debug_neq/debug_via_hier, start
LEC.
3. Try debugging to pinpoint the error gate.
4. If you havent pinpointed the error gate, try narrowing down the
non-equivalent module using a hierarchical compare.
a) Switch to SETUP mode.
b) set gui off
c) Generate a hierarchical compare script, and then execute the script.
Note that one module will be reported non-equivalent.
5. Set root module to the non-equivalent module, and then start
comparing this module flat.
8. Labs
Lab 7 (contd)
Sort the non-equivalent key points by size with the command:
diagnose -summary -sort size.
From the report, find the key points with smaller cone size to
diagnose. Note these key points by their ID number, and then invoke
the Mapping Manager to start the diagnosis process. From the
schematic window, you should be able to see that the Revised design
has an extra inverter.
7. Exit LEC.
Note: Solution is at the end of this section and current working
directory.
8. Labs
Lab solutions
Lab1: Add renaming rules to complete mapping key points
add notranslate module regfile_9x30 regfile_9x64 -lib
read library lib/baselib.v lib/lib.v lib/regfile_9x30.v lib/regfile_9x64.v
read design golden.v
read design revised.v -rev
set undriven signal 0
add pin constraint 0 scan_en -rev
set mapping method -name only
set system mode lec
add renaming rule R1 \/ _ -gold
add renaming rule R2 \/ _ -rev
map key point
Lab1: Add renaming rules to complete mapping key points
add notranslate module regfile_9x30 regfile_9x64 -lib
read library lib/baselib.v lib/lib.v lib/regfile_9x30.v lib/regfile_9x64.v
add pin constraint 0 scan_en -rev
set mapping method -name only
set system mode lec
add renaming rule R1 \/ _ -gold
add renaming rule R2 \/ _ -rev
map key point
8. Labs
Lab solutions
Lab 2: Mapping black box pins
add notranslate module DP_SRAM*
add search path ./rtl/ -gold
read library lib/*.v -gold
read design -f rtl/filelist -root PCI -gold
read library lib/lib.vpx.v -rev
read design gate/PCI.gv -root PCI -rev
set flatten model -nodff_to_dlat_feedback
add renaming rule R1 reg_%d reg[@1] -rev //this rule speeds up the mapping process
add renaming rule R2 in_I in -pin -bbox DP_SRAM_ADDR_LENGTH5_SIZE32_1 -rev
add renaming rule R3 inA in -pin -bbox DP_SRAM_ADDR_LENGTH5_SIZE32_1 -rev
set sys mode lec
add compare point -all
compare
Lab 2: Mapping black box pins
add renaming rule R2 in_I in -pin -bbox DP_SRAM_ADDR_LENGTH5_SIZE32_1 -rev
add renaming rule R3 inA in -pin -bbox DP_SRAM_ADDR_LENGTH5_SIZE32_1 -rev
set sys mode lec
compare
8. Labs
Lab solutions
Lab 3: Debug non-equivalent key points through the Diagnosis Manager
add renaming rule R2 isr_bit3_0_reg%d_%d isr_bit3_0_reg[@2] -rev
set sys mode lec
compare
Lab 3: Debug non-equivalent key points through the Diagnosis Manager
add renaming rule R2 isr_bit3_0_reg%d_%d isr_bit3_0_reg[@2] -rev
set sys mode lec
compare
8. Labs
Lab solutions
Lab 4: Debug non-equivalent key points
The output data_out[31]the BBOX bridge/pci_target_unit_fifos/pciw_ram is disconneted
on the revised design.
Lab 4: Debug non-equivalent key points
The output data_out[31]the BBOX bridge/pci_target_unit_fifos/pciw_ram is disconneted
on the revised design.
8. Labs
Lab solutions
Lab5: Mapping modules with renaming rules
read library lib.v -rev
add renaming rule R1 %s_scan$ @1 -module -rev
add renaming rule R2 %s_%d$ @1 -module -rev
write hier dofile hier.do -noexact -constraint -replace
//dofile hier.do
Lab5: Mapping modules with renaming rules
read library lib.v -rev
add renaming rule R1 %s_scan$ @1 -module -rev
add renaming rule R2 %s_%d$ @1 -module -rev
//dofile hier.do
Lab 6: Mapping modules with uniquify command
read library lib.vpx.v -rev
uniquify lrp -gold
uniquify burp -gold
//dofile hier.do
Lab 6: Mapping modules with uniquify command
read library lib.vpx.v -rev
uniquify lrp -gold
uniquify burp -gold
//dofile hier.do
8. Labs
Lab solutions
Lab 7: Debug non-equivalent key points using hierarchical compare technique
dofile hier.do
set root module PCI_TARGET32_SM -both //non-equivalent module needs to be diagnosed
set sys mode lec
compare
diagnose -summary -sort size
//diagnose the NEQ key point bc0_out will show very obviousely that there is
//an extra inverter in the revised logic cone, which causes NEQ
Lab 7: Debug non-equivalent key points using hierarchical compare technique
dofile hier.do
set root module PCI_TARGET32_SM -both //non-equivalent module needs to be diagnosed
set sys mode lec
compare
diagnose -summary -sort size
//diagnose the NEQ key point bc0_out will show very obviousely that there is
//an extra inverter in the revised logic cone, which causes NEQ
8. Labs

Conformal Lec Training Basic Advance

Uploaded by

Copyright:

Available Formats

Conformal Lec Training Basic Advance

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Conformal Lec Training Basic Advance

Uploaded by

Copyright:

Available Formats

CADENCE CONFIDENTIAL 1 CADENCE DESIGN SYSTEMS, INC.

Design (Synthesizable RTL, gate, transistor)

Main GUI window

You might also like