LEC Command Reference
LEC Command Reference
Command Reference
Conformal L, Conformal XL, and Conformal GXL
Contents
2
Command Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Wildcards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Using UNIX Commands with Conformal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
ABSTRACT LOGIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
ADD ALIAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
ADD BLACK BOX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
ADD CELL PORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
ADD CLOCK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
ADD COMPARED POINTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
ADD CUT POINT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
ADD DONTTOUCH REGISTERS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
ADD DYNAMIC CONSTRAINTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
ADD IGNORED GRID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
ADD IGNORED INPUTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
ADD IGNORED OUTPUTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
ADD INSTANCE ATTRIBUTE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
ADD INSTANCE CONSTRAINTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
ADD INSTANCE EQUIVALENCES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
ADD INSTANCE RENAMING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
ADD KEYPOINT INFO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
ADD LIBERTY_COMPARE FILTER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
ADD LOWPOWER CELLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
ADD LP_CONTROL IGNORED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
ADD LP_CONTROL PAIR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
ANALYZE DC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
ANALYZE DESIGN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
ANALYZE EXPRESSION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
ANALYZE EXTENDED MAPPING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
ANALYZE GATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
ANALYZE HIER_COMPARE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
ANALYZE IMPLICATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
ANALYZE LP_CONTROL PAIR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
ANALYZE MODULE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
ANALYZE MULTIPLIER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
ANALYZE NETLIST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
ANALYZE NONEQUIVALENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
ANALYZE PARTITION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
ANALYZE POWER ASSOCIATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
ANALYZE PROJECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
ANALYZE REDUNDANCY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
ANALYZE RESULTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
ANALYZE RETIMING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
ANALYZE SEQUENTIAL CONSTANTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
ANALYZE SETUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
ANALYZE SEQUENTIAL DUPLICATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
ANALYZE X . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
APPLY GUIDED TRANSFORMATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
ASSIGN PIN DIRECTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
BACKWARD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
BREAK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
CHANGE GATE TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
CHANGE NAME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
CHECK LOWPOWER CELLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
CHECK MAPPING SETUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
CHECK VERIFICATION INFORMATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
CHANGE NET TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
CHECKPOINT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
CLOSE SCHEMATICS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
COMMIT POWER INTENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
COMPARE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
MAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
MAP KEY POINTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
MOS2BUFIF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366
MOVE INSTANCE DOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368
NCENCRYPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369
OPEN SCHEMATICS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370
PIN GROUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371
PRINTENV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
PROGRAM MONITOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374
PROVE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376
READ DESIGN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378
READ EXTENDED MAPPING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399
READ FSM ENCODING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401
READ GUIDE FILE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403
READ GUIDANCE INFORMATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404
READ IMPLEMENTATION INFORMATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405
READ KEYPOINT MAPPING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408
READ LEF FILE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409
READ LIBRARY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410
READ MAPPED POINTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422
READ MEMORY PRIMITIVE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424
READ PATTERN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425
READ POWER INTENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428
READ ROM PRIMITIVE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431
READ RULE CHECK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432
READ TESTCASE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434
READ SETUP INFORMATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436
READ VERIFICATION INFORMATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439
REDUCE MOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440
REMODEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442
REMOVE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446
REPORT ABSTRACT MODEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448
REPORT ALIAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 449
REPORT BLACK BOX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450
REPORT CLOCK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452
REPORT COMMAND PROFILE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454
3
ECO Command Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 909
ADD ECO CUTPOINT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 911
ADD ECO PIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 913
ADD SPARE CELL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 915
ANALYZE ECO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 917
ANALYZE ECO CUTPOINT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 923
APPLY PATCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 924
CHECK ECO SETUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 927
COMPARE ECO HIERARCHY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 928
DELETE ECO CUTPOINT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 930
DELETE ECO PIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 931
DELETE SPARE CELL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 932
OPTIMIZE PATCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 933
REPORT ECO CHANGES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 941
REPORT ECO CHECK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 943
REPORT ECO CUTPOINT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 945
REPORT ECO GATEDCLOCK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 947
REPORT ECO HIERARCHY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 948
4
Modeling Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 983
F1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 984
F2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 985
F3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 986
F3.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 987
F3.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 988
F3.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 989
F3.4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 990
F3.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 991
F3.6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 992
F5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 993
F6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 994
F7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 995
F8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 996
F8.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 997
F9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 998
F10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 999
F11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1000
F12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1001
F13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1002
F14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1003
F14.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1004
F16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1005
F17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1006
F18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1007
F19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1008
F19.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1009
F20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1010
F21 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1011
F23 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1012
F25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1013
F26 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1014
F27 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1015
F28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1016
F30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1017
F32 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1018
F34 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1019
F34.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1020
F34.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1021
F34.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1022
F36 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1023
F36.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1024
F39 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1025
F41 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1026
F42 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1027
F43 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1028
F44 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1029
F45 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1030
F46 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1031
F47 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1032
F49 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1033
F50 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1034
F51 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1035
F52 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1036
F53 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1037
F54 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1038
F55 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1039
F56 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1040
F57 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1041
F59 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1042
F65.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1043
F65.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1044
F65.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1045
F68 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1046
F69 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1047
F73 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1048
5
Tcl Command Entry Mode Support. . . . . . . . . . . . . . . . . . . . . . . . . . . 1049
add_to_collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1052
append_to_collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1053
cfm_is_gui_mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1054
compare_collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1055
copy_collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1056
echo_result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1057
encrypt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1058
exit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1059
find . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1060
find_cfm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1063
foreach_in_collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1067
get_attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1068
get_compare_points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1070
get_compare_result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1071
get_exit_code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1072
get_current_module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1074
get_fanins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1075
get_fanouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1076
get_gate_count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1077
get_gate_id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1078
get_gate_type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1079
get_handle_type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1080
get_instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1081
get_keypoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1083
get_license_mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1084
get_map_points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1085
get_module_definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1086
get_module_instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1087
get_names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1088
get_nets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1089
get_parent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1091
get_pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1092
get_ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1094
get_primitive_type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1096
get_project_name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1097
get_property . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1098
get_relative_path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1100
get_root_module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1101
get_top_module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1102
get_unmap_points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1103
get_version_info . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1104
help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1105
index_collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1106
ncdecrypt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1107
objtype . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1108
query_collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1109
redirect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1110
remove_from_collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1112
set_current_module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1113
sizeof_collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1114
sort_collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1115
tcl_set_command_name_echo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1116
This manual documents commands and modeling messages for the following Encounter®
Conformal® Equivalence Checking solutions:
■ Conformal L
Conformal L has equivalency checking capabilities with functional checks for ASIC
design flows.
■ Conformal XL
Conformal XL includes Conformal L and extends equivalency checking capabilities to
datapath synthesis and layout.
■ Conformal GXL
Conformal GXL includes Conformal XL and extends equivalency checking capabilities to
digital custom logic and custom memories.
■ Conformal ECO
Conformal ECO Designer offers functional ECO analysis, optimization, and generation
capability.
(Requires a Conformal ECO XL or GXL license)
■ Conformal Low Power
Conformal Low Power enables low power equivalence and functional checks for isolation
cells, level-shifter cells, and state retention cells.
(Requires a Conformal LP/LPXL or LPGXL license)
Audience
This manual is written for experienced designers of digital integrated circuits who must be
familiar with RTL, synthesis, and design verification; as well as having a solid understanding
of UNIX and Tcl/Tk programming.
Related Documents
For more information about the Conformal family of products, see the following documents.
You can access these and other Cadence documents with the Cadence Help online
documentation system. For a complete list of documents provided with this release, see the
CDSDoc library.
■ User Guide for Conformal Equivalence Checking
Describes how to install, configure, and use Conformal to verify RTL, gate, or transistor-
level designs.
Syntax Conventions
Convention Definition
Bold Case Indicates the command name.
UPPERCASE Indicates the required minimum character entry.
< > Indicates required arguments. Do not type the angle brackets.
[ ] Indicates optional arguments. Do not type the square brackets.
| Indicates a choice among alternatives. Do not type the vertical bar.
\ The backslash character (\) at the end of a line indicates that the
command you are typing continues on the next line.
... Indicates multiple entries of an argument.
* Indicates that the entry can use the wildcard (*) to represent zero or
more characters.
2
Command Reference
This chapter describes the Encounter® Conformal® commands. The commands are
presented in alphabetical order.
Command Syntax
■ Conformal commands are not case sensitive.
■ For every Conformal ADD command, there are corresponding DELETE and REPORT
commands. For example:
ADD OUTPUT EQUIVALENCES
DELETE OUTPUT EQUIVALENCES
REPORT OUTPUT EQUIVALENCES
■ Conformal commands adhere to the "3-2-1" rule, which reduces the number of
characters you must type.
❑ 3: Type the leading three characters of the first term.
❑ 2: Then type the leading two characters of the second term.
❑ 1: End with the leading character of the third term.
In some cases, you must use more characters to resolve ambiguity. In this manual, the
minimal sets of characters you must type are shown as uppercase letters in the syntax.
When you use the 3-2-1 rule in conjunction with the syntax guide to resolve any possible
ambiguity, you reduce the number of characters in a command, as the following example
shows:
ADD OUtput Equivalences
becomes
add ou e
■ Reduce the number of characters you type for command options to the characters shown
in uppercase in the syntax, as the following example shows:
add output equivalences out10 out20 -module sub_mod1 -revised
becomes
add ou e out10 out20 -m sub_mod1 -r
Use the SEARCH command to search s the Help database of commands and options for
matches to strings you specify.
The HELP command also displays a list of Conformal TCLmode commands. While in
TCLmode, use the following syntax:
HELp
To view command usage for a specific command, use the HELP command followed by the
command name.
HELp [command_name]
Important
Observe the following requirements for viewing UNIX-style man pages:
You must type the entire command name.
Do not apply the 3-2-1 rule (described below).
Do replace each space in the command name with an underscore ( _ ).
1. To access this resource from your UNIX shell, add the following variable:
% setenv MANPATH "<install_dir>/doc:$MANPATH"
For example:
man read_design
man set_system_mode
Wildcards
On an as-needed basis, Cadence adds wildcard pattern-matching support to Conformal
commands. The syntax convention that alerts you to wildcard support is the asterisk (*).
If you use a pattern where a filename or design object is expected, Conformal Equivalence
Checker expands the pattern using the same conventions as in the UNIX shell.
■ Triggering pattern matching for filenames
To trigger pattern matching for filenames, a string must include at least one asterisk (*),
question mark (?), or a pair of square brackets ( [ ] ).
■ Triggering pattern matching for design objects
To trigger pattern matching for design objects, a string must include at least one asterisk
(*) or question mark (?).
In arguments that are considered patterns, the following characters have special meaning: ^,
{, }, [, ], ?, *. The dash (-) also has special meaning when it falls between square brackets.
Note: When you use wildcards for design objects, a wildcard can match a string that includes
the hierarchical delimiter (/). For example, the pattern *[10] matches the design object a/
b/c[10].
When you use wildcards for filenames, every wildcard applies to part of a single directory or
filename (this convention is the normal UNIX convention). For example, the pattern *.v does
not match the filename a/b/c.v.
Wildcard
Definition Example
Character
? Match any single character. a?c matches:
aac, abc, a4c, a?c
* Match any (possibly empty) string. a*c matches the following:
ac, abc, a*c
Wildcard
Definition Example
Character
[ ] Match any single character listed For filenames:
between the square brackets: "["
That is, "[" a[145] matches the following:
and "]".
followed by
a1
characters and If the first character is "^",
"]" Conformal Equivalence Checker a4
matches any single character not
listed between the brackets. a5
Wildcard
Definition Example
Character
{p1,p2,...} Matches any string matched by any design/{top,sub{5,11}}/*.v
of the sub-patterns listed. matches the following:
design/top/a.v
design/sub5/b.v
design/sub11/c.v
Braces can nest.
a/{d{e,f},g{h,i}}_0 matches
the following:
a/de_0
a/df_0
a/gh_0
a/gi_0
In the above syntax, -golden is a default. Therefore, if you type the command with primary
pin names and the -all option, but no other option, this command specifies output pin
equivalences on all output boundary module pins in the Golden design.
Notice -both in the above syntax. If you specify three primary pins (for example, a1, a2, and
a) and the -both option; all three pin names must exist in both the Golden and Revised
designs. If they do not, LEC returns an error message.
If you specify a1, a2, a and include the -revised option; LEC applies equivalence to the
pins in the Revised design only (even if these three pins also exist in the Golden design).
For example, to save the default output of the REPORT GATE command to a file named
gate.out, you would run the following:
report gate > gate.out
You can also use the >> operator to append output text to an existing file.
Note: Although some commands include a -file <filename> type option to save the
command's output to a file, you should use the command line > operator.
ABSTRACT LOGIC
ABSTract LOGic
[-All]
[-ASM | -NOASM]
[-AUTO | -NOAUTO]
[-REDUNDANT | -NOREDUNDANT]
[-MODule <module_name>]
[-NOPINDirection]
[-NOPREResolve]
[-POWER_VIEW]
[-PURE]
[-TEST_VIEW]
[-UNRESOLVE_MOdule <module_name ...>]
[-Golden | -Revised]
(Setup Mode)
Performs functional analysis on circuit netlists, which can contain different devices, including
transistors, gates, and state elements. The analysis abstracts the netlist into a logically-
equivalent gate model. Use the abstracted model and compare it to the RTL model for
complete functional verification. You can also write out the logic model and use it during high-
performance simulation or fault grading.
Note: If neither the -all nor -module option is specified, Conformal abstracts the current
root module and any modules that are instantiated under it.
Tcl Command
abstract_logic
Parameters
Tip
If there are any unexpected results, you can use this
option to revert back to the functionality of the 6.2
release and earlier.
-AUTO Enables propagation of constants, pin constraints, non-
inverted and inverted pin relationships across module
boundaries. This is the default.
-NOAUTO Do not enable propagation of constants, pin constraints, and
non-inverted/inverted pin relationships across module
boundaries.
-REDUNDANT Removes three types of redundant inverters. First, remove
the inverter whose fanin gate contains other inverters in the
fanouts of the gate. Second, remove the inverters which
sequentially connect together. Third, remove the inverters
which connects to the input and output of a DFF/DLAT. This
is the default.
-NOREDUNDANT Do not enable the removal of redundant inverters.
-MODule <module_name> Abstracts logic information from the specified module and its
hierarchy.
-NOPINDirection By default, the tool automatically assigns a pin direction
(INPUT or OUTPUT) to bidirectional pins during abstraction.
However, the tool cannot always determine a pin direction
based on the design architecture.
When this option is set, the tool will not automatically assign
a pin direction to bidirectional pins during abstraction.
-NOPREResolve Do not resolve any sub-modules. Be default, the tool
resolves sub-modules that have a small number of devices
during the abstraction process to form the circuit.
-TEST_VIEW Performs structurally accurate abstraction. With this option,
only limited boolean simplification is done for abstraction. As
a result, the gate-level structure of the original logic is
preserved as much as possible after abstraction.
Related Commands
ADD CLOCK
DELETE CLOCK
MOS2BUFIF
READ PATTERN
REPORT CLOCK
RESOLVE
ADD ALIAS
ADD ALias
<aliasname> <string>
(Setup / LEC Mode)
Adds alias names for quick command entry. Assign an alias to long command names and
arguments to minimize typing and character entry.
If you add an alias with an alias name that already exists, Conformal accepts the new alias
and returns a warning as shown in the following example:
// Warning: Alias 'myread' is already defined, will be replaced by the new
definition
For the greatest benefit, create aliases at the start of a Conformal session. Also, add aliases
to an initial command file: .conformal_lec.
Conformal checks for the CONFORMAL_RC environment variable. If this variable is set,
Conformal uses the file this variable refers to and does not search for other files.
If the CONFORMAL_RC variable is not set, Conformal continues the search as follows:
■ First, the installation directory:
<install_dir>/share/cfm/lec/.conformal_lec
■ Second, the user's home directory: ~/.conformal_lec
■ Third, the current working directory: ./.conformal_lec
If one or more of these initial command files exist, Conformal runs them in the order noted
above. This process offers flexibility in the way you choose to use the initial command file. You
can set up initial command files for any or all of the following purposes:
■ A global initial command file for all users
■ A global initial command file for an individual user
■ An initial command file for a test case
Tcl Command
add_alias
Parameters
Related Commands
DELETE ALIAS
REPORT ALIAS
Specifies modules or instances that will be defined as blackboxes. These newly defined
blackboxes are classified in the User class of blackboxes. Blackboxes already contained in
the original design are classified in the System class of blackboxes.
Note: The wildcard (*) represents any zero or more characters in blackbox names.
Tcl Command
add_black_box
Parameters
-Library (Used with the -all option only) Blackboxes all modules in
the library.
If you do not specify either -design or -library,
blackboxing applies to both the library and the design.
-Hier Used by the tool in hierarchical comparison dofiles to add
hierarchically compared modules as blackboxes.
Note: This option is documented for informational purposes
only and should not be used in a dofile.
-Golden Blackboxing applies to the Golden design only. This is the
default.
-Revised Blackboxing applies to the Revised design only.
-Both Blackboxing applies to both the Golden and Revised designs.
Related Commands
DELETE BLACK BOX
Tcl Command
add_cell_port
Parameters
Example
The following command creates a new port VDD, VDDL[0], VSS to the module LP_CELL and
make VDD, VDDL[0] the power port and VSS the ground port:
add cell port -power VDD \VDDL[0] -ground VSS -module LP_CELL
ADD CLOCK
ADD CLock
<0 | 1 | -STABLE_control>
<net_name ...>
[-Module <module_name>]
[-Golden | -Revised | -Both]
(Setup Mode)
Defines a clock state where data can change. You can use this command to define:
■ Pre-charge clock states for domino style circuits
■ Stable nets for clock-gating modeling
Caution
When using the ADD CLOCK command with set flatten model
-gated_clock, there is an assumption that the ENABLE signal going into
the AND gate of the clock cone is stable. Use with caution.
Tcl Command
add_clock
Parameters
0 Specifies that the off-state of the clock pin is 0. This means that
when the pin is low, pre-charge occurs.
1 Specifies that the off-state of the clock pin is 1.
-STABLE_control Specifies the stable control nets for latch-free clock gate
modeling.
<net_name ...> Specifies the net name(s).
-Module <module_name>
Specifies that the defined clock pin is located in this module.
-Golden Specifies that the clock is in the Golden design. This is the
default.
-Revised Specifies that the clock is in the Revised design.
-Both Specifies that the clock is in both the Golden and Revised
design.
Related Commands
ABSTRACT LOGIC
DELETE CLOCK
READ PATTERN
REPORT CLOCK
RESOLVE
Adds mapped points to the compare list. You can add compare points for all mapped points,
or for a list of the gate ID numbers, instance paths, or pin paths.
If you add a compare point to the Golden design, the Conformal software also adds its
mapped compare point from the Revised design. Alternately, if you add a compare point to
the Revised design, the software also adds its mapped compare point in the Golden design.
Wildcard: The wildcard (*) represents any zero or more characters in instance or pin paths.
Tcl Command
add_compared_points
Parameters
-FRONTier Adds the specified key points and its frontier to the compare list.
If no key points are specified, the frontier is computed from the
existing compare points, and added to the compare list. No key
points are added to the compare list if the frontier contains any
unmapped key points.
-SUPport Adds the specified key points and their support key points to the
compare list. If no key points are specified, the support key
points are computed from the existing compare points, and
added to the compare list. No key points are added to the
compare list if the support contains any unmapped key points.
-Golden The gate ID numbers, instance paths, or pin paths are in the
Golden design. This is the default.
-Revised The gate ID numbers, instance paths, or pin paths are in the
Revised design.
Examples
For a set of sample commands that shows this and related commands in context, see the
example for the COMPARE command.
Related Commands
DELETE COMPARED POINTS
Adds a cut point to the specified net or pin path. This overrides automatic feedback loop cuts,
which Conformal otherwise establishes on entering the LEC mode.
Tcl Command
add_cut_point
Parameters
pathname Specifies the path that is the cut point of the feedback loop.
-Net Specifies that the path is a net. This is the default.
-Pin Specifies that the path is a pin.
-Golden Applies the cut point to the Golden design. This is the default.
-Revised Applies the cut point to the Revised design.
-Both Applies the cut point to both the Golden and Revised designs.
Related Commands
DELETE CUT POINT
REPORT PATH
Tcl Command
add_donttouch_registers
Parameters
<register_pathname* ...>
-seq_constant Specified registers will not be modeled for sequential constant.
-seq_merge Specified registers will not be modeled for sequential merge.
-Golden Specified don’t-touch registers to the Golden design.
-Revised Specified don’t-touch registers to the Revised design.
-Both Specified don’t-touch registers to both the Golden and Revised
designs.
Related Commands
DELETE DONTTOUCH REGISTERS
Adds dynamic constraints for use with the PROVE command. Place constraints on the
following:
■ Hierarchical instance paths
■ Hierarchical pin paths
■ Hierarchical net paths
■ Gate identification numbers
These constraints are either a 0-state or 1-state. Use this command as you diagnose and
debug logic cones to help prove gate equivalence.
Tcl Command
add_dynamic_constraints
Parameters
-Net Net path, which is the instance name concatenated with the net
name.
-ID Identification number (ID) of a gate.
The identification number is an integer assigned automatically
by Conformal.
Note: ID numbers can differ from one version of Conformal to
another. Always use the full path in dofiles and any time you
rerun a design with a different Conformal version.
-Golden Adds the dynamic constraints to the Golden design only. This
is the default.
-Revised Adds the dynamic constraints to the Revised design only.
-Both Adds the dynamic constraints to both the Golden and Revised
designs.
Examples
For a set of sample commands that shows this and related commands in context, see the
example for the COMPARE command.
Related Commands
DELETE DYNAMIC CONSTRAINTS
PROVE
This command allows users to specify supply points to be ignored in power grid comparison,
by either specifying a supply pin or supply port name, any supply points of a module, or any
supply points of a module instance. Note that the downstream of an ignored supply point will
also be ignored by such command.
Tcl Command
add_ignored_grid
Parameters
Related Commands
COMPARE POWER GRID
Specifies which input pins Conformal ignores during comparison. You can use this command
when the input pins are part of a blackboxed module.
Note: Specified pins must be boundary module pins. Although boundary module pins are
generally not compared points, they are compared points when the corresponding module
becomes a blackbox.
For example, when Conformal compares two blackboxes and one of them has extra input
pins, such as scan in and scan enable pins, use this command to tell Conformal to ignore
these extra input pins during comparison.
Wildcard: The wildcard (*) represent any zero or more characters in ignored inputs and
module names.
Tcl Command
add_ignored_inputs
Parameters
<primary_pin* ...> Ignores this list of primary input pins (associated with the root
module or the specified submodule).
-ROot Ignores the specified input pins in the root module. This is the
default.
-Module <module_name*>
Ignores the specified input pins in this module.
-Instance <module_instance_name*>
Ignores the specified input pins for the specified module
instance(s).
-All Ignores the specified input pins in "all" the modules, including
the root module. -All applies within the given defaults.
-Golden Ignores the specified input pins in the Golden design. This is
the default.
-REvised Ignores the specified input pins in the Revised design.
-Both Ignores the specified input pins in both the Golden and Revised
designs.
Related Commands
DELETE IGNORED INPUTS
Wildcard: The wildcard (*) represents any zero or more characters in ignored outputs and
module names.
Tcl Command
add_ignored_outputs
Parameters
<primary_pin* ...> Ignores this list of primary output pins (associated with the
root module or the specified submodule).
-EQuivalences Ignores the specified output pins and their equivalences.
The equivalences of a pin must be specified by the ADD
OUTPUT EQUIVALENCES command prior to using this
option. Equivalences created after using this option will not
be ignored.
-Module <module_name*>
Ignores the output pins in the specified module. The
default is the root module.
-All Ignores the specified output pins in "all" the modules,
including the root module. -All applies within the given
defaults.
-Golden Ignores the specified output pins in the Golden design.
This is the default.
Related Commands
ADD OUTPUT EQUIVALENCES
Specifies how to treat an attribute for a gate or transistor primitive. Attributes can either be
WEAK or deleted from the database for the purposes of a complete abstraction and
comparison. However, newer abstraction capabilities can make the WEAK feature
unnecessary.
Tcl Command
add_instance_attribute
Parameters
Tip
The preferred method is to use the REMOVE command.
-Golden Applies the instance attribute to the Golden design. This is the
default.
Related Commands
DELETE INSTANCE ATTRIBUTE
REMOVE
Places constraints on specified instance paths in either the Golden or Revised design. You
can only place 0-state or 1-state constraints on the outputs of instances. You can only apply
instance constraints to DFFs and D-latches inside the specified instance paths.
Wildcard: The wildcard (*) represents any zero or more characters in instance and module
names.
Tcl Command
add_instance_constraints
Parameters
Examples
The following two commands are equivalent:
add instance constraints 0 U1/U2/out_reg -revised
add instance constraints 0 out_reg -module U2 -revised
However, these will be reported differently when running the REPORT INSTANCE
CONSTRAINTS command, because of the -module option.
// Command: report instance constraints
Constrained instances in Golden:
0 /U1/U2/out_reg
0 Module U2: Instance out_reg
Related Commands
DELETE INSTANCE CONSTRAINTS
Defines D-latches, DFFs or black boxes as equivalent or inverted equivalences. Use this
command when you have one element in a design that corresponds to two or more elements
in another design.
When used, this command includes instance equivalent results in the compare results. For
example:
================================================================================
Compare results of instance/output/pin equivalences and/or sequential merge
================================================================================
Compared points DFF Total
--------------------------------------------------------------------------------
Equivalent 234 234
================================================================================
Effects on Comparison
This command affects comparisons when you use add compared points -all. In that
situation, Conformal merges the instances specified with the ADD INSTANCE
EQUIVALENCES command and then verifies them at the end of the comparison.
Wildcard: The wildcard (*) represents any zero or more characters in instance names.
Tcl Command
add_instance_equivalences
Parameters
<instance_pathname* ...>
Defines the group of instances that are equivalent. The first
instance is the representative instance. The following instances
are equivalent to the representative instance. This accepts
wildcards.
Note: The instances can be D-latches, DFFs or black boxes.
-Invert <instance_pathname* ...>
Defines a group of instances that is an inverted equivalence of
the group that is equivalent.
Note: The instances can be D-latches, DFFs or black boxes.
-MODULE <module_name>
Applies the instance equivalences to the specified module.The
default is the root module.
-Pattern <pattern> Applies the instance equivalences to registers which match the
pattern. For example, if the <pattern> is "_rep\d+" LEC will
merge <path>_rep1, <path>_rep2 ... to <path>
-HIERarchy Applies instance equivalences to all the sub D-latches, DFFs
and black boxes with corresponding sub keypoints in other
instances if all the instances are the same module and not
invert equivalences.
-Golden Applies instance equivalences to the Golden design. This is
the default.
-Revised Applies instance equivalences to the Revised design.
-Both Applies instance equivalences to both the Golden and Revised
designs.
Related Commands
ADD COMPARED POINTS
Creates an instance renaming rule that will be used during the MAP SUPPLY command.
Enables instance renaming for when the design hierarchy differs between the Golden and
Revised designs. The rule will define how the full pathname of a supply keypoint in the Golden
design will be renamed to find a corresponding supply key point on the Revised side.
Applies only to the Golden design. Regular expressions (such as wildcards) are not
supported for pattern.
Tcl Command
add_instance_renaming
Parameters
Example
The following indicates that all instances under "a/b" should be flattened to "a":
add instance renaming R1 "a/b" "a"
Related Commands
ADD MAPPING MODEL
MOS2BUFIF
Adds user-specified information to key points. This information is kept in the global database
and can be queried using the REPORT KEY POINT -info command.
Tcl Command
add_keypoint_info
Parameters
Related Commands
DELETE KEYPOINT INFO
SET PROJECT
Description
Note: This is a Conformal Low Power command.
Filters are a useful way to see only the data that you want displayed. Use this command to
filter the results of the COMPARE LIBERTY command (for example, when reporting the results
using the REPORT COMPARED LIBERTY command).
Tcl Command
add_liberty_compare_filter
Parameters
<filter_name> Specifies the name of the filter. The filter name must
be specified first. If a filter name is not specified, the
tool automatically generates a name.
-ATTRIBUTE_NAME <name*> Filters out all differences for attributes with the
specified name(s). Wildcards are supported.
-DESCRIPTION <description> Specifies a description for the filter. This description
is displayed when you use the REPORT
LIBERTY_COMPARE FILTER command.
-GLOBAL Specifies that the filter is global. This is the default.
Example
■ The following command filters out all differences related to attribute switch_function:
add liberty_compare filter -attribute_name switch_function
■ The following command filters out all differences for attribute related_ground_pin
where the compared value matches "*VSS*":
add liberty_compare filter -attribute_name related_ground_pin -value "*VSS*"
■ The following command filters out all differences related to Liberty cells which match
"RAM*":
add liberty_compare filter -lib_cell_name RAM*
■ The following command filters out all differences related to Liberty pin which match
"*clk*":
add liberty_compare filter -lib_pin_name *clk*
Related Commands
COMPARE LIBERTY
Tcl Command
add_lowpower_cells
Parameters
Examples
■ The following command assigns cell fdf1a1 as a state retention cell with a CLK_LOW
attribute:
add lowpower cells fdf1a1 -retention -attribute CLK_LOW -revised
Related Commands
CHECK LOWPOWER CELLS
Ignores the specified low-power control signal(s) during comparison. The probe point for the
ignored low-power control signal will not be created in LEC mode.
This command works after READ POWER INTENT for both designs.
Tcl Command
add_lp_control_ignored
Parameters
Isolation: <domain_name>.<strategy_name>
Retention:
<Save|Restore>_<domain_name>.<strategy_name>
Power Switch: <control_pinname>.<strategy_name>
-Golden Ignores the specified low-power control signal in the Golden
design. This is the default.
-Revised Ignores the specified low-power control signal in the Revised
design.
-Both Ignores the specified low-power control signals in both Golden
and Revised designs.
Related Commands
SET LOWPOWER OPTION
This command works after READ POWER INTENT for both designs..
Tcl Command
add_lp_control_pair
Parameters
<identifier1> <identifier2>
Specifies two lower-power control signals as a compared pair.
By default, the first identifier is from the Golden design, and the
second identifier is from the Revised design.
The identifier must be in the following formats:
Isolation: <domain_name>.<strategy_name>
Retention:
<Save|Restore>_<domain_name>.<strategy_name>
Power Switch: <control_pinname>.<strategy_name>
-Golden When two low-power control signals are specified, indicates
that both are from the Golden design.
The first identifier is the representative.
-Revised When two low-power control signals are specified, indicates
that both are from the Revised design.
The first identifier is the representative.
Examples
The following example sets the control signal of isolation strategy PD1.iso1 in the Golden
design and the control signal of isolation strategy PD1.iso1 in the Revised design as a
compared pair.
add lp_control pair PD1.iso1 PD1.iso1
The following example adds the control signal of PD1.iso1 and PD1.iso_dft in the Revised
design as a compared pair. PD1.iso1 is the representative.
SETUP> add lp_control pair PD1.iso1 PD1.iso_dft -revised
Mapping result:
1-th mapped points:
G) + 15 CUT /ISO_PD1.iso1
R) + 15 CUT /ISO_PD1.iso1
(R) + 16 CUT /ISO_PD1.iso_dft
Comparison result:
================================================================================
Compared points CUT Total
-------------------------------------------------------------------------------
-
Equivalent 1 1
================================================================================
Compare results of instance/output/pin equivalences and/or sequential merge
================================================================================
Compared points CUT Total
-------------------------------------------------------------------------------
-
Equivalent 1 1
================================================================================
Related Commands
SET LOWPOWER OPTION
Design object names can be changed due to synthesis or implementation. This command
specifies the mappings of instances from the golden design to the revised design.
Tcl Command
add_mapped_instance
Parameters
Examples
add mapped instance -golden u1/inst[0] -revised u1/inst_0_
When Conformal moves from Setup to LEC system mode, it automatically maps key points
and places them in the System class of mapped points. If any additional mapped points are
necessary, use this command, and Conformal will place them in the User class of mapped
points.
Note: If you attempt to add mapped points that were already mapped, Conformal returns a
warning message.
The -invert option makes one mapped point inverted with respect to the other mapped
point. The (-) sign represents an inverted-mapped point. The (+) sign represents a
non-inverted mapped point.
Tcl Command
add_mapped_points
Parameters
Examples
In the following two commands, A1 is the instance path of a blackbox:
add mapped points A1 A1 -input_pin in1[0] inA[0] -input_pin in1[1] inA[1]
add mapped points A1 A1 -output_pin out1[0] outA[0] -output_pin out1[1] outA[1]
Related Commands
DELETE MAPPED POINTS
The ADD MAPPING MODEL command specifies the phase information for the given modules.
Use this command together with SET MAPPING METHOD -PHASEMAPMODEL.
Tcl Command
add_mapping_model
Parameters
<module_name> ... Specifies the name(s) of the module(s). This accepts wildcards.
-DESign Specifies that the phase information applies to the modules in
the design space. When -library is not specified, -design
is the default. When both -library and -design are not
specified, they are both turned on by default.
-LIBrary Specifies that the phase information applies to the modules in
the library space. When -design is not specified, -library is
the default. When both -library and -design are not
specified, they are both turned on by default.
-Inverted Specifies inverted phase information for the given modules.
This is the default.
-NONInverted Specifies non-inverted phase information for the given modules.
-Golden Specifies that the phase information applies to the modules in
the Golden design. This is the default.
-Revised Specifies that the phase information applies to the modules in
the Revised design.
-Both Specifies that the phase information applies to the modules in
both the Golden and Revised design.
Examples
The following command specifies that module "mymod" in the library of the Golden design
has an inverted phase.
MODE> add mapping model mymod -library
Related Commands
DELETE MAPPING MODEL
Tcl Command
add_module_attribute
Parameters
<module_name* ...> Applies the attribute to the specified modules. This accepts
wildcards.
-PIPELINE_Retime Checks the specified modules for pipeline retiming (and
remodel if pipeline retiming is detected).
This option requires Conformal to check the module and
remodel it if the Golden and Revised designs have
pipeline-retiming.
For advanced pipeline retiming, see ANALYZE RETIMING.
-DFF2Buffer Changes registers to buffers.This option lets you compare
models with no registers to those with pipeline registers
inserted.
add_module_attribute moduleA -
analyze_eco_string
-HIER_Compare <hier_compare_script>
For the specified module, replaces the default ADD COMPARED
POINTS -all and COMPARE commands in the hierarchical
script generated using the WRITE HIER_COMPARE DOFILE
command with the specified <hier_compare_script>.
Note: This option is not supported if you want to perform
hierarchical comparison using the RUN HIER_COMPARE
command.
-ISOlate_module <g_instance_name> <r_instance_name>
Specifies the full path names of the Golden and Revised
instances that need to be isolated. The specified module
instances will then be isolated by the ANALYZE
HIER_COMPARE -isolate_module command.
Isolating modules can help perform stand-alone analysis
without reading the entire design.
Note: This option is available for beta-testing. The options may
be changed prior to the final release. The name of this
command is also subject to change.
-NOBBOXEMpty Un-blackboxes the specified empty module(s).
-NOFLatten Disables the specified module(s) from being flattened during
the dynamic hierarchical run.
-NODYNAMIC_RESOLUTION
Does not perform dynamic flattening when the specified
module(s) are the current root module(s).
-DONTTOUCH_ICG The ICG cell specified by -donttouch_icg would not perform
gated-clock modeling.
Example
In the following command sequence, the hierarchical dofile script hier.do that is generated
with the write hier_compare dofile command contains the commands add
partition points -all, set compare effort high, add compared points
-all, and compare for module modA, instead of the default add compared points -all
and compare command sequence:
add module attribute modA -hier_compare "add partition points -all; set compare
effort high; add compared points -all; compare"
write hier_compare dofile hier.do -constraints
Related Commands
ANALYZE HIER_COMPARE
ANALYZE RETIMING
Adds unidirection to bidirectional MOS devices. This can change a tranif0 into a PMOS,
or change a tranif1 to an NMOS.
Use the REPORT MOS DIRECTION command to display the list of all unidirectional and
bidirectional transistor-MOS instances and their source and drain ports.
Use this command to resolve bidirectional transistor-MOS instances, when the ABSTRACT
command is not able to fully resolve all bidirectional transistor-MOS instances not supported
for comparison.
Tcl Command
add_mos_direction
Parameters
-Golden Applies the MOS direction to the Golden design. This is the
default.
-Revised Applies the MOS direction to the Revised design.
Related Commands
ABSTRACT LOGIC
ADD CLOCK
DELETE CLOCK
READ PATTERN
REPORT CLOCK
RESOLVE
Specifies a JSON data file that contains name aliases for changing keypoint names during
mapping. These aliases are enabled with the "SET MAPPING METHOD -alias" command.
The JSON data file must use following format for the array of name aliases:
[{"m":"<module_name>","t":"ins","n":"<name>","a":"<alias>"},...]
The tool will change the name of the driver DFF/DLatch of pin "pin_name" into "alias".
Tcl Command
add_name_alias
Parameters
<filename> Specifies the JOSN file that contains the name aliases.
-GOLden Use the name aliases for the Golden design.
-REVised Use the name aliases for the Revised design.
-REPlace Clear any previous name alias data before adding new name
aliases.
Related Commands
DELETE NAME ALIAS
REPORT GATE
Defines pre-charge nets; power and ground; or with DYNSTate, defines a dynamic latch
state.
If you do not use the -module option with this command, Conformal applies the attribute to
every module on the specified side (Golden or Revised).
Tcl Command
add_net_attribute
Parameters
Related Commands
ABSTRACT LOGIC
ADD CLOCK
DELETE CLOCK
READ PATTERN
REPORT CLOCK
RESOLVE
Adds one-hot or one-cold constraints on specified net paths. The one-hot constraint lets only
one net be at a 1-state and the remaining nets be at a 0-state. The one-cold constraint lets
only one net be at a 0-state and the remaining nets be at a 1-state.
Tcl Command
add_net_constraints
Parameters
Related Commands
DELETE NET CONSTRAINTS
Specifies the modules that are excluded from the hierarchical dofile script generation. Run
this command before running the WRITE HIER_COMPARE DOFILE command.
Wildcard: The wildcard (*) represents any zero or more characters in module names.
Tcl Command
add_noblack_box
Parameters
Example
For the following example, module mod1 instantiates module submod1, which in turn
instantiates module sub_submod1. The following command adds noblack box to submod1
and sub_submod1:
add noblack box mod1 -submodules
Related Commands
DELETE NOBLACK BOX
Specifies library or design files, where modules defined in these files will not be translated
when running the READ LIBRARY or READ DESIGN command. These modules will
automatically become blackboxes.
This command is applied during initial parsing, so name matching applies only to original
module names. For parameterized or VHDL generic modules whose names are determined
and applied by the Conformal software after parsing and preprocessing, you must use the
ADD BLACK BOX command.
Wildcard: The wildcard (*) represents any zero or more characters in module names.
Tcl Command
add_notranslate_filepathnames
Parameters
<filepath_names* ...>
Specifies the file pathname, which can be directory names
and Verilog filenames.The wildcard (*) and search path is
supported.
-Library Do not translate the modules in the specified library. If you do
not specify -library or -design, Conformal applies this
command to both the library and design modules.
Related Commands
ADD NOTRANSLATE MODULES
Specifies lines to skip in a Verilog or VHDL file. This has the same effect as commenting out
the lines in the file. With this command, you can instruct the Conformal software to skip
certain lines in the design file without having to modify the file.
Tcl Command
add_notranslated_lines
Parameters
<filename> Verilog or VHDL file. This option does not use the search path;
the full path or relative path to the file is required.
<partial_filename> Verilog file. This option searches files in the read design file list;
The wildcard (*) represents any zero or more characters in
partial filename.
-lib libname Search filename or partial_filename in a specific library
specified by -library option of read design.
start:end Specifies the a line number range to skip. For example, 6:8
would skip lines 6, 7, and 8.
line Specifies a line number to skip.
-Golden Skips the specified lines in the Golden design. This is the
default.
-Revised Skips the specified lines in the Revised design.
-Both Skips the specified lines in the Golden and Revised designs.
Example
The following commands skip lines 6 through 8 and line 17 in the foo.v file when reading in
the design:
Related Commands
READ DESIGN
READ LIBRARY
Specifies library or design modules that are parsed, but will not be translated when running
the READ LIBRARY or READ DESIGN command. These modules automatically become
blackboxes.
Note: The ADD NOTRANSLATE MODULES command is applied during initial parsing, so
name matching applies only to original module names. For parameterized or VHDL generic
modules whose names are determined and applied by Conformal after parsing and
preprocessing, you must use the ADD BLACK BOX command.
Wildcard: The wildcard (*) represents any zero or more characters in module names.
Tcl Command
add_notranslate_modules
Parameters
<module_name* ...> Do not compile the listed library or design modules. This
accepts wildcards.
-Library Do not compile the specified library modules. If you do not
specify -library or -design, Conformal applies this
command to both the library and design modules.
-Design Do not compile the specified design modules. If you do not
specify -library or -design, Conformal applies this
command to both the library and design modules.
Related Commands
ADD BLACK BOX
READ DESIGN
READ LIBRARY
Specifies output pin equivalences or inverted pin equivalences on output boundary module
pins. Conformal uses the equivalences when the parent module is being compared and the
subsequent module is a blackbox. The first specified output pin is the representative pin. The
remaining primary output pins refer to the representative pin in that added equivalence group.
Effects on Comparison
This command affects comparisons when you use add compared points -all. In that
situation, Conformal merges the output pins specified with the ADD OUTPUT EQUIVALENCES
command and then verifies them at the end of the comparison.
Wildcard: The wildcard (*) represents any zero or more characters in output boundary
module pin and module names.
Tcl Command
add_output_equivalences
Parameters
Related Commands
ADD COMPARED POINTS
Places values at the output boundary module pins. This value has no effect on the current
specified module comparison. However, Conformal uses the value when it compares the
parent (or higher) module.
Note: This command is limited to blackboxes. For a flat run, if the module is not blackboxed,
all applied constraints will not take effect.
Wildcard: The wildcard (*) represents any zero or more characters in boundary module pin
and module names.
Tcl Command
add_output_stuck_at
Parameters
Related Commands
DELETE OUTPUT STUCK_AT
Specifies the pin or instance names that partition the design into different compare iterations
when the normal comparison process cannot finish. Execute this command before the WRITE
PARTITION DOFILE command.
■ The -all_pattern option creates all possible binary combinations for n key points
specified.
■ The -one_hot option creates all combinations where only one key point has a 1-state
and the rest have a 0-state.
■ The -one_cold option creates combinations where only one key point has a 0-state
and the rest have a 1-state.
Important
A maximum of 14 partition points can be added. If you try to add more than 14
partition points, then only the first 14 will be taken.
Tcl Command
add_partition_key_point
Parameters
-Pin Specifies that the partition key point names are pin names.
This is the default.
-Instance Specifies that the partition key point names are instance
names.
<keypoint_name ...> Specifies a list of partition pin or instance key point names.
-Golden Specifies that the partition key points are in the Golden design.
This is the default.
-Revised Specifies that the partition key points are in the Revised design.
<gname0> <rname0> <gname1> <rname1> ... -Pair
Individually specifies that the Golden and Revised partition key
point names when the names differ between the Golden and
Revised designs.
-ALL_pattern Applies all possible combinations of constraints to the partition
key point names. This is the default.
-ONE_Cold Applies a one-cold constraint to the partition key point names.
-ONE_Hot Applies a one-hot constraint to the partition key point names.
Related Commands
DELETE PARTITION KEY_POINT
Adds partition (cut) points to the design. If a location in one design is specified, the Conformal
software will attempt to find the corresponding point in the other design. If found, it adds a cut
point to both the Golden and Revised designs. These cut points are automatically mapped.
This command automatically handles inverted points.
In the cases where the added cut points are not equivalent, you will need to diagnose them.
If the nonequivalency is caused by the cut point, then you will need to delete that pair of cut
points with the DELETE PARTITION POINTS command.
The ADD PARTITION POINTS command appends the existing compare list with the newly
added partition points. In addition, it also performs comparison on some of the compare
points to ensure that the newly added partition points do not cause any false nonequivalence.
Note: If a cut point has already been added to a location, a second cut point cannot be added
to the same location. If a specified point has more than one corresponding point in the design,
the software will not add a cut point.
Caution
Adding cut points in LEC mode causes flattened netlists to change. As a
result, all the gate IDs are subjected to change. Adding cut points does
not affect the existing compare points list; however, all the compare data
is invalidated after adding cut points.
Tcl Command
add_partition_points
Parameters
-OUTPUT_port Specifies the partition points as all the output pins of the
module instance or datapath operator. This is the default.
-INPUT_port Specifies the partition points as all the input pins of the
module instance or datapath operator.
-INTRA_operator Specifies the partition points as the gates inside the
datapath operator.
-Golden Specifies that the partition points are from the Golden
design. This is the default.
-Revised Specifies that the partition points are from the Revised
design.
-Verbose Reports the partition points with correspondences in the
other design.
Examples
■ The following command specifies partition points in Golden and Revised design by pin
pathnames:
add partition points -pin i0_gold/sum[17] i0_rev/z[17] -pair
■ The following command specifies the partition points in the Golden design. The
command automatically finds the corresponding gates in the Revised design, and if
found, physically adds the cut gate pair in the flattened netlist.
add partition points -pin i0/sum[17] i0/sum[16] -golden
■ The following command specifies the partition points from the output pins of multiplier
operators in the Golden design. The command automatically finds the correspondence
gates in the Revised design, and adds partition point pairs as cut gates in the flattened
netlists.
add partition points -datapath
■ The following command specifies an instance of datapath operator in the Golden design
and adds some gates inside the operator as partition points:
add partition points -instance i0 -intra_operator
■ The following command specifies all the datapath operators in the Golden design and
adds some gates inside the operators as partition points:
add partition points -datapath -intra_operator
■ The following command adds partition points for all the tristate buffers at the primary
outputs:
add partition points -output_tristate
■ The following command adds partition points to all instances of the DW_ module:
add partition points -module DW_*
■ The following command adds partition points at all the possible locations in the fan-in
logic cone of the compare points with abort or unknown compare results:
add partition points -all -abort_cone
Related Commands
ADD COMPARED POINTS
Tcl Command
add_physical_cells
Parameters
<module_name* ...>
Adds the specified module(s) to the physical_cell_list,
which is created by the EXTRACT PHYSICAL CELL command.
Simple wildcard matching is supported.
-BOTh Looks for the module(s) in both the Golden and Revised
designs. This is the default.
-GOLden Add physical cells in the Golden design.
-REVised Add physical cells in the Revised design.
Related Commands
DELETE PHYSICAL CELLS
The pin binding process is in the mapping process which occurs automatically during the
system mode switch from Setup to LEC.
Tcl Command
add_pin_binding
Parameters
-MOdule Specify that the pin binding rules apply to the specified module
pairs. Default module pair is the golden and revised top
modules.
-INvert Indicates the phases of the two pins are inverted..
Related Commands
DELETE PIN BINDING
Constrains primary input pins to a logic value or relationship. The supported constraints are:
■ 0-state
■ 1-state
■ One-hot
■ One-cold
■ Zero-one-hot
■ Zero-one-cold
■ Base 2, 8, 10, and 16 Verilog constants
The one-hot constraint lets only one pin be at a 1-state and the remaining pins be at a 0-state.
The one-cold constraint lets only one pin be at a 0-state and the remaining pins be at a
1-state.
Wildcard: The wildcard (*) represents any zero or more characters in primary input and
module names.
Tcl Command
add_pin_constraints
Parameters
ONE_Cold Specifies that only one of the pins can have a low value.
ZERO_ONE_Hot Specifies that all pins can have a low value, but only one can
have a high value.
ZERO_ONE_Cold Specifies that all pins can have a high value, but only one can
have a low value.
<primary_pin*...> Specifies that a list of primary input names that will be
constrained to a certain state. (These primary inputs are from
either the Golden or Revised design.) This accepts wildcards.
-REPlace Changes the previously specified pin constraint.
-ROot Applies the constraints to the root module(s). This is the
default.
-Module <module_name*>
Applies the constraints to the specified module(s). The
constraints are applied when the specified module is the root
module or when it is blackboxed. This accepts wildcards.
Note: In a flat comparison, to specify a constraint for a
submodule, you must use the ADD PRIMARY INPUT command
and specify a pin or net pathname. This cuts the existing driver
of the net/pin and forces a new value to be propagated. If the
submodule net/pin is floating, use the ADD TIED SIGNALS
command instead.
-All Applies to all root or blackboxed modules (does not apply to
sub-modules during a flat comparison).
-Golden Specifies that the primary input names are from the Golden
design. This is the default.
-Revised Specifies that the primary input names are from the Revised
design.
-Both Specifies that the primary input names are from both the
Golden and Revised designs.
Related Commands
ADD PRIMARY INPUT
Defines the relationship between pins; specifies whether module pins are equal or inverted.
Use this command to complete logic abstraction or to resolve differences in logic during
comparisons.
Note: Pin equivalences are considered only when the pin equivalences are on a root module.
If a submodule has black-box pin equivalences, the Conformal Equivalence Checker checks
to see if they are true when you use the ADD COMPARE POINT -all command.
Wildcard: The wildcard (*) represents any zero or more characters in primary input and
module names. Wildcards are not valid for buses.
Tcl Command
add_pin_equivalences
Parameters
Example
The following example implies that p1, p2, and p3 are equivalent and are inverted to p4, p5,
and p6:
add pin equivalences p1 p2 p3 -inv p4 p5 p6
Related Commands
DELETE PIN EQUIVALENCES
Filters are a useful way to see only the data that you want displayed. Use this command to
filter the results of the COMPARE POWER INTENT command (for example, when reporting the
results using the REPORT COMPARED INTENT command).
Tcl Command
add_power_intent_compare_filter
Parameters
-FILTER <filter_expression> Filters only compared points for which the specified
filter_expression evaluates to true. The
syntax for filter_expression is the same as
for the Tcl find command. Use command 'report
compared intent -attributes' see the
available attributes. See Example section for the
example.
-REGEXp Specifies that the pattern matching operators used
inside filter expression (such as =~) should use
regular expressions as patterns, rather than glob-
style patterns. This option only has any effect if
combined with -FILTER and/or -
DESIGN_OBJECT_FILTER.
-VALUE <value*> Filters out differences for which the compared
value matches the specified value pattern.
Wildcards are supported.
-GOLDEN_VALUE <value*> Filters out differences for which the compared
Golden value match the specified value.
-REVISED_VALUE <value*> Filters out differences for which the compared
Revised value match the specified value.
-OBJECT_TYPE <name*> Filter out differences for the specified power intent
object type. For a list of supported options, see the
section Power Intent Object Types in the REPORT
POWER INTENT command page.
-COMMAND_NAME <name> Filter out differences for power intent objects
related to the specified command.
-OBJECT_NAME <name*> Filter out differences for power intent objects with
the specified name(s). Wildcards are supported.
-OPTION_NAME <name*> Filter out differences for options with the specified
name(s). Wildcards are supported.
-ATTRIBUTE_NAME <name*> Filters out all differences for attributes with the
specified name(s). Wildcards are supported.
Example
■ The following command filters out all differences related to power switches:
add power_intent_compare filter -object_type power_switch
■ The following command filters out all differences for port states where the compared
value matches "*onH 1.2*":
add power_intent_compare filter -object_type port_state -value "*onH 1.2*"
■ The following command filters out all differences related to option -applies_to of
isolation strategies:
add power_intent_compare filter -object_type isolation -option_name \
-applies_to
■ The following filters all failed isolation design object compared points that are named
'inst2/count[2]'
add power_intent_compare filter -object_type isolation \
-design_object_filter "object_name==inst2/count[2]"
■ The following filters all failed isolation design object compared points that are inside
instance 'inst2':
add power_intent_compare filter -object_type isolation \
-design_object_filter "object_name==~inst2/*" -regexp
■ The following filters the connect_supply_net compared points that are connected to
design macro instances 'macro1':
add power_intent_compare filter -command_name connect_supply_net \
-design_object filter "object_name = ~macro1/*"
or
or
Note: To view what available attribute name of set_isolation, use ’REPORT COMPARED
INTENT -set_isolation -attributes’
Related Commands
Adds a new primary input pin to a specified net or pin name. This new primary input pin is
classified in the User class of primary inputs. (The original primary inputs of the design are
classified in the System class of primary inputs.) Use the -cut option if the added primary
input is the only driver to the net or pin. Otherwise, along with the other original drivers, the
net becomes a wired net.
Wildcard: The wildcard (*) represents any zero or more characters in net paths.
Tcl Command
add_primary_input
Parameters
<pathname*> -Net Adds the primary input to the specified net path. -Net is the
default.
<pathname*> -Pin Adds the primary input to the specified pin path.
-Cut Cuts the other original drivers of the specified path and allow
only the newly added primary input as the driver of the net or
pin. This is the default.
-NOCut Do not cut the other original drivers of the specified net or pin
name. This option makes the new net a wired net.
-LIBRARY Specifies that the specified modules names are in the library
space. The default is in both library and design spaces.
-NOLIBRARY Specifies that the specified modules names are in the design
space. The default is in both library and design spaces.
-MODULE <module_name* ...>
Example
For example, the following adds primary inputs to pin 'SI' of modules whose name contains
string "FSD", but in the library space only. Then, it adds pin constraint 1 on all these newly
added inputs.
Related Commands
DELETE PRIMARY INPUTS
Adds a new primary output pin to a specified net name. This new primary output pin is
classified in the User class of primary outputs. (The original primary outputs of the design are
classified in the System class of primary outputs.) This command is used for diagnosis when
an internal value can be observed at a primary output.
Wildcard: The wildcard (*) represents any zero or more characters in net paths.
Tcl Command
add_primary_output
Parameters
<net_pathname*> Adds the primary output to the specified net path. This accepts
wildcards.
-Golden Adds the new primary output in the Golden design. This is the
default.
-Revised Adds the new primary output in the Revised design.
-Both Adds the new primary output in both the Golden and Revised
designs.
Related Commands
DELETE PRIMARY OUTPUTS
Adds a probe point to the specified path of a net or a pin of a module instance. The probe
point is named by the user-specified name. The probe point is an observation point to check
the logic cone driving the specified path. Exactly name-matched probe points between
designs will be automatically mapped when mapping. A probe point is a subset of CUT point
that does not involve actually cutting the net. Users can compare and diagnose the mapped
probe points. Note that probe points cannot be added within a blackbox.
Tcl Command
add_probe_point
Parameters
-NOStrict Specifies the added the probe point is a non-strict probe point.
Not-mapped non-strict probe point will not cause dynamic
flattening in hierarchical flow.
-Verbose Prints out additional messages when adding a probe point.
Example
For example, the following commands add a probe point named probe_1 at net path /inst1/
SO in the golden design, add a probe point named probe_1 at net path /inst_sub/SO in the
revised design, and add two probe points named probe_2 at module instance pin /inst2/SE
in both designs. The probe points named probe_1 and probe_2 are mapped once the system
mode is changed to LEC mode, and compared by 'add compared point probe*' and 'compare'
commands.
Related Commands
Specifies renaming rules for key point mapping, module renaming (when reading in the library
and designs for hierarchical comparisons), pin renaming for blackboxes, and instance
renaming for module pairing (when writing the hierarchical dofile).
Use the REPORT RENAMING RULE command to display the list of all renaming rules.
Conformal applies renaming rules sequentially, in the order they were added.
When you define renaming rules in the Setup system mode, they guide the automatic
mapping process that occurs during the system mode switch from Setup to LEC. When you
are in the LEC system mode, and find that the key point mapping is not complete, define
additional renaming rules and repeat key point mapping to improve the mapping results. The
automatic mapping process refers to the naming specified by the final renaming rules.
Module Renaming
You must use this command before the WRITE HIER_COMPARE DOFILE command. It helps
map modules together for hierarchical comparisons.
Pin Renaming
This command applies to the specified blackbox or to all blackboxes, which is the default.
When defining renaming rules, the first string specifies the pattern to be matched; the second
string specifies how Conformal is to rename or make substitutions. The first string can contain
expressions of the following types:
Any character can be preceded by the escape character "\" to cancel any special meaning it
has. Use the escape character whenever any of the following special characters represents
a simple character.
% . * + ^ $ | ( ) [ ] \
@n Replaces the string that matches the nth %d, %a, %s, or a
pattern enclosed in parentheses.
The n is a digit other than 0, and you can use @{nn} to refer to
further matches (that is, 10...99)
#(expr) Where "expr" is an arbitrary expression that can only contain
constant integers, @n expressions, and the operators +,-,*, /
and ( )
The following table shows implementation examples for various pattern-matching and
substitution strings. For pattern-matching strings, use parentheses to group individual
patterns into a single pattern, as demonstrated in the example (ab|de)*.
Important
Do not include the forward slash, "/", at the top level for either the first or second
string.
For example, express /top_module/adder/reg[5] as
top_module/adder/reg[5].
Tcl Command
add_renaming_rule
Parameters
-PIN_MULTIDIM_TO_1DIM
Allows you to create renaming rules to map multidimensional
array pins to one-dimensional array pins.
-ADD Shows the pins found when adding the rules into the system.
This is the default.
-NOADD Shows the pins found without adding the rules.
-NOASCEND Renames the pins in an descending order. This is the default.
-ASCEND Renames the pins in an ascending order.
-VERBOSE Shows the renaming patterns.
<rule_name> Specifies a rule identification name assigned to a specific
renaming rule.
<string> <string> The first string represents the pattern to be matched.
The second string represents the substitution pattern.
-MAp Specifies that the renaming rule applies to key point mapping.
Note that it also specifies an instance renaming rule with the
same rule name and rule pattern. This is the default.
-TYpe Renames all key points with the specified type. Renaming rules
for instance renaming will not be created. The available types
are as follows:
PI Primary Inputs
E TIE-E gates
Z TIE-Z gates
DFF D flip-flops
DLAT D-latches
CUT Artificial gates for breaking combinational
feedback loops
BBOX Blackboxes
PO Primary Outputs
-NOTYpe Renames all key points except the specified types. Renaming
rules for instance renaming will be created. The available types
are as follows:
PI Primary Inputs
E TIE-E gates
Z TIE-Z gates
DFF D flip-flops
DLAT D-latches
CUT Artificial gates for breaking combinational
feedback loops
BBOX Blackboxes
PO Primary Outputs
-LIMIT_MODule <module_name>
Specifies that the renaming rule only applies to the specified
modules (including children). Where <module_name> can be a
list of names or wildcard name, such as "mod*". The option is
only for key point mapping.
-MOdule Specifies that the renaming rule applies to module renaming
when the library and design are read in.
-PIn Specifies that the renaming rule applies to pin names of
blackboxes.
-INSTance Specifies that the renaming rule applies to instance renaming
for module pairing when writing the hierarchical dofile. Note that
it also specifies a renaming rule for blackbox keypoints with the
same rule name and rule pattern.
Tip
The difference between using add renaming rule
-replace as opposed to using delete renaming
rule followed by add renaming rule is that
renaming rules that are redefined remain in the same
position in the list of renaming rules. By deleting and
adding a rule, the new definition will appear at the end
of the list. In some cases, the order in which renaming
rules are applied might affect the result.
-Golden Specifies that the renaming rule applies to the Golden design.
This is the default.
-Revised Specifies that the renaming rule applies to the Revised design.
-BOth Specifies that the renaming rule applies to both the Golden and
Revised designs.
Example
In the following command, y2[1:0][2:0] in module test2 is renamed y2[5:0]:
add renaming rule -pin_multidim_to_1dim
// Rule created for (test2) y2[1:0][2:0]
// Rule created for (test1) y1[1:0][1:0]
// Rule created for (top) y2[1:0][2:0]
// Rule created for (top) y1[1:0][1:0]
// Rule created for (top) ym[2:3][2:0][1:0]
// 5 rules created. Rules for top module must be manually validated.
You can use the REPORT RENAMING RULE command to view the added rules.
When in Tcl mode, it is recommended to wrap the pattern and substitution strings in curly
braces to protect them from command substitution. For example, the following changes left
square brackets to an underscore:
add_renaming_rule r1 {\[ _}
Related Commands
CHANGE NAME
READ DESIGN
READ LIBRARY
Adds the state retention mapping rules for validation of technology mapping of the sequential
elements (DFFs or DLATs) from RTL to gate-level, gate-level to gate-level, or RTL to RTL.
For a description of the default rules that are added by the system, see CHECK LOWPOWER
CELLS.
Tcl Command
add_retention_register_mapping
Parameters
-Tag Specifies the tag name in the RTL Golden side. The 'tag
name' refers to the label names used with a) 'process'
blocks in the VHDL RTL and b) 'always' blocks in the Verilog
RTL. All the DFFs or DLATs under the tag-named block will
be subjected to this rule.
Wildcards (*) are supported.
-Attribute Specifies the 'power gating cell attribute' for the DFFs or
DLATs in the Revised netlist. Different power gating cell
attributes are defined for different sets of retention cells in
the Synopsys Liberty library format. When synthesized
(technology mapped), the DFFs or DLATs in the Golden
design (specified using module-name, instance-name, or
tag-name) should have the named attribute in Revised
netlist.
-NOAttribute Specifies that, when synthesized (technology mapped), the
DFFs or DLATs in the Golden design (specified using
module-name, instance-name, or tag-name) should not
have any attribute (power gating cell attribute) in Revised
netlist. In other words, the specified DFFs or DLATs should
be technology mapped as ordinary or non-retention cells.
-TYpe <ALL | DFF | DLAT>
Indicates the sequential element type on which to apply the
retention mapping rule.
ALL applies the retention mapping rule to all sequential
elements (both DFF and DLAT type). This is the command
default when you do not specify the -TYpe option.
DFF applies the retention mapping rule to DFFs only, and
DLAT applies the retention mapping rule to DLATs only.
Examples
■ The following command verifies that all registers with a tag label lp_sel* are
implemented with a state retention cell whose power_gating_cell attribute is
LPRET_DFF1:
add retention mapping R0 -tag lp_sel* -attribute LPRET_DFF1
■ The following command verifies that all registers in module blockA are implemented
with a state retention cell whose power_gating_cell attribute is LPRET_DFF1:
add retention mapping R1 -module dma -attribute LPRET_DFF1
■ The following command verifies that all registers with instance name /U0/*/
fifo_dma* are implemented with a state retention cell whose power_gating_cell
attribute is LPRET_DFF2:
add retention mapping R2 -instance "/U0/*/fifo_dma*" -attribute LPRET_DFF2
Related Commands
CHECK LOWPOWER CELLS
Tcl Command
add_rule_filter
Parameters
Examples
The following adds a filter called f1 that filters out occurrences where the message contains
the string "special_cell":
add rule filter f1 -message "*special_cell*"
The following adds a filter called f2 that filters out occurrences of PDM4d where the message
contains the string "special_cell":
add rule filter f2 -rule PDM4d -AND -message "*special_cell*"
Related Commands
DELETE RULE FILTER
Defines additional search paths outside the current directory for filenames you use in the
READ DESIGN and READ LIBRARY commands. This command is necessary because the
default is to search for filenames in the current directory; but your design or library can include
filenames that are housed in other directories. The default search path is the current working
directory.
When you add multiple search paths to the list, Conformal does the search in the order that
those paths were added to the list.
Use the REPORT SEARCH PATH command to display all search paths. Use the tilde character
(~) to shorten the specified path.
Tcl Command
add_search_path
Parameters
<pathname ...> Specifies the search path for filenames used in the READ
DESIGN and READ LIBRARY commands.
-Design The READ DESIGN command uses the specified search path.
If you do not specify -library or -design, Conformal
applies this command to both the READ DESIGN and READ
LIBRARY commands.
-Library The READ LIBRARY command uses the specified search path.
If you do not specify -library or -design, Conformal
applies this command to both the READ DESIGN and READ
LIBRARY commands.
-POWER_intent This is a low power command option. Specifies the search path
for power intent files.
Related Commands
DELETE SEARCH PATH
READ DESIGN
READ LIBRARY
ADD SEQ_CORRESPONDENCE
ADD SEQ_CORRespondence
<golden_identifier> <revised_identifier>
(LEC Mode)
Adds the Golden register and the Revised state point as the pair of sequential corresponding
points.
After adding the sequential corresponding pairs, use the ANALYZE RETIMING -general
command to retime the Revised design to the state points according to the sequential
correspondence information.
Tcl Command
add_seq_correspondence
Parameters
<golden_identifier>
Specifies the sequential corresponding gate ID or instance pathname for
the Golden register.
<revised_identifier>
Specifies the sequential corresponding gate ID or instance pathname for
the Revised state point.
Example
The following commands add the sequential corresponding points and perform general
retiming analysis:
add seq_corr reg1 g1
add seq_corr reg2 g2
analyze retiming -general -verbose
Related Commands
ANALYZE RETIMING
DELETE SEQ_CORRESPONDENCE
REPORT SEQ_CORRESPONDENCE
ADD SUPPLY
ADD SUpply
<object_list>
[-POWER | -GROUND]
[-ROOT | -Module <name_list*> | -ALL]
[-PORT | -GLOBAL ]
[-Golden| -Revised | -Both]
(Setup Mode)
Defines power and ground ports of a module or the global power and ground signals for the
entire design.
Tcl Command
add_supply
Parameters
-Golden Specifies that the listed names are from the Golden
design. This is the default.
-Revised Specifies that the listed names are from the Revised
design.
-Both Specifies that the listed names are from both the Golden
and Revised designs.
Related Commands
DELETE SUPPLY
REPORT SUPPLY
Assigns the specified floating nets or pins to a 0-state or a 1-state in the Golden or Revised
design. These tied signals are classified in the User class of tied signals. The original tied
signals of the design are classified in the System class of tied signals.
Wildcard: The wildcard (*) represents any zero or more characters in net, pin, and module
names.
Tcl Command
add_tied_signals
Parameters
-All Applies the tied signals to "all" the modules. -All applies within
the given defaults.
-Design Applies the tied signals to the design.
If you do not specify -design or -library, Conformal applies
tied signals to both designs and libraries.
-Library Applies the tied signals to the library.
If you do not specify -design or -library, Conformal applies
tied signals to both designs and libraries.
-Golden Adds the tied signals to the Golden design. This is the default.
-Revised Adds the tied signals to the Revised design.
-Both Adds the tied signals to both the Golden and Revised designs.
Related Commands
DELETE TIED SIGNALS
ANALYZE ABORT
ANAlyze ABort
[-All
| <<gate_id> | <instance_pathname> | <pin_pathname> ...
[-Golden | -Revised]> | -Number <number>]
[-CLass <Abort | Notcompared | ALL>]
[-PRESERVE_NET]
[-SNAPSHOT_DIRectory <directory>]
[-Summary | -COmpare [-THREADS <integer>]]
[-Verbose]
[-XORTREE]
(LEC Mode)
Analyzes abort points and recommends actions to help solve the abort points. This command
can also provide useful information for further abort investigation.
Tcl Command
analyze_abort
Parameters
Example
The following commands run abort analysis after the initial compare:
compare
analyze abort -compare
Related Commands
COMPARE
RUN HIER_COMPARE
ANALYZE COMPARE
ANAlyze COMpare
[-ABORT_Stop <integer>]
[-RESOURCEFILE <filename>]
[-THREADS <integer>[,<integer>]]
[-NONEQ_Stop <integer>]
[-VERbose]
(LEC Mode)
Smart Compare is done through the analyze compare command. This command executes
the entire comparison step in the most optimal turnaround time. Based on the design's
characteristics, analyze compare automatically executes the most appropriate combination
of commands and options to complete the comparison
Tcl Command
analyze_compare
Parameters
-ABORT_Stop Stops the command after finding the specified number of abort
<integer> points.
-RESOURCEFILE Specifies the resource filename to analyze the datapath
<filename> modules. This is used for DC netlists.
[-THREADS Specifies the minimum and maximum number of threads. If only
<integer>[,<integer one number entered, this specifies both the minimum and
>]] maximum number of threads.
Example
To use Smart Compare in a hierarchical comparison, use write_hier_compare_dofile
-compare_string or analyze_hier_compare_dofile -compare_string to replace
the default compare command with the analyze_compare command. The following is a
sample dofile for an RTL-to-synthesized gate netlist hierarchical comparison using
analyze_compare.
DC Synthesized Netlist
// Reads in the library design files
Related Commands
SET DATAPATH OPTION
Analyze the sequential constant from guidance in LEC mode. This can help analyze the
consistency and further use GUI to debug the source of the problem when sequential
constant is not applied.
Tcl Command
analyze_constant_information
Parameters
ANALYZE CONSTRAINT
ANAlyze COnstraint
[-PROPagate]
[-REPort]
[-GOLden | -REVised]
(LEC Mode)
Analyzes constraints in the design. Conformal can create more accurate constraints to
resolve some sequential verification issues.
Tcl Command
analyze_constraint
Parameters
ANALYZE DATAPATH
ANAlyze DAtapath
[-MODULE [-RESOURCEFILE <filename>] [-ISOLATE_ABORT_MODULE] ]
[-DIAGNOSIS]
[-EFFort <MEDium | HIgh>]
[-MERGE | -NOMERGE]
[-NOADDERTREE | -ADDERTREE]
[-NOSHARE | -SHARE]
[-NOWORDLEVEL | -WORDLEVEL]
[-NOFLOWGRAPH | -FLOWGRAPH]
[-SHARE_OPerator <r1 r2 [.. rN]> ]
[-THREADS <integer>[,<integer>]]
[-Verbose]
[-GOLDEN | -REVISED]
(LEC Mode)
Analyzes datapath modules. Based on the results of the analysis, Conformal can
automatically resolve multipliers, operator merging, and resource sharing problems.
Note: You cannot run datapath analysis without first mapping the Revised design key points
to the Golden design key points.
Tcl Command
analyze_datapath
Parameters
-ISOLATE_ABORT_MODULE
Isolates the module which is aborted during module-based
datapath (MDP) analysis. The module's gate-level netlist will be
abstracted into RTL for comparison at the top module.
-DIAGNOSIS Displays information that can help diagnose the low quality of
datapath analysis.
-EFFort <MEDium | HIgh>
Specifies the effort level. Choose MEDium (the default), or HIgh
to help provide better analysis of some multipliers, but might
increase the analysis run time.
-MERGE Applies the operator merging technique. This is the default.
-NOMERGE Do not apply the operator merging technique.
-NOADDERTREE Do not automatically add parentheses to the input operands of
adder trees. This is the default.
-ADDERTREE Automatically adds parentheses to the input operands of adder
trees.
-NOSHARE Do not apply the resource sharing technique. This is the
default.
-SHARE Analyzes the design for datapath resource sharing.
-NOWORDLEVEL Do not apply word-level datapath analysis. This is the default.
-NOFLOWGRAPH Do not apply flow-graph based datapath analysis. This is the
default.
-FLOWGRAPH Applies flow-graph based datapath analysis. This helps analyze
complex and advanced datapath clustering, product-of-sum
multipliers or datapath with control logics or constants.
-WORDLEVEL Applies word-level datapath analysis. This helps analyze
advanced word-level optimizations on designs with complex
adder-tree clustering, product-of-sum, XOR-tree, or datapath
with control logics or constants.
-SHARE_OPerator Shares the specified operators. See the example for the
recommended flow.
Note: If this option is specified, only the sharing is performed,
and does not run datapath analysis.
-THREADS <integer>[,<integer>]
Examples
■ The following commands show an example of the recommended flow when using the
-SHARE_OPerator option:
analyze datapath -verbose -share_operator mult_30 mult_31
// Note: mult_30: shared
analyze datapath -verbose -share_operator mult_32 mult_33
// Note: mult_32: shared
analyze datapath -verbose
// Note: add_2(clustered): quality evaluated 70% success
// Note: mult_30: quality evaluated 80% success
// Note: mult_32: quality evaluated 100% success
■ The following is an example of what is displayed when using the -diagnosis option:
================================================================================
[GOLD] mult_26 (z = in1 * in2)
--------------------------------------------------------------------------------
Boundary Match(%) Bits(#) Const(#) Unreach(#)
--------------------------------------------------------------------------------
IN1 (unsigned) 100 16 0 0
IN2 (unsigned) 100 16 0 0
OUT (unsigned) 0 32 0 0
INTERNAL 8 132 15 -
--------------------------------------------------------------------------------
Note:
PPGEN boundary is not perfectly matched.
--------------------------------------------------------------------------------
// Note: mult_26: quality evaluated 10% success
Related Commands
ANALYZE MODULE
COMPARE
ANALYZE DC
ANAlyze DC
<[-REMOVE_RANGE_CONSTRAINT]
[-REMOVE_RANGE_CONSTRAINT_X]
[-RESOLVE_RANGE_CONSTRAINT]
[-REPORT_REDUNDANT_OVL_CONSTRAINT]
[[-REPORT_STATUS | -REVIEW_CONSTRAINT] | [-VERBOSE]]
>
(LEC Mode)
This command can improve compare performance by turning off DC gates. Having a large
number of DC gates in your design can slow down the compare process, resulting in aborts.
DC gates are usually caused by range constraints (VHDL only) and explicit X assignments.
This command focuses only on DC gates that are caused by range constraints.
This command can also detect redundant OVL assertion constraints in the Golden netlist.
You must use this command with one of the following options.
Tcl Command
analyze_dc
Parameters
-REMOVE_RANGE_CONSTRAINT
Turns off DC constraints that are due to VHDL range constraint
and System Verilog assertions.
Note: This option may cause false NEQs.
-REMOVE_RANGE_CONSTRAINT_X
Removes x-assignments modeled due to range constraints in
VHDL.
Note: This option may cause false NEQs.
-REPORT_REDUNDANT_OVL_CONSTRAINT
Related Commands
COMPARE
READ DESIGN
ANALYZE DESIGN
ANAlyze DEsign
[|-Golden] [-Revised | -Both]
[|-SEQ_INPUT_INTERACT_STRuctural | -SEQ_INPUT_INTERACT_LOgical
|-CLOCK_GATING_STRucture]
[-SEQ_RESET_X]
[-TRIGGER_EDGE_DIFF[|-HIer]]
(LEC Mode)
Tcl Command
analyze_design
Parameters
Example
The following shows an example of a report when running the ANALYZE DESIGN command:
■ When used for zero-delay simulation mismatch check:
LEC> ANALYZE DESIGN -REV -SEQ_INPUT_INTERACT_LOGICAL
Sequential gates in revised design with input interaction:
ID Type Sig-pair Com-sups Com-gates Gate-name
================================================================================
19 DLAT (D, CLK) 2 1 out_reg[0]/U$1/i0
20 DLAT (D, CLK) 2 1 out_reg[6]/U$1/i0
where
ID: Gate ID
Type: Specifies whether the gate is DFF or DLATCH;
Sig-Pair: The two overlapping input signals. Possible signals that can appear include
D(data), CLK(clock), S(set), R(reset);
Com-sprts: Number of common supports;
Com-gates: Number of common gates;
ANALYZE EXPRESSION
ANAlyze EXPression
<<module_name*> | -SUBSTITUTED MODULES>
[-GOLden|-REVised]
(Setup Mode)
Transforms a gate-level module into its equivalent word-level model. In the DW verification
flow, analyze expression can replace the substituted generic-gate model with the word-
level RTL model, then datapath analysis can be applied to avoid aborts in the comparisons.
For a complex DW module with sub-modules, analyze expression replaces the sub-
modules with their respective word-level RTL models.
Note: In the DW verification flow, you should use analyze expression immediately after
the module substitution command write blackbox wrapper.
Tcl Command
analyze_expression
Parameters
This command analyzes two extended mapping information to generate a file that helps to
enable complex flows.
This command does not require any design to be read in and does not check the instance
name with LEC DB. The analysis uses the instance names in the files as unique keys to
perform text analysis.
Tcl Command
analyze_extended_mapping
Parameters
<filename1> Specifies the emap file name for the comparison between
design1 and design2.
<filename2> Specifies the emap file name for the comparison between
design2 and design3.
-Output Specifies the output file name for the comparison between
design1 and design3.
-REPlace Replaces the output file if the file exists.
-GZIP Writes out the output file in GZIP.
-VERBose Prints out additional information.
-INPUT_SPECification
Related Commands
READ EXTENDED MAPPING
ANALYZE GATE
ANAlyze GAte
<[identifier* ...] | [-NONEQ] | [-ABORT] >
[-FILE <file_name> [-REPLACE]]
[-CHECK_CONSTant | -NOCHECK_CONSTant]
[-GOLden | -REVised]
[-VERBOSE]
(LEC Mode)
Analyzes gates in the design. This command reports all the messages associated with a
specific gate and provides additional analysis messages.
For more information on this command, refer to the 14.1 web interface document (the web
interface is enable through the set web interface command) titled Advanced Message
Reporting.
Tcl Command
analyze_gate
Parameters
ANALYZE HIER_COMPARE
ANAlyze HIER_compare
[-APPEND_String <string>]
[-COMPARE_String <string>]
[-CONDitional]
[-DOFile <hier_dofile>][-REPlace]
[-ECO_aware]
[-EFFort <Medium | High>]
[-EXact_pin_match | -NOEXact_pin_match]
[-HIERarchical | -FLATten]
[-INPUT_OUTPUT_Pin_equivalence]
[-KEEP_TOP_level_constraints | -NOKEEP_TOP_level_constraints]
[-LEVEL <integer>]
[-MODULE <Golden_module> <Revised_module>]
[-NOCONstraints | -CONstraints]
[-NOEXACT_MODULE_match | -EXACT_MODULE_match]
[-NOFUNCTION_Pin_mapping | -FUNCTION_Pin_mapping]
[-PREPEND_String <string>]
[-THReshold <integer>]
[-USAge]
[-VERbose]
(LEC Mode)
Analyzes the modules and their instantiations in LEC mode to generate the hierarchical dofile
script that verifies the two hierarchical designs (starting from the lower-level modules,
progressing to the top root module).
To enable hierarchical dofile generation in LEC mode, you must use the following command
in Setup mode.
SETUP> set flatten model -enable_analyze_hier_compare
You cannot use this command when performing custom analysis of switch-level networks that
were enabled through the SET XC command
Tcl Command
analyze_hier_compare
Parameters
Example
LEC> analyze hier_compare -dofile hier.do -replace
The following is a sample dofile that reads in the two hierarchical designs, writes out the
hierarchical dofile script, and compares design hierarchies:
set log file hier.log -replace
read library golden.lib -verilog -golden
read design golden.v -verilog -golden
read library revised.lib -verilog -revised
read design revised.v -verilog -revised
set flatten model -enable_analyze_hier_compare
set system mode lec
analyze hier_compare -dofile hier.do -replace -constraints
dofile hier.do
exit -force
In the following example, top-level pathname-based constraints are applied to the appropriate
submodules, during hierarchical comparison.
-------------------------------------------------------------------
In dofile
-------------------------------------------------------------------
add primary input a0/b0/scan_en -net -Golden
add pin constraint 0 a0/b0/scan_en -Golden
analyze hier_compare -dofile hier.do -replace -constraints -
keep_top_level_constraints -noexact_pin_match
dofile hier.do
...
-------------------------------------------------------------------
During hierarchical comparison; part of logfile
-------------------------------------------------------------------
// Running Module modB and modB
// Command: set root module modB -Golden
// Command: set root module modB -Revised
// Command: set module property -instance /a0/b0 -Golden
// Command: set module property -instance /a0/b0 -Revised
// Command: report black box -NOHidden
// Command: set system mode lec
Related Commands
ADD NOBLACK BOX
DOFILE
READ DESIGN
READ LIBRARY
RUN HIER_COMPARE
UNIQUIFY
ANALYZE IMPLICATION
ANAlyze IMplication
[-ADD <-ONE | -1 | -ZERO | -0> <GateID...>]
[-Block <GateID ...>]
[-CHECK_Constant <GateID ...> ]
[-CHECK_Redundancy <GateID ...>]
[-DELete <GateID ...>]
[-DEPTH <depth>]
[-ONE | -1 <GateID ...>][-ZERO | -0 <GateID ...>]
[-Golden | -Revised]
(LEC Mode)
Analyzes implication values on the design. If you assign value(s) on certain gate(s), this
command shows what the necessary values are on other gates to satisfy the assignment. It
can also show if a gate has redundant fanin and if a gate is a constant gate.
The results are displayed in the schematic view with the following colors:
■ Blue: initial assignments
■ Green: current implication values
■ Red: gates on the conflict path
■ Purple: location where conflict occurred
In the schematic view, you can also right click the gate and set a value. Holding the mouse
pointer on a gate, an information box will show if this gate has redundant fanin and if it is a
constant gate.
Tcl Command
analyze_implication
Parameters
Related Commands
READ DESIGN
READ LIBRARY
Automatically sets up matched low-power control signals between Golden and Revised
designs as compared pairs, and checks if there are any mismatched low-power control
signals.
This command works after READ POWER INTENT for both designs.
Tcl Command
analyze_lp_control_pair
Parameters
Related Commands
SET LOWPOWER OPTION
ANALYZE MODULE
ANAlyze MOdule
<module_name*> ...
[-BREAK_ABORT]
[-BREAK_NONEQ]
[-EFFORT <Low | Medium | High>]
[-MSB_TRUNCATIONS | -NOMSB_TRUNCATIONS]
[-LSB_TRUNCATIONS | -NOLSB_TRUNCATIONS]
[-PARTIAL_SUM_OUTPUTS]
[-REPLACE | -NOREPLACE]
[-TMPDIR <string>]
[-GOLden | -REVised]
[-VERBose]
(Setup Mode)
Analyzes non-exact synthesis modules in the Revised netlist and replaces the corresponding
RTL models in the Golden netlist with the synthesized modules if the synthesized modules
can be proven equivalent using the specified comparison mode. The method of module
correspondence between the Golden and Revised netlist is identical to hierarchical
comparisons. Therefore, module renaming rules and uniquification can also be applied.
For analyze module to be successful, the modules must be hierarchically comparable and
must be included in the hierarchical dofile script generation. Do not use any commands that
may affect these requirements (such as ADD NOBLACK BOX) before ANALYZE MODULE.
Caution
The ANALYZE MODULE command should be used after uniquification.
After running this command, all design level settings cannot be modified.
These settings include, but are not limited to, pin constraints and
renaming rules.
Tcl Command
analyze_module
Parameters
Example
The following command analyzes modules DW02_multp and DW02_tree in the Revised
netlist and replaces the corresponding RTL models in the Golden netlist with the synthesized
modules if the synthesized modules can be proven equivalent using the partial sums outputs
comparison mode:
analyze module *DW02_multp* *DW02_tree* *DW_squarep* -partial_sum_outputs
Related Command
ANALYZE MULTIPLIER
ANAlyze MUltiplier
[-NOCDP_INFO | -CDP_INFO]
(LEC Mode)
Initiates an analysis of multiplier modules. Based on the results of the analysis, Conformal
can automatically resolve architecture mismatches and operand swapping problems.
Additionally, use the -cdp_info option if you want Conformal to let you know when
Conformal XL will be helpful.
Tcl Command
analyze_multiplier
Parameters
Related Commands
ANALYZE DATAPATH
ANALYZE MODULE
ANALYZE NETLIST
ANAlyze NEtlist
[-ABSTRACT [HFA | LIBCELL | MUXDFF]
[-VERBose]
[-GOLden | -REVised]
(LEC Mode)
Tcl Command
analyze_netlist
Parameters
Examples
The following command abstracts half-adder or full-adder function blocks in the revised
netlist.
LEC> ANALYZE NETLIST -ABSTRACT HFA -REVISED
The following command identifies library cells used in the golden netlist and re-synthesizes
them with a simpler circuit transformations.
LEC> ANALYZE NETLIST -ABSTRACT LIBCELL -GOLDEN
Related Command
ANALYZE DATAPATH
COMPARE
ANALYZE NONEQUIVALENT
ANAlyze NOnequivalent
[ | <gate_id> | <instance_pathname*> ...
[-Golden | -Revised] ]
[-Type <PO | DFF | DLAT | BBOX | CUT > ...]
[-DFT_Constraint_diagnosis]
[-SOURCE_diagnosis]
[-Summary | -Verbose]
(LEC Mode)
Tcl Command
analyze_nonequivalent
Parameters
Examples
The following shows an example of a report when running the ANALYZE NONEQUIVALENT
command. The lines in bold indicate the cause of the problems:
LEC> analyze noneq 213
//Command analyze noneq 213
Analyzing nonequivalent compared points:
(G) + 213 DFF /wbs/hvlen_reg[28]
(R) + 6277 DFF /wbs/hvlen_reg[28]/U$1
The clock of DFF in Golden is not gated.
The clock of DFF in Revised is gated.
Analysis of nonequivalent compared points:
Gated clock of of DFF or DLAT. (Occurrence: 1)
Unknown reason. (Occurrence: 1)
LEC> analyze noneq 170 -revised
//Command analyze noneq 170 -revised
Analyzing nonequivalent compared points:
(G) + 167 PO /wbm_sel_o[0]
(R) + 170 PO /wbm_sel_o[0]
Following constraints may be necessary:
Constant 1: (G) 1026 DFF /wbm/sel_o_reg[0]
Analysis of nonequivalent compared points:
Sequential constant. (Occurrence: 1)
Unknown reason. (Occurrence: 1)
Clock Gating
Sequential Constant
Related Command
ANALYZE SETUP
ANALYZE PARTITION
ANAlyze PArtition
[-DATAPATH_TYPEs <<MUL | DIV | ADD | SUB> ...>]
[-DOFile <filename>][-Replace]
[-EFFORT [MEDIUM | HIGH]]
[-GROUPs <id ...>]
[-KEYPOINTs <identifier ...>]
[-MAX_KEYPOINTs <integer>]
[-MAX_PARTITIONs <integer>]
[-NOABORT_STOP | -ABORT_STOP]
[-NOINTERNAL | -INTERNAL]
[-VERBose]
(LEC Mode)
This command derives partition groups by analyzing the datapath resources in the fanin-
cones of not-compared or abort compared points. A partition group consists of three parts:
■ A set of partition key points
■ Partitions of the functional space of the partition key points
■ A set of compared points suitable for the partitions.
Based on the derived partition groups, the tool can generate a dofile that performs functional
partitioned comparisons (you can the -keypoints option of this command in place of the ADD
PARTITION KEY_POINT and WRITE PARTITION DOFILE commands.
Tcl Command
analyze_partition
Parameters
-DOFile <filename> Specifies the name of the partition dofile script that performs
functional partitioned comparisons. Use the tilde character (~)
to shorten the path of the file.
-Replace Replaces the existing file.
[-EFFORT [MEDIUM | HIGH]]
Specifies the abort analysis effort level; medium is the default.
Effort high enables abort analysis targeted at partitioned
comparisons. For more information, refer to the 13.1 web
interface article titled Enhanced Functional Partition Execution.
-GROUPs <id ...> Specifies the partition groups that are used to generate the
partition dofile script. If not specified, all the derived partition
groups are used to generate the partition dofile script.
-KEYPOINTs <identifier ...>
Generates partitions based on the user-provided partition key
points that are in the Golden netlist. You can use this option in
place of the ADD PARTITION KEY_POINT and WRITE
PARTITION DOFILE commands.
-MAX_KEYPOINTs <integer>
Specifies the maximum number of partition keypoints in a
partition group. The default value is 8.
-MAX_PARTITIONs <integer>
Specifies the maximum number of partitions in a partition
group. The default value is 256.
-NOABORT_STOP Disables the adaptive partitioned comparison flow. This is the
default.
-ABORT_STOP Enables the adaptive partitioned comparison flow. In this flow, if
there are aborts in a partitioned comparison, the rest of the
partitioned comparisons are skipped. For more information,
refer to the 13.1 web interface article titled Enhanced Functional
Partition Execution.
-NOINTERNAL Generates partitions based on key points. This is the default.
-INTERNAL Generates partitions based on internal points and key points.
Note that you can only run the dofile created by this option in
the same LEC session.
-VERbose Control the output information for resource sharing and derived
partition groups.
Examples
The following illustrates various command line examples:
LEC> analyze partition -verbose
LEC> analyze partition -verbose -dofile partition.do -replace
LEC> analyze partition -dofile partition.do -max_keypoints 30 -max_partitions 1000
LEC> analyze partition -dofile partition.do -datapath_types mul div -replace
The following illustrates a sample script that performs functional partitioned comparisons:
add compared points -all
analyze partition -verbose -dofile partition.do -replace
dofile partition.do
Related Commands
ADD COMPARED POINTS
DOFILE
Analyzes the module's SPICE netlist and identifies the power/ground pin for each input and
output pin with which it is associated.
Notes:
■ The power/ground pin definition can come from LEF or SPICE.
■ Run the SET SPICE OPTION -NOBULK command before reading in the SPICE design
to maintain the connectivity of power/ground ports.
■ Each input or output pin can have only one associated power/ground pin. Multiple power/
ground pin association are ignored.
Tcl Command
analyze_power_association
Parameters
Related Commands
READ DESIGN -spice
ANALYZE PROJECT
ANAlyze PRoject
[-HIER_TO_FLAT
[-VERbose <MAPPED_POINTS | UNMAPPED_POINTS | COMPARED_POINTS |
COMPARE_DATA [-CLASS <EQuivalent | INVequivalent
| NONEQuivalent | ABort | NOTcompared>]>]
[-MAPPING_FILE <filename> [-REPlace]]
]
(Setup/LEC)
This command analyzes the information of multiple LEC runs for the specified LEC project.
You must use the SET PROJECT NAME command before this command.
Tcl Command
analyze_project
Parameters
Related Commands
DELETE PROJECT
ANALYZE REDUNDANCY
ANAlyze REDundancy
<[Identifier <-ONE | -ZERO | -UNREACH>] |
[-Operand_isolation]>
[-EFFORT <Low | Medium | High> ]
[-Golden | -Revised]
[-NOCommit | -Commit]
[-Verbose]
(LEC)
Analyzes the flattened netlist to find and resolve redundancy within signals and operand
isolation cells. This command works for both hierarchical and flat comparisons.
For more information on how and when to use this command, launch the web interface using
the SET WEB_INTERFACE ON command.
Tcl Command
analyze_redundancy
Parameters
Examples
■ The following command sequentially checks the fanouts of a specified gate. Using this
command, the tool finds that gate u2 has two fanouts with redundant value of one.
LEC> analyze redundancy -rev u2 -one
// Note: 2 net(s) have redundant value 1.
LEC> analyze redundancy -rev u2 -one -verbose
// Note: GATE 'u2' to GATE 'u5' has redundant value 1
// Note: GATE 'u2' to GATE 'u4' has redundant value 1
// Note: 2 net(s) have redundant value 1.
LEC> analyze redundancy -rev u2 -one -commit -verbose
// Note: GATE 'u2' to GATE 'u5' has redundant value 1
// Note: GATE 'u2' to GATE 'u4' has redundant value 1
// Note: 2 net(s) have redundant value 1 (committed).
■ Operand isolation analysis should be done before datapath analysis. The following
illustrates typical usage in the flow for invoking operand isolation analysis:
■ The following performs redundancy analysis on the isolation cells in the revised netlist,
and remodels the cells using the proved redundant values:
analyze redundancy -operand_isolation -commit -revised
■ The following command reports whether operand isolation occurs in the synthesis netlist:
LEC> analyze redundancy -operand_isolation -verbose
// Operand Isolation Analysis Status
=================================================================
Design_Mod Operand_Instance Data_Width Analysis_Quality
-----------------------------------------------------------------
top RC_OI_HIER_INST10 16 100%
RC_OI_HIER_INST11 16 100%
RC_OI_HIER_INST12 16 100%
RC_OI_HIER_INST9 16 100%
-----------------------------------------------------------------
Total isolation cells detected 4
Total isolation cells analyzed successfully 4
Operand isolation analysis success rate 100%
=================================================================
Related Commands
ANALYZE ABORT
ANALYZE DATAPATH
ANALYZE RESULTS
ANAlyze RESults
-LOgfiles <filename> ...
[-Explain]
[-GZIP_suffix <pattern> ...]
[-Verbose]
(Setup / LEC Mode)
Analyze results from LEC log files and produces a detailed summary. The report provides
recommendation on suitable number of workers for parallelization of module comparison.
Tcl Command
analyze_results
Parameters
Examples
The following sets an LEC log file and specifies that log file for results analysis at the end of
the run.
set_log_file -replace lec_run.log
usage -auto -elapse
...
analyze_results -logfile lec_run.log
exit
Related Commands
SET LOG FILE
RUN HIER_COMPARE
GO HIER COMPARE
ANALYZE RETIMING
ANAlyze REtiming
[-ABSTRACT_MUXDFF | -NOABSTRACT_MUXDFF]
[-DIAGNOSIS [<identifier>] [-BACKWARD] ]
[-GENERAL [<identifier* ...> [-BACKWARD]] ]
[-MERGE | -NOMERGE]
[-PIPELINE [<identifier* ...>] [-BACKWARD] [-FIXNAMEmapped][-REPEAT] ]
[-PREDICT <identifier> [-BACKWARD] ]
[-VERBose]
[-BOth | -GOLden | -REVised]
(LEC Mode)
Initiates pipeline retiming, retiming for Genus synthesized netlist, or retiming for designs that
are combinationally equivalent. Normally, you use this command to retime a Revised design
to match a referenced Golden design. If this command is successful, you can use the
COMPARE command to ensure that the two designs are equivalent. If this command is
unsuccessful, then the original retiming you performed is incorrect.
For more guidelines and examples, see the "Advanced Capabilities" chapter in the
Conformal Equivalence Checking User Guide.
Tcl Command
analyze_retiming
Parameters
Examples
■ The following command initiates backward pipeline retiming for register r1 and registers
whose identifiers begin with r2, such as r2a and r21, in the Revised design:
analyze retiming -pipeline r1 r2* -revised -backward
Related Commands
ADD SEQ_CORRESPONDENCE
COMPARE
DELETE SEQ_CORRESPONDENCE
REPORT SEQ_CORRESPONDENCE
Compare the original trigger function of registers which are remodeled into sequential
constants by LEC.
Their mapping is based on original mapping and name mapping. Note that the compared
netlists during sequential constants' comparison are not the final netlist remodeled by LEC.
Besides, for this kind of comparison, few remodeling behaviors will be modified.
Tcl Command
analyze_sequential_constants
Parameters
Related Commands
ANALYZE SETUP
ANAlyze SEtup
[-EFFORT <Medium | High | Ultra>]
[-CUT | -NOCUT]
[-DELETE_UNREACHable | -NODELETE_UNREACHable]
[-GATED_Clock | -NOGATED_Clock]
[-LATCH_TRANSPARENT | -NOLATCH_TRANSPARENT]
[-NOABSTRACT_GATED_CLOCK | -ABSTRACT_GATED_CLOCK]
[-NOFORCE | -FORCE]
[-NOLATCH_NO_HOLDING | -LATCH_NO_HOLDING]
[-NOLIBRARY_VERIFICATION | -LIBRARY_VERIFICATION]
[-NOMODIFY_MAP | -MODIFY_MAP]
[-NOPHASE_MAPPING | -PHASE_MAPPING]
[-NOREPORT_MAP | -REPORT_MAP]
[-REPORT_RUNTIME]
[-SEQ_MERGE | -NOSEQ_MERGE]
[-SEQ_REDUNDANT | -NOSEQ_REDUNDANT]
[-TRANSFORM_SET_DOMINANT | -NOTRANSFORM_SET_DOMINANT]
[-VERBose]
(LEC Mode)
Analyzes the netlists and sets up the flattened design for accurate comparison. This helps
avoid false nonequivalences. This command can also analyze and remodel the following
commonly-encountered setup issues: sequential constants, sequential merging, loop cutting,
clock gating, and phase mapping.
Note: To resolve sequential constant optimization with this command, you must use the
following command:
set flatten model -seq_constant
Tcl Command
analyze_setup
Parameters
Related Commands
ANALYZE NONEQUIVALENT
This command performs two checks for sequential duplication sets in the netlist.
❑ Feedback check: duplicated registers have no functional dependence on other
registers within the duplication set.
❑ Convergence check: any comparison point depends on, at most, one register in the
duplication set.
Tcl Command
analyze_sequential_duplication
Parameters
-WRITE_LIST <filename>
Write the merge points to the specified file.
-REPlace Replaces the existing file.
-FILE <filename> Specifies the duplication set.
-ALL Perform both feedback and convergence validation. This is the
default.
-FEEDback Perform feedback validation.
-CONVergence Perform convergence validation.
-REVised Indicates revised design to validate. This is the default.
-GOLden Indicates Golden design to validate.
-VERBose Provides verbose information.
Related Commands
ANALYZE X
ANAlyze X
[ -ALL | <identifiers> | -Source <filename> <line> <column> ]
[-Level <num> ]
[ -Verbose ] [ -FILE <annotation filename> ] [-REPlace]
[ -APPLY <annotation filename> [-NOIFDEF] ]
(LEC Mode)
This command analyzes X assignments in the golden RTL design to find corresponding
functions in the revised gate-level design. Replacing X assignments with these functions
maintains the equivalence between RTL and gate-level designs.
This command can automatically write out analyzed functions into an annotation file and
apply them to the RTL design to replace X assignments. Applied RTL should be in the same
location recorded in the annotation file.
In the ECO flow, replacing X assignments in the new RTL (R2) can help to reduce synthesis
differences in G2 and can help achieve a smaller ECO patch.
Note: The golden flattened netlist will be changed after calling this command to analyze X-
assignments.
Tcl Command
analyze_x
Parameters
<identifiers> Analyze X assignments for the specified don't care gates. The
identifiers of gates can be the instance path name or identification
number. The identifiers can be an ID or instance path name. For
example, a gate with an ID of 89 or gate-name of /top/n44[0] (as
reported by REPORT GATE) can be specified as either of the
following:
analyze x 89
analyze x /top/n44[0]
-Source <filename> <line> <column>
Analyze X assignments in the specified locations of the RTL source
file. If omitting the column, all X assignments in the specified line of
file are targets. If omitting the line and column, all X assignments in
the specified file are targets.
-Level <num> Sets limitation of traversed circuit levels for analyzing functions and
expressions.
If level is 0, the possible analyzed functions will be limited to 0, 1, or a
net. If level is 1, it allows 1 operator in analyzed functions. Higher
level takes long runtime and higher success rate.
Default is 14 according to performance trade-off.
-Verbose Displays a report of the analyzed expressions.
-FILE <annotation filename>
Write out expressions for analyzed X assignments with their location
in the RTL source file.
-REPlace Replaces any existing annotation files with the same name.
-APPLY <annotation filename>
Examples
For example, given RTL "o = s ? 1'bx : a;" and a gate-level design "or ( o, s, a
);", you can:
■ Use the following commands in LEC mode to get analyzed functions of X assignments.
LEC> analyze x -all -verbose -file xfunction.json
// Remodel 1 X assignments
(test.v:4,16) X is converted to:
{ 1'b1 }
■ Use the following commands to apply the annotation file "xfunction.json" to replace
X-assignments in RTL code automatically:
LEC> analyze x -apply xfunction.json
// Succeed to apply X in (test.v:4,16)
Applies the datapath transformations, recorded in the OVF (Open Verification Format) guide
file(s), to the LEC Golden design database that is created from RTL. For an overview of the
OVF flow, refer to the Interfacing between RTL Compiler and Conformal User Guide
(this document is available within the RTL Compiler document set). This command
is a part of the RC-LEC Scripted Verification Flow, where the transformations are
used as a strategy to resolve aborts. For more information on this flow, refer to the
13.1 web interface documented Scripted RC Verification.
To commit the transformations recorded in the guide file(s), LEC can create the Golden
design database with a higher structural similarity to the netlist synthesized by the synthesis
tool, which may help resolve abort points or enhance comparison performance.
By default, this command validates all transformations before committing them to the Golden
design database. This ensures that the Golden design functionality must not divert from the
original interpretation of the Golden RTL design.
You can use the -module option to selectively choose one or more modules to apply the
transformation: instead of the entire design.
Tcl Command
apply_guided_transformations
Parameters
Related Commands
Defines a module pin's direction. SPICE netlist ports do not have direction, unless you supply
*.pininfo <pin>:<direction> as a CDL comment and read it in as an inout.
Abstraction analyzes the circuit and assigns pin direction: when determinable. In some cases,
you need to assign pin direction manually to complete abstraction.
Note: You can use this command instead of the ADD MOS DIRECTION command to assist
abstraction.
Wildcard: The wildcard (*) represents any zero or more characters in module/pin names.
Tcl Command
assign_pin_direction
Parameters
Examples
assign pin direction in mux2p sela -revised
assign pin direction out mux4p y -golden
assign pin direction in mux2p sela y -both
//Assigns direction to pins sela and y.
assign pin direction OUT * VDD
//Specifies that the assigned direction of pins named VDD in all modules is output.
assign pin direction IN mod pin_* -from_dir IO
//Changes all IO pins whose name matches 'pin_*' in
//module 'mod' to IN pins on the golden side.
Related Commands
ABSTRACT LOGIC
ADD CLOCK
DELETE CLOCK
READ PATTERN
REPORT CLOCK
RESOLVE
BACKWARD
BACkward
[<integer>]
(LEC Mode)
Reports fanin gate information from the currently displayed flattened gate information. The
fanin gate you choose with this command becomes the current flattened gate. Use this
command to trace gates in place of repeatedly using the REPORT GATE command.
Note: This command does not report gates at the design level.
Tcl Command
backward
Parameters
<integer> Specifies which fanin gate is reported. The value 1 denotes the
first fanin. The default value is 1.
Related Commands
FORWARD
REPORT GATE
BREAK
BREak
(Setup / LEC Mode)
Terminates the dofile script and returns you to the system mode prompt.
Related Commands
CONTINUE
DOFILE
Tcl Command
change_gate_type
Parameters
Related Commands
REPORT GATE
CHANGE NAME
CHAnge NAme
<filename>
[-Summary | -Verbose]
[-Golden | -Revised | -Both]
(Setup Mode)
Converts netlist net names, port names, and cell names back to their original names. Thus,
Conformal does key point mapping faster and more efficiently. The most common use of this
command is to change the names in a post synthesis netlist back to their original, pre-
synthesis forms.
After Conformal reads in the file containing the original names and new names, it makes the
conversion. Generally, the synthesis tool you have used generates the file describing the
changes. Consult the specific vendor's tool documentation for additional change name
information.
Tcl Command
change_name
Parameters
Related Commands
ADD RENAMING RULE
This command performs two checks, both of which apply to all mapped state elements (DFF
and DLAT). Power domains are compared; if they are not equivalent, the design may not be
functionally equivalent. State retention strategy is also compared; sometimes, differing
retention strategies are applied when the Golden and Revised power intent is different.
Tcl Command
check_lowpower_cells
Related Commands
COMMIT POWER INTENT
This command reports the quality of the mapping file without having to go into LEC mode.
This command should be invoked after elaborating both designs and reading the mapping file
with set_analyze_option -mapping_file.
Tcl Command
check_mapping_setup
Parameters
-ALIAS Checks and reports the quality of alias mapping. Name alias are
specified using the ADD NAME ALIAS command.
-CASE_sensitive
Checks if the keypoints mapping are case sensitive.
-MAPPING_FILE_QUALITY
Reports the quality of mapping file for mapping two designs. All valid,
invalid, mapped, and unmapped data are reported in default.
-SUMMARY Instructs the command to print only a summary report. otherwise, by
default, a detailed listing of the names in the mapping file will be
reported.
-MAPPED Instructs the command to report only names that can be mapped by
the file.
-UNMAPPED Reports the points that cannot be mapped by the file. Use this option
to reduce the size of the report.
-VALID | - Reports the valid/invalid names.
INVALID
-ERROR This option will error out and stop to run dofile when the total number
<number> of invalid entries in the mapping file is more than or equal to the
number <number>.
Related Command
SET ANALYZE OPTION
This command checks the guild information quality, contains verification information and
implementation information.
Tcl Command
check_verification_information
Parameters
-IMPLEMENTATION
Checks the implementation information. The implementation is read by
READ IMPLEMENTATION INFORMATION.
-VERIFICATION Checks the verification information. The implementation is set by SET
IMPLEMENTATION INFORMATION.
-TYPE Specifies the type of information that would be checked. The default is
ALL.
-VERBOSE Displays the detailed information of the check result..
Related Command
SET IMPLEMENTATION
Modifies the database so that it appears that the changed net types were declared in the
original Verilog netlist.
Tcl Command
change_net_type
Parameters
Related Command
ADD NET ATTRIBUTE
CHECKPOINT
CHECKPOINT
<checkpoint_file_name>
[-PROTECT <password>]
[-REPlace]
(Setup/LEC Mode)
Creates a checkpoint file. A checkpoint file contains a complete snapshot of the Conformal
run up until the CHECKPOINT command is issued. The tool preserves the entire memory
contents of the Conformal run. The checkpoint file includes:
■ Hierarchical and flattened databases
■ Environment settings
■ Constraints
■ Verification results
■ User-defined variables
■ User-defined procedures
Review the set of limitations at the end of this section before using the CHECKPOINT
command.
For more information on the checkpoint and restart facility, refer to "Checkpoint and Restart
Facility" in the Conformal Equivalence Checking User Guide.
Tcl Command
checkpoint
Parameters
-protect <password> Encrypts the checkpoint file with the specified password.
The password cannot lead with a dash ("-"); for example, -
mypassword is not allowed.
-REPlace Removes any existing file of the same name and replaces
them with the specified file.
Limitations
■ Checkpoint and restart works on only Linux, and only on the following platforms:
64-bit Linux kernel versions 2.6.9-34, 2.6.9-42, 2.6.9-67, 2.6.9-78, 2.6.9-89, 2.6.10,
2.6.14, 2.6.16, 2.6.18, 2.6.25, 2.6.26, 2.6.27, 2.6.29.4, 3.0.13 and 3.0.101.
■ Checkpoint files should be created and restarted using the same machine.
The tool issues warnings when you try to restart a checkpoint file from a different
machine. The warning message can be ignored if the restart is always successful. For
example, in a homogenous virtual machine computation environment, the host name
might be different, but the OS version and configuration are the same. Thus, the warning
message can be ignored.
If you are creating a checkpoint file that you plan to restart using a different license
server, add the restart license server to the LM_LICENSE_FILE variable before invoking
Conformal and before creating the checkpoint file; otherwise, you will not be able to
restart the checkpoint file with the new server. For example:
setenv LM_LICENSE_FILE "$LM_LICENSE_FILE":5280@mylic01
■ Do not enter the GUI mode if you plan to create a checkpoint file that you will want to run
later in the GUI mode.
If a checkpoint file is created after having entered GUI mode, when the checkpoint file is
restarted, it will restart and run in non-GUI mode and the GUI mode is disabled. If a
checkpoint file is created before entering the GUI mode, the checkpoint file can enter the
GUI mode when it is restarted.
The Conformal -restart_checkpoint option tries to restore the process to the same
status as when it was checkpointed. If a file cannot be re-opened during restart
(permission problems, for instance), Conformal issues an error and opens it at /dev/
null with only read permissions. You can restart again in the correct directory, or ask
the file owner to change the permissions and try restarting the checkpoint file.
<Conformal_tool> -restart_checkpoint [-protect <password>]
■ You cannot specify the stack limit in a restarted tool process. You can, however, specify
the stack limit when you issue the CHECKPOINT command:
Related Commands
INFO CHECKPOINT
CLOSE SCHEMATICS
CLOse SChematics
(Setup / LEC Mode)
Related Command
OPEN SCHEMATICS
Note: This is a Conformal Low Power command and is for the CPF flow only.
Tcl Command
commit_power_intent
Parameters
-INSERT_ISOLATION
Inserts isolation cells for all isolation rules that are inserted for
equivalence checking. Level shifters, switch cells, and retention
are not inserted.
Note: This is for the CPF flow only.
-GOLden Inserts low power cells in the Golden design. This is the
default.
-REVised Inserts low power cells in the Revised design.
-BOTH Inserts low power cells in both the Golden and Revised
designs.
Related Command
COMMIT POWER INTENT
COMPARE
COMpare
[-EFFORT < Low | Medium | High | Auto | LIght | COMPlete>]
[-ABORT_Print]
[-ABORT_Stop <integer>]
[-GATE_TO_GATE]
[-NONEQ_Print]
[-NONEQ_Stop <integer>]
[-Random [<integer>]]
[-SIngle]
[-THREADS <integer>[,<integer>]]
[-TIMEstamp]
[-TURBO | -NOTURBO]
[-Verbose]
(LEC Mode)
Starts the equivalency checking comparison between the Golden and Revised designs on the
added compared points. During the comparison, the following information is displayed:
■ Progress percentile number, which displays the completion rate
■ Running count, which displays the number of key points that have been compared along
with the total number of non-equivalent key points
Each compared point results in a status drawn from the following five possibilities:
■ Equivalent
■ Inverted equivalent
■ Nonequivalent
■ Abort
■ Not compared
When Conformal completes the comparison, it displays a summary table of the number of
equivalent and nonequivalent compared points.
Notes:
■ If you must interrupt the comparison, the Control-C keys stop the process.
■ By default, when the clock port is disabled, the data cone will not be compared. The
software might perform modeling that disables the clock port, so the disabled clock might
not necessarily mean the clock in original netlist is disabled.
■ For datapath intensive designs, run time can take longer when the ANALYZE DATAPATH
command is not used before the comparison.
Tcl Command
compare
Parameters
-NONEQ_Stop <integer> Stops the comparison after finding the specified number of
nonequivalent points.
-Random <integer> Performs random-based simulation on the compare points,
where integer specifies the number of random patterns
to use. The default is 1600.
-SIngle Compares each key point as a single point. By default, the
COMPARE command compares by key point groups.
-THREADS <integer>[,<integer>]
Specifies the minimum and maximum number of compare
threads. If only one number entered, this specifies both the
minimum and maximum number of threads. For example,
'-threads 2' specifies two threads; '-thread 2,4'
specifies a minimum of two threads, and a maximum of four
threads.
This supersedes the SET PARALLEL OPTION -threads
setting.
-TIMEstamp Displays the system time (HH:MM format) of the last
compare status update.
-TURBO Specifies using parallel turbo threads.
-NOTURBO Specifies without using parallel turbo threads. This is the
default.
-Verbose Displays detailed comparison information, such as the
circuit duplication in multithreaded comparison.
Examples
The following is a set of sample commands that shows this and related commands in context.
The following set of commands assumes that you have read in your library, design, and have
switched to the LEC mode.
1. Use the ADD COMPARED POINTS command to add mapped points to the compare list.
LEC> add compare point -all
//2 compared points added to compare list
2. Use the COMPARE command to start the equivalency comparison between the Golden
and Revised designs.
LEC> compare
============================================================================
Compared points PO Total
----------------------------------------------------------------------------
Equivalent 1 1
----------------------------------------------------------------------------
Nonequivalent 1 1
============================================================================
3. Use the REPORT COMPARE DATA command to report the nonequivalent points.
LEC> rep comp data -noneq
Compared points are: Nonequivalent
+ 11 PO /x + 11 PO /x
4. Use the ADD DYNAMIC CONSTRAINT command to add a dynamic constraint to the
design.
LEC> add dyn con 0 /c -gold
LEC> add dyn con 0 /c -rev
5. Use the REPORT DYNAMIC CONSTRAINTS to report the dynamic constraints in the
design.
LEC> report dynamic constraints
============================================================================
Design ID Type Value Name
----------------------------------------------------------------------------
Golden 3 PI 0 /c
Revised 3 PI 0 /c
============================================================================
6. Use the PROVE command to show whether the specified gates are equivalent or not
equivalent.
LEC> prove /x /x
//Compared points are: Nonequivalent
//(G) + 11 PO /x
//(R) + 11 PO /x
8. Use the REPORT MESSAGE command to show the message related to the comparison.
LEC> report message -compare -verb
// Warning: 1 DFFs/DLATs have 1 disabled clock port: skipped data cone comparison
(G) + 4 DLAT /z_reg - skipped data cone z_reg with corresponding clock cone z_reg
(R) + 4 DLAT /z_reg - skipped data cone z_reg with corresponding clock cone z_reg
Related Commands
ADD COMPARED POINTS
ANALYZE DATAPATH
DIAGNOSE
PROVE
USAGE
COMPARE LIBERTY
COMpare LIberty
(Setup/LEC Mode)
Description
Note: This is a Conformal Low Power command.
The following lists some of the over 70 attributes compared by this command:
■ is_macro_cell
■ pg_type
■ switch_function
■ pg_function
■ voltage_name
■ std_cell_main_rail
■ related_power_pin
■ related_ground_pin
■ related_bias_pin
■ is_isolated
■ power_down_function
■ switch_pin
■ is_analog
■ isolation_enable_condition
■ antenna_diode_type
■ antenna_related_power_pin
■ antenna_related_ground_pin
Use this command after you have read in the Liberty library. No design needs to be read to
use this command.
Tcl Command
compare_liberty
Example
The following is a sample dofile that reads in two Liberty libraries and compares them:
read library -liberty gold_sample.lib -golden -lp
read library -liberty revs_sample.lib -revised -lp
compare liberty
report compared liberty -verbose
After you read in the libraries, use the COMPARE LIBERTY command to compare the two
libraries, and the REPORT COMPARED LIBERTY to view the details of the comparison.
Related Commands
DELETE LIBERTY_COMPARE FILTER
Note: This is a Conformal Low Power command and is for the 1801 flow. For CPF flow, this
command is the same as "check lowpower cells".
Checks the consistency of the supply set and applied retention strategy of mapped state
elements (DFF and DLAT) between Golden and Revised. Specifically, power domains are
compared; if they are not equivalent, the design may not be functionally equivalent. State
retention strategy is also compared for the part of retention power and ground supplies which
determine the power domain assignment. Different retention strategies can be applied when
the Golden and Revised power intent are different.
Tcl Command
compare_power_consistency
Parameters
-EXCLUDE_ICG_mapped_pair_retention_strategy_compare
Exclude the mapping state element pair at the retention
strategy comparison and the retention supply set
comparison when either one side element has the
integrated clock gating attribute.
-EXCLUDE_DIODE_CLAMP_CELL
Exclude the mapping black box pair at the supply set
comparison when the black box instances in both side
contain pins with antenna_diode attribute.
Related Commands
READ POWER INTENT
Compares the supply network connectivity between the golden design and the revised
design. The comparison starts from each supply source and ensures that a supply network
is implemented consistently with the corresponding supply network on the other side, where
two supply networks are considered corresponded if they are driven or partially driven by the
supply sources that are mapped to each other by name. The supply network comparison
results in a status with the following three possibilities:
■ Equivalent: The two supply networks are mapped and are driven by the same supply
sources
■ Nonequivalent: There is at least one supply point of the supply network whose driving
supply source is different than that of the mapped supply point.
■ Inconclusive: There is at least one supply point of the supply network that does not have
a corresponding mapped supply point in the other design, while all of the mapped supply
points are driven by the same supply source.
Tcl Command
compare_power_grid
Parameters
Examples
To filter the supply points that are implemented and only used for always-on buffers/inverters
insertions.
TCL_SETUP > compare_power_grid -exclude unmapped_aon_buf_inv_supply
In the below example, u1 is the domain boundary instance. u1/y1 and u1/y2 of the revised
supply network and u1/x1 of the golden supply network are simple domain elements because
their supply sources are implied or implemented by the automatic connections from the
domain, which can be filtered with -exclude_unmapped_simple_domain_element
option.
Related Commands
ADD MAPPED INSTANCE
This is a Conformal Low Power command. Compares the Golden power intent specification
against the revised power intent specification.
Design objects that are specified in the power intent can be renamed during synthesis and
place-and route causing subsequent attempts to verify the design data using the original
power specification to fail. Implementation tools are then used to write out revised power
intent using the new design object names. Power intent comparison is necessary to ensure
that the revised power intent has not changed the intention of the original power intent
specification.
Note: The two power intent files must be of the same format type (either CPF or UPF).
The following lists some of the power intent aspects compared by this command:
■ Nominal conditions
■ Library sets and Liberty file names
■ Power modes
■ Analysis views and SDC file names
Note: This command does not compare design objects such as instance names and pin
names, because these can be changed by the implementation tools.
Use this command after you have read in the library, design data, library power intent, and
Golden and Revised design power intent. You can use this command before or after you
commit the power intent. See example section for a sample dofile.
Tcl Command
compare_power_intent
Parameters
Example
Related Commands
READ DESIGN
READ LIBRARY
CONTINUE
CONTinue
(Setup / LEC Mode)
Used in conjunction with the BREAK command in a dofile, when a dofile executes the BREAK
command, Conformal issues a warning and prompts you to use the CONTINUE command.
The CONTINUE command has no effect if you type it without being prompted by Conformal.
The CONTINUE command supports mixed GUI and non-GUI mode. For example, you can run
a dofile in non-GUI mode, encounter a break in the dofile, issue set gui on, and run
continue from the GUI. The same applies when you break in the GUI mode: switch to
command mode and enter continue.
Conformal also supports nested breaks inside dofiles, working in a stack fashion. For
example, when you type in continue from a lower-level dofile, Conformal proceeds until it
encounters the next BREAK command.
Example
//Warning: Break dofile 'my_dofile' at line 32. Use 'continue' command to continue.
LEC> continue
Related Commands
BREAK
DOFILE
COPY MODULE
COPy MOdule
<[-Golden | -Revised] <source_module_name>
[-Revised | -Golden] <target_module_name>>
[-LOGIC | -PINDIR]
[-USE_RENAME_RULE | -NOUSE_RENAME_RULE]
(Setup Mode)
Copies the logic or pin direction from a source module in one design to a target module in the
other design. If you must copy both the logic and the pin direction, use two separate
commands.
Tcl Command
copy_module
Parameters
-USE_RENAME_RULE Uses renaming rules for matching pin and module names.
This is the default.
-NOUSE_RENAME_RULE Do not use renaming rules for matching pin and module
names.
Related Command
ASSIGN PIN DIRECTION
DELETE ALIAS
DELete ALias
<aliasname* ...>
(Setup / LEC Mode)
Deletes aliases created with the ADD ALIAS command. Use the REPORT ALIAS command
to display a list of all aliases.
Wildcard: The wildcard (*) represents any zero or more characters in alias names.
Tcl Command
delete_alias
Parameters
Related Commands
ADD ALIAS
REPORT ALIAS
Deletes specified blackboxes from the design. These blackboxes were either created with the
ADD BLACK BOX command or were a part of the original design.
Use the REPORT BLACK BOX command to display a list of all blackboxes.
Wildcard: The wildcard (*) represents any zero or more characters in module names.
Tcl Command
delete_black_box
Parameters
Related Commands
ADD BLACK BOX
DELETE CLOCK
DELete CLock
<-ALL | net_name...> [-Module <module_name>]
[-Golden | -Revised]
(Setup Mode)
Tcl Command
delete_clock
Parameters
-ALL Deletes all the defined clocks within the given defaults.
<net_name ...> Deletes the net(s) that were defined as clock(s) and specified
in this list.
-Module <module_name> Specifies that the defined clock pin is located in this module.
-Golden Deletes the clock(s) from the Golden design. This is the
default.
-Revised Deletes the clock(s) from the Revised design.
Related Commands
ABSTRACT LOGIC
ADD CLOCK
READ PATTERN
REPORT CLOCK
RESOLVE
Deletes compared points originally added with the ADD COMPARED POINTS command. If the
compared point is deleted from the Golden design, Conformal also deletes its mapped
compared point from the Revised design. Alternately, if the compared point is deleted from
the Revised design, Conformal also deletes its mapped compared point from the Golden
design.
Use the REPORT COMPARED POINTS command to display a list of all added compared
points.
Wildcard: The wildcard (*) represents any zero or more characters in instance and pin paths.
Tcl Command
delete_compared_points
Parameters
Related Commands
ADD COMPARED POINTS
COMPARE
Deletes cut points originally added with the ADD CUT POINT command.
Use the REPORT CUT POINT command to display a list of all added cut points.
Tcl Command
delete_cut_point
Parameters
Related Commands
ADD CUT POINT
REPORT PATH
Deletes sequential constant and/or sequential merge don’t-touch registers to Golden and/or
Revised designs which were specified with the add_donttouch_registers command.
Tcl Command
delete_donttouch_registers
Parameters
<register_pathname* ...>
-seq_constant Deletes sequential constant don’t-touch registers.
-seq_merge Deletes sequential merge don’t-touch registers.
-Golden Deletes don’t-touch registers to the Golden design.
-Revised Deletes don’t-touch registers to the Revised design.
-Both Deletes don’t-touch registers to both the Golden and Revised
designs.
Related Commands
ADD DONTTOUCH REGISTERS
Deletes dynamic constraints originally added with the ADD DYNAMIC CONSTRAINTS
command.
Use the REPORT DYNAMIC CONSTRAINTS command to display a list of all added dynamic
constraints.
Tcl Command
delete_dynamic_constraints
Parameters
Related Commands
ADD DYNAMIC CONSTRAINTS
PROVE
Delete ignored port, instance, or module added by command ADD IGnored Grid.
Tcl Command
delete_ignored_grid
Parameters
Related Commands
COMPARE POWER GRID
Deletes input pins originally added as ignored inputs in the Golden or Revised design with the
ADD IGNORED INPUTS command.
Use the REPORT IGNORED INPUTS command to display a list of all added ignored input pins.
Wildcard: The wildcard (*) represents any zero or more characters in ignored input names.
Tcl Command
delete_ignored_inputs
Parameters
-ALL_Pin Deletes all previously added ignored inputs within the given
defaults.
<primary_pin* ...> Deletes the specified pins as ignored inputs. This accepts
wildcards.
-ROot Deletes the ignored inputs in the root module. This is the
default.
-Module <module_name>
Deletes the ignored inputs from the specified module.
-ALL_Module Deletes the ignored inputs from all of the modules, including the
root module.
-Golden Deletes the specified ignored inputs from the Golden design.
This is the default.
-REvised Deletes the specified ignored inputs from the Revised design.
-Both Deletes the specified ignored inputs from both the Golden and
Revised designs.
Related Commands
ADD IGNORED INPUTS
Deletes output or I/O pins originally added as ignored outputs with the ADD IGNORED
OUTPUTS command.
Use the REPORT IGNORED OUTPUTS command to display a list of all added ignored output
or I/O pins.
Wildcard: The wildcard (*) represents any zero or more characters in ignored output names.
Tcl Command
delete_ignored_outputs
Parameters
-ALL_Pin Deletes all added ignored outputs within the given defaults.
<primary_pin* ...> Deletes the specified pins as ignored outputs. This accepts
wildcards.
-ROot Deletes the ignored outputs in the root module. This is the
default.
-Module <module_name>
Deletes the ignored outputs from the specified module.
-ALL_Module Deletes the ignored outputs from all modules, including the root
module.
-Golden Deletes the specified ignored outputs from the Golden design.
This is the default.
-REvised Deletes the specified ignored outputs from the Revised design.
-Both Deletes the specified ignored outputs from both the Golden and
Revised designs.
Related Commands
ADD IGNORED OUTPUTS
Deletes instance attributes originally added with the ADD INSTANCE ATTRIBUTE command.
Use the REPORT INSTANCE ATTRIBUTE command to display a list of all added instance
attributes.
Tcl Command
delete_instance_attribute
Parameters
Related Commands
ADD INSTANCE ATTRIBUTE
Deletes instance constraints originally added with the ADD INSTANCE CONSTRAINTS
command.
Use the REPORT INSTANCE CONSTRAINTS command to display a list of all added instance
constraints.
Tcl Command
delete_instance_constraints
Parameters
Related Commands
ADD INSTANCE CONSTRAINTS
Deletes instance equivalences originally added with the ADD INSTANCE EQUIVALENCES
command.
Use the REPORT INSTANCE EQUIVALENCES command to display a list of all added instance
equivalences.
Tcl Command
delete_instance_equivalances
Parameters
<instance_pathname* ...>
Deletes equivalences on the specified instance path(s). This
accepts wildcards.
-All Deletes all instance equivalences within the given defaults.
-Golden Deletes instance equivalences in the Golden design. This is the
default.
-Revised Deletes instance equivalences in the Revised design.
-Both Deletes instance equivalences in both the Golden and Revised
designs.
Related Commands
ADD INSTANCE EQUIVALENCES
Deletes the specified instance renaming rule (added through the ADD INSTANCE RENAMING
COMMAND).
Tcl Command
delete_instance_renaming
Parameters
Related Commands
ADD INSTANCE RENAMING
MOS2BUFIF
REPORT MESSAGES
This command deletes information added to key points using the with the ADD KEYPOINT
INFO command.
Tcl Command
delete_keypoint_info
Parameters
Related Commands
ADD KEYPOINT INFO
Description
Note: This is a Conformal Low Power command.
Deletes Liberty compare filters that were added by the ADD LIBERTY_COMPARE FILTER
command.
Tcl Command
delete_liberty_compare_filter
Paramters
<filter_name*> ... Specifies the name of the filter(s) to delete. Wildcards are
supported.
Example
■ The following command deletes Liberty compare filter 'ign_related_power'
delete liberty_compare filter ign_related_power
Related Commands
ADD LIBERTY_COMPARE FILTER
COMPARE LIBERTY
Deletes low power cells that were originally defined for modules with the ADD LOWPOWER
CELLS command.
Use the REPORT LOWPOWER CELLS command to display a list of the low power cells used
in the design.
Tcl Command
delete_lowpower_cells
Parameters
<module_name*> Deletes previously added low power cells from the specified
modules. This accepts wildcards.
-ALL Deletes previously added low power cells from all modules. All
applies within the given defaults.
-Both Deletes the low power cells in the Golden and Revised designs.
This is the default.
-Golden Deletes the low power cells in the Golden design.
-Revised Deletes the low power cells in the Revised design.
Related Commands
ADD LOWPOWER CELLS
Additionally, Conformal deletes all compared points associated with the deleted mapped
points.
Use the REPORT MAPPED POINTS command to display a list of all mapped points in the User
and System classes of the Golden and Revised designs.
Wildcard: The wildcard (*) represents any zero or more characters in instance or pin paths
of mapped points.
Tcl Command
delete_mapped_points
Parameters
Related Commands
ADD MAPPED POINTS
The DELETE MAPPING MODEL command deletes the phase information that was added for
the given modules using the ADD MAPPING MODEL command.
Tcl Command
delete_mapping_model
Parameters
Examples
The following command deletes the phase information that is attached to module "mymod"
in the Revised design.
MODE> delete mapping model mymod -revised
Related Commands
Deletes attributes originally assigned to modules with the ADD MODULE ATTRIBUTE
command.
Use the REPORT MODULE ATTRIBUTE command to display a list of all added module
attributes.
Tcl Command
delete_module_attribute
Parameters
<module_name ...> Deletes previously added attributes from the specified modules.
-ALL Deletes previously added attributes from all modules within the
given defaults.
-PIPELINE_Retime Deletes attributes previously added for pipeline-retiming.
-COMPARE_Effort Deletes compare effort levels previously added to modules.
-CPU_Limit Deletes the CPU time limit imposed with the ADD MODULE
ATTRIBUTE command.
-NOBBOXEMpty Deletes attributes previously added by ADD MODULE
ATTRIBUTE -NOBBOXEMpty attribute.
-NOFLatten Deletes attributes previously added by ADD MODULE
ATTRIBUTE -NOFlatten.
-NODYNAMIC_RESOLUTION
Deletes attributes previously added by ADD MODULE
ATTRIBUTE -NODYNAMIC_RESOLUTION.
-ISOlate_module <g_instance_name><r_instance_name>
Deletes the module attribute required for module isolation
(added by ADD MODULE ATTRIBUTE -isolate_module
option).
-FLAT_ECO_module Deletes attribute previously added and specified by the ADD
MODULE ATTRIBUTE -FLAT_ECO_module attribute.
-Golden Deletes the specified module attributes in the Golden design.
This is the default.
-Revised Deletes the specified module attributes in the Revised design.
Related Commands
ADD MODULE ATTRIBUTE
Deletes name alias as specified in a JSON data file, or deletes all existing name aliases.
The JSON data file must use following format for the array of name aliases to delete:
[{"m":"<module_name>","t":"ins","n":"<name>",...},...]
The tool will delete the name alias of keypoint "name" in "module_name".
Tcl Command
delete_name_alias
Parameters
<filename> Specifies the JSON file that contains the name aliases to
delete.
-ALL Delete name aliases for the specified design (Golden or
Revised).
-GOLden Delete name alias data for the Golden design.
-REVised Delete name alias data for the Revised design.
Related Commands
ADD NAME ALIAS
REPORT GATE
Deletes the unidirection that was placed on transistor-MOS instances with the ADD MOS
DIRECTION command.
Use the REPORT MOS DIRECTION command to display a list of all transistor-MOS direction
instances.
Tcl Command
delete_mos_direction
Parameters
Related Commands
ABSTRACT LOGIC
ADD CLOCK
DELETE CLOCK
READ PATTERN
REPORT CLOCK
RESOLVE
Deletes attributes that were placed on transistor-MOS nets with the ADD NET ATTRIBUTE
command.
Use the REPORT NET ATTRIBUTE command to display a list of all attributes placed on
transistor-MOS nets.
Tcl Command
delete_net_attribute
Parameters
Related Commands
ABSTRACT LOGIC
ADD CLOCK
DELETE CLOCK
READ PATTERN
REPORT CLOCK
RESOLVE
Deletes either the Golden or Revised design net constraints originally added with the ADD
NET CONSTRAINTS command.
Use the REPORT NET CONSTRAINTS command to display a list of all added net constraints.
Tcl Command
delete_net_constraints
Parameters
-Golden Deletes net constraints from the Golden design. This is the
default.
-Revised Deletes net constraints from the Revised design.
-Both Deletes net constraints from both the Golden and Revised
designs.
Related Commands
ADD NET CONSTRAINTS
Deletes the specified module names originally added with the ADD NOBLACK BOX command.
Use the REPORT NOBLACK BOX command to display a list of all of the modules that will be
resolved (flattened) to their parents' modules during hierarchical dofile script generation.
Wildcard: The wildcard (*) represents any zero or more characters in module names.
Tcl Command
delete_noblack_box
Parameters
Related Commands
ADD NOBLACK BOX
Deletes the specified file pathnames originally added with the ADD NOTRANSLATE
FILEPATHNAMES command.
Use the REPORT NOTRANSLATE FILEPATHNAMES command to display a list of all of the
library and design file pathnames.
Wildcard: The wildcard (*) represents any zero or more characters in module names.
Tcl Command
delete_notranslate_filepathnames
Parameters
Related Commands
ADD NOTRANSLATE FILEPATHNAMES
Deletes the specified module names originally added with the ADD NOTRANSLATE MODULES
command.
Use the REPORT NOTRANSLATE MODULES command to display a list of all of the library and
design module names that will not be compiled.
Wildcard: The wildcard (*) represents any zero or more characters in module names.
Tcl Command
delete_notranslate_modules
Parameters
Related Commands
ADD NOTRANSLATE MODULES
READ DESIGN
READ LIBRARY
Deletes the specified file pathname originally added with the ADD NOTRANSLATED LINES
command.
Use the REPORT NOTRANSLATED LINES command to display a list of all of the library and
design file pathnames.
Wildcard: The wildcard (*) represents any zero or more characters in partial filename.
Tcl Command
delete_notranslated_lines
Parameters
Related Commands
ADD NOTRANSLATED LINES
Deletes the output pin equivalences placed on output boundary module pins with the ADD
OUTPUT EQUIVALENCES command.
Use the REPORT OUTPUT EQUIVALENCES command to display a list of all added output pin
equivalences.
Wildcard: The wildcard (*) represents any zero or more characters in output boundary
module pin names.
Tcl Command
delete_output_equivalences
Parameters
-ALL_Pin Deletes all output pin equivalences within the given defaults.
<primary_pin* ...> Deletes output pin equivalences from the listed output
boundary module pins.
-ROot Deletes the output pin equivalences from the root module.
-Module <module_name>
Deletes the output pin equivalences from the specified module.
-ALL_Module Deletes the output pin equivalences from all modules.
-Golden Deletes the specified output pin equivalences in the Golden
design. This is the default.
-Revised Deletes the specified output pin equivalences in the Revised
design.
-Both Deletes the specified output pin equivalences in both the
Golden and Revised designs.
Related Commands
ADD OUTPUT EQUIVALENCES
Deletes the output stuck_at values placed on output boundary module pins with the ADD
OUTPUT STUCK_AT command.
Use the REPORT OUTPUT STUCK_AT command to display a list of all added output
stuck_at values and their pin names.
Tcl Command
delete_output_stuck_at
Parameters
-ALL_Pin Deletes all output stuck_at values within the given defaults.
<primary_pin* ...> Deletes the output stuck_at values associated with the listed
output boundary module pins. This accepts wildcards.
-ROot Deletes the output stuck_at values in the root module
boundary pin. This is the default.
-Module <module_name*>
Deletes the output stuck_at values in the specified module.
This accepts wildcards.
-All Deletes the output stuck_at values in all output boundary
module pins.
-Golden Deletes the output stuck_at values in the Golden design.
This is the default.
-Revised Deletes the output stuck_at values in the Revised design.
-Both Deletes the output stuck_at values in both the Golden and
Revised designs.
Related Commands
ADD OUTPUT STUCK_AT
Deletes all of the specified partition key points originally added with the ADD PARTITION
KEY_POINT command.
Use the REPORT PARTITION KEY_POINT command to display a list of all added partition
key points.
Tcl Command
delete_partition_key_point
Related Commands
ADD PARTITION KEY_POINT
Deletes the partition points that were created with the ADD PARTITION POINTS command.
Note: Partition points are always deleted in pairs.
Tip
You can get the pathname of the partition point with the REPORT PARTITION
POINT command.
Caution
Deleting partition (CUT) points in LEC mode causes flattened netlists to
change. As a result, all the gate-ids are subjected to change. Deleting cut
points does not affect the existing compare points list; however, all the
compare data is invalidated after deleting cut points.
Tcl Command
delete_partition_points
Parameters
<pathname> Specifies the name of the path for the partition points to be
deleted.
-All Specifies that all the existing partition points will be deleted.
-BAD_cuts Automatically deletes the set of partition points that cause false
nonequivalence.
Related Commands
ADD PARTITION POINTS
Deletes physical cells from the physical_cell_list, which is created by the EXTRACT
PHYSICAL CELL command.
Tcl Command
delete_physical_cells
Parameters
Related Commands
ADD PHYSICAL CELLS
Deletes pin binding pairs originally added with the ADD RENAMING RULE command. Use
REPORT PIN BINDING command to display a list of all of the pairs of pin binding.
Tcl Command
delete_pin_binding
Parameters
-MOdule Specifies the module pair that the pin binding rules are applied
in. Default module pair is the golden and revised top modules.
Related Commands
ADD RENAMING RULE
Deletes constraints originally placed on named primary input pins with the ADD PIN
CONSTRAINTS command.
Use the REPORT PIN CONSTRAINTS command to display a list of all added pin constraints.
Wildcard: The wildcard (*) represents any zero or more characters in primary input names.
Tcl Command
delete_pin_constraints
Parameters
-ALL_Pin Deletes all constraints placed on primary input pins within the
given defaults.
<primary_pin* ...> Deletes constraints from the listed primary inputs.
-Module <module_name>
Deletes pin constraints from the specified module.
-Golden Deletes the specified pin constraints from the Golden design.
This is the default.
-Revised Deletes the specified pin constraints from the Revised design.
-Both Deletes the specified pin constraints from both the Golden and
Revised designs.
Related Commands
ADD PIN CONSTRAINTS
Deletes the added pin equivalences from the specified primary input pins. These
equivalences were placed on primary input pins with the ADD PIN EQUIVALENCE command.
Use the REPORT PIN EQUIVALENCES command to display a list of all of the added pin
equivalences.
Wildcard: The wildcard (*) represents any zero or more characters in primary input names.
Tcl Command
delete_pin_equivalences
Parameters
-ALL_Pin Deletes all added pin equivalences within the given defaults.
<primary_pin* ...> Deletes pin equivalences from the listed primary input pins. (Pin
equivalence was originally added with the ADD PIN
EQUIVALENCES command.)
-ROot Deletes pin equivalences from the root module.
-Module <module_name>
Deletes pin equivalences from the specified module.
-ALL_Module Deletes pin equivalences from all modules.
-Golden Deletes the specified pin equivalences from the Golden design.
This is the default.
-REvised Deletes the specified pin equivalences from the Revised
design.
-Both Deletes the specified pin equivalences from both the Golden
and Revised designs.
Related Commands
ADD PIN EQUIVALENCES
Deletes the specified power intent compare filters. Power intent compare filters are added
using the ADD POWER_INTENT_COMPARE FILTER command.
Tcl Command
delete_power_intent_compare_filter
Parameters
Example
■ The following command deletes power intent compare filters 'iso_loc'
delete power_intent_compare filter iso_loc
Related Commands
COMPARE POWER INTENT
Deletes specified primary inputs that were originally added with the ADD PRIMARY INPUT
command. After you delete the primary input pins from either the Golden or Revised design,
the associated nets become floating nets, unless there are other net drivers.
Use the REPORT PRIMARY INPUTS command to display a list of all primary inputs.
Wildcard: The wildcard (*) represents any zero or more characters in paths of primary
inputs.
Tcl Command
delete_primary_inputs
Parameters
Related Commands
ADD PRIMARY INPUT
Deletes primary outputs that were originally added with the ADD PRIMARY OUTPUT
command. When you delete the primary output pins from the Golden or Revised design, the
nets become floating nets, unless there are other net drivers.
Use the REPORT PRIMARY OUTPUTS command to display a list of all primary outputs.
Wildcard: The wildcard (*) represents any zero or more characters in paths of primary
outputs.
Tcl Command
delete_primary_outputs
Parameters
Related Commands
ADD PRIMARY OUTPUT
DELETE PROJECT
DELete PRoject
<-Run <integer ...> >
(Setup/LEC Mode)
This command deletes the LEC run information (specified by the Run number) from the
current LEC project. Use the SET PROJECT NAME command to set the current LEC project.
Tcl Command
delete_project
Parameters
Related Commands
ANALYZE PROJECT
Deletes renaming rules originally added with the ADD RENAMING RULE command.
Use the REPORT RENAMING RULE command to display a list of all of the renaming rules and
their rule numbers.
Tcl Command
delete_renaming_rule
Parameters
-All Deletes all previously added renaming rules from the Map,
Module, Pin, and Instance categories.
If you do not specify a category, Conformal deletes all
previously added renaming rules from the Map category.
<rule_name> Deletes the specified renaming rule.
-MAp Deletes only map renaming rules. This is the default.
-MOdule Deletes only module renaming rules.
-PIn Deletes only pin renaming rules.
-INSTance Deletes only instance renaming rules.
Related Commands
ADD RENAMING RULE
CHANGE NAME
READ DESIGN
READ LIBRARY
Deletes the state retention mapping rules added using the ADD REtention_register
Mapping command.
Note: Use the REPORT RETENTION MAPPING command to display a list of all the state
retention mapping rules. Note that the default rule added by the system can never be deleted.
For a description of the default rules that are added by the system, see CHECK LOWPOWER
CELLS.
Tcl Command
delete_retention_register_mapping
Parameters
-All Deletes all the state retention register mapping rules added
using the ADD RETENTION MAPPING Mapping command.
This option does not delete the default rule added by the
system.
<rule_name> Deletes the specified state retention mapping rule.
Note: The default rule added by the system cannot be deleted.
Related Commands
ADD RETENTION MAPPING
Tcl Command
delete_rule_filter
Parameters
Related Commands
ADD RULE FILTER
Deletes the runtime limit for the specified module, hierarchical_compare and
commands. The unit of time is in seconds..
Tcl Command
delete_runtime_limit
Parameters
-MODule Deletes the runtime limit of LEC in the specified module. If the
module name is not specified, the runtime limit of the root
module will be deleted.
-HIER_compare Deletes the runtime limit of the hierarchical comparison.
-COMmand Deletes the runtime limit of the specified command. If the
command name is not specified, the runtime limit of all the
commands would be deleted.
Related Commands
DELETE RUNTIME LIMIT
Deletes search paths Conformal uses for the READ DESIGN and READ LIBRARY commands.
Use the REPORT SEARCH PATH command to display a list of all search paths.
Tcl Command
delete_search_path
Parameters
-All Deletes all previously added search paths within the given defaults.
<pathname ...> Deletes the specified search paths.
-Design Deletes search paths used by the READ DESIGN command. This
is the default.
-Library Deletes search paths used by the READ LIBRARY command.
-POWER_intent This is a low power command option. Deletes the search path(s) for
power intent files.
-Golden Deletes search paths used by the Golden design or library. This is
the default.
-Revised Deletes search paths used by the Revised design or library.
-RECursive Deletes the subdirectories of the specified directory from the
search paths.
Related Commands
ADD SEARCH PATH
READ DESIGN
READ LIBRARY
DELETE SEQ_CORRESPONDENCE
DELete SEQ_CORRespondence
<-ALL | <golden_identifier> <revised_identifier> >
(LEC Mode)
Deletes the sequential corresponding points that were added with the ADD SEQ_CORR or
ANALYZE RETIMING -general command.
Tcl Command
delete_seq_correspondence
Parameters
Example
The following command deletes all the sequential corresponding points:
delete seq_corr -all
Related Commands
ANALYZE RETIMING
ADD SEQ_CORRESPONDENCE
REPORT SEQ_CORRESPONDENCE
DELETE SUPPLY
DELete SUpply
<object_list>
[-ROOT | -Module <name_list*> | -ALL]
[-PORT | -GLOBAL ]
[-Golden| -Revised | -Both]
(Setup Mode)
Deletes power and ground pins in the design that were defined with the ADD SUPPLY
command.
Tcl Command
delete_supply
Parameters
<object_list> Specifies that the list of net or port names that will have
their attribute settings deleted.
-ROOT Delete this supply attribute to the specified objects in the
current scope and all hierarchy of this scope. This is the
default.
-Module <name_list*> Delete the attribute setting to the specified module. This
accepts wildcards.
-ALL Deletes the attribute settings to the objects for all
modules.
-PORT The defined object(s) must be the port(s) at the root or
the specified module level. This is the default.
-GLOBAL The defined object(s) could be the port(s) and wire(s) in
the hierarchy of the root or the specified module.
-Golden Specifies that the listed names are from the Golden
design. This is the default.
-Revised Specifies that the listed names are from the Revised
design.
-Both Specifies that the listed names are from both the Golden
and Revised designs.
Related Commands
ADD SUPPLY
REPORT SUPPLY
Use the REPORT TIED SIGNALS command to display a list of all of the tied signals.
Tcl Command
delete_tied_signals
Parameters
Related Commands
ADD TIED SIGNALS
DIAGNOSE
DIAgnose
<<gate_id> | <instance_pathname> | <pin_pathname>
[-Golden | -Revised]
[-SUPport]
[-MERge]
[-NUm <integer>]
| -SUMmary [integer][-SOrt <SUpport | SIze>]
|[-NOneq]>
[-GROup]
[-VERBose]
(LEC Mode)
Runs diagnosis on a specified compared point. Specify the compared point by its gate
identification number, instance path, or a pin path. Use this command to determine why the
software identified nonequivalence between compared points.
The diagnosis displays all of the non-corresponding support key points with a list of all likely
error candidates from the Revised design. The list organizes likelihood in descending order
with 1.00 being the greatest possible error candidate.
Use the REPORT ENVIRONMENT command to display the maximum diagnosis candidates
setting.
Note: The syntax above assumes you are diagnosing mapped compare points (where you
only need to specify one compare point). When you are diagnosing instance/sequential
merge nonequivalence, you must specify two compare points.
Tcl Command
diagnose
Parameters
Examples
Note: For a set of sample commands that shows this and related commands in context, see
the example for the COMPARE command.
diagnose -merge 6 10
The diagnose command specifies two compare points, the first in Golden design and the
second in the Revised design.
diagnose -revised 9 10
The diagnose command specifies two compare points in the Revised design.
Related Commands
PROVE
REPORT ENVIRONMENT
Tcl Command
diagnose_rule_check
Parameters
Example
The following command runs diagnosis on occurrence 1 in CROSSING2/1:
diagnose rule check CROSSING2/1
DOFILE
DOFile
<<filename> [-FORCE] | -SHOW_STACK>
[-NOECHO]
(Setup / LEC Mode)
Executes a set of commands contained in a specified file. If there is an error while the
Conformal software is executing the dofile script, it terminates the dofile execution and returns
to the system mode prompt.
Use the SET DOFILE ABORT command to specify how you want the Conformal software to
respond when an error message occurs. You can choose to terminate, continue, or exit the
session.
Use the BREAK command in a dofile script to terminate the dofile script and return to the
system mode prompt.
Note: The DOFILE command is recommended (over the Tcl source command, for example)
when executing a CFM command dofile.
Tcl Command
dofile
Parameters
Related Commands
BREAK
CONTINUE
ELABORATE DESIGN
ELAborate DEsign
[-PARAmeter [-INT | -STR | -ENUM | -TYPE] <parameter_name> <value>]
[-RAngeconstraint]
[-ROot <module_name>]
[-ROOTConfig <configuration_name>]
[-NOCONFiguration]
[-ROOTONLY]
[-GOlden | -REvised]
(Setup Mode)
Completes the READ DESIGN command specified with the -noelaborate option. During
this step, modules are synthesized and the complete design hierarchy is created.
This command is typically used for mixed design flows where the Verilog modules and VHDL
entity or architectures are read in separately. Then they can be elaborated using this
command.
Tcl Command
elaborate_design
Parameters
Related Commands
READ DESIGN
READ LIBRARY
EXIT
EXIt
[-Force]
(Setup / LEC Mode)
Ends the existing Conformal session and returns you to the operating system.
On exiting, Conformal returns a status code. A nonzero status code means there is a potential
error; that is, either no comparison was done or unmapped, abort, or nonequivalent points
exist. The exit status code consists of flags that represent different conditions.
By default, Conformal does not automatically save GUI settings for future sessions. To save
your preferred settings, use the GUI exit window and click the Save GUI settings check box.
Refer to the Conformal Equivalence Checking User Guide for additional information about
exit status codes and the procedure to save GUI settings.
Tcl Command
exit
Parameters
Physical cells do not affect the behavior of the circuit and therefore they are not necessary for
structural and functional analysis. However, a netlist containing physical cells may increase
run time and memory usage. To mitigate the run time and memory usage, you can remove
the physical cells in the design before performing any analysis or rule checks.
A cell is included in this list if it has satisfied all the following conditions:
■ Has no output pins
■ Is blackboxed
■ Not defined as macro model
■ Not defined as a diode clamp cell or with diode clamp pins
■ Only has supply pins
Once the list is created, you can report the list of physical cells (REPORT PHYSICAL CELLS),
add to the list (ADD PHYSICAL CELLS), or delete from the list and netlist (DELETE
PHYSICAL CELLS).
Tcl Command
extract_physical_cells
Parameters
-GOLden Extract the cell(s) from the Golden design. This is the default.
-REVised Extract the cell(s) from the Revised design.
-BOTh Looks for the cell(s) in both the Golden and Revised designs.
Related Commands
ADD PHYSICAL CELLS
FLATTEN
FLAtten
<-MODule <module_name> | -ALL>
[-Force | -NOForce]
[-Library | -NOLibrary]
[-MATCHHierarchy [-INSTancename | -NOINSTancename][-USE_RENaming_rules]]
[-Golden | -Revised]
(Setup Mode)
Tip
When using this command with Conformal ECO, you should use the -nolibrary
option to prevent flattening to the primitive level.
Removes all hierarchy on a specified module or for all modules in the database. If you do not
specify one or all modules, Conformal flattens the root module by default. Thus, this
command expands all of the gate primitive or transistor primitive devices into the cell that is
being flattened.
A cell that is to be flattened contains three cells. One cell has 25 gates and the other two are
the same, each with 33 gates. After flattening, the cell now contains 0 cells and 91 gates (1 *
25 + 2 * 33 = 91).
To ensure that the hierarchy matches between the designs, it is recommended that you match
the hierarchy between the Golden and Revised designs (FLATTEN -MATCHHierarchy)
before you use UNIQUIFY. Note that in the ECO flow, the module and instance names should
not be changed in the golden G1 netlist. Therefore, the FLATTEN and UNIQUIFY commands
should only be applied to the revised G2 netlist in that particular use case.
Tcl Command
flatten
Parameters
-MODule <module_name>
Related Command
RESOLVE
UNIQUIFY
FORWARD
FORward
[<integer>]
(LEC Mode)
Reports fan-out gate information from the currently displayed flatten gate information. The
fan-out gate you choose with this command becomes the current flattened gate. Use this
command to trace gates in place of repeatedly using the REPORT GATE command.
Note: This command does not report gates at the design level.
Tcl Command
forward
Parameters
<integer> Reports the specified fan-out gate. The value 1 denotes the first
fan-out. The default is 1.
Related Commands
BACKWARD
REPORT GATE
GENERATE DOFILE
GENerate DOfile
<verification_dir_name>
<-INPUT_DOFILE <dofile> |
[-GOLden <netlist_name>]
-REVised <netlist_name>>
-IMPLementation_information_directory <dir_name>
(Setup/LEC Mode)
Tcl Command
generate_dofile
Parameters
<verification_directory_name >
Name of the directory that will contain the generated
dofile. The directory will be named as
<verification_directory_name >.cfm and will be
created in the current directory.
-INPUT_DOFILE <dofile>
Specifies an input dofile.
Currently, only dofiles generated by the RTL Compiler
write_do_lec command are supported.
-Golden <netlist_name> Specifies the Golden netlist to verify. The default is
RTL.
-REVised <netlist_name> Specifies the Revised netlist to verify.
-IMPLementation_information_directory <dir_name>
Specifies the directory that contains the implementation
information. Currently, only fv/* directories generated
by RTL Compiler are supported.
Related Commands
READ IMPLEMENTATION INFORMATION
Generates a ROM primitive model that you can use to verify against a valid ROM circuit.
Conformal generates a ROM primitive that has the following interface:
■ Addr: Address bus for accessing ROM data.
■ Dout: Output data from ROM.
■ RE: Control clock for the output latch or flip-flop, when you set the -outstate option to
dlat or dff. When RE is high, ROM data is sampled.
■ CK: Address decode clock for ROM read operations. ROM is read when the clock is high.
This command reads in a code file that initializes the ROM. This code file should contain one
number per line, in binary format. The number of entries in the code file should match the
number of words in the memory. As Conformal reads the code file, it assigns each entry to a
successive word element in the memory.
The following illustrates sample contents for a code file called rom.code, which initializes a
4 X 4 ROM:
0000
1111
1010
0111
Note: To perform simulation, you must define the macro SIM.
Tcl Command
generate_rom_primitive
Parameters
-SIM <outfile> Specifies the output file for the ROM primitive.
-CODE_FILE <codefilename>
Specifies the code file that will initialize the ROM.
This code file should contain initialization data in
binary format.
-CODE_FILE_FORMAT [BIN | HEX]
Specifies the output file format for the ROM primitive.
-CODE_SIGNATURE Includes the signature generated in the ROM
primitive in the code file content.
-MOD <module_name> Specifies the module name of the ROM primitive that
is created.
-NO_ACCESS_OUT_LOW Fills the memory address with '0' when it is not
initialized. This is the default.
-NO_ACCESS_OUT_HIGH Fills the memory address with '1' when it is not
initialized.
Related Command
READ ROM PRIMITIVE
Examples
The following command generates a ROM model with a code file called rom.code.
generate rom primitive -sim VROM.v -code_file rom.code -mod VROM /
-code_file_format bin -no_access_out_low
GROUP
GROUP
<-Module <module_name>>
<-Instance <instance_name* ...>>
<-NEWModule <module_name> >
<-NEWInstance <instance_name>>
[-net_to_pin_name]
[-Golden | -Revised]
(Setup Mode)
Groups defined instances together so that they become a new submodule. This command is
the opposite of the RESOLVE command; it applies to submodules, latches, registers, gates,
and transistors. By default, this command assigns unique and arbitrary submodule pin
names.
Wildcard: The wildcard (*) represents any zero or more characters in existing instance
names.
Tcl Command
group
Parameters
-Module <module_name>
Specifies a module for which to apply the grouping.
-Instance <instance_name* ...>
Specifies the instances to group. This accepts wildcards.
-NEWModule <module_name>
Specifies the name of the new module.
-NEWInstance <instance_name>
Specifies the instance name for the new module.
-net_to_pin_name Specifies that the pin names of the new modules will be the
same as the nets connected to them, and not unique and
arbitrary.
Related Command
RESOLVE
GO HIER COMPARE
GO HIer_compare
<dofile_name>
[-CHECK_NONEQ]
[-COMPARE_String <string>]
[-DYNamic_hierarchy | -NODYNamic_hierarchy]
[-HIER_STATUS <file>]
[-NOANALYZE_abort | -ANALYZE_abort]
[-NOREStart | -REStart]
[-RETIMED_modules [-TOP | -NOTOP]]
[-ROOT_module <golden_module> <revised_module>]
[-VERBOSE]
(Setup Mode)
Smart LEC offers distributed hierarchical comparison, where modules can be compared in
parallel and over multiple computation resources. For a design with an evenly distributed
module complexity, performing the hierarchical comparison this way can significantly reduce
the turnaround time.
To achieve parallel efficiency, LEC uses workers to execute the module compare. A worker is
an LEC process used for module comparisons. Workers can be invoked on the localhost or
on remote machines.
In a run, workers collaborate with each other to compare the modules in parallel. When
switching between the different modules, workers quickly set the target module and perform
verification without reloading the design data. Workers can use all LEC multi-threading
features, including compare and module datapath analysis (MDP), to achieve massive
parallelization.
Tcl Command
go_hier_compare
Parameters
<dofile_name> Specifies the name of the hierarchical dofile that was generated
with the write_hier_compare_dofile command
-CHECK_NONEQ Identify NEQ modules before running the analyze_datapath
command and skip datapath analysis for these modules.
-COMPARE_String Replaces the compare command in the hierarchical dofile with
<string> a string of compare commands while running hierarchical
comparison.
If the option -compare_string <string> is also specified
with the write_hier_compare_dofile command, LEC still
replaces the commands while running hierarchical comparison.
Use the semi-colon character (;) to separate commands. Use
double quotes to surround each compare command (see
"Examples" section below).
-DYNamic_hierarchy Auto-flattens the submodules to propagate any design errors to
the top level. The flattened modules are merged to the next
level in the hierarchy and compared at that level. This is the
default.
Examples
The following is the distributed hierarchical comparison flow; it is very similar to a dynamic
hierarchical comparison, but steps 2 and 5 apply only to the hierarchical comparison flow:
For example, a dofile for a distributed hierarchical comparison flow would look like:
read_library lib.v -both
read_design Golden.v -verilog -golden
read_design revised.v -verilog -revised
add_pin_constraint 0 scan_en -revised
add_renaming_rule hier_rule1 "%s_%d$" "@1" -module -revised
set_parallel_option -workers localhost localhost localhost localhost
write_hier_compare_dofile hier_compare.do -constraint ... -replace
go_hier_compare hier_compare.do
■ In the following command, the compare command in the hierarchical dofile is replaced
with two commands during each module comparison, set compare effort low and
compare -abort_stop 1 -noneq_stop 1:
go_hier_compare hier.do -compare_string \
"set compare effort low; compare -abort_stop 1 -noneq_stop 1"
Related Commands
ANALYZE ABORT
COMPARE
HELP
HELp
[<command_name> | <message_name> | -message] [-Verbose [-VERSION]]
[-COLOR | -NOCOLOR]
[-NOSHOW_ERROR_ID | -SHOW_ERROR_ID]
[-NOSHOW_EXTENDED_HELP | -SHOW_EXTENDED_HELP]
[-PAGE | -NOPAGE]
[<error_id>]
(Setup / LEC Mode)
Note: Although the HELP command is still available, it is recommended that you use the MAN
command.
Displays the Conformal commands and their command syntax. To display a group or set of
commands, use a keyword such as ADD, DELETE, REPORT, or SET.
While in the Tcl mode, the HELP command displays a list of all available Conformal Tcl mode
commands.
Tcl Command
help
Parameters
-VERSION Displays the software version at the end of the help output. This
can only be used with the -Verbose option.
-NOSHOW_ERROR_ID Do not display the error ID. This is the default.
-SHOW_ERROR_ID Displays the error ID.
-NOSHOW_EXTENDED_HELP
Do not display the extended help. This is the default.
-SHOW_EXTENDED_HELP
Displays the extended help only. This does not include error
IDs.
-PAGE Displays the help text one screenful at a time. This is the
default. The output is paused for input after one screenful of
text is displayed, where you can continue by pressing the
following:
space bar: displays the next page
h key: displays a complete list of options
q key: quits from the pager
Note: Output displayed with the pager is not saved to the log file
specified by SET LOG FILE command.
Note: The pager is not enabled if the help text is less than a
screenful, when output is redirected to a file, or when running
HELP in the GUI window.
-NOPAGE Disables the help text paging display feature.
<error_id> Displays the error message of the specified message ID.
Example
The following is an example of the Tcl mode system prompt and the HELP command:
TCL_SETUP> help set_current_module
Related Command
SEARCH
HISTORY
HISTory
[int]
[-ALL]
(Setup/LEC mode)
Tcl Command
history
Parameters
INFO CHECKPOINT
INFo CHeckpoint
<checkpoint_file_name>
(Setup / LEC Mode)
Tcl Command
info_checkpoint
Parameters
Related Command
CHECKPOINT
INFO SESSION
INFo SEssion
<session_file>
[-VERsion | -PLATform]
(Setup / LEC Mode)
Displays information about a specified session file. By default (without any options specified),
the tool displays the version and platform for the session file.
Note: Restoring a session file from a version of the tool or for a platform that is different from
the one you are currently using can cause unexpected results.
Tcl Command
info_session
Parameters
Example
info session -version session_file
Related Command
RESET
RESTORE SESSION
SAVE SESSION
SEARCH
When switching the system from Setup mode to LEC mode, Conformal automatically maps
key points and places them in the System class of mapped points. Use this command to
invert the mapping phase for any mapped points. This command also places the points in the
User class of mapped points.
In the GUI Mapping and Diagnosis Managers, a (-) sign represents an inverted-mapped point.
A (+) sign represents a non-inverted mapped point.
Tcl Command
invert_mapped_points
Parameters
<gate_id> Inverts the mapping phase for the specified gates (identified
by number).
Note: ID numbers can differ from one version of Conformal
to another. Always use the full path in dofiles and any time
you rerun a design with a different Conformal version.
<instance_pathname> Inverts the mapping phase for the specified instances.
<pin_pathname> Inverts the mapping phase for the specified pins.
-MODULE <module_name> Specifies the root module for the specified instance
pathname.
-GOLden Specifies that the point identifier refers to the Golden design.
This is the default.
-REVised Specifies that the point identifier refers to the Revised
design.
Related Commands
ADD MAPPED POINTS
LICENSE
LICense
[<license_string>]
(Setup / LEC Mode)
Displays information about the Conformal licenses that you currently have checked out.
Tcl Command
license
Parameters
MAN
MAN
[<expression>] [-Keyword] [-Verbose]
[-COLOR | -NOCOLOR] [-PAGE | -NOPAGE]
(All Modes)
This displays the manual pages for a given expression. By default, the MAN command
searches through command names, TCL function names, and rule or modeling message IDs
for a best match. You can also use the -Keyword option to search through descriptions. If an
exact match is not found, this command returns a list of all matches. Running this command
without any arguments returns a list of all available pages.
Note: In TCL mode, this command is VPXMODE MAN.
Tcl Command
man
Parameters
Category Description
LEC-CMD LEC Commands
CFM-RULE HDL Rules
LEC-MODEL LEC Modeling Rules
LEC-TCL LEC TCL Commands
ECO-CMD Conformal ECO Commands
CCD-CMD Conformal CD Commands
CCD-LINT Conformal CD Lint Rules
CCD-MODEL Conformal CDCCD Modeling Rules
Category Description
CCD-TCL Conformal CD TCL Commands
SDC-RULE SDC Rules
CLP-CMD Conformal Low Power Commands
CPF-RULE Common Power Format Rules
CLP-RULE Conformal Low Power Rules
CDC-CMD Conformal Extended Checks Commands
CDC-MODEL Conformal Extended Checks Modeling Rules
CDC-TCL Conformal Extended Checks TCL Commands
If there are more than one page page for a command. For example:
LEC> man exit
To obtain the man page for the exit Tcl command, use the following command:
LEC> man exit ccd-tcl
Example
For example, the following command displays the manual page for the REPORT DESIGN
DATA command:
MODE> man rep de d
For example, the following command retrieves all entries with the word datapath.
MODE> man datapath
ANALYZE DATAPATH (LEC)
REPORT DATAPATH OPTION (LEC)
The following lists all pages whose Syntax section contains the word thread.
MODE> man -k syntax thread
The following displays all RTL rules whose default severity is error:
MODE> man -k rule default severity error
There are times when there are multiple uses for a command. For example, the USAGE
command also has a Tcl version. In those cases, the MAN command will list all the possible
uses with descriptors. For example:
TCL_SETUP> man usage
USAge (LEC-CMD)
usage (LEC-TCL)
Related Commands
HELP
Automatically maps all key points, then displays a summary of the mapped points in the
Golden and Revised designs. In addition, if there are any unmapped points, Conformal
displays a summary of the unmapped points in the Golden and Revised designs. Conformal
automatically executes this command the first time you exit the Setup system mode and when
the flattened gate model changes.
Tcl Command
map_key_points
Related Commands
ADD MAPPED POINTS
MOS2BUFIF
MOS2BUFIF
[-MODule <mod1> <mod2> ... <modn> | -ALL]
[-FORce | -DRIVENmos | -INStance <ins1> <ins2> ... <insn>]
[-Golden | -Revised]
(Setup Mode)
After abstraction for emulation and test support, this transforms all of the unidirectional NMOS
devices to BUFIF1 and unidirectional PMOS devices to BUFIF0.
Tcl Command
mos2bufif
Parameters
Example
Sample Netlist Transformation:
Related Command
ABSTRACT LOGIC
Tcl Command
move_instance_down
Parameters
-MODule <module_name>
Specifies the parent module
-From <from_instance>
Specifies the instance that is to be moved.
-TO <to_instance>
Specifies the destination instance or list of instances.
-Golden Applies in the Golden design. This is the default.
-Revised Applies in the Revised design.
NCENCRYPT
NCENCRYPT
<<input_file>
<output_file>
[-VErilog | -VHdl | -TCL]
[-PRAgma]
[-REPlace]
| -VERSion >
(Setup / LEC Mode)
Use the NC Protect protection scheme to encrypt the specified files. This command also
works in Tcl mode.
Tcl Command
ncencrypt
Parameters
Related Commands
ncdecrypt (Tcl command)
OPEN SCHEMATICS
OPEn SChematics
[-Golden | -Revised]
[<full_pathname>]
(Setup / LEC Mode)
Opens the schematic viewer and displays the root module schematics. This command cannot
be used in the non-graphic mode.
Tcl Command
open_schematics
Parameters
Related Commands
CLOSE SCHEMATICS
DIAGNOSE
REPORT GATE
PIN GROUP
PIN GRoup
[-Golden | -Revised]
[-DEScend | -ASCend]
[-ADDEXPression <string> <string>]
[-ADDList <name>[#:#] "<net> <net> ..."]
[-ALL | -Module "<module_name> <module_name> ..."]
(Setup Mode)
Combines a group of single nets or pins into a bus. The Conformal software uses the following
two default patterns to group pins or nets into buses:
■ Name[#]
■ Name<#>
For example, nets blb[3], blb[4], and blb[5] will be grouped into bus blb[5:3],
and pins wladd[1], wladd[2], and wladd[3] will be grouped into bus wladd[3:1].
Tcl Command
pin_group
Parameters
-Golden Performs pin grouping in the Golden design. This is the default.
-Revised Performs pin grouping in the Revised design.
-DEScend Defines the bus in descending numerical order. This is the
default.
-ASCend Defines the bus in ascending numerical order.
This maps the following names into the first default bus name:
Related Command
GROUP
PRINTENV
PRINTENV
[<variable>]
(Setup / LEC Mode)
Tcl Command
printenv
Parameters
<variable> Prints the value of the specified variable. If you do not specify a
variable, this command displays the value of every environment
variable.
Related Command
SETENV
PROGRAM MONITOR
PROgram MOnitor
[-INTERVAL <number>]
[-FILE <name>]
[-PROFILE <ON|OFF>]
[-MAX_FILE_SIZE <number>]
(Setup / LEC Mode)
The program monitor is a run time engine that transparently profiles and checks the execution
of the program. This information can help troubleshoot performance issues. The profiling file
records traces of the program execution and does not contain any design specific information
such as netlist and names.
Tcl Command
program_monitor
Parameters
Example
The following command enables profiling at a monitoring interval of 100000 microseconds
and saves the information in a file called prof.txt:
SETUP> program monitor -profile on -file prof.txt -interval 100000
PROVE
PROve
<identifier1>
<-ONe | -ZEro | <identifier2>>
[-NOInvert | -Invert | -Both]
[-Golden | -Revised]
(LEC Mode)
Starts a process that shows whether the specified gates are equivalent or nonequivalent. The
proof process checks equivalency for one of the following pairs:
■ One gate in each of the Golden and Revised designs
■ Two gates in the Golden design
■ Two gates in the Revised design.
Use the ADD DYNAMIC CONSTRAINTS command to specify constraints you want to use
during this proof process.
Tcl Command
prove
Parameters
<identifier1> Specifies the gates from the given design as the first and
second prove points. The identifier will be either a gate
<identifier2> identification number, instance path, or pin path.
Note: ID numbers can differ from one version of Conformal to
another. Always use the full path in dofiles and any time you
rerun a design with a different Conformal version.
-ONe Prove whether the gate specified by <identifier1> is equal
to a one value.
-ZEro Prove whether the gate specified by <identifier1> is equal
to a zero value.
-NOInvert Proves for equivalence. This is the default.
-Invert Proves for inverted equivalence.
Examples
For a set of sample commands that shows this and related commands in context, see the
example for the COMPARE command.
Related Commands
ADD DYNAMIC CONSTRAINTS
DIAGNOSE
READ DESIGN
REAd DEsign
<filename* ...>
[-ARchitecture <architecture_name>]
[ | -BBOXUNResolve | -NOBBOXEMpty]
[-BLAST_inst_port]
[-CONFiguration | -NOCONFiguration]
[-CONTINUOUSASSIGNment <BIdirectional | UNIdirectional>]
[-Define <variable_name>]
[-ENUMConstraint]
[-EXClude <exclude_file_name*>]
[-File <command_filename>]
[-FUnctiondefault [0 | 1 | x | z]]
[-INITial_value]
[-INSERT_FEEDTHROUGH_buffer]
[-KEEP_ESCAPED_ID]
[-KEEP_Float_instance | -KEEP_All_instance | -REMOVE_Float_instance]
[ | -LAstmod | -OVERWrite_mod]
[-LIBRary <library_name> <library_path>]
(this option is the same as -Map)
[-LOCalref]
[-LOGIC_ENCODING_OFF]
[-Map <library_name> <library_path>]
[-MAPFile <library_name> [=<library_name2>] <filename ...>[-ENDMAPFile]]
[-MAPRecursive <library_name> <library_path>]
[-MErge BBox]
[-MIXvlog]
[-NETLIST]
[-NOELaborate]
[-NOKeep_unreach | -Keep_unreach]
[-NOREName]
[-NOSTRength]
[-NOZPUSHing | -ZPUSHing]
[-OPTimize | -NOOPTimize]
[-PARAmeter [-INT | -STR | -ENUM | -TYPE] <parameter_name> <value>]
(combined with -ROot option)
[-RAngeconstraint | -NORAngeconstraint]
[ | -REPlace | -APPend]
[-ROot <module_name>]
[-ROOTConfig <configuration_name>]
[-ROOTONLY]
[-SEnsitive | -NOSEnsitive]
[-STATEtable | -NOSTATEtable]
[-SUMmary_report | -NOSUMmary_report]
[-SUPPLY | -NOSUPPLY]
[-UNCompress <zip_file_name>]
[-UNZip <zip_file_name ...>]
[-VErilog | -VERILOG2K | -V1995 | -SYStemverilog | -SVA | -SV09
| -VHdl [93 | 87 | 2008] | -SPice [-NO_RESistor]| -Ndl | -EDIF | -LIBErty]
[-VHDLESCaped_to_verilog]
[-VMEM_LIB]
[-VMEM_ULTRA]
[-VERBose]
[-Golden | -REVised]
(Setup Mode)
Important
Review these important reminders before using the READ DESIGN command:
■ Use the SET NAMING RULE command first if you intend to read in an RTL design that
requires specific naming conventions.
■ Use the SET UNDEFINED CELL command before the READ DESIGN command if your
design includes undefined cells that should be treated as blackboxes.
Note:
■ If your design includes duplicate modules, Conformal uses the first module and ignores
later ones. However, you can use the -lastmod option to specify that Conformal use the
last module and ignore the earlier ones.
■ Use the tilde character (~) to shorten the path of the file.
■ Use the backslash character (\) at the end of a line to show that the command you are
entering continues on the next line.
Supported Options
You can specify how VHDL and Verilog 2001 libraries are mapped using the READ DESIGN
command's -map, -mapfile, or -library options.
The -map and -library options work the same in that they map logical library names to
physical directories. You can use multiple -map commands to map multiple physical
directories to one logical library. Use the -mapfile option for more specific library mapping,
such as specifying that a list of files must be compiled into a specified library. If you read in a
file without specifying its library mapping, that file is stored in a default library called work.
Note: You can map a file into more than one library. In this case, the file is stored in each
library for which it is mapped.
See the "VHDL Support" and "Verilog Support" appendices in the Conformal Equivalence
Checking User Guide for additional information, including examples on library mapping.
IP Protection
Conformal can read in files that are encrypted using the ncprotect utility (available with the
Cadence® NC-Verilog Simulator and Cadence® NC-VHDL Simulator) or Cadence
encryption tools. Designs that are encrypted can be read into Conformal and compared with
other non-encrypted designs.
When there are protected modules, the WRITE DESIGN command will write out the full netlist
of the protected modules in either clear text or encrypted text, depending on the level of
protection specified when the file was encrypted (for example, the output_netlist
attribute of NC-Protect specifies the encryption level of the output netlist).
Note: Conformal does not support Cadence Verilog-XL protected files (they are only for
simulations), and any other proprietary encryption files.
For more information on protection and synthesis rights, refer to the Protecting IP Source
Files document of the Cadence simulation tool.
Tcl Command
read_design
Parameters
Note: This option is valid only for VHDL and System Verilog.
-EXClude <exclude_file_name*>
Specifies files to exclude when reading in the design. This
accepts wildcards.
Note: You cannot use multiple wildcards with this option.
-File <command_filename>
Reads in the specified command file as a design.
Note: This option is for Verilog, VHDL, or Spice command file
lists.
The options for <command_filename> are described in this
document below in Table 2-1 on page 393 for Verilog and
Table 2-2 on page 396 for VHDL.
-FUnctiondefault Specifies the default return value for unspecified or
incompletely specified functions.
0 returns zero. This is the default.
1 returns one.
x returns x.
z returns z.
-INITial_value Specifies that the variable's initial value will not be ignored.
Note: This option applies only to VHDL designs.
-INSERT_FEEDTHROUGH_buffer
When a continuous assignment has a signal that inputs into a
submodule and outputs directly, the tool will interpret this as a
through wire (no direction). LEC will insert a buffer to
indicate the wire direction.
-KEEP_ESCAPED_ID When used, this option keeps escaped identifiers, as in Verilog
2001. See "Support for Macro Expansions" in the
Conformal Equivalence Checking User Guide for more
information.
-KEEP_Float_instance Keeps Verilog/VHDL floating module instances that do not
have instance pin connections. Note that this option does not
keep unreachable Verilog primitives or unreachable logic
inferred from the Verilog/VHDL RTL statements. This is the
default.
-KEEP_All_instance Keeps all Verilog/VHDL floating module instances, the
unreachable Verilog primitives, and the unreachable logics
inferred from the Verilog/VHDL RTL statements.
-REMOVE_Float_instance
Removes Verilog/VHDL floating instance and its
corresponding modules in the design database.
-LAstmod Specifies that if duplicate modules exist, the Conformal
software uses the last module and ignores the earlier ones.
By default, Conformal uses the first module and ignores later
ones.
-OVERWrite_mod All module names must be unique within a given library, and
same module name can exist in the different libraries. Use this
option to keep the current module and delete all existing
modules with the same name from all libraries. Without this
option, only the module with the same name within the target
library is affected.
-LIBRary <library_name> <library_path>
Reads in the specified file in the given library and path for
user-defined VHDL libraries. (This option is the same as
-map)
-LOCalref Keep all Verilog modules as local private modules if they are
referenced by any module within the same Verilog file. Local
private modules cannot be referenced from other Verilog files.
-LOGIC_ENCODING_OFF Do not interpret the user-defined enum types with literal value
0, 1, X, Z, and so on as one-bit logic values.
For example, MY_MVL is the user-defined enum type:
type MY_MVL is ('X', '0', '1', 'Z');
The type of signal val is MY_MVL. For the statement:
val <= 'Z';
With this option, val is 2'd3; without this option, val is 1'bx.
-Map <library_name> <library_path>
Reads in files for the specified <library_name> from
<library_path>.
Use this option to read in all of the files in the specified library
path for the given library name. You can also map multiple
directories to a single library. Supported for only VHDL files.
For example:
read design -vhdl top.vhd -map mylib /design/path1 \
-map mylib /design/path2
-OPTimize Optimizes redundant logic (in library cells) that can affect the
way Conformal interprets the design. This is the default.
Note: Using this option does not always optimize all redundant
logic.
See the following example:
read design
file1 -nooptimize
file2 -optimize
file3 -nooptimize \
-replace
-APPend Appends the design to the one that was previously read.
For example, you can use this option to fix a top module and
then read it in again without parsing the entire design file
again:
read design top.v -append -lastmod
-NOSUMmary_report Do not print out HDL rule check messages while reading the
library or design file(s).
-SUPPLY Keeps all Verilog supply0 and supply1 type nets
unchanged. This is the default for all Conformal tools.
-NOSUPPLY Converts the Verilog supply0 and supply1 type nets to
Verilog wire type nets.
-UNCompress <zip_file_name>
Reads in the specified compressed file. By default, the
Conformal software uses the gunzip tool to uncompress the
file into the /tmp directory. Files created with gzip or
compress are supported.
If the compressed file cannot be uncompressed using the
gunzip tool, you specify another tool by setting UNIX
variable CONFORMAL_UNCOMPRESS
You can also set the UNIX variable CONFORMAL_TMP to a
path other than the default /tmp directory.
-UNZip <zip_file_name ...>
This option has the same function as -UNCompress except
that it can include a list of filenames. For example:
read design fileABC -UNZ zip1 zip2 zip3
The list of filenames end when a subsequent option is
specified, or if it is at the end of the command line.
Note: Specifying -uncompress or -unzip is optional for
gzipped files because the Conformal software can
automatically recognize the file type created by the gzip tool.
This includes command file lists specified with -file
-VErilog Specifies that this design is a Verilog design. (Use this option
for Verilog designs that comply with IEEE 1364-2001.) This is
the default.
-VERILOG2K Specifies that this design is a Verilog2K design (Use this
option for Verilog designs that comply with IEEE 1364-2001).
-V1995 Specifies that this design is a Verilog-1995 design (Use this
option for Verilog designs that comply with IEEE 1364-1995).
-SYStemverilog Specifies that this design is a SystemVerilog design.
-SVA Enables SystemVerilog Assertion (SVA) support.
The following table lists the Verilog command options that Conformal supports.
Verilog command options used to resolve Verilog module references (such as -y/-yd, -v/-
vd, and +libext+<ext_suffix>) can also affect the search path order. When a Verilog
module instance cannot be resolved to any existing modules in memory, the Verilog parser
searches for the module from the directories (-y/-yd) or files (-v/-vd) specified by these
options. The order in which module references are resolved is the order specified in the
Verilog command file.
To search for files in the directories specified by the -yd option in the Verilog command file,
use the +search_yd_path. The additional search paths specified by -yd are effective only
in the current READ DESIGN command.
In LEC, READ DESIGN -f gol.f will search for mux.vs in the following directories (in the
order listed):
■ Current working directory "."
■ -yd hdl
■ -yd test
■ Any other paths specified by ADD SEARCH PATH
When a Verilog include file is specified using `include directive, the default file search order
is as follows:
1. Current working directory
2. Directories specified by +incdir option in the Verilog command file
3. Directory that contains the file that specifies the `include directive
4. Search paths added by the ADD SEARCH PATH command
5. Directories specified by -yd in the Verilog command file
6. Directories specified by -y in the Verilog command file
When using the command SET HDL OPTIONS -INCLUDE_SRC_DIR OFF (note that the
default is ON), which disables and prevents LEC from reading include files in the source's
relative path, the search order becomes as follows.
1. Current working directory
2. Directories specified by +incdir option in the Verilog command file
3. Search paths added by the ADD SEARCH PATH command
4. Directories specified by -yd in the Verilog command file
5. Directories specified by -y in the Verilog command file
To customize the search order, use the SET HDL OPTIONS -verilog_include_dir
command option.
The following table lists the VHDL command options that Conformal supports.
The VHDL command file options behave the same way as if they are specified as command
line parameters. Refer to the Parameters section for details of each of the option.
Examples
The following example demonstrates how to use the backslash character to show that your
command continues on the next line.
read design tran1.spi tran2.spi tran3.spi \
-spice -revised
In the following example, only ent2.vhdl and arch2.vhdl will be parsed according to
VHDL 87 syntax rules. All the other files will be parsed according to VHDL 93 syntax rules.
read design ent0.vhdl arch0.vhdl \
-vhdl 93 ent1.vhdl arch1.vhdl \
-vhdl 87 ent2.vhdl arch2.vhdl \
-vhdl ent3.vhdl arch3.vhdl
In the following example, you can use read design -localref command to use local
module sub1 (see line10 of each file).
For each file, the instantiation of sub1 in line10 will use the sub1 defined in line 1 (module
sub1(aa, oo)).
File mod1.v
1 module sub1(aa, oo);
2 input aa;
3 output oo;
4 assign oo = aa;
5 endmodule
6
File mod2.v
1 module sub1(aa, oo);
2 input aa;
3 output oo;
4 assign oo = !aa;
5 endmodule
6
7 module mod2(aa, oo);
8 input aa;
9 output oo;
10 sub1 u0 (aa, oo);
11 endmodule
Related Commands
ADD NOTRANSLATE MODULES
READ LIBRARY
REPORT MESSAGES
REPORT MODULES
SET DIRECTIVE
SET STATETABLE
WRITE DESIGN
This command reads in the extended mapping information for the specified file to help in LEC
mapping and verification setup. LEC does not check if the information in the file has conflicts.
If you are reading a file which is not generated by WRITE EXTENDED MAPPING, use the read
command with caution.
This command should be executed after both Golden and Revised designs and libraries are
read in.
Tcl Command
read_extended_mapping
Parameters
This option lets Conformal read the extended mapping file for a
higher-level module containing hierarchy.
-REVIsed_prefix <string>
Appends this revised prefix string to the instance names in the
extended mapping file.
This option lets Conformal read the mapping file for a higher-
level module containing hierarchy.
-CHECK_names Performs a check on the extended mapping file. A warning will
be generated if LEC cannot find the pin or instance specified in
the file.
Related Commands
ANALYZE EXTENDED MAPPING
Directs Conformal to read in a file that defines new Finite State Machine (FSM) encoding.
By default, Conformal reads binary encoding when building an FSM. Therefore, if your gate
netlist uses different encoding (for example, one-hot), you must use the READ FSM
ENCODING command to specify the correct encoding. See the example of an FSM encoding
file below.
Tcl Command
read_fsm_encoding
Parameters
Examples
The following example shows the need for the READ FSM ENCODING command. In this case,
the user was alerted to encoding differences during mapping. The Golden design showed two
registers, while the Revised showed four registers. The following is an example of an FSM
encoding file that replaces the binary encoding with one-hot encoding:
.fromstates current_state_reg[1] current_state_reg[0]
.tostates current_state_reg[3] current_state_reg[2] current_state_reg[1]
current_state_reg[0]
.begin
00 0001
01 0010
10 0100
11 1000
.end
Reads in the OVF guide file. Synthesis tools generate a guide file to record information, such
as instance or module naming, sequential element merging or duplication, module
ungrouping or unification, and datapath logic transformation. LEC uses this information for
setup, hierarchical comparison, abort resolving, or comparison performance.
Read in the guide file before you read in the Golden RTL design; information in the guide file
might be referenced during the LEC-RTL interpretation and hierarchy build-up stage.
The READ GUIDE FILE command takes a list of guide files (reading them in the order
specified), as guide information is sometimes recorded into separate files. Take note of any
dependencies in the content of the guide files, as you might need to specify the files in a
specific order.
Tcl Command
read_guide_file
Parameters
Related Commands
The automatic flow to apply the SETUP_NAME command to enable the mapping and modeling
guidance.
Tcl Command
read_guidance_information
Parameters
Related Command
SETUP NAME
This command reads in verification-related synthesis information that can help improve
verification setup. This command can only be used after the SET VERIFICATION
INFORMATION command. Currently, this command can only read from the Genus generated
fv directory.
For information on how to use this command when verifying Genus synthesized netlists with
sequential phase inversion optimization, go to the web interface by using the set
web_interface ON command.
Tcl Command
read_implementation_information
Parameters
<implementation_information_directory>
Name of the directory from which to read the
implementation information.
Currently, this command can read from only the Genus
generated fv/* directory.
-Golden <label> Specifies the label of the set of information for the
golden netlist.
-REvised <label> Specifies the label of the set of information label for the
revised netlist.
-Golden <json filename> | -REVised <json filename>
Related Commands
SET VERIFICATION INFORMATION
This command reads in the key point file(s) generated by WRITE MAPPED POINT command
to assist supply mapping in power grid comparison.
Tcl Command
read_keypoint_mapping
Parameters
Examples
read keypoint mapping -golden_revised mapfile
Reads in the Library Exchange Format (LEF) file, which contains the design's library
information.
During design elaboration, Conformal checks whether each cell used in the specified design
(Golden, Revised, or both) has a corresponding cell in the library. This command reads in the
LEF file and checks that the port declarations are in both the LEF and library. If a power/
ground port declaration exists only in the LEF file, Conformal will add the port to the library
cell.
Tcl Command
read_lef_file
Parameters
READ LIBRARY
REAd LIbrary
<filename* ...>
[-VErilog | -VERILOG2K | -V1995 | -SYStemverilog | -SVA | -SV09
| -VHdl [93 | 87 | 2008] | -Liberty [-LP [ALL | STD] [1.1 | 2.0]][-PG_PIN]
| -CPF [-LP [STD | ALL][1.1 | 2.0]]]
[-BBOXSolver]
[-CONFiguration | -NOCONFiguration]
[-Define <variable_name>]
[-EXClude <exclude_file_name*>]
[-EXtract]
[-File <command_filename>]
[-KEEP_ESCAPED_ID]
[-LAstmod]
[-LOGIC_ENCODING_OFF]
[-Map <library_name> <library_path>]
[-MAPFile <library_name> [=<library_name2>] <filename ...>]
[-MAPRecursive <library_name> <library_path>]
[-MULTIPLE_LIBraries]
[-NOELaborate]
[-NOKeep_unreach | -Keep_unreach]
[-NOShare]
[-NOSTRength]
[-OPTimize | -NOOPTimize]
[ | -REPlace | -APPend]
[-RESPECT_timing_type_for_flop]
[-SEnsitive | -NOSEnsitive]
[-STATEtable | -NOSTATEtable]
[-SUMmary_report | -NOSUMmary_report]
[-SUPPLY | -NOSUPPLY]
[-UNCompress <zip_file_name>]
[-UNZip <zip_file_name ...>]
[-Both | -Golden | -Revised]
[-VERBose]
(Setup Mode)
Reads in the library model descriptions for Verilog, VHDL, or Liberty designs. The library is
either a Verilog simulation library or a Synopsys Liberty library. It is read for the Golden,
Revised, or both designs.
Note: For RTL to gate formal equivalence checking, use simulation libraries instead of
synthesis libraries because design verification signoff happens for simulation libraries: not for
synthesis libraries.
The READ LIBRARY command must be used before the READ DESIGN command if the
design is Verilog, VHDL, or Liberty.
Note: Library in this context refers to the technology library, such as ASIC cell and memory
definitions. See READ DESIGN for information on reading VHDL libraries and packages.
Important
■ If there are duplicate modules, the Conformal software uses the first module and ignores
later ones. However, you can use the -lastmod option to specify that Conformal use the
last module and ignore earlier ones.
■ Use the backslash character (\) at the end of a line to show that the command you are
entering continues on the next line.
■ Use the tilde character (~) to shorten the path of the file.
Conformal tools support Verilog and VHDL files which are encrypted by the NC-Protect and
Cadence encryption Cadence tools. NC-Protect is available from Cadence NC-VHDL and
Verilog simulators. Cadence encryption is Cadence proprietary tool.
The Cadence Verilog-XL protected files are for simulations only and are unsupported by
Conformal tools. Other proprietary encryption files are unsupported by Conformal tools.
Tcl Command
read_library
Parameters
<filename* ...> Reads in the specified file(s). This option is a required filename
that contains the Verilog simulation library or the Synopsys
Liberty library. This accepts wildcards.
-VErilog Contains the Verilog library model descriptions. This is the
default.
Note: This supports NC-Protect and Cadence encryption.
-VERILOG2K Contains Verilog2k library model descriptions.
-V1995 Contains Verilog-95 library model descriptions.
Examples
In the following example, read library mod1.v mod2.v will select blackbox module
sub1() from mod1.v, and read library -lastmod mod1.v mod2.v will select
blackbox module sub2() from mod2.v.
To avoid selecting blackboxes, use read library -bboxsolver mod1.v mod2.v, which
will select sub1() from mod2.v, and sub2() from mod1.v.
File mod1.v:
File mod2.v:
module sub1(aa, oo);
input aa;
output oo;
assign oo = !aa;
endmodule
module sub2(aa, oo);
input aa;
output oo;
// This is a blackbox
endmodule
Related Commands
ADD NOTRANSLATE MODULES
READ DESIGN
REPORT MESSAGES
REPORT MODULES
SET DIRECTIVE
SET STATETABLE
WRITE LIBRARY
Reads in the mapped point information you created with the WRITE MAPPED POINTS
command. By default, Conformal automatically maps key points during the transition from
Setup to LEC mode. And if the key points are already mapped, Conformal ignores any
mapped point information in the file. Thus, to prevent Conformal from automatically mapping
key points during the transition from Setup to LEC mode and enable Conformal to read in
mapped point information completely from the file, do one of the following:
■ Use the set flatten model -nomap command before you set the system mode to
LEC.
■ Use the set system mode lec -nomap command to suppress automatic mapping
during the transition to LEC mode.
Tcl Command
read_mapped_points
Parameters
-GOLDen_prefix <string>
Appends this Golden prefix string to the instance names.
This option lets Conformal read the mapped point file for a
higher-level module containing hierarchy.
-REVIsed_prefix <string>
Appends this revised prefix string to the instance names.
This option lets Conformal read the mapped point file for a
higher-level module containing hierarchy.
-SEARCH Search for the specified gates' drivers to find the corresponding
keypoints for mapping.
Related Commands
SET FLATTEN MODEL
Reads in Verilog memory primitive simulation models that were created using the Conformal
memory primitive generator. This command creates a memory-friendly, synthesized view that
you can use for comparison with a memory circuit.
Important
Read in designs that use the memory primitive after you use this command.
Tcl Command
read_memory_primitive
Parameters
Related Command
READ DESIGN
READ PATTERN
REAd PAttern
<filename>
[-Verilog | -SPice ]
[-Golden | -Revised | -Both]
[-SEnsitive | -NOSEnsitive]
[-LAstmod]
(Setup Mode)
Reads in the transistor description from a file that Conformal GXL applies to the Golden and
Revised designs. (The file format type is either Verilog or SPICE.)
The transistor description represents a pattern that Conformal GXL seeks during abstraction.
When Conformal GXL detects a pattern, it substitutes a user-specified functional model.
Before this command can be executed correctly, you must provide the user-specified
functional model using the READ LIBRARY command. The transistor description file and
functional model have the same module and port names; port direction can be different, but,
neither the transistor description file nor the library database can contain submodules: every
cell must be flat.
Use the tilde character (~) to shorten the path of the file.
Tcl Command
read_pattern
Parameters
-Both Applies the file's sub-circuit information to both the Golden and
Revised designs.
-SEnsitive The transistor description file is case-sensitive. This is the
default.
-NOSEnsitive The transistor description file is not case-sensitive.
-LAstmod If duplicate modules exist, Conformal uses the first module and
ignores the later ones by default. Use this option to specify that
Conformal use the last module and ignore earlier ones.
Examples
read pattern DLTCH1.v -verilog -revised
read pattern DLT2.v -verilog -both
read pattern xtran.spi -spice -golden
Related Commands
ABSTRACT LOGIC
ADD CLOCK
DELETE CLOCK
REPORT CLOCK
RESOLVE
(1801 Options)
[-1801]
[-INSERT_ISOLATION]
[-GOLden | -REVised | -BOTH]
[-REPlace]
(Setup Mode)
Reads and elaborates design power intent. Use the READ LIBRARY command to read in
library power intent.
■ Conformal Low Power does not support mixed languages. You cannot mix CPF libraries
and 1801 power intent.
■ Some options are different for the 1801 flow. To enable this flow, use the SET LOWPOWER
OPTION -native_1801 option.
■ In the 1801 flow, there are rules that can identify potential setup issues or critical issues
in the power intent or design. The rule violations identified by these rules must be
resolved before the rest of the rule checks are performed. These critical rules cannot be
disabled, downgraded or ignored.
■ In the 1801 flow, once reading power intent, all the rule checks will be performed and
reported. Verification process is only terminated when there is linter error or critical issue
in power intent or design.
If you used the CPF integrator to create integrated power intent, you must read the integrated
CPF file back in using the READ POWER INTENT <file> -replace command followed
by the COMMIT POWER INTENT command.
Tcl Command
read_power_intent
Parameters
Related Commands
COMMIT POWER INTENT
READ LIBRARY
Reads in Verilog ROM primitive simulation models that were created using the Conformal
ROM primitive generator.
Tcl Command
read_rom_primitive
Parameters
Related Command
READ DESIGN
Performs incremental rule checks. The first time you run a session, write the rule violations
into a rule file using the write rule check <filename> -golden (or
-revised) command. For later runs, exclude the violations already flagged with the read
rule check -exclude <filename> command.
Use the tilde character (~) to shorten the path of the file.
Tcl Command
read_rule_check
Parameters
<filename> Specifies the name of the file that contains rule violations from a
previous session.
-EXClude Excludes checks for violations noted in the specified file.This
option works as a filter; therefore, use it after the READ
DESIGN command.
-INClude Includes checks for violations noted in the specified file. This
option lets you reinstate violations that were previously
excluded.
-DEsign Reads only design rule check violations. If you do not specify
-design or -library, Conformal reads rule check violations
from both designs and libraries.
-LIbrary Reads only library rule check violations. If you do not specify
-design or -library, Conformal reads rule check violations
from both designs and libraries.
-Golden Applies this command to the Golden design. This is the
default.
-Revised Applies this command to the Revised design.
Examples
In the following example, the second report rule check will not report any rules.
read design g.v -golden
read design r.v -revised
write rule check rule.g -golden -replace
write rule check rule.r -revised -replace
read design g.v -golden -replace
read design r.v -revised -replace
report rule check -verbose -both
read rule check rule.g -exclude -golden
read rule check rule.r -exclude -revised
report rule check -verbose -both
Related Command
WRITE RULE CHECK
READ TESTCASE
REAd TEstcase
<filename>
[-DIR_name <directory_name>]
[-RUN]
[-REPlace]
(LEC Mode)
Reads in the encapsulated testcase file which is extracted with the REPORT TESTCASE
command. The testcase file is described in data exchange format, Extensible Markup
Language (XML). After reading in the testcase file, the embedded information is separated
into files, including one generated dofile. Running the generated dofile can reproduce the
problem in original design.
Tcl Command
read_testcase
Parameters
Example
The following command reads in the testcase file named testcase.xml and separate out
the embedded information into files under the run_testcase directory. It also runs the
generated dofile to reproduce the problem in original design:
read testcase testcase.xml -dir run_testcase -replace -run
Related Command
REPORT TESTCASE
This command reads in setup information from the specified files to help in LEC setup and
diagnosis.
Reading in setup information from RC log files can help resolve sequential constant,
sequential phase inversion, and sequential merge related setup issues. This command
supports the following:
For RC log files, sequential merge information (non-inverted and inverted), sequential
constant information, and sequential phase inversion are supported. Note that using attribute
information is recommended for sequential phase inversion. For more information on the RC
LEC Verification Flow with Attribute Information and its latest enhancements, refer to the 13.1
web interface document titled RC LEC Verification Flow with Attribute Information.
For RC, Conformal uses sequential constant information to handle sequential elements that
are not modeled as a sequential constants due to balanced modeling, but the synthesis tool
propagated the constant value. LEC automatically identifies the flop as candidate and
remodels it to constant after proof. Conformal also uses constant information to handle
sequential elements that are not modeled as a sequential constants because they are
merged into other sequential elements. LEC automatically identifies the flop as a sequential
constant candidate and remodels it to constant after proof.
For RC, where the log file records the sequential constant value, LEC can also handle
sequential constant X issues where the synthesis tool optimized some sequential constant X
to zero and some to one.
Tcl Command
read_setup_information
Parameters
Examples
To read in an RC log file (rc.log):
SETUP> read setup information rc.log
// Processing file rc.log ...
// 749 sequential constant information are recorded
Related Commands
REPORT SETUP INFORMATION
Tcl Command
read_verification_information
Parameters
<verification_information_directory>
Name of the directory from which to read the verification
information.
-GOLden <label> Specifies the label of the set of information for the golden
netlist. This label can be used later to refer to this set of
information.
-REVised <label> Specifies the label of the set of information for the revised
netlist. This label can be used later to refer to this set of
information.
Related Commands
SET VERIFICATION INFORMATION
REDUCE MOS
REDuce MOs
[-ALL | -MODule <module_name> ...]
[-Golden | -Revised]
[-MERGE_TRAN]
[-SD_GND]
[-SD_VDD]
[-DIODE]
[-PARALLEL]
[-GATE_ON]
[-GATE_OFF]
[-NOVERbose]
(Setup Mode)
Tcl Command
reduce_mos
Parameters
-GATE_ON Collapses non-weak MOS devices into the wire if the gate is
a constant that causes current to flow.
-GATE_OFF Removes non-weak MOS devices if the gate is a constant
that does not cause the current to flow.
-NOVERbose Do not report detailed statistical information.
Related Commands
ABSTRACT LOGIC
REMODEL
REMODEL
<-SEQ_MERGE | -SEQ_CONSTant | -DFF_CONST_ASYNC | -UNFOLD_DFF
| -BBOX_MERGE | -RED_DLAT | -GATED_CLOCK | -REVERSE_SEQ_REDundant
| -SEQ2BUFfer | -SEQ_CONSTANT_GROUP | -INSTANCE_EQuivalence
| -TRANSFORM_SET_DOMINANT | -SEQ_CONSTANT_X_TO_DC
| -REVERSE_LATCH_REDundant>
<-UNMAPPED | -NOTMAPPED | -MAPPED | -ALL | <gate_id> ... | <instance_pathname>
...>
[-MAX_UNMAP <number_of_keypoints>]
[-BOTH | -GOLden | -REVised]
[-REPEAT]
[-VERBose]
(LEC Mode)
Used in LEC mode and after mapping, this takes a set of key points and attempts to remodel
them. Use this command in conjunction with the SET FLATTEN MODEL command to resolve
mis-compares due to key point issues.
When you use this command, the Conformal software invalidates compare results (if they
exist), closes schematics, and updates the Mapping Manager.
Note: For a more automated way of setting up the comparison, use the ANALYZE SETUP
command.
Tcl Command
remodel
Parameters
-SEQ_CONSTANT_X_TO_DC
Converts a DFF or D-latch to don't care when its asynchronous
set or reset and clk are all disabled.
Note: This modeling can only be applied when X assignment(s)
is treated as don't care for the design.
-REVERSE_LATCH_REDundant
Restores the latch redundancy to the outputs of the specified
DLATs.
-UNMAPPED | -NOTMAPPED | -MAPPED | -ALL | <gate_id> |
<instance_pathname>
Applies the specified remodeling to all unmapped key points,
not-mapped key points, all mapped key points, all key points, or
the specified gate or instance. By default, Conformal
remodels all unmapped points.
Examples
■ Sample Implementation for REMODEL:
set flatten model -seq_constant
set system mode lec
remodel -seq_constant Q1_reg
■ In the following example, the design can be mapped almost completely by name, but
there are key points that have not been merged. To remodel replicated registers into a
single register, use the REMODEL command. Then Conformal can remap key points and
compare.
...
set flatten model -seq_merge
set map method -name only
set system mode lec
remodel -seq_merge -both -unmapped
set map method -name first
map key points
add compare points -all
compare
■ In the following command adds two instance equivalences (Q1_reg and Q2_reg) and
(Q4_reg and Q3_reg). Q1_reg and Q4_reg are the representatives.
remodel -instance_equivalence -gold Q1_reg Q2_reg Q4_reg Q3_reg
Related Commands
COMPARE
REMOVE
REMove
<name* ...>
[-Golden | -Revised]
[-INSTance | -INS_Module]
[-MODule <mod_name*> | -ALL]
(Setup Mode)
Tip
To report instances removed with this command, run the REPORT REMOVED
INSTANCE command.
Tcl Command
remove
Parameters
Example
For these lines:
module top (...);
mod1 u01 (...); // inst1
mod2 u02 (...); // inst2
mod3 u03 (...); // inst3
endmodule
module mod3 (...);
mod1 u01 (...); // inst4
mod2 u02 (...); // inst5
endmodule
■ The following command removes u01 from the root module top:
remove u01 -ALL // remove inst1, inst4
■ The following command removes all mod1 instances from the root module top:
remove mod1 -INS_Module // remove inst1
■ The following command removes all mod1 instances from all modules:
remove mod1 -INS_Module -ALL // remove inst1, inst4
Related Commands
REPORT REMOVED INSTANCE
If you used SET ABSTRACT MODEL command to abstract transistor logic from particular
modules, this reports their abstraction conditions.
Tcl Command
report_abstract_model
Parameters
Related Commands
ABSTRACT LOGIC
REPORT ALIAS
REPort ALias
[<aliasname* ...>]
(Setup / LEC Mode)
Displays a list of all or specified aliases you created with the ADD ALIAS command.
Wildcard: The wildcard (*) represents any zero or more characters in alias names.
Tcl Command
report_alias
Parameters
Related Commands
ADD ALIAS
DELETE ALIAS
Displays blackboxes from the Golden and Revised designs. The blackboxes either already
existed in the design, or you previously added them with the ADD BLACK BOX command.
Tcl Command
report_black_box
Parameters
Related Commands
ADD BLACK BOX
REPORT CLOCK
REPort CLock
[-Both | -Golden | -Revised]
(Setup / LEC Mode)
Reports all clocks from the Golden and Revised designs that were added with the ADD
CLOCK command.
Tcl Command
report_clock
Parameters
-Both Displays all added clocks from both the Golden and Revised
designs. This is the default.
-Golden Displays all added clocks from the Golden design.
-Revised Displays all added clocks from the Revised design.
Related Commands
ABSTRACT LOGIC
ADD CLOCK
DELETE CLOCK
READ PATTERN
RESOLVE
Displays a profile of all of the commands you executed after you used SET COMMAND
PROFILE with the ON option. (The default setting for SET COMMAND PROFILE is OFF.)
The profile report includes the order in which commands were executed and the memory use.
The profile includes commands that were executed in the GUI mode.
Tcl Command
report_command_profile
Parameters
Related Commands
SET COMMAND PROFILE
Displays a list of all or specified compared points. If no options are specified, Conformal
identifies all equivalent and nonequivalent compared points and displays a summary.
The compared points are listed in pairs of rows with three fields in each row. The first row in
each pair represents the Golden design. The second row in each pair represents the Revised
design. The three fields in each row are:
■ First–the gate identification number
■ Second–the gate type
■ Third–the instance path or pin path
Tcl Command
report_compare_data
Parameters
-INSTance_eq <identifier>
Displays compare data for a pair of instances previously
identified with the ADD INSTANCE EQUIVALENCE command.
Note: ID numbers can differ from one version of Conformal to
another. Always use the full path in dofiles and any time you
rerun a design with a different Conformal version.
-OUTput_eq <identifier>
Displays compare data for a pair of outputs previously identified
with the ADD OUTPUT EQUIVALENCES command.
Note: ID numbers can differ from one version of Conformal to
another. Always use the full path in dofiles and any time you
rerun a design with a different Conformal version.
-PIN_eq <identifier>
Display compare data for a pair of pins previously identified with
the ADD PIN EQUIVALENCE command.
Note: ID numbers can differ from one version of Conformal to
another. Always use the full path in dofiles and any time you
rerun a design with a different Conformal version.
-HIER_TO_Flat Analyzes the verification information and the hierarchical
comparison information to produce the report as if it was a
flattened run. Verification information must have been enabled
using SET VERIFICATION INFORMATION
-LOng Displays pairs of points on separate lines.
-Golden The specified identifiers are from the Golden design. This is
the default.
-REvised The specified identifiers are from the Revised design.
-NOREPORT_BBox_input
Do not report the blackbox input pins in the compare report
results. This is the default.
-REPORT_BBox_input Report the blackbox input pins in the compare report results
(Equivalent, Nonequivalent, Abort, and Not-compared).
-UNReachable Reports only unreachable compare points.
Examples
For a set of sample commands that shows this and related commands in context, see the
example for the COMPARE command.
Related Commands
COMPARE
DIAGNOSE
PROVE
REPORT STATISTICS
You must enable this feature before starting a comparison; otherwise, Conformal does not
record any information.
For example:
compare
report compare time -enable
compare
report compare time
In this example, Conformal records the CPU time for the second comparison only.
Note: Conformal does not record compare time for trivial cones.
Tcl Command
report_compare_time
Parameters
Examples
The following demonstrates how to use this command with other commands.
Note: Use these steps after you read in your library and design files.
1. Add your compare points.
LEC > add compared points -all
// 3113 compared points added to compare list
4. Report the compare time. In this example, Conformal sorts the information based on
CPU time and only reports RTL information within the cone.
LEC>report compare time -sort -rtlinfo
.
.
.
Related Commands
ADD COMPARED POINTS
COMPARE
Tcl Command
report_compared_intent
Parameters
-FILTERED_BY <name>* Filter the results using the specified power intent compare
filter(s): filters are added using the ADD
POWER_INTENT_COMPARE FILTER command. This
accepts wildcards.
-OBJECT_TYPE <type> Reports only compared points for the specified power
intent object type. For a list of supported options, see the
section Power Intent Object Types in the REPORT
POWER INTENT command page.
-ATTRibutes Reports attributes of compared points.
-COMMAND_SUMMARY Reports summary based on number of commands. This
is the default.
-COMPARED_POINT_SUMMARY Reports summary based on number of compared points.
-FILTER <filter_expression>
Reports only compared points for which the specified
filter_expression evaluates to true. The syntax for
filter_expression is the same as for the Tcl find
command. Use the -ATTRibutes option to see the
available attributes.
-DESIGN_OBJECT_FILTER <filter_expression>
Reports only design object compared points for which the
specified evaluates to true. The syntax for
filter_expression is the same as for the Tcl find
command. Use the -ATTRibutes option to see the
available attributes.
-REGEXp Specifies that the pattern matching operators used inside
filter expression (such as =~) should use regular
expressions as patterns, rather than glob-style patterns.
This option only has any effect if combined with -FILTER
and/or -DESIGN_OBJECT_FILTER.
-FAIL_TYPE <type> Reports only compared points which match the specified
fail type. Use the -ATTRibutes option to see the fail
types of compared points.
-Summary A summary table of the power comparison results. This
is the default.
-Verbose Displays the results in detail.
-Golden Only reports points for which the golden object exists.
-REvised Only reports points for which the revised object exists.
Example
The following is a sample dofile that reads in two power intent files (in CPF format) and
compares them:
set lowpower option -golden_netlist_style logical
set lowpower option -revised_netlist_style logical
add notranslate module RamMod -both -library
read library Lib/Waz.l -gol -lib
read power intent Des/RTL.c -gol -cpf
read library Lib/Waz.l -rev -lib
read design Des/RTL.v -gol -v2k -root MyChip
read design Des/Syn.v -rev -v2k -root MyChip
read power intent Des/Syn.c -rev -cpf
compare power intent
report compared intent -verbose
After you read in the designs, libraries, and power intent, use the COMPARE POWER INTENT
command to compare the two power intent files, and the REPORT COMPARED INTENT to view
the details of the comparison. In the following sample output, the two power intent files are
not equivalent due to a missing power mode and mismatched values for a nominal condition:
SETUP> compare power intent
// Power Intent Compare finished and found 2 differences:
// power intent object name differences: 1
// power intent object option differences: 1
|
| 5) Supply Port 'tt1/ll1/xx1/VDD' missing in Golden:
| Golden file: not specified
| Revised file: 'Power_Intent/top.rev1.upf', line 25
|
| 6) Supply Port 'tt1/ll1/xx1/VSS' missing in Golden:
| Golden file: not specified
| Revised file: 'Power_Intent/top.rev1.upf', line 26
|
| 7) Supply Port 'tt1/ll1/xx2/VDD' missing in Golden:
| Golden file: not specified
| Revised file: 'Power_Intent/top.rev1.upf', line 27
|
| 8) Supply Port 'tt1/ll1/xx2/VSS' missing in Golden:
| Golden file: not specified
| Revised file: 'Power_Intent/top.rev1.upf', line 28
================================================================================
================================================================================
= Power Intent Compare Summary =
================================================================================
| Power intent command EQ Non-EQ | Total
| ----------------------------------------------- -------- -------- | --------
| add_power_state 6 0 | 6
| associate_supply_set 6 0 | 6
| create_power_domain 2 0 | 2
| create_supply_net 3 0 | 3
| create_supply_port 3 8 | 11
| create_supply_set 2 0 | 2
| define_isolation_cell 17 0 | 17
| define_retention_cell 12 0 | 12
| name_format 1 0 | 1
| set_scope 1 0 | 1
| supply_net_handle (created by other commands) 4 0 | 4
--------------------------------------------------------------------------------
| Power intent command with no one-to-one mapping EQ Non-EQ | Total
| ----------------------------------------------- -------- -------- | --------
| set_port_attributes 4 0 | 4
--------------------------------------------------------------------------------
| Total 61 8 | 69
================================================================================
Related Commands
READ DESIGN
READ LIBRARY
Description
Note: This is a Conformal Low Power command.
Tcl Command
report_compared_liberty
Parameters
Example
The following is a sample dofile that reads in two Liberty libraries and compares them:
read liberty -liberty gold_sample.lib -golden -lp
read liberty -liberty revs_sample.lib -revised -lp
compare liberty
report compared liberty -verbose
After you read in the libraries, use the COMPARE LIBERTY command to compare the two
libraries, and the REPORT COMPARED LIBERTY to view the details of the comparison.
Related Commands
ADD LIBERTY_COMPARE FILTER
COMPARE LIBERTY
Displays the compared points that were added with the ADD COMPARED POINTS command.
The first row represents the Golden design; the second row represents the Revised design.
It also shows a tabulated summary of the compared points for each design. This report
includes the total number of compared points for primary outputs, DFFs, D-latches,
blackboxes, and cut gates.
If you do not specify any options, Conformal lists all added compared points, and a tabulated
summary appears at the end of the list. However, if you use the -summary option, Conformal
displays only the tabulated summary.
Tcl Command
report_compared_points
Parameters
Related Commands
ADD COMPARED POINTS
COMPARE
REPORT STATISTICS
Reports the result of power grid comparison performed by the COMPARE POWER GRID
command.
Tcl Command
report_compared_power_grid
Parameters
-LEAF_cell_type Reports the types of leaf cells which are inside the sub-
hierarchy of the specified supply point and connected through
the specified supply point.
-DRIVER Reports the driving path from the supply source(s) to the
specified supply point.
-LOAD Reports the direct loads of the specified supply point.
-INStance <instance_name>
Specifies the instance name to display the supply points of the
instance. Use -GOLden or -REVised to specify the instance
name is a golden or revised instance. If -GOLden and -
REVised are not specified, default is -GOLden.
-GOLden Specifies that the supply point name or instance name is in the
golden design. This is the default.
-REVised Specifies that the supply point name or instance name is in the
revised design.
Examples
■ Use -CLASS UNMAPPED to view unmapped supplies detail information:
// Command: report_compared_power_grid -class unmapped -ver
Compare Power Grid: Non-Equivalent
Unmapped golden supplies:
1: (G) xMux/xSW/xSL/VDD (Virtual Supply Pin) (xMux/xSW/xSL:xMux/
MuxB.primary.power) (instance: xMux/xSW/xSL, unmapped)
2: (G) xMux/xSW/xSL/VSS (Virtual Supply Pin) (xMux/xSW/xSL:xMux/
MuxB.primary.ground) (instance: xMux/xSW/xSL, unmapped)
Unmapped revised supplies:
1: (R) xMux/xSWx.xSL/VDD (Physical Supply Pin) (xMux/xSWx.xSL:xMux/
Mux.primary.power) (instance: xMux/xSWx.xSL, unmapped)
2: (R) xMux/xSWx.xSL/VSS (Physical Supply Pin) (xMux/xSWx.xSL:xMux/
Mux.primary.ground) (instance: xMux/xSWx.xSL, unmapped)
3: (R) xMux/xSWx.xSLw/VDD (Physical Supply Pin) (xMux/xSWx.xSLw:xMux/
Mux.primary.power) (instance: xMux/xSWx.xSLw, unmapped)
4: (R) xMux/xSWx.xSLw/VSS (Physical Supply Pin) (xMux/xSWx.xSLw:xMux/
Mux.primary.ground) (instance: xMux/xSWx.xSLw, unmapped)
■ To report the driving path from the supply sources to a specific supply, use -POINT, -
DRIVER. Below examples shows how to view the diving supply source to a golden supply
point, xMux/xSW/xSL/VDD
TCL_SETUP> report_compared_power_grid -point xMux/xSW/xSL/VDD -driver -golden
(G) xMux/xSW/xSL/VDD (Virtual Supply Pin) (xMux/xSW/xSL:xMux/MuxB.primary.power)
(instance: xMux/xSW/xSL, unmapped) (unmapped)
■ Report the direct loading supply points of the revised supply point VDD:
TCL_SETUP> report_compared_power_grid -point VDD -load -revised
(R) VDD (Physical Supply Pin) (/:Def.primary.power) (instance: /, mapped instance:
/) (mapped: VDD) (equivalent)
Loads:
|-VDD (Physical Supply Pin) (/:Def.primary.power) (instance: /, mapped instance: /
) (mapped: VDD) (equivalent)
|-xReg/VDD (Physical Supply Pin) (xReg:Def.primary.power) (instance: xReg, mapped
instance: xReg) (mapped: xReg/VDD) (equivalent)
|-xMux/VDD (Physical Supply Pin) (instance: xMux, mapped instance: xMux) (mapped:
xMux/VDD) (equivalent)
|-xRamWrap/VM (Physical Supply Pin) (xRamWrap:Def.primary.power) (instance:
xRamWrap, mapped instance: xRamWrap) (mapped: xRamWrap/VM) (non-equivalent)
Related Commands
COMPARE POWER GRID
Reports the low power cells that were inserted by the Conformal Low Power software.
Tcl Command
report_cpf_logic
Parameters
-ISOlation Reports the inserted isolation cells only. This is the default.
-VERbose Reports detailed information of each defined CPF cell, including
cell types and rules that triggered this cell to be inserted in the
design.
Note: By default, this command reports all inserted low power cell types.
Example
The following commands read the lib.cpf and design.cpf files, performs low power cell
insertion, and reports only the inserted isolation and level-shifter cells:
read power intent -cpf lib.cpf design.cpf
commit power intent -insert_isolation
report cpf logic -isolation -level_shifter
Related Commands
COMMIT POWER INTENT
Reports paths that are analyzed by the tool, including all potential domain crossings. In GUI
mode, it can be used to visualize the reported paths in a schematic window.
The reported paths may contain objects that are not in the design, but are inferred by
application of the insertion strategies in the power intent.
Not every path will be reported. For example, paths that lie completely within a power domain
are not available in this report. The paths reported traverse across low-power cells,
hierarchical boundaries, macro feedthroughs and certain buffers/inverters. They start and
end at primary ports and/or logic leaf cells such as combinational cells or sequential cells,
macros, and other blackboxes.
Tcl Command
report_crossing_path
Parameters
-SRC_supply <supplyset> Report only paths whose start point has the specified
related driver supply set.
-DEST_supply <supplyset> Report only paths whose end point has the specified
related receiver supply set.
-DRIVER <pin*> Report only paths starting at the specified drivers.
-GUI In GUI mode, this option opens a schematic window
displaying the reported paths.
Example
To report all paths across u1/in[*] starting in a cell output with driver supply SS1:
report crossing path -src_supply SS1 -through u1/in[*]
To visualize them in the schematics and report all their intermediate points in the transcript
window:
report crossing path -src_supply SS1 -through u1/in[*] -verbose -gui
Related Commands
REPORT LOWPOWER INFO
Displays all cut points from the Golden and Revised designs that were added with the ADD
CUT POINT command.
Tcl Command
report_cut_point
Parameters
-Both Lists all cut points in both the Golden and Revised designs.
This is the default.
-Golden Lists all cut points in the Golden design.
-Revised Lists all cut points in the Revised design.
Related Commands
ADD CUT POINT
REPORT PATH
Related Commands
ANALYZE DATAPATH
ANALYZE MODULE
Displays information about datapath resources from the Golden and Revised designs.
Tcl Command
report_datapath_resource
Parameters
Related Commands
ANALYZE DATAPATH
ANALYZE MODULE
Displays design data on the Golden and Revised designs. It displays the number of design
modules, library cells, inputs, outputs, primitives, and one-to-one mapped state points.
This report includes word-level information about the design in terms of the number of
arithmetic/keyword operations. This report includes datapath elements such as WMUX,
WAND, WXOR and other word-level representations of Boolean logic. It displays simpler
representations of datapath logic that may need to be separated out for the comparison
process.
Press Ctrl-C to interrupt the key point listing if you find that the report is too long.
Tcl Command
report_design_data
Parameters
<module_name> Reports design data for the named module. By default, the
Conformal software reports design data on the top root design
module.
-Summary Summarizes the design data for the total number of design
modules, library cells, inputs, outputs, and primitives.
This is the default.
-Verbose Reports a detailed list of the design's total number of design
modules, inputs, outputs, each different library cell, and each
different primitive.
-NOKey_point Do not report the total one-to-one mapped state points. This is
the default.
Related Commands
READ DESIGN
READ LIBRARY
Displays the similarity degree of a design with reference to the other netlist. The similarity is
measured by the number of corresponding points in the two designs. The value of similarity
ranges from 0% to 100%. If the two designs are identical in structure, the similarity degree is
100%. The reporting can be used to evaluate the complexity of comparing two designs.
Tcl Command
report_design_similarity
Parameters
-INStance <instance_name*>
Displays the similarity degree of the netlist
inside the specified instance. The similarity
is evaluated with reference to the other
netlist.
If no instance is specified, the similarity is for
the entire design.
-Golden Specifies that the similarity evaluation is
performed on the Golden design. The
Revised netlist is used for reference. This is
the default.
-Revised Specifies that the similarity evaluation is
performed on the Revised design. The
Golden netlist is used for reference.
-Verbose Displays detailed information of the
comparison evaluation.
Examples
■ The following command displays the similarity of the Golden design's netlist. The
Revised design's netlist is used for reference.
report design similarity
■ The following command displays the similarities of the instances whose name begins
with mult in the Golden design's netlist:
report design similarity -instance mult*
Related Topic
Reporting Design Similarities
Display the don’t-touch registers in Golden and/or Revised designs which were specified with
the add_donttouch_registers command.
Tcl Command
report_donttouch_registers
Parameters
Related Commands
ADD DONTTOUCH REGISTERS
Displays all of the dynamic constraints you added to the Golden and Revised designs with
the ADD DYNAMIC CONSTRAINTS command.
Tcl Command
report_dynamic_constraints
Parameters
-Both Lists all dynamic constraints in both the Golden and Revised
designs. This is the default.
-Golden Lists all dynamic constraints in the Golden design.
-Revised Lists all dynamic constraints in the Revised design.
Examples
For a set of sample commands that shows this and related commands in context, see the
example for the COMPARE command.
Related Commands
ADD DYNAMIC CONSTRAINTS
COMPARE
PROVE
REPORT ENVIRONMENT
REPort ENvironment
[ |-Setup | -MOdeling | -MApping | -COMpare | -Diagnosis | -FUnctiondefault]
[ |-BOTH | -GOLDen | -REVised]
(Setup / LEC Mode)
Displays global settings for the Golden and Revised designs and system settings. The default
is to report all global settings.
Tcl Command
report_environment
Parameters
Related Commands
SET CASE SENSITIVITY
SET IMPLEMENTATION
SET X CONVERSION
Displays all floating signals in the Golden and Revised designs or in specified modules of a
design. The reported floating signals are either nets or pins and are either undriven or
unused. Use the SET UNDRIVEN SIGNAL command to specify the global behavior of the
undriven floating signals in the Golden and Revised designs.
Tcl Command
report_floating_signals
Parameters
-ROot Displays all floating signals in the root module. This is the
default.
-Module <module_name>
Displays all floating signals in the specified module within
the given defaults.
-All Displays all floating signals in "all" design modules within
the given defaults.
-UNDriven Displays only undriven floating signals. This is the
default.
-UNUsed Displays only unused floating signals.
-Net Displays only floating nets. If you do not specify -net or
-pin, Conformal displays both floating nets and floating
pins.
-Pin [-Direction] Displays only floating pins. If you do not specify -net or
-pin, Conformal displays both floating nets and floating
pins.
If -Direction is used, Conformal will also display the pin
direction information.
-Both Displays floating signals from both the Golden and
Revised designs. This is the default.
-Golden Displays floating signals from the Golden design.
-Revised Displays floating signals from the Revised design.
Related Commands
ADD TIED SIGNALS
REPORT GATE
REPort GAte
<identifier>
[-INStance | -Pin | -Net | -ID]
[-ALIAS]
[-Golden | -Revised]
[-SUPport]
[-FRONTIER]
[-FANIn <integer>]
[-FANOut <integer>]
[-UNReach]
[-SHORT_list | -NOSHORT_list]
[-SOURCE]
[-Collapse]
[-MAP_NAME]
[-NODYNamic | -DYNamic]
[-INDent <integer>]
[-Type <PI | 0 | 1 | E | Z | BBOX | DFF | DLAT | CUT | OUT | COMB | PO>]
[-RETention]
[-CORRespondence]
[-SUMmary]
[-CONSTRAINT]
[-ASSERTION]
[-ALLDNET]
[-SETUP_INFO]
(LEC Mode)
Displays flattened gate information. By default, it reports the gate ID, type, name, and its
fanins and fan-outs at the primitive level. After you specify options for the initial report, use the
REPORT GATE command without options to generate a report on the same gates, or specify
new options as needed.
Important
ID numbers can differ from one version of Conformal to another. Always use the full
path in dofiles and any time you rerun a design with a different Conformal version.
Tcl Command
report_gate
Parameters
-Collapse Do not report inverters and buffers in the fanin cone. The
default is to report all inverters and buffers in the fanin/
fan-out cone.
-MAP_NAME Displays the gate’s used names during mapping.
-NODYNamic Use this option in conjunction with the -fanin option.
The fanin cone does not stop at a gate with dynamic
constraints. This is the default.
-DYNamic Use this option in conjunction with the -fanin option. The
fanin cone stops at the gate with dynamic constraints.
-INDent <integer> Displays this amount of whitespace when reporting the fanin
and fan-out cones. The default value is 2.
-Type Reports all gates with the specified gate type. The available
gate types are as follows:
PI: Primary inputs
0: TIE-0 gates
1: TIE-1 gates
E: TIE-E gates
Z: TIE-Z gates
BBOX: Blackboxes
DFF: D flip-flops
DLAT: D-latches
CUT: Artificial gates for breaking combinational feedback loops
OUT: Artificial gates for the multiple outputs of blackboxes
COMB: Combinational gates
PO: Primary Outputs
Related Commands
ADD NAME ALIAS
BACKWARD
FORWARD
REPORT PATH
Tcl Command
report_guide_information
Parameters
Example
In summary mode, this command categorizes the statistics for guide information. The
following is an example of the default report:
=======================+=========+==============================+==========
| | Processed |
| +---------+----------+---------+ Not Yet
Information Type | Total | Applied | Rejected | Ignored | Processed
-----------------------+---------+---------+----------+---------+----------
instance_module_name | 100 | 100 | 0 | 0 | 0
uniquify | 2300 | 2200 | 80 | 10 | 10
ungroup | 1800 | 1800 | 0 | 0 | 0
group | 10 | 9 | 1 | 0 | 0
share transform | 30 | 28 | 1 | 1 | 0
speculation transform | 15 | 10 | 2 | 0 | 0
tree-typed transform | 10000 | 9999 | 0 | 1 | 0
sequential merge | 280 | 0 | 0 | 0 | 280
=======================+=========+=========+==========+=========+==========
When you use the -VERBose option, this command returns detailed information for each
module:
module mid_w32 :
[A] 1 : tree : t_rc.ovf:1
module tst :
[A] ungroup u1 : t_rc.ovf:22
[A] ungroup u2 : t_rc.ovf:29
[I] 1 : tree : t_rc.ovf:1
[R] 2 : tree : t_rc.ovf:1
[A] 3 : share : t_rc.ovf:36
Where the letter in square brackets indicates the processing status of the guide information:
A : Applied
R : Rejected
I : Ignored
N : Not yet be processed
Related Commands
Displays the results of the hierarchical comparison. If the WRITE HIER_COMPARE DOFILE
command is used, this command is automatically placed at the end of the hierarchical dofile
script. It lists the summary results and any modules that are nonequivalent, aborted, or
uncompared.
Tcl Command
report_hier_compare_result
Parameters
-DYNamicflattened Displays only the hierarchical modules that were either found to
be nonequivalent, or were equivalent but caused
nonequivalence at the parent level, and were automatically
flattened.
Use this option when performing hierarchical comparison with
the RUN HIER_COMPARE command.
-EXTRA_po Displays only the hierarchical modules that have extra (not-
mapped) primary outputs.
-ALL Displays the results of all of the modules.
-DEtail Displays the results in detail. This option is only effective if you
have executed the SET PROJECT NAME command at the start
of the LEC run.
-USage Displays the CPU use time for each module comparison.
Related Commands
RESET HIER_COMPARE RESULT
RUN HIER_COMPARE
Report ignored supply objects, instances, or modules added by command ADD IGnored
Grid.
Tcl Command
report_ignored_grid
Parameters
-Both Reports ignored objects of both Golden netlist and Revised netlist.
This is the default.
-Golden Reports the ignored objects of Golden netlist.
-Revised Reports the ignored objects of Revised netlist.
-ALL Reports all ignored objects, including supply objects, instances, and
modules. This is the default.
-SUPply Reports ignored supply objects. Which are supply pins in the design
netlist or virtual supply ports created in the 1801 power intent.
-Module Reports ignored modules.
-INStance Reports ignored instances.
Related Commands
ADD IGNORED GRID
Displays the input pins, which were added as ignored inputs, in the Golden and Revised
designs. These pins were originally specified with the ADD IGNORED INPUTS command.
Tcl Command
report_ignored_inputs
Parameters
-ROot Displays only the input pins in the root module. This is the default.
-Module <module_name>
Displays only the ignored input pins in the named module.
-All Displays all ignored input pins in all modules within the given
defaults.
-Both Displays both the Golden and Revised added ignored inputs. This is
the default.
-Golden Displays the added ignored inputs from the Golden design.
-REvised Displays the Revised ignored inputs.
Related Commands
ADD IGNORED INPUTS
Displays the output or I/O pins, which were added as ignored outputs, in the Golden and
Revised designs. These outputs were originally specified with the ADD IGNORED OUTPUTS
command.
Tcl Command
report_ignored_outputs
Parameters
-ROot Displays only the input pins in the root module. This is the
default.
-Module <module_name>
Displays only the ignored output or I/O pins in the specified
module.
-All Displays all ignored input pins in all modules within the given
defaults.
-Both Displays both the Golden and Revised added ignored outputs.
This is the default.
-Golden Displays only the Golden added ignored outputs.
-REvised Displays only the Revised ignored outputs.
Related Commands
ADD IGNORED OUTPUTS
Tcl Command
report_implementation_information
Parameters
Related Commands
READ IMPLEMENTATION INFORMATION
Displays the attributes placed on instances in the Golden and Revised designs. These
attributes were originally specified with the ADD INSTANCE ATTRIBUTE command.
Tcl Command
report_instance_attribute
Parameters
Related Commands
ADD INSTANCE ATTRIBUTE
Displays design instance on the Golden and Revised designs.It display the design instance
full hierarchical name ( include root module name ) and its binding module's user-defined
name, Conformal uniquified/parameterized name, source file name, and library name.
Tcl Command
report_instance_binding
Parameters
-NOTBoundbycfg CFM will list instance which is not bound by configuration file,
and with the other information [-MODULEname][-
ORIGMODULEname][-SOURCEfile][-LIBname] based on
user setting.
-BOTH Report design instance data on both the Golden and Revised
designs. This is the default.
-Golden Report design instance data on the Golden design.
-Revised Report design instance data on the Revised design.
Related Commands
Displays the constraints placed on instances in the Golden and Revised designs. These
constraints were originally specified with the ADD INSTANCE CONSTRAINTS command.
Tcl Command
report_instance_constraints
Parameters
Related Commands
ADD INSTANCE CONSTRAINTS
Displays the equivalences placed on instances in the Golden and Revised designs. These
equivalences were originally specified with the ADD INSTANCE EQUIVALENCES command.
Tcl Command
report_instance_equivalences
Parameters
Related Commands
ADD INSTANCE EQUIVALENCES
Reports the details for the specified instance renaming rule (added through the ADD
INSTANCE RENAMING COMMAND). When used without any options, reports details for all
instance renaming rules.
Tcl Command
report_instance_renaming
Parameters
Example
================================================================================
// Note: There are 2 instance renaming rule(s) found.
Related Commands
ADD INSTANCE RENAMING
MOS2BUFIF
REPORT MESSAGES
Tcl Command
report_key_point
Parameters
Related Commands
Description
Reports the Liberty compare filters added by the ADD LIBERTY_COMPARE FILTER
command.
Tcl Command
report_liberty_compare_filter
Paramters
<filter_name* ...> Specifies the name of the filter(s) to report. By default, this
command reports all Liberty compare filters. Wildcards are
supported.
Examples
■ The following command reports all Liberty compare filters:
report liberty_compare filter
■ The following command reports all Liberty filters whose name matches
"related_filter*":
report liberty_compare filter related_filter*
Related Commands
ADD LIBERTY_COMPARE FILTER
COMPARE LIBERTY
By default, Conformal reports on the library for the Golden design if you do not specify
options.
Note: When you read in a library, you can specify whether it is for the Golden or Revised
design.
Tcl Command
report_library_data
Parameters
Related Commands
READ LIBRARY
READ DESIGN
Tcl Command
report_lowpower_cells
Parameters
-Module Reports only the modules with low power cells. This is the default.
-Instance Reports only the instances with low power cells.
-Summary Displays a summary of low power cells.
Related Commands
ADD LOWPOWER CELLS
Reports the low power data. These are the results of the low power check performed on low
power cells using the CHECK LOWPOWER CELLS command.
For a description of the default rules that are added by the system, see CHECK LOWPOWER
CELLS.
Tcl Command
report_lowpower_data
Parameters
For isolation and level-shifter cell types, the -STatus arguments are
described as follows:
All: Reports all the low power cut gates that passed or failed the
technology mapping check. This is the default.
Pass: Reports all the low power cut gates that passed the technology
mapping check
Fail: Reports all the low power cut gates that failed the technology
mapping check
Notcheck: Reports the low power cut gates that were not checked for
isolation and level-shifter consistency
For the power domain consistency check, the -STatus arguments are
described as follows:
All: Reports all the mapped sequential points that passed and failed the
power domain consistency check. This is the default.
Pass: Reports the mapped sequential points that passed the power
domain consistency check
Fail: Reports the mapped sequential points that failed the power
domain consistency check
Notcheck: Reports the mapped sequential points that were not checked
for power domain consistency
-TYpe Specifies the module type reporting.
All Reports on all low power cells. This is the default.
Retention [-Rule <rulename>]
Reports on only the low power state retention cells.
-Rule <rulename> reports all the sequential pairs that
passed or failed the specified rulename.
-Isolation_cells
Reports on only the low power isolation cells.
-Level_shifter_cells
Reports on only the low power level-shifter cells.
-POWER_domain_check
Reports the results of power domain consistency check for
the mapped sequential points.
-SUMmary Displays the status summary of the check performed on low power cells.
This is the default.
-Verbose For state retention cells, this reports the sequential pairs (LEC mapped
points) that passed or failed the default rule or user rule. For each passed
or failed sequential pair, the corresponding rule it passed or failed on is
also reported. In addition, this reports any tag-name for the sequential
element in the Golden Design, and any power gating cell attribute for the
sequential element in the Revised Design.
For isolation cells and level-shifter cells, this reports the PASS or FAIL
status of low power cut gates that correspond to the isolation cells and
level-shifter cells.
Related Commands
ADD LOWPOWER CELLS
Reports low power information for different types of design objects (real objects), objects
inferred by low power intent (virtual objects), or low power strategies specified by power
intent.
When using wildcards, the choice of objects for which to display selected information can be
narrowed using filters, such as a filter to display only information for low power cells, filter to
display only information about objects in the design or only objects inferred by power intent.
Tcl Command
report_lowpower_info
Parameters
-PIN Specifies that the object is a pin. Pins can be design pins or
pins inferred by power intent.
-NET Specifies that the object is a net. Nets can be design nets or
nets inferred by power intent.
-STRategy Specifies that the object is a power intent strategy.
-LIBcell Specifies that the object is a library cell.
-ALL Display all available information for the specified object. This is
the default.
-DOMAIN_ASSIGNMENT Display the object's low power domain (applies only to
instances).
-SUPPLY_SET Displays the object's assigned supply set (applies only when
the object is a logic pin or an instance). For instances, the
information will be displayed for all logic pins of the instance.
For a given logic pin, this option displays the driver and receiver
supply sets. If -Verbose is used, this also lists the driver/
receiver pins. To limit the number of displayed driver/receiver
pins, use -MAX_driver_load.
-RELATED_PG_PIN Displays the related pg pins. Applies only when the object is a
logic pin or an instance. For instances, the information will be
displayed for all logic pins of the instance. This information is
displayed only for objects with physical use.
-PROPAGATED_SUPPLY Displays the propagated supply. Applies only when the object is
a supply pin, supply net, or an instance. For instances, the
information will be displayed for all supply pins of the instance.
This information is displayed only for objects with physical use.
-CLAMP_VALUE Displays the isolation cell clamping values. Applies only when
the object is a cell with isolation clamping function.
-MATCHING_STRATEGY Displays the low power strategies. Applies only when the object
is a low power instance or a logic pin. For low power instances,
this option reports the matching strategies used to infer or
implement the instance. For a logic pin, this option reports the
strategies that act on that pin.
-TARGETING_STRATEGY Displays the low power strategies. Applies only when the object
is a domain boundary pin. This option reports all strategies
acting on the pin and, for each strategy, the specific filters or
reasons that strategy could not be applied . When a strategy is
implementable, it reports the instances inferred by the strategy.
-LIBRARY_CELL Displays extracted low power cells. Applies only when the
object is a low power instance.
-DEDICATED_iso Displays information for dedicated isolation instances.
-ELABORATED Displays information for library cells in the elaborated design.
-LIMIT <num> Specifies the maximum number of objects to display when
using wildcards in the object name. Default is 0, which is used
to report all matching objects.
-LP Displays information for low power instances.
-LSH Displays information for level-shifter instances.
-ISO Displays information for isolation instances.
-COMBO Displays information for isolation and level-shifter combination
instances.
-RET Displays information for retention instances.
-PSW Displays information for power-switch instances.
-AON Displays information for always-on instances.
-MACRO Displays information for macro instances.
-MAX_DRIver_load <num>
Specifies the maximum number of driver/receiver pins to
display when using the -verbose option. Default is 1.
-MAX_LIBcell_instance <num>
Specifies the maximum number of library cell instances to
display when reporting a given library cell. Default is 1 and
assigning 0 will display all instances.
-NON_DEDICATED_iso Displays information for non-dedicated isolation instances.
-REAL Display information only for objects in the design.
-VIRTUAL Display information only for objects inferred from power intent
that are not already in the design.
-SINGLE_PIN_ret Displays information for single-pin retention instances.
-SUPPLY Displays information only for supply pins and supply nets.
-LOGIC Displays information only for logic pins and logic nets.
-TWO_PIN_ret Displays information for two-pin retention instances.
Example
The following command displays information about strategy TDR.iso1.
SETUP> report lowpower info -strategy TDR.iso1 -v
■ Floating Port Elements: Not inferred because they do not have logic receivers
■ Undriven Port Elements: Not inferred because they do not have logic drivers
■ Analog Port Elements: Not inferred because they are connected to analog signals
■ Zero Pin Retention Elements: Not inferred because isolation strategy applied to the zero-
pin retention clock, set or reset pin is dropped. For isolation insertions applied to zero-
pin retention clock, set, or reset pin, the tool derives the required isolation insertion
strategy from the retention strategy. Hence, the isolation strategy applied to the clock/set/
reset of the zero-pin retention cell is ignored
■ Antenna Diode Elements: Not inferred because all receivers of the domain boundary pin
are antenna diode pins.
■ Clamp Value 'any' Elements: Not inferred because the isolation clamp value is 'any' and
the tool does not know which isolation cell type should be implemented.
■ Implementable Elements: Reports implementable elements, (L) means strategy acts on
the lowconn of element, (H) means strategy acts on the highconn of element. Priority of
the element for the given strategy is printed as well. For each element, the inferred
instance name is printed. The (R) denotes a real instance, instance that is already
implemented in the design, while (V) denotes a virtual instance, an instance inferred by
power intent.
Related Command
REPORT POWER INTENT
This command works after READ POWER INTENT for both designs.
Tcl Command
report_lp_control_ignored
Parameters
Related Commands
SET LOWPOWER OPTION
Reports the specified low-power control compared pairs and not-paired low-power control
signals.
This command works after READ POWER INTENT for both designs..
Tcl Command
report_lp_control_pair
Parameters
Related Commands
SET LOWPOWER OPTION
Tcl Command
report_lp_control_verification
Related Commands
SET LOWPOWER OPTION
Displays the mapped points that were automatically identified or added with the ADD MAPPED
POINTS command. Each mapped point from the Golden and Revised design is displayed
along with a summary of all Golden and Revised mapped points.
The summary includes the total number of primary inputs, primary outputs, DFFs, D-latches,
TIE-Es, TIE-Zs, blackboxes, and cut gates.
If no options are entered, the command default is to display both the User and System
classes of mapped points.
Wildcard: The wildcard (*) represents any zero or more characters in instance or pin paths
of mapped points.
Tcl Command
report_mapped_points
Parameters
-Golden The mapped points are from the Golden design. This is the
default.
-REVised The mapped points are from the Revised design.
Related Commands
ADD MAPPED POINTS
REPORT STATISTICS
Displays the global setting of the mapping method and phase. For detailed information of
each usage in the report, run man on SET MAPPING METHOD command.
Tcl Command
report_mapping_method
Related Commands
SET MAPPING METHOD
The REPORT MAPPING MODEL command report the phase information added using the ADD
MAPPING MODEL command.
Tcl Command
report_mapping_model
Parameters
-Golden Reports the phase information for the modules in the Golden
design. This is the default.
-Revised Reports the phase information for the modules in the Revised
design.
-Both Reports the phase information for both the Golden and Revised
designs.
Related Commands
This command reports the information of all the mapping key points that are read in using the
command SET ANALYZE OPTION -MAPPING_FILE.
Tcl Command
report_mapping_information
Parameters
-Verbose Lists mapping data in details for all categories. The format is:
Examples
TCL_LEC> report_mapping_information -verbose
=============================================================================
Used Unused Rejected
-----------------------------------------------------------------------------
map_info 1 1 0
=============================================================================
Unused information:
-----------------------------------------------------------------------------
g1_reg -> + r1_reg mapping_file:1
=============================================================================
Used information:
-----------------------------------------------------------------------------
g1_reg -> - r1_reg mapping_file:1
=============================================================================
Related Commands
SET ANALYZE OPTION
REPORT MESSAGES
REPort MEssages
[-MOdeling | -MAPping | -Compare]
[-NOSORT | -SORT]
[-RUle <rule_name>]
[-Summary | -Verbose]
[-Both | -Golden | -REvised]
(Setup / LEC Mode)
Displays either a summary or complete list of the warning messages that come from the
modeling, mapping, or comparison process. (The modeling process occurs when Conformal
exits the Setup mode.) A summary of the warning messages is always displayed when the
modeling, mapping, or comparison process is in progress; however, this command displays
each individual warning message for the Golden and Revised designs, according to your
specifications.
See "Modeling Messages" in the Conformal Equivalence Checking User Guide for
information on the Modeling Messages and the commands/options that trigger them.
Tcl Command
report_messages
Parameters
Related Commands
READ DESIGN
READ LIBRARY
Displays the module attributes in the Golden and Revised designs. These attributes were
originally added with the ADD MODULE ATTRIBUTE command.
Tcl Command
report_module_attribute
Parameters
-ALL Displays "all" added module attributes within the given defaults.
-PIPELINE_Retime Displays only the modules added for pipeline-retiming.
-COMPARE_Effort Displays only the modules that have specified compare effort
levels.
-CPU_Limit Displays the modules with a specified CPU time limit.
-ECO_module Displays the ECO module(s) specified by the ADD MODULE
ATTRIBUTE -ECO_module attribute. Any mismatched ports
for these modules are ignored when running the WRITE
HIER_COMPARE DOFILE command.
-NOBBOXEMpty Displays the module(s) specified by the ADD MODULE
ATTRIBUTE -NOBBOXEMpty attribute.
-ISOlate_module Displays the modules marked for isolation (through the ADD
MODULE ATTRIBUTE -isolate_module option).
-MODULE <module_name* ...>
Reports the attribute for the specified module. Wildcards are
supported.
-FLAT_ECO_module Displays the ECO module(s) specified by the ADD MODULE
ATTRIBUTE -FLAT_ECO_module attribute.
-Both Displays the module attributes for both the Golden and Revised
designs. This is the default.
-Golden Displays the module attributes for the Golden design.
-Revised Displays the module attributes for the Revised design.
Related Commands
ADD MODULE ATTRIBUTE
ANALYZE HIER_COMPARE
READ DESIGN
READ LIBRARY
REPORT MODULES
REPort MOdules
[-ROot | <module_name> [-Down | -Up] | -All | -Top]
[-INSTantiation [-PARAMinfo | -CONST]]
[-LEVEL <value>]
[-Library]
[-NOINTERLeave |-INTERLeave]
[-Source]
[-USer]
[-VHDLname]
[-Both | -Golden | -Revised]
(Setup / LEC Mode)
Displays module information for the Golden and Revised designs. If you specify a module,
Conformal displays additional information on modules and library cells up or down the
hierarchy of the given module name.
Tcl Command
report_modules
Parameters
Examples
This example shows the difference between running the REPORT MODULES command
without any options versus running the command with the -USer option.
The following design file contains only one module named test. Module
VDW_mult_nbw_u8_u8_16 is internal module which is not defined in this file:
module test(aa, bb, oo);
input [7:0] aa, bb;
output oo;
assign oo = aa * bb;
endmodule
Related Commands
REPORT MODULE ATTRIBUTE
REPORT PATH
Displays the unidirectional and bidirectional transistor-MOS instances with their source and
drain ports.
Tcl Command
report_mos_direction
Parameters
Related Commands
ABSTRACT LOGIC
ADD CLOCK
DELETE CLOCK
READ PATTERN
REPORT CLOCK
RESOLVE
Related Commands
ANALYZE DATAPATH
ANALYZE MODULE
The ADD NAME ALIAS command specifies a JSON data file that contains name aliases for
changing keypoint names during mapping. These aliases are enabled with the "set
mapping method -alias" command. The REPORT NAME ALIAS command will the status
of the name alias, specifically whether the name alias has been applied. If the name alias has
not been applied, the report will indicate the reason why it has not been applied.
This command can be used only after mapping with name alias enabled (set mapping
method -alias).
Tcl Command
report_name_alias
Parameters
-GOLden Report the name alias status for the Golden design.
-REVised Report the name alias status for the Revised design.
-TYPE <type_name> Report the name alias for the specified type.
-MODULE <module_name>
Report the name alias status for the specified module.
-ALL Report the status for both not-applied and applied name
aliases. By default, this command reports only name aliases
that have not been applied.
Example
The following is a sample dofile and report from this command.
The following commands add name aliases from the na.json file and report the not-applied
name alias data after mapping:
add name alias na.json
set mapping method -alias
map key points
report name alias
Report:
=====================================
File: na.json:1 module: top type: ins
name: abc_reg
alias: xyz_reg
Not applied because it cannot find the module
======================================
Related Commands
ADD NAME ALIAS
REPORT GATE
Displays attributes on transistor-MOS nets. The attributes were originally added with the ADD
NET ATTRIBUTE command.
Tcl Command
report_net_attribute
Parameters
-ALL Displays "all" added net attributes within the given defaults.
-VDD Displays only the added VDD net attributes.
-GND Displays only the added GND net attributes.
-CLOCK0 Displays only the added Clock-0 net attributes.
-CLOCK1 Displays only the added Clock-1 net attributes.
-DYNSTate Displays only the added dynamic state net attributes.
-Module <module_name>
Reports net attributes from the named module.
-Both Displays net attributes from both the Golden and Revised
designs. This is the default.
-Golden Displays net attributes from the Golden design.
-Revised Displays net attributes from the Revised design.
Related Commands
ABSTRACT LOGIC
ADD CLOCK
DELETE CLOCK
READ PATTERN
REPORT CLOCK
RESOLVE
Displays all net constraints in the Golden and Revised designs that were added with the ADD
NET CONSTRAINTS command.
Tcl Command
report_net_constraints
Parameters
-Both Displays added net constraints in both the Golden and Revised
designs. This is the default.
-Golden Displays the added net constraints in the Golden design.
-Revised Displays the added net constraints in the Revised design.
Related Commands
ADD NET CONSTRAINTS
Displays all of the modules in the Golden and Revised designs that will not be included in the
hierarchical dofile script generation. These modules were originally specified with the ADD
NOBLACK BOX command.
Tcl Command
report_noblack_box
Parameters
Related Commands
ADD NOBLACK BOX
Tcl Command
report_nonequivalent_analysis
Parameters
Related Commands
ANALYZE NONEQUIVALENT
Displays all of the library and design file pathnames originally added with the ADD
NOTRANSLATE FILEPATHNAMES command. The Conformal software will not compile these
modules defined in libraries and design files.
Tcl Command
report_notranslate_filepathnames
Parameters
Related Commands
ADD NOTRANSLATE FILEPATHNAMES
Report what has been specified by add_notranslated_lines command and the full path
of files matched after reading in the design.
The command reports lines that are successfully skipped or lines that are not matched.
An (O) in the report means the line specification is fully matched, an (*) means partially
matched, and an (X) means the line specification has not been matched due to a short design
file.
Tcl Command
report_notranslated_lines
Related Commands
ADD NOTRANSLATED LINES
Displays all of the library and design modules originally added with the ADD NOTRANSLATE
MODULES command. Conformal will not compile these modules when reading in libraries and
designs.
Related Commands
ADD NOTRANSLATE MODULES
READ DESIGN
READ LIBRARY
Displays the output pin equivalences in the Golden and Revised designs. These output pin
equivalences were originally added with the ADD OUTPUT EQUIVALENCES command.
Tcl Command
report_output_equivalences
Parameters
-ROot Displays all output pin equivalences from the root module. This
is the default.
-Module <module_name>
Displays the output pin equivalences in the specified module.
-All Displays "all" output pin equivalences in all modules within the
given defaults.
-Both Displays the output pin equivalences in both the Golden and
Revised designs. This is the default.
-Golden Displays the output pin equivalences in the Revised design.
-Revised Displays the output pin equivalences in the Golden design.
Related Commands
ADD OUTPUT EQUIVALENCES
Displays the output stuck_at values and pin names in the Golden and Revised designs.
These output stuck_at values were originally added to pins with the ADD OUTPUT
STUCK_AT command.
Tcl Command
report_output_stuck_at
Parameters
-ROot Displays the output stuck_at values and pin names from the
root module. This is the default.
-Module <module_name>
Displays the output stuck_at values and pin names from the
specified module.
-All Displays all output stuck_at values and pin names in all
modules within the given defaults.
-Both Displays the output stuck_at values and pin names in both
the Golden and Revised designs. This is the default.
-Golden Displays the output stuck_at values and pin names in the
Revised design.
-Revised Displays the output stuck_at values and pin names in the
Golden design.
Related Commands
ADD OUTPUT STUCK_AT
Displays the partition key points originally added with the ADD PARTITION KEY_POINT
command.
Related Commands
ADD PARTITION KEY_POINT
Displays the partition points that were created with the ADD PARTITION POINTS command.
Tcl Command
report_partition_points
Parameters
-Both Lists the partition points in both the Golden and Revised
designs. This is the default.
-Golden Lists the partition points in the Golden design.
-Revised Lists the partition points in the Revised design.
-Verbose Displays all added partition points. This is the default.
-Summary Displays a summary message of the total number of added
partition points.
Related Commands
ADD PARTITION POINTS
Related Commands
ADD PARTITION KEY_POINT
REPORT PATH
REPort PAth
<<source> <destination> | -Feedback | -SELF | -SELF <gate>>
[-NET]
[-SEQ_ASYNC]
[-Source]
[-Golden | -Revised]
(Setup / LEC Mode)
Displays the paths between a source gate and a destination gate. The -feedback option
displays all feedback paths for all CUT gates. The source and destination gates can be gate
ID numbers, instance paths, or pin paths.
To report the feedback path on one CUT gate, use the same CUT gate ID, instance path, or
pin path for both the source and the destination.
Tcl Command
report_path
Parameters
<source> Specifies the gate ID number, instance path, or pin path of the
source gate.
Note: ID numbers can differ from one version of Conformal to
another. Always use the full path in dofiles and any time you
rerun a design with a different Conformal version.
<destination> Specifies the gate ID number, instance path, or pin path of the
destination gate.
Note: ID numbers can differ from one version of Conformal to
another. Always use the full path in dofiles and any time you
rerun a design with a different Conformal version.
-Feedback Reports the feedback path of all CUT gates, within the given
defaults.
-SELF <gate> Reports all loops to DFF and DLATs. If you specify a gate, it
reports only loops to that gate.
-NET Displays the corresponding net of the gate in the path.
Related Commands
ADD CUT POINT
REPORT GATE
Tcl Command
report_physical_cells
Parameters
Related Commands
ADD PHYSICAL CELLS
Displays the list of pairs of pin names for pin binding in the mapping process. If you do not
enter options, Conformal displays all binding pairs..
Tcl Command
report_pin_binding
Parameters
-Module Specifies the module pair that the pin binding rules are applied
in.
Related Commands
ADD PIN BINDING
Displays the constraints placed on primary input pins in the Golden and Revised designs.
These constraints were originally specified with the ADD PIN CONSTRAINTS command.
Tcl Command
report_pin_constraints
Parameters
Related Commands
ADD PIN CONSTRAINTS
Displays the assigned pin directions for each module: pin directions are either assigned by
the tool or assigned using the ASSIGN PIN DIRECTION command for I/O pins. The default
is to display only a summary message.
Tcl Command
report_pin_direction
Parameters
Related Commands
ABSTRACT LOGIC
ADD CLOCK
DELETE CLOCK
READ PATTERN
REPORT CLOCK
RESOLVE
Displays a list of added pin equivalences and inverted pin equivalences. These pin
equivalences were originally added with the ADD PIN EQUIVALENCE command. Inverted
pin equivalences are distinguished by a "-" next to the primary input pin name.
Tcl Command
report_pin_equivalences
Parameters
-ROot Displays pin equivalences from the root module. This is the
default.
-Module <module_name>
Displays pin equivalences from the specified module.
-All Displays pin equivalences in all modules within the given defaults.
-Both Displays pin equivalences from both the Golden and Revised
designs. This is the default.
-Golden Displays pin equivalences from the Golden design.
-REvised Displays pin equivalences from the Revised design.
Related Commands
ADD PIN EQUIVALENCES
Note: This is a Conformal Low Power command and is for the 1801 flow. For CPF flow, this
command is the same as "report lowpower data".
Reports the result of consistency checks performed by the COMPARE POWER CONSISTENCY
command.
Tcl Command
report_power_consistency
Parameters
DFF: D flip-flop
DLAT: D-latch
BBOX: Blackbox data pins
-SUMmary Lists a summary report of the power consistency comparison
result. This is the default.
-Verbose Displays a detailed report for each mapped key point and the
corresponding supply set information and the power consistency
result.
(CPF flow)
-STatus <All | Pass | Fail | Notcheck>
Displays the specified status of compared points.
All is the default.
Related Commands
REPORT POWER INTENT
Reports the power intent compare filters for the current session. Power intent compare filters
are added using the ADD POWER_INTENT_COMPARE FILTER command.
Tcl Command
report_power_intent_compare_filter
Parameters
Example
■ The following command reports all power intent compare filters:
report power_intent_compare filter
■ The following command reports all power intent filters which name match
"iso_filter*":
report power_intent_compare filter iso_filter*
Related Commands
ADD POWER_INTENT_COMPARE FILTER
Reports information about power intent objects and their attributes as well as design
references stored in the power intent database.
Tcl Command
report_power_intent
Parameters
<-type_name...> Selects the power intent objects to report by type. For a list of
supported options, see the following section "Power Intent
Object Options".
<name* ...> Selects the power intent objects to report by pattern.
-DUPLICATED Report duplicated library definitions.
-FILES With this option, report power intent will report all power
intent files read during read power intent.
-HIERarchical Report only hierarchical (non-elaborated) power intent objects.
-IMPLICIT Report implicit power intent objects. Unless this option is
specified, only explicit power intent objects will be reported.
-INVALID Report invalid power intent objects.
bind_verification_component or verification_component
Reports bind_verification_component
commands.
create_analysis_view or analysis_view
Report analysis views defined by
create_analysis_view commands.
create_assertion_control or assertion_control
Reports assertion controls defined by
create_assertion_control commands.
create_bias_net or bias_net
Reports bias nets defined by
create_bias_net commands.
create_global_connection or global_connection
Reports create_global_connection
commands.
create_ground_nets or ground_net
Reports ground nets by
create_ground_nets commands.
create_isolation_rule or isolation_rule
Reports isolation rules defined by
create_isolation_rule commands.
create_level_shifter_rule or level_shifter_rule
Reports level shifter rules defined by
create_level_shifter_rule
commands.
create_mode or mode
Reports modes defined by create_mode
commands.
create_mode_transition or mode_transition
Reports mode transitions defined by
create_mode_transition commands.
create_nominal_condition or nominal_condition
Reports nominal conditions defined by
create_nominal_condition commands.
create_operating_corner or operating_corner
Reports operating corners defined by
create_operating_corner commands.
create_pad_rule or pad_rule
Reports pad rules defined by
create_pad_rule commands.
create_power_domain or power_domain
Reports power domains defined by
create_power_domain commands.
create_power_mode or create_power_mode
Reports power modes defined by
create_power_mode commands.
create_power_nets or power_net
Reports power nets defined by
create_power_nets commands.
create_power_switch_rule or power_switch_rule
Reports power switch rules defined by
create_power_switch_rule commands.
create_state_retention_rule or retention_rule
Reports retention rules defined by
create_state_retention_rule
commands.
define_always_on_cell or always_on_cell
Reports always on cells defined by
define_always_on_cell commands or
extracted from Liberty.
define_global_cell or global_cell
Reports global cells defined by
define_global_cell commands or
extracted from Liberty.
define_isolation_cell or isolation_cell
Reports isolation cells defined by
define_isolation_cell commands or
extracted from Liberty.
define_level_shifter_cell or level_shifter_cell
Reports level shifter cell cells defined by
define_level_shifter_cell commands
or extracted from Liberty.
define_library_set or library_set
Reports library sets defined by
define_library_set commands.
define_open_source_input_pin or open_source_input_pin
Reports cells that contain open source input
pins defined by
define_open_source_input_pin
commands.
define_pad_cell or pad_cell
Reports pad cells defined by
define_pad_cell commands or extracted
from Liberty.
define_power_clamp_cell or power_clamp_cell
Reports diode cells defined by
define_power_clamp_cell commands or
extracted from Liberty
define_power_clamp_pins or power_clamp_pins
Reports clamp cells defined by
define_power_clamp_pins commands or
extracted from Liberty
define_power_switch_cell or power_switch_cell
Reports power switch cells defined by
define_power_switch_cell commands
or extracted from Liberty
define_related_power_pins or related_power_pins
Reports define_related_power_pins
commands
define_state_retention_cell or retention_cell
Reports state retention cells defined by
define_state_retention_cell
commands or extracted from Liberty
identify_always_on_driver Reports identify_always_on_driver
commands.
identify_power_logic Reports identify_power_logic
commands.
identify_secondary_domain Reports identify_secondary_domain
commands.
io_pad Reports IO pad cells defined by power intent
commands.
set_analog_ports or analog_ports
Reports analog ports defined by
set_analog_ports commands.
set_design or design
Reports design models defined by
set_design commands.
set_diode_ports or diode_ports
Reports diode ports defined by
set_diode_ports commands.
set_equivalent_control_pins or equivalent_control_pins
Reports set_equivalent_control_pins
commands.
set_floating_ports or floating_ports
Reports floating ports defined by
set_floating_ports commands.
set_input_voltage_tolerance or bias_group
Reports input supply voltage tolerance
constraints defined by
set_input_voltage_tolerance
commands.
set_instance or design_scope
Reports design scopes defined by
set_instance commands.
set_macro_model or macro_model
Reports macro models defined by
set_macro_model commands or extracted
from Liberty
set_pad_ports or pad_ports
Reports pad ports defined by set_pad_ports
commands.
set_power_source_reference_pin or power_source_reference_pin
Reports
set_power_source_reference_pin
commands.
set_power_target or power_target
Reports set_power_target commands.
set_sim_control or sim_control
Reports set_sim_control commands.
set_switching_activity or switching_activity
Report set_switching_activity
commands.
set_wire_feedthrough_ports or feedthrough_group
Report wire feedthrough ports defined by
set_wire_feedthrough_ports
commands
add_port_state or port_state
Reports port states defined by
add_port_state commands.
add_power_state or power_state_set
Reports add_power_state
commands.
add_pst_state or pst_state
Reports pst states defined by
add_pst_state commands.
apply_power_model Reports apply_power_model
commands.
associate_supply_set or supply_set_handle
Reports supply set handles defined
by create_power_domain or
associate_supply_set
commands.
begin_power_model or power_model
Reports power models defined by
begin_power_model commands.
bind_checker Report bind_checker commands.
create_supply_net or supply_net
Reports supply net defined by
create_supply_net commands.
create_supply_port or supply_port
Reports supply ports defined by
create_supply_port
commands.
create_supply_set or supply_set
Reports supply sets defined by
create_supply_set commands.
create_upf2hdl_vct or upf2hdl_vct
Reports upf2hdl VCT defined by
create_upf2hdl_vct
commands.
define_always_on_cell or always_on_cell
Reports always on cell defined by
define_always_on_cell
commands or extracted from Liberty
define_diode_clamp or power_clamp_cell
Reports diode cells or cell pins
defined by define_diode_clamp
commands or extracted from
Liberty.
define_isolation_cell or isolation_cell
Reports isolation cells defined by
define_isolation_cell
commands or extracted from
Liberty.
define_level_shifter_cell or level_shifter_cell
Reports level shifter cells defined by
define_level_shifter_cell
commands or extracted from
Liberty.
define_power_switch_cell or power_switch_cell
Reports power switch or ground
switch cells defined by
define_power_switch_cell
commands or extracted from
Liberty.
define_retention_cell or retention_cell
Reports state retention cells defined
by define_retention_cell
commands or extracted from
Liberty.
describe_state_transition or state_transition
Reports state transitions defined by
describe_state_transition
commands.
map_isolation_cell Reports map_isolation_cell
commands
map_level_shifter_cell Reports
map_level_shifter_cell
commands
map_power_switch Reports map_power_switch
commands.
map_retention_cell Reports map_retention_cell
commands.
name_format or settings
Reports 1801 settings defined by
name_format commands.
power_state Reports power states defined by
add_power_state commands.
set_design_attributes or design_attributes
Reports
set_design_attributes
commands.
set_equivalent or equivalent
Reports set_equivalent
commands.
set_isolation or isolation
Reports isolation strategies defined
by set_isolation commands.
set_level_shifter or set_level_shifter
Reports level shifter strategies
defined by set_level_shifter
commands.
set_pin_related_supply or pin_related_supply
Reports pin related supplies defined
by set_pin_related_supply
commands.
set_port_attributes or port_attributes
Reports set_port_attributes
commands.
set_related_supply_net or related_supply_net
Reports
set_related_supply_net
commands.
set_repeater or repeater
Reports repeater (buffer) strategies
defined by set_repeater
commands.
set_retention_elements or retention_elements
Reports named list of elements
defined by
set_retention_elements
commands.
set_retention or retention
Reports retention strategies defined
by set_retention commands.
set_scope or scope
Reports scopes defined by
set_scope commands.
set_sim_control Reports simulation controls defined
by set_sim_control commands.
set_simstate_behavior or simstate_behavior
Reports
set_simstate_behavior
commands.
supply_net_handle Reports supply net handles
use_interface_cell or interface_cell
Reports use_interface_cell
commands.
Example
The following command reports all supply set power intent objects specified in the power
intent:
report power intent –supply_set
The following command reports all supply set power intent objects specified in the power
intent as well as the implicit supply sets created by the tool:
report power intent –supply_set -implicit
The following command reports power intent objects whose name matches pattern 'PD1':
report power intent PD1
Related Commands
READ POWER INTENT
Displays primary input pins from the Golden and Revised designs.
Tcl Command
report_primary_inputs
Parameters
Related Commands
ADD PRIMARY INPUT
Displays primary output pins from the Golden and Revised designs.
Tcl Command
report_primary_outputs
Parameters
Related Commands
ADD PRIMARY OUTPUT
REPORT PROJECT
REPort PRoject
[-ALL]
[-DB_INFO]
[-Run <integer ...>]
[-Verbose]
(Setup / LEC Mode)
This command reports the LEC runs that have been tracked in the current LEC project, which
is specified using SET PROJECT NAME command.
Tcl Command
report_project
Parameters
-ALL Reports the information of all LEC runs. When using this option,
the verbose mode is off by default.
-DB_INFO Reports the verification database information of the LEC runs.
-Run <integer ...> Reports the details of one or more LEC runs. When using this
option, the verbose mode is on by default.
-Verbose Reports the details for the run (including the host name and
dofile for each LEC run).
Related Commands
DELETE PROJECT
REPORT PST
REPort PST
[-COMPACT [-FLATtened_report]]
[-ID <state_id> ]
[-LIMit <n>]
[-STATE_COUNT]
[-SUPply <name*> [-STATE <state_name*> | -VOLTAGE <voltage_value*>]]
[-SUPPLY_IN_PST_ONLY]
[-EXCLUDE_SUPPLY_IN_SUPPLY_SET_STATE_ONLY]
[-GOLden | -REVised]
(Setup Mode)
Each row of the table presents the voltage values of the supplies. By default, the report is
displayed with the alignment table format unless a compact view (-compact) is specified.
When -compact is specified without -flattened_report, multiple global consistent states are
grouped if some of their supplies share common voltage values. See the Example section
for more details.
Each row is also associated with an ID, which can be used to further report the detailed
information of the global state(s) when -id is specified.
If there is no global power state that is consistent with all the power state tables, an empty
table will be reported.
Tcl Command
report_pst
Parameters
Example
Example 1
In the results, if multiple voltage values of a signal are consistent with the voltages of other
signals, those voltage values are collected and grouped by {} to be collapsed into one state.
For example,
1, 0.9, 0.9, 0, 0.9, {0.9, OFF}
If multiple signals are found to have different voltage values but are consistent with the
voltages of other signals, the voltage values of those signals are grouped by [ ]. For example,
2, OFF, {[0.81, 0, OFF], [0.72, 0, OFF]}, OFF
If multiple groups of voltage values exist, each combination of the voltage values of the groups
represents a global consistent state. For example,
3, 0.81, {[0.81, 0, 0.81], [0.81, 0, OFF]}, {0.81, OFF}
Following is the reporting format when both -compact and -flattened_report are specified:
ID, VDD, VDD_AON, VSS, VDDSW, i0/VDDSW
1, 0.9, 0.9, 0, 0.9, 0.9
2, 0.9, 0.9, 0, 0.9, OFF
3, 0.81, 0.81, 0, 0.81, 0.81
4, 0.81, 0.81, 0, 0.81, OFF
5, 0.81, 0.81, 0, OFF, 0.81
6, 0.81, 0.81, 0, OFF, OFF
7, OFF, 0.81, 0, OFF, OFF
8, OFF, 0.72, 0, OFF, OFF
Example 2
The following reports states for specific supplies: the power of supply set SS_A and the power
of supply set SS_B.
SETUP> report pst -supply SS_A.power SS_B.power
---------------------
ID
| VDDA
| | VDDB
---------------------
1 | 0.9 | 0.9
2 | OFF | 0.9
3 | OFF | OFF
Example 3
The following checks if there is a legal (global consistent) state where supply VDD_AON
works with voltage 0.81 and VDD_SW is OFF:
SETUP> report pst -supply VDD_AON VDD_SW -voltage 0.81 OFF
Reports the instances that were transformed with the SET ABSTRACT MODEL
-transform_pulse_generator_on command.
Tcl Command
report_pulse_generator
Parameters
Related Commands
SET ABSTRACT MODEL
Execute the report command of targeted running LEC by process ID and watch directory.
Tcl Command
report_remote_data
Parameters
-Pid <integer> The process ID of targeted LEC. It needs to be in the same machine.
-Watch_dir <string>
The watch directory of targeted LEC. It can cross different machines.
The targeted LEC needs to run set_watcher on -directory
<string> first.
<report command>
It supports report_mapped_points, report_unmapped_points,
report_compare_data with their corresponding options.
Example
report remote data -pid 12345 report_compare_data -class abort
Related Command
SET WATCHER
Tcl Command
report_removed_instance
Parameters
-Golden Reports instances removed from the Golden design. This is the
default.
-Revised Reports instances removed from the Revised design.
Related Command
REMOVE
Displays the list of renaming rules for mapping, module, pin, and instance renaming. These
rules were originally added with the ADD RENAMING RULE command. The list displays a rule
number along with a renaming rule. If you do not enter options, Conformal displays all
renaming rules.
Tcl Command
report_renaming_rule
Parameters
-MAp Displays only mapping renaming rules. If you do not specify -map,
-module, or -pin, Conformal reports all renaming rules.
-MOdule Displays only module renaming rules.
-PIn Displays only pin renaming rules.
-INSTance Displays only instance renaming rules.
-Both Displays the renaming rules applied to both the Golden and Revised
designs. This is the default.
-Golden Displays the Golden design renaming rules.
-Revised Displays the Revised design renaming rules.
Related Commands
ADD RENAMING RULE
READ DESIGN
READ LIBRARY
Reports the retention mapping rules. The set of rules reported include the user rules added
using the ADD RETENTION MAPPING command and the default rule added by the system.
For a description of the default rules that are added by the system, see CHECK LOWPOWER
CELLS.
Note: The default rule is always reported even if no user rule is added using the ADD
RETENTION MAPPING command.
Tcl Command
report_retention_register_mapping
Related Commands
ADD RETENTION MAPPING
Displays the list of rule violations after the designs and libraries have been read in. Use the
-summary option to display all of the violated rules.
Use the SET RULE HANDLING command to change the handling of any of these reported
rule violations.
See the Conformal Equivalence Checking User Guide for rule definitions and sample
cases.
Rules with a severity of "Ignore" are not reported except with the rule_name or -ignore
options.
Tcl Command
report_rule_check
Parameters
-NOHidden Reports only occurrences that are not hidden. This is the
default.
-Note Displays violations that have a severity level of note.
-HIDden Reports only occurrences that are hidden.
-COMplete Reports all occurrences regardless whether they are hidden or
not
-FILTERED_out Reports only occurrences excluded by filters (regardless
whether they are waived or not).
-NOFILTERED_out Reports only occurrences not excluded by filters (regardless
whether they are waived or not).
-WAIved Reports only occurrences that are waived (regardless whether
they are excluded by filters or not).
-NOWaived Reports only occurrences that are not waived (regardless
whether they are excluded by filters or not).
-OCCURRENCE_COUNT Report the number of occurrences even if it is zero.
-MAX_PRINT_COUNT <limit>
Limits the verbose display of all the reported rules to the
specified number of occurrences. Used with -help, it reports
the rule checking limit set by the set rule handling
-limit command.
-RULE_SEParation <num>
<num> specifies the number of blank lines to print before each
rule is reported. Without this option, no blank lines are printed
before each reported rule.
-SETTING Displays the current severity level for the rule.
-STATUS Selects rules to be displayed based on their execution status.
ALL: All rules. This is the default.
FAIL: Rules with failure occurrences.
PASS: Rules without failure occurrences.
IGNORED: Rules that are not run because their severity is
'ignore'.
NOT-APPLICABLE: Rules not applicable for the run.
-Summary Displays the status in summary format. This is the default.
Related Commands
READ DESIGN
READ LIBRARY
Tcl Command
report_rule_filter
Parameters
Examples
The following command saves the ABC filter report to a file named XYZ:
report rule filter ABC > XYZ
Related Commands
ADD RULE FILTER
This command reports the runtime for the specified module, hierarchical_compare,
timeout modules and commands. The unit of time is in seconds.
Tcl Command
report_runtime_limit
Parameters
-MODule Reports the runtime limit of LEC in the specified module. If the
module name is not specified, the runtime limit of the root
module will be reported
-HIER_compare Reports the runtime limit of the hierarchical comparison and the
file name of the specified dofile.
-TIMEOUT_MODule Reports the timeout module compare in the hierarchical
comparison and the command which reaches the runtime limit.
-COMmand Reports the runtime limit of the specified command. If the
command name is not specified, the runtime limit of all the
commands will be reported.
Related Commands
DELETE RUNTIME LIMIT
Displays the paths Conformal searches to locate filenames included in the READ DESIGN
and READ LIBRARY commands.
Tcl Command
report_search_path
Parameters
-Design Reports the search path used by the READ DESIGN command.
If you do not specify -design or -library, Conformal reports the
search path used by both the READ DESIGN command and the READ
LIBRARY command.
-Library Reports the search path used by the READ LIBRARY command.
If you do not specify -design or -library, Conformal reports the
search path used by both the READ DESIGN command and the READ
LIBRARY command.
-POWER_intent This is a low power command option. Reports the search path(s) for
power intent files.
-Both Reports the search path used by both the Golden and Revised
designs. This is the default.
-Golden Reports the search path used by the Golden design and library.
-Revised Reports the search path used by the Revised design and library.
Related Commands
ADD SEARCH PATH
READ DESIGN
READ LIBRARY
REPORT SEQ_CORRESPONDENCE
REPort SEQ_CORRespondence
[-ALL [-GOLden | -REVised]]
[-GATe <identifier> [-GOLden | -REVised]]
[-RETime < ALL | SUCCESS | FAIL>]
[-UNAccounted]
(LEC Mode)
Displays the sequential corresponding points that were automatically identified or added with
the ADD SEQ_CORR command. Use this command to help debug general retiming by
displaying the sequential correspondence and retiming results.
Tcl Command
report_seq_correspondence
Parameters
Examples
■ The following command reports a list of Golden registers that are neither mapped by
name nor have sequential correspondence:
report seq_corr -unaccounted
Related Commands
ANALYZE RETIMING
ADD SEQ_CORRESPONDENCE
DELETE SEQ_CORRESPONDENCE
This command displays information about setup information that has been read in using the
READ SETUP INFORMATION command.
Tcl Command
report_setup_information
Parameters
Examples
■ To view a summary of the setup information that has been read in, use the following
command:
SETUP/LEC> report setup information -summary
This report displays the number of occurrences with setup information and the source of
the setup information.
SETUP/LEC> report setup information -summary
================================================================
Occurrences Source
----------------------------------------------------------------
4 seq_merge
4 total rc.log1
================================================================
■ The following displays which occurrences of setup information are used in the current
run, not used in the current run, and rejected:
SETUP/LEC> report setup info -usage -verbose
================================================================================
Used Unused Rejected
--------------------------------------------------------------------------------
seq_merge 2 1 1
================================================================================
Related Commands
READ SETUP INFORMATION
REPORT STATISTICS
REPort STatistics
(LEC Mode)
Summarizes the mapping and comparison statistics for the Golden and Revised designs in a
table.
Tcl Command
report_statistics
Related Commands
REPORT COMPARE DATA
REPORT SUPPLY
REPort SUpply
[-PORT | -GLOBAL]
[-ROOT| -Module <name_list*> | -ALL]
[-Golden | -Revised | -Both]
(Setup Mode)
Reports the power and ground pins in the design that were defined with the ADD SUPPLY
command.
Tcl Command
report_supply
Parameters
Related Commands
ADD SUPPLY
DELETE SUPPLY
Tcl Command
report_tcl_attributes
Parameters
Example
■ The following command reports attributes of all objects:
report tcl attributes
■ The following command reports attributes of CPF objects which match 'power*'
report tcl attributes -cpf_obj power*
REPORT TESTCASE
REPort TEstcase
< [-NONEQ]
[-ABORT]
[-Golden <<gate_id> | <instance_pathname> ...> ]
[-Revised <<gate_id> | <instance_pathname> ...> ]
[-DATAPATH_module <-INST_name <instance_name*> ...>
| <-QUAlity <number>>]
>
[-DIR_name <directory_name>]
[-FIle <filename>]
[-KEYPOINT_DEPTH <number>]
[-NAME | -NONAME]
[-REPlace | -APPend]
(LEC Mode)
Automatically extracts testcases for selected key points and generates a dofile and a file
containing mapping information. Running the generated dofile can reproduce the problem in
original design, such as nonequivalences and aborts.
The -datapath_module option applies the testcase extraction to datapath modules in the
resource file. This option is used after datapath module-based analysis. The extracted
testcase is encapsulated in the XML file.
Tcl Command
report_testcase
Parameters
Examples
■ The following command selects all nonequivalent points, all abort points, and key points
with gate id 10, with instance dlat in the Golden design netlist and the key point with
instance dff in the Revised design netlist, allowing the names of design objects to be
included in the generated testcase:
report testcase -noneq -abort -golden 10 dlat -revised dff
■ The following command will select key point with gate id 10 in Revised design netlist for
testcase extraction. The names of design objects will use generic names (gate type and
a serial number)
report testcase -revised 10 -noname
■ The following command will select all nonequivalent points for testcase extraction, using
key point depth:
report testcase -noneq -keypoint_depth 1
■ The following command will report testcases on the datapath module whose instance
name starts with add into the file add.xml under the directory LEC_testcase:
report testcase -datapath_module -inst_name add* -file \
add.xml -dir_name LEC_testcase -replace
■ The following command will report testcase on the datapath modules whose evaluated
quality are less than or equal to 30% into the file low_quality.xml under the directory
LEC_testcase:
report testcase -datapath_module -quality 30 -file low_quality.xml \
-dir_name LEC_testcase -replace
Related Command
READ TESTCASE
You can also use this command with the -noneq option to report error patterns for every
nonequivalent compared key point.
Tcl Command
report_test_vector
Parameters
Example
Using the Report Generated by -ncsim
To generate a test vector report that can be consumed by NC-Sim, use the -ncsim option to
output the test vectors to a Tcl File:
report test vector kp1 -ncsim > lecvec.tcl
Conformal will create a Tcl script of the test vectors. This file will contain two procedures:
golforce1 and revforce1, which you can use to put test vectors in the design. For
example (after you load the Golden/Revised design into NC-Sim and source the Tcl file), you
can use the following command:
source lecvec.tcl
golforce1 <index>
where <index> is the nth index of the test vector to insert. For example,
golforce1 2
revforce1 1
Related Command
DIAGNOSE
Tcl Command
report_tied_signals
Parameters
-TIEX Displays signals tied to logic X. If you do not specify the logic,
Conformal displays signals tied to logic 0, 1, Z, and X.
-All Displays all net and instance names, within the given defaults,
that have tied signals assigned to them. This is the default.
-Net Displays net names that have tied signals assigned to them.
-Pin Displays pin names that have tied signals assigned to them.
If -Direction is used, Conformal will also display the pin
direction information.
-Both Displays tied signals from both the Golden and Revised
designs. This is the default.
-Golden Displays tied signals from the Golden design.
-REvised Displays tied signals from the Revised design.
Examples
Reporting Tied Signals from the remodeling of Conformal Low Power
SETUP> report tied signal -class lowpower
Tied nets in Golden: LOWPOWER class
In module SRDFFRQX1: RT <TIE0>
In module SRDFFSRX1: RT <TIE0>
Tied nets in Revised: LOWPOWER class
In module SRDFFRQX1: RT <TIE0>
In module SRDFFSRQX1: RT <TIE0>
Reporting Tied Signals from Both the User and System Classes
SETUP> report tied signal -class full
Tied nets in Golden: SYSTEM class
In module TIELO: Y <TIE0>
In module SDFFRHQX1: U$1/S <TIE0>
Tied nets in Golden: USER class
In module mac_tx_fifo_1: afull <TIE0>
Tied nets in Golden: LOWPOWER class
In module SRDFFRQX1: RT <TIE0>
In module SRDFFSRX1: RT <TIE0>
Tied nets in Revised: SYSTEM class
In module TIELO: Y <TIE0>
In module SDFFRHQX1: U$1/S <TIE0>
Tied nets in Revised: LOWPOWER class
In module SRDFFRQX1: RT <TIE0>
In module SRDFFSRQX1: RT <TIE0>
Related Commands
ADD TIED SIGNALS
This report lists unmapped points, along with a summary of all of the unmapped points in the
Golden and Revised designs.
Note: If you do not specify options, Conformal identifies all unmapped points and displays a
summary. Furthermore, if you do not specify either Golden or Revised, Conformal reports
unmapped points for both designs.
Tcl Command
report_unmapped_points
Parameters
Related Commands
ADD MAPPED POINTS
REPORT STATISTICS
REPORT VERIFICATION
REPort VErification
[-COMPare_result]
[-HIER]
[-IGNORE_VERIFIED_PO_UNMAP]
[-Summary]
[-Verbose]
(LEC/SETUP Mode)
Reports a table of all violated checklist items for the categories listed below.
■ Non-standard modeling options used:
❑ Tristated output: checked | not checked
❑ Revised X signals set to E: yes | no
❑ Floating signals tied to Z: yes | no
❑ Command add clock for clock-gating used: yes | no
■ Incomplete verification:
❑ All primary outputs are mapped: yes | no
❑ All mapped points added as compare points: yes | no
❑ All compare points compared: yes | no
❑ User added black box: yes | no
❑ Black box mapped with different module name: yes | no
❑ Command add ignore outputs used: yes | no
■ Modification to design:
❑ Change gate type: yes | no
❑ Change wire: yes | no
❑ Primary inputs added: yes | no
■ Conformal Constraint Designer clock domain crossing checks recommended:
❑ Multiple clocks in the design: yes | no
■ Design ambiguity:
❑ Duplicate module definition: yes | no
Tcl Command
report_verification
Parameters
-Summary Prints all items for each category and the violated items are
marked with an asterisk (*).
-Verbose Prints out each category and the count of violations.
Example
This specifies that there are some constraints that are always violated, and this may lead to
incomplete verification. For example, in the following VHDL code, the range constraint is
always violated.
signal a: std_logic_vector(1 downto 0);
signal a_num: integer range 4 to 9;
a_num <= conv_integer(a);
Related Command
COMPARE
Provides a report regarding verification information. Currently, this command only supports
the reporting of information described in the web interface article titled Conformal Automatic
Reporting in the LEC Web Interface.
This command can be used only when SET VERIFICATION INFORMATION is enabled.
Tcl Command
report_verification_information
Parameters
-ADVANCED_REPORT Provides a text report of the information available from the web
interface. For example, specifying USAge would display the
data shown in the USAge tab of the web interface.
-SECOND_RUN_STATUS Provides a table to report the status of each second run
information category in verification information, include the
existence in previous run, existence in current run, permission
to apply and permission to record.
Related Command
SET VERIFICATION INFORMATION
RESET
RESET
(Setup / LEC Mode)
Resets the system to the initial state. All existing designs and libraries are deleted, and all
previously issued commands are cancelled.
Tcl Command
reset
Related Commands
RESET HIER_COMPARE RESULT
EXIT
Resets the abstraction conditions that you set using the SET ABSTRACT MODEL command.
Tcl Command
reset_abstract_model
Parameters
Related Commands
ABSTRACT LOGIC
Resets the results of the hierarchical comparison. It is useful when you do multiple
hierarchical compare runs and you wish to display the results of each hierarchical compare
separately.
Tcl Command
reset_hier_compare_result
Related Commands
RUN HIER_COMPARE
RESET
RESOLVE
RESolve
<module_name>
[-All]
[-Golden | -Revised]
(Setup Mode)
Tcl Command
resolve
Parameters
Related Commands
ABSTRACT LOGIC
ADD CLOCK
DELETE CLOCK
READ PATTERN
REPORT CLOCK
UNIQUIFY
RESTORE SESSION
REStore SEssion
<session_name>
(Setup / LEC Mode)
Restores a session you previously initiated and saved using the SAVE SESSION command.
Before entering this command, Conformal must be in its initial state. Therefore, you must
either use the RESET command, or exit Conformal and restart it.
Important
You must run this restarted session on the same platform, same Conformal version,
and same license configuration for which it was saved.
Tcl Command
restore_session
Parameters
Related Commands
INFO SESSION
RESET
SAVE SESSION
RUN HIER_COMPARE
RUN HIer_compare
<dofile_name>
[-ANALYZE_BOUNDARY_conditions | -NOANALYZE_BOUNDARY_conditions]
[-BREAK_ABORT]
[-BREAK_NONEQ]
[-CHECK_NONEQ]
[-COMPARE_String <string>]
[-DYNamic_hierarchy | -NODYNamic_hierarchy]
[-NOANALYZE_abort | -ANALYZE_abort]
[-NODYNAMIC_MODULEs <golden_module> <revised_module> ...]
[-NOREStart | -REStart]
[-RETIMED_modules [-TOP | -NOTOP]]
[-ROOT_BLACKBOX]
[-ROOT_module <golden_module> <revised_module>]
[-COMPARE_TOP_MODULE]
[-VERBOSE]
(Setup Mode)
Runs dynamic hierarchical comparison. This command on completion produces one of the
following three statuses:
■ Equivalent: all the compared modules are equivalent.
■ Nonequivalent: at least one of the compared module is nonequivalent.
■ Inconclusive: indicates one of the following conditions:
❑ at least one of the compared module has abort points
❑ at least one module is not-compared (for example, due to running the ADD MODULE
ATTRIBUTE -compare_effort none command)
❑ at least one module has incomplete compare result (for example, due to extra
primary outputs)
Note: When the status is Inconclusive the number of abort modules, not-compared
modules, or modules that have incomplete compare result are reported.
During each module comparison, the COMPARE command is appended with the "-
abort_stop 1" option to provide quick turnaround time.
For more information, see Dynamic Hierarchical Comparison in the Conformal Equivalence
Checking User Guide.
Tcl Command
run_hier_compare
Parameters
<dofile_name> Specifies the name of the hierarchical dofile that was generated
with the WRITE HIER_COMPARE DOFILE command.
Note: Manually editing or modifying this hierarchical dofile prior
to running the RUN HIER_COMPARE command might lead to
unexpected results. If you want to edit or modify the hierarchical
dofile, use the static hierarchical comparison (dofile
hier.do).
-ANALYZE_BOUNDARY_conditions
Reduces the number of flattened modules by resolving
boundary constraints. This is the default.
-NOANALYZE_BOUNDARY_conditions
Do not perform resolution on boundary constraints.
-BREAK_ABORT The comparison stops when it encounters an abort module. To
continue comparing from the next module in the hierarchy, run
the RUN HIER_COMPARE command.
-BREAK_NONEQ The comparison stops when it encounters a nonequivalent
module. To continue comparing from the next module in the
hierarchy, use the RUN HIER_COMPARE command.
Note: This command option is only supported when using the -
NODYNamic_hierarchy option.
-CHECK_NONEQ Identify NEQ modules before running the ANALYZE DATAPATH
command and skip datapath analysis for these modules.
Examples
■ The following command uses the hier.do dofile for hierarchical comparison:
run hier_compare hier.do
If the previous comparison run of the hier.do dofile resulted in three aborted modules,
you can run a second comparison using the following command:
run hier_compare hier.do -analyze_abort
This command only operates on aborted modules from the previous run, and
automatically runs the ANALYZE ABORT -compare command after the default
COMPARE command.
■ The following command uses m4 as the root module for both the Golden and Revised
designs, deleting the previous comparison results:
run hier_compare hrcmod.do -root_module m4 m4 -restart
■ In the following command, the compare command in the hierarchical dofile is replaced
with two commands during each module comparison, set compare effort low and
compare -abort_stop 1 -noneq_stop 1:
run hier_compare hier.do -compare_string \
"set compare effort low; compare -abort_stop 1 -noneq_stop 1"
Related Commands
ANALYZE ABORT
COMPARE
Note: This is a Conformal Low Power command and a native 1801 feature.
Performs 1801 library checkers. This command can be run without reading the design.
Tcl Command
run_library_check
Parameters
Example
The following performs 1801_LIB checkers at all read-in library files. Not require a design
read-in.
TCL_SETUP > set_lowpower_option -native_1801
TCL_SETUP > read_library -liberty -lp <liberty files>
TCL_SETUP > run_library_check
The following performs 1801_LIB checkers at the library cells used at the design.
TCL_SETUP > set_lowpower_option -native_1801
TCL_SETUP > read_library -liberty -lp <liberty files>
TCL_SETUP > read_design <design>
TCL_SETUP > run_library_check -used
Runs equivalency checking comparison between the Golden and Revised designs on the
added compared points using parallel processing. During the comparison, the Conformal
software displays following information:
■ A progress percentile number that shows the completion rate
■ A running count that shows the number of key points that have been compared along
with the total number of nonequivalent key points
Alternatively, you can run parallel comparison using multithreads; this method is easier to use
and eliminates the complexity of setting up the parallel processing environment. Instead of
RUN PARALLEL COMPARE, use compare -threads or set parallel option -
threads.
Tcl Command
run_parallel_compare
Parameters
-NONEQ_Stop <integer>
Stops the comparison after finding the specified number of
nonequivalent points.
-SUBMIT_OPTIONs Specifies the options which will replace the keyword
<submit_options> in the submit command line (see the SET
PARALLEL OPTION -SUBMIT_COMMAND_LINE command).
-TEST Launches qualification run to test if the environment is suitable
for parallel processing.
Examples
■ The following command tests if the environment is suitable for parallel processing:
run parallel compare -test
■ The following command will start the equivalency comparison using parallel processing
with the parameters specified by the previously run SET PARALLEL OPTION command.:
run parallel compare
■ The following commands run the first parallel job in queue q1, and the second parallel
run in queue q2.
run parallel compare -submit_options "-q q1"
run parallel compare -submit_options "-q q2"
Related Commands
COMPARE
RUN PARTITION_COMPARE
RUN PARTition_compare
[-Keypoint <identifier...>]
[-Number <number>]
[-THREADS <integer>[,<integer>]]
[-VERBOSE]
(LEC Mode)
Runs comparisons with functional partitioning. You can specify partitioned key points in the
Golden design and the number of key points for a partition. If no key points are specified, this
command will automatically choose appropriate key points for the partition.
Note: You do not need to switch to Setup mode to flatten the netlist in each partition iteration.
With the constants assigned on the selected key points, comparison can become easier in
each partition iteration.
For example, when abort points are encountered in comparison, you can run this command
to do functional partitioning for the abort points.
-Keypoint <identifier...>
Specifies the partition key point in the Golden design. The key
point can be specified by gate instance pathname or gate ID. If
no key points are specified, this command will automatically
choose appropriate key points for the partition.
-Number <number> Specifies the number of key points for a partition. The maximum
number of compare iterations is the base-2 exponent of the
partitioned key point number. The default partitioned key point
number is 8.
-THREADS <integer>[, <integer>]
Specifies the minimum and maximum number of threads that
can be executed at the same time. If only one number entered,
this specifies both the minimum and maximum number of
threads. For example, '-threads 2' specifies two threads; '-
threads 2,4' specifies a minimum of two threads, and a
maximum of four threads.
-VERBOSE Provides additional information in the functional partition.
Related Commands
COMPARE
SAVE DOFILE
SAVe DOfile
<filename>
[-Replace]
(Setup / LEC Mode)
Saves the commands entered during the current session to a file. Use the saved dofile later
as a batch file to repeat the Conformal session.
When running a Conformal session from a dofile, this command does not save individual
commands included in a separate dofile (that is, Conformal saves the manually entered
commands, which can include a dofile <filename> command).
Note: If the filename you specify already exists, you must use either the -replace or
-append option.
Tcl Command
save_dofile
Parameters
Related Commands
DOFILE
Saves the hierarchical comparison results of the module comparison. If the WRITE
HIER_COMPARE DOFILE command is used, this command is placed after every module
compared.
After the hierarchical comparison of all modules is complete, use the REPORT
HIER_COMPARE RESULT command to display the results of the hierarchical comparison.
Related Commands
REPORT HIER_COMPARE RESULT
RUN HIER_COMPARE
SAVE SESSION
SAVe SEssion
<session_name>
[-REPlace]
(Setup / LEC Mode)
Saves your session up to a current point and outputs the session file.
To restore the session later using the RESTORE SESSION command. You can use this
command if priorities demand that another session preempt your session.
Important
When you use the RESTORE SESSION command, you must run the restarted
session on the same platform and same Conformal version.
For more, refer to Saving and Restoring a Session in the Conformal Equivalence Checking
User Guide.
NOTE: SAVE SESSION command only saves design data and will be obsolete in the future.
Use the new CHECKPOINT command to save complete process data.
Tcl Command
save_session
Parameters
Related Command
INFO SESSION
RESTORE SESSION
SEARCH
SEArch
[-USage] <string1> [<string2>] ...
(Setup / LEC Mode)
Searches the database of commands and parameters, and displays those commands that
match all of the specified strings. Strings can be specified in any order; however, every
specified string must match.
Tcl Command
search
Parameters
-USage Displays the commands that have parameters that match the
search string. This outputs the entire command syntax for each
command.
<string1> Displays commands that match the specified string.
<string2> ... Displays commands that match additional specified strings.
Related Command
HELP
Specifies certain conditions for abstracting transistor logic. The design must be read in (READ
DESIGN command) before using this command.
Refer to the Conformal Equivalence Checking User Guide for additional information about
using this command in the Conformal GXL flow.
Tcl Command
set_abstract_model
Parameters
-ALL Abstracts transistor logic from all modules within the given
defaults. This option is the default.
-NOBUF_AMP Do not handle buffered-type sense amplifiers, level
shifters, pre-charge, and equalization. This is the
default.
-NOMEM_BL_EQualizer
Do not handle bit-line pre-charge, and equalization. This
is the default.
-MEM_BL_EQualizer Handles circuits that include bit-line pre-charge, and
equalization.
-NOMULTICLOCKPRECHARGE
Do not propagate clocks through logic gates which have
more than one clock input. This is the default.
-MULTICLOCKPRECHARGE
Propagates clocks through logic gates which have more
than one clock input.
-NOPRE_CHARGE_KEEP_Clock
In domino logic, does not regard pre-charge clocks as part
of the logic function. This is the default.
-PRE_CHARGE_KEEP_Clock
For domino logic, regards pre-charge clocks as part of the
logic function.
Examples
Sample Dofile:
read design test.v -golden
set abstract model -keeper2pullup -weakpullup -golden
report abstract model -golden
abstract logic
Related Commands
ABSTRACT LOGIC
ADD CLOCK
Sets advanced methodology and related options for abstracting transistor logic.
Tcl Command
set_abstract_option
Parameters
Examples
The following example demonstrates the usage of a Verilog constraint file for the Circuit
Analysis Based Logic Abstraction method.
set abstract option -enable_cell_compare -constraint_file constraint.v
module top(a,b,o);
input a,b;
output o;
$constraint(a&b);
endmodule
Related Commands
ABSTRACT LOGIC
VALIDATE LIBRARY
When you use the -AUTO option, it automatically determines the best place to run the
ANALYZE SETUP command. The ANALYZE SETUP command analyzes the netlists and sets
up the flattened design for accurate comparison. This helps avoid false nonequivalences.
This command can also analyze and remodel the following commonly-encountered setup
issues: sequential constanting, sequential merging, loop cutting, clock gating, and phase
mapping.
In addition, the Conformal software automatically runs the ANALYZE ABORT command
whenever the comparison returns abort points but no nonequivalent points.
Tcl Command
set_analyze_option
Parameters
-ANALYZE_RENAMING_RULE
Enables renaming rule analysis during the flattening process.
This applies only when balanced modeling is enabled.
-CUT Enables cut point analysis during automatic setup. This is
the default.
-NOCUT Disables cut point analysis during automatic setup.
-DELETE_UNREACHable Deletes functionally mapped unreachables during auto setup
if they are non-equivalent. This is the default.
-NODELETE_UNREACHable
Do not delete functionally mapped unreachables during auto
setup.
-EFFORT <MEDIUM | HIGH | ULTRA>
Specifies the effort level for automatic setup and abort point
analysis. The higher the effort level, the better the analysis
(however, it can increase analysis time as well).
Medium is the default when using the -auto option.
-EFFORT_ANALYZE_ABORT <MEDIUM | HIGH>
Specifies the effort level for the ANALYZE ABORT command.
MEDIUM: Default effort level.
HIGH: Invokes functional partitioning for resource sharing in
datapath analysis. It also invokes word-level datapath
analysis for non-threaded 'ANALYZE ABORT'.
-EFFORT_ANALYZE_SETUP <MEDIUM | HIGH | ULTRA>
Sets the auto analyze abort snapshot for the RTL annotation
OFF. This is the default
-ANALYZE_ABORT_SNAPSHOT
Sets the auto analyze abort snapshot for the RTL annotation
ON. Use SNAPSHOT_DIRectory to specify the snapshot
directory.
-NOAUTO Disables automatic analysis. This is the default.
-AUTO Enables automatic analysis.
-ANALYZE_ABORT Enables automatic abort point analysis. When -auto is used
with this option, the tool enables the ANALYZE ABORT -
compare command when it encounters an abort during
compare.
This is the default when running this command with the
-auto option.
-NOANALYZE_ABORT Disables automatic abort point analysis.
-ANALYZE_SETUP Enables automatic setup analysis. This is the default when
running this command with the -auto option.
-NOANALYZE_SETUP Disables automatic setup analysis.
-NOLATCH_NO_HOLDING Automatic analysis will not model latches that do not have
holding functions. This is the default.
-LATCH_NO_HOLDING When enabled, automatic analysis models latches that do not
have holding functions.
-NOMODIFY_MAP Disable the modification of functional mapping after
remodeling in automatic setup. This is the default.
-MODIFY_MAP Enable the modification of functional mapping after
remodeling in automatic setup.
-NOPHASE_MAPPING Disables phase adjustment for DFF/D-LATCH mapping
during automatic analysis. This is the default.
Examples
Mapping file format:
The following illustrates the sample format of a mapping file (designated using this
command's -mapping_file option):
map.f:
add mapped points dec_data[7] dec_data[7] \
-type PI PI -module err_detect err_detect
add mapped points dec_data[6] dec_data[6]
-type PI PI -module err_detect err_detect
add mapped points dec_data[5] dec_data[5]
-type PI PI -module err_detect err_detect
add mapped points dec_data[4]
dec_data[4] -type PI PI -module err_detect err_detect
In the following example, SET ANALYZE OPTION -auto enables automatic abort point
analysis.
set analyze option -auto
set system mode lec
add compare point -all
compare
If the tool encounters an abort after compare, it automatically enables the ANALYZE ABORT
-compare command to resolve abort key points.
During the run, the tool displays something similar to the following:
========================================================
Compared points PO DFF Total
--------------------------------------------------------
Equivalent 59 224 283
--------------------------------------------------------
Abort 0 2 2
========================================================
// Command: analyze abort -compare
========================================================
Compared points PO DFF Total
--------------------------------------------------------
Equivalent 59 226 285
========================================================
Usage example:
For example, the following illustrates the usage of this command with the -mapping_file
option in a flattened flow:
set analyze option -auto -mapping_file map.f
set system mode lec
add compare point -all
compare
The following illustrates the usage of this command with the -mapping_file option in a
hierarchical flow:
set analyze option -auto -mapping_file map.f
write hier dofile hier.do ...
run hier hier.do
...
Related Command
ANALYZE ABORT
ANALYZE SETUP
SET_ATTR INPUT_PRAGMA_KEYWORD
SET_ATtr INPUT_PRAGMA_Keyword
<string>
(Setup Mode)
Specifies a keyword that the Conformal software must consider as an input pragma when it
encounters it as the first word in a Verilog or VHDL source comment.
A pragma is a comment in the Verilog or VHDL source and is set off from ordinary comments
by the pragma keyword. The pragma keyword is the first word listed in a pragma, and it
notifies the Conformal software that the remainder of the comment is a command and not a
comment. Changing this keyword allows you to set up compatibility with other tools.
Tcl Command
set_attr_input_pragma_keyword
Parameters
Examples
Sample Dofile:
set_attr input_pragma_keyword rtl
set synthesis_off_command turn_off
set synthesis_on_command turn_on
After running these three commands, the Conformal and VHDL parsers will recognize the
pragmas in the VHDL and Verilog Source files.
In a VHDL file, the code between -- rtl turn_off and -- rtl turn_on will not be
translated.
In a Verilog file, the code between // rtl turn_off and // rtl turn_on will not be
translated.
Related Commands
SET SYNTHESIS_OFF_COMMAND
SET SYNTHESIS_ON_COMMAND
Specifies whether names you enter are case sensitive. The system default is no case
sensitivity for both the Golden and Revised designs.
Execute this command before READ LIBRARY and READ DESIGN. Use the REPORT
ENVIRONMENT command to display the case sensitivity setting.
Tcl Command
set_case_sensitivity
Parameters
Related Command
REPORT ENVIRONMENT
Note: Enabling/disabling source code tracing functions must be done before reading in the
design.
When source code tracing is enabled, the following advanced design browsing capabilities
are available in the Source Code Manager:
1. Macro expansion: Macro expansion results are displayed in an information window when
you click on a macro variable.
2. Parameter value annotation: Parameter values are annotated in an information window
when you click on a parameter variable.
3. Symbol definition lookup: You can view the definition of a symbol by clicking on it and
choosing Definition from the pop-up menu.
4. Code block folding/unfolding: Code blocks (such as modules, functions, tasks, always
blocks, case switches, if-else, and loops) can be folded and unfolded for better readability.
To fold a code block, right click on the first line and select Fold from the pop-up menu.
This folds the whole code block into one line.
To unfold a code block, right click on the block, and select Unfold in the pop-up menu.
The code block is restored back to its original status.
For more information on these capabilities, refer to the 14.1 web interface article titled,
Conformal Verilog Design Tracing.
Tcl Command
set_code_trace
Parameters
OFf Turn off the source code tracing functions in the Source Code Manager.
This is the default.
ON Turn on the source code tracing functions in the Source Code Manager.
AUto Automatically enables source code tracing functions in the Source Code
Manager for RTL designs; automatically disables these functions for
large scale gate-level netlists.
Controls whether the tool echos (or repeats on the screen) the command typed.
Tcl Command
set_command_echo
Parameters
Example
For example, we save the following in the dofile and call it mydofile1.do:
read design ./ccr871626/test.v -verilog -root sub0
set command echo off
read design ./ccr871626/test.v -verilog -root sub0 -replace
set command echo on
read design ./ccr871626/test.v -verilog -root sub0 -replace
When you execute the dofile, the tool will only echo two of the READ DESIGN commands. It
does not echo the second READ DESIGN command, because it was typed after the SET
COMMAND ECHO OFF command was set:
// Command: dofile r
// Command: read design ./ccr871626/test.v -verilog -root sub0
// Parsing file ./ccr871626/test.v ...
// design root module is set to 'sub0'
// Note: Read VERILOG design successfully
// Read design summary: Error: 0, Warning: 10, Note: 0
// Note: Use 'report rule check -category library_design -verbose' for details.
// Command: set command echo off
// Warning: Existing design has been deleted
// Parsing file ./ccr871626/test.v ...
// design root module is set to 'sub0'
// Note: Read VERILOG design successfully
// Read design summary: Error: 0, Warning: 10, Note: 0
// Note: Use 'report rule check -category library_design -verbose' for details.
// Command: read design ./ccr871626/test.v -verilog -root sub0 -replace
// Warning: Existing design has been deleted
// Parsing file ./ccr871626/test.v ...
// design root module is set to 'sub0'
// Note: Read VERILOG design successfully
// Read design summary: Error: 0, Warning: 10, Note: 0
// Note: Use 'report rule check -category library_design -verbose' for details.
Tcl Command
set_command_profile
Parameters
Related Commands
REPORT COMMAND PROFILE
Specifies the amount of effort equivalency checking applies to the key points comparison. If
you know your designs have many complex key points, increase the effort level. However,
when you raise the effort level, you also increase the amount of time involved in checking.
Hence, you increase the total CPU time.
Use the REPORT ENVIRONMENT command to display the compare effort setting. The
system default is set to low compare effort.
Tcl Command
set_compare_effort
Parameters
Low Applies low effort to equivalency checking for each gate. This
is the default.
Medium Applies greater effort to equivalency checking for each gate.
High Applies the maximum effort to equivalency checking for each
gate.
Auto Starts with low effort and automatically increases the compare
effort if abort points are present in the design.
LIght Applies minimal effort to equivalency checking for each gate.
COMPlete Performs equivalency checking for each gate until the
comparison results in an EQ or NONEQ result. With this option,
the tool never returns an abort (in other words, if EQ or noneq is
not returned, the compare will go on indefinitely).
Related Commands
COMPARE
REPORT ENVIRONMENT
Tcl Command
set_compare_options
Parameters
-REPORT_SINGLE_LINE_SUMMARY
Prints a single line summary of the compare results.
-NOSINGLE Compares key points in groups. This is the default.
-SINGLE Compares each key point as a single point.
-NOVERBOSE Do not display the detailed compare information, such as the
logic duplication in multithreaded comparison. This is the
default.
-VERBOSE Display detailed compare information, such as the logic
duplication in multithreaded comparison.
-THREADS <integer>[,<integer>]
Specifies the number of compare threads for only the
COMPARE command. For example, '-threads 2' specifies
two threads; '-thread 2,4' specifies a minimum of two
threads, and a maximum of four threads.
The set parallel option -threads # command
specifies the number of threads for both the COMPARE and
the ANALYZE ABORT commands. If you specify both the SET
COMPARE OPTIONS -threads and the SET PARALLEL
OPTION -threads commands, the SET COMPARE
OPTIONS -thread command supersedes the setting of the
SET PARALLEL OPTION -threads command, but for just
the number of threads in the COMPARE command. See
example below.
-TURBO Fine-grained partition for compare parallelization to utilize
CPU more efficiently.
-NOTURBO Specifies not using parallel turbo threads in compare
command. This is the default.
-VERIFY_Disabled_ports
Compares data cones even if their clocks are disabled. By
default, a data cone will not be compared if its corresponding
clock port is tied to a constant (for DFFs) or to zero (for
latches).
Note: You should use this command option before running
the first COMPARE command. If you use this after running
COMPARE, this option has no effect.
Examples
LEC uses two threads for the COMPARE command and four threads for the ANALYZE ABORT
command.
set parallel option -threads 4
set compare options -threads 2
Related Command
COMPARE
Specifies the time limit for the LEC session. The system default is 525,600 minutes. Set the
time limit for minutes, hours, or days.
Use the REPORT ENVIRONMENT command to display the setting for the CPU time limit.
Note: When the Conformal software reaches the specified CPU limit, it stops all processing
and exits.
Tcl Command
set_cpu_limit
Parameters
Examples
■ The following commands show an example of using the SET CPU LIMIT command with
and without the -WALLTIME option.
The time is 11:00 am and you start two Conformal sessions on the same machine,
executing the same dofile, that will run more than 20 minutes. You set the time limit for
session 1 in real clock time with the following command:
set cpu limit 10 -minutes -walltime
You set the time for session 2 at the same limit but without using the real clock time with
the following command:
set cpu limit 10 -minutes.
At 11:10, session 1 will terminate because the real clock time has elapsed 10 minutes.
However, session 2 might not terminate because the real time it consumed during this
10 minutes is less than 10 minutes if some of the time is consumed by other processes
running on the machine.
■ The following command specifies that before the software exits after reaching 1 minute
CPU time limit, it will run the USAGE command.
set cpu limit 1 -minute -command usage
Related Command
REPORT ENVIRONMENT
Specifies whether Conformal automatically analyzes the datapath on switching from Setup to
LEC mode and whether to apply operator merging. The results of the analysis enable
Conformal XL to automatically resolve multipliers, operator merging, and resource sharing
problems. Note that portions of this command are global settings (specifically, anything not
under -auto) and can override ANALYZE DATAPATH default settings (see example section).
Note: You cannot run datapath analysis without first mapping the Revised design key points
to the Golden design key points.
Tcl Command
set_datapath_option
Parameters
Examples
■ The following command applies module-based datapath analysis followed by the
operator-level datapath analysis when switching from Setup to LEC mode:
set datapath option -auto -module -verbose
set system mode lec
■ The following command applies operator-level datapath analysis when switching from
Setup to LEC mode:
set datapath option -auto
set system mode lec
■ Portions of this command are global settings (specifically, anything not under -auto) and
can override ANALYZE DATAPATH default settings. For example, if you set SET
DATAPATH OPTION -wordlevel, Conformal performs word level analysis despite
ANALYZE DATAPATH's default setting of bit level analysis. In this case, to perform bit-
level analysis with ANALYZE DATAPATH, you need to manually set ANALYZE DATAPATH
-nowordlevel.
set datapath option -wordlevel
analyze datapath -nowordlevel
Related Commands
ANALYZE DATAPATH
ANALYZE MODULE
SET DIRECTIVE
SET DIrective
<ON | OFf>
[ [synthesis | <vendor_name>] <directives>]
[-file <filename*>]
(Setup Mode)
Specifies whether to enable or disable the effects of the specified synthesis directives when
reading in a Verilog or VHDL file. If you enter this command and do not specify any directives,
this command enables or disables all of the directive effects. The system default enables
all directives. Thus, if you want Conformal to enable all directives, no action is necessary.
For each disabled directive used in the HDL source code, Conformal responds as follows:
■ If the directive is supported but disabled, Conformal returns a message stating the
directive is disabled.
■ If the directive is unsupported and disabled, Conformal returns a message stating that
the directive is unsupported.
See Conformal Directive Examples in the Conformal Equivalence Checking User Guide
for short descriptions and examples of supported Conformal directives.
Tcl Command
set_directive
Parameters
Examples
■ When you employ the SET DIRECTIVE command and you do not specify a directive,
the command applies to all directives. In the following example, the objective is to enable
only the parallel_case directive. To do so, first disable all directives, then enable the
specified directive (parallel_case).
//disable all directives
set directive off
//enable parallel_case
set directive on parallel_case
Related Commands
READ DESIGN
READ LIBRARY
Specifies how Conformal handles the dofile when an error message occurs.
■ If the dofile abort handling is set to On, the dofile terminates when an error message
occurs. This is the default.
■ If the dofile abort handling is set to Off, the dofile continues even if an error message
occurs.
■ If the dofile abort handling is set to Exit, the session exits when an error message occurs.
Tcl Command
set_dofile_abort
Parameters
Related Commands
BREAK
CONTINUE
DOFILE
SET DW DEFINITION
SET DW Definition
<-USER_FIRST [-BBOX] | -USER_ONLY | -BUILTIN_only | -DW_MULt_div>
(Setup Mode)
Specifies the DesignWare (DW*) modules' definition that the Conformal software will use. By
default, the software specifies using the user-defined DW* modules first.
If you are using the built-in directory (where the DW* files are located), you can set the path
with the following command:
setenv DW_DEFINE <path_name>
Tcl Command
set_dw_definition
Parameters
-BUILTIN_only Use only built-in DW* modules and skip user-defined DW*
modules.
-DW_MULt_div Use only user-defined DW* modules, except DW02_MULT
and DW_DIV modules.
Example
The following shows an example of the RTL code in a file absval.v.
module sample( A, ABSVAL );
input [7 : 0] A;
output [7 : 0] ABSVAL;
DW01_absval #(width) U1 ( .A(A), .ABSVAL(ABSVAL) ); endmodule
The DW01_absval.v file is automatically read in from the built-in directory because there is
no definition provided.
This command allows users to specify equivalent supplies by giving a list of supply source
points from the golden design and the revised design, and report the specified equivalent
supplies. Each of the command issued will be given an ID number such that it can be
identified to be reported in a list or deleted anytime. Note that the supply list from a design
must be equivalent in such design through either physical connection, virtual connection, or
1801 power intent set equivalent command.
Tcl Command
set_equivalent_supply_sources
Parameters
-Golden <supply source Specifies a list of the supply sources from the
list>* Golden design
-Revised <supply source Specifies a list of the supply sources from the
list>* Revised design
-Delete <id> Deletes the equivalent supplies with the specified
id
-List Reports a list of equivalent supplies that are
specified by the command
Examples
Specify two different switch chain output supply sources, x1/VSW and x2/VSW, are
equivalent to a revised supply source, VSW.
TCL_SETUP> set_equivalent_supply_sources -golden {x1/VSW x2/VSW2} -revised {VSW}
To report the specified equivalent, use -list, an ID number of each specified equivalent is
displayed:
TCL_SETUP> set_equivalent_supply_sources -list
1:
(G): x1/VSW x2/VSW
(R): VSW
Related Commands
COMPARE POWER GRID
Controls and displays the exit code for the Conformal session. This command is useful when
running a complex flow, such as hierarchical comparison and iterative comparison.
Tcl Command
set_exit_code
Parameters
-CLEAR Clears the exit code to only reflect most current running status.
-VERBOSE Displays a table listing the status codes.
-INTERNAL_ERROR Sets the internal error bit.
-NOINTERNAL_ERROR Clears the internal error bit.
-COMMAND_ERROR Sets the command error bit.
-NOCOMMAND_ERROR Clears the command error bit.
Examples
■ The following command displays current exit code:
set exit code
[-PRESERVE_SEQ_CONSTANT | -NOPRESERVE_SEQ_CONSTANT]
[-SEQ_CONSTANT_ENDPOINT]
[-SEQ_CONSTANT_FEEDBACK | -NOSEQ_CONSTANT_FEEDBACK]
[-SEQ_CONSTANT_X_TO <NONE | 0 | 1>]
[-Z_CONVERSION <0 | 1| DC>]
[-BOTH | -GOLDEN | -REVISED]
[-VERBOSE]
(Setup Mode)
Specifies certain conditions for the flattened model. Refer to the arguments table for a
complete list of options and their effects.
Use the REPORT ENVIRONMENT command to display the settings for the flattened model, or
you can run this command without any options (in either Setup or LEC mode) to report a
complete list of flattened modeling options.
Tcl Command
set_flatten_model
Parameters
Examples
Sequential Merge
Given the following example, if you used the -SEQ_MERGE option, LEC merges common
groups of sequential elements that are in the clock and set/reset cones of other sequential
elements and prints out:
// (F19) Merged 1 DFF/DLAT(s) in clock cones due to functional equivalence
// (F19.1) Merged 1 DFF/DLAT(s) in set/reset cones due to functional equivalence
While with -ALL_SEQ_MERGE merges all the sequential elements that are functionally
equivalent and prints out:
// (F20) Merged 3 DFF/DLAT(s) due to functional equivalence
Golden:
module top (input A, input rst, input clk, input clk2, output B, output C);
reg clk_reg0, clk_reg1;
reg rst_reg0, rst_reg1;
reg a_reg, b_reg;
assign B = a_reg;
assign C = b_reg;
endmodule
Revised:
module top (input A, input rst, input clk, input clk2, output B, output C);
reg clk_reg0;
reg rst_reg0;
reg a_reg;
endmodule
Related Commands
ANALYZE HIER_COMPARE
REMODEL
REPORT ENVIRONMENT
REPORT MESSAGES
Tcl Command
set_fpga_technology
Parameters
Specifies the detail level of gate reports in the Conformal gate information display. Gate report
features include the following:
■ Returns information at the design or primitive level
■ Displays the dynamic constraints
■ Displays the fanin cone of the zero/one gates
By default, this command reports gate information at the primitive level, displays the dynamic
constraints, and does not display the fanin cone of the zero or one gates.
Use the REPORT ENVIRONMENT command to display the gate report level settings.
Note: If the gate report is set to Design, you must use the SET FLATTEN MODEL command
with the -pin_keep option in the Setup system mode. The gate information is reported in
the LEC system mode.
Tcl Command
set_gate_report
Parameters
-NOUSE_LIBRARY_PINNAME Do not use library pin name in gate report. This is the
default.
-USE_LIBRARY_PINNAME Uses library pin name in gate report if the gate comes
from library.
-PRImitive Displays the gate report information at the primitive level.
This is the default.
-DESign Displays the gate report information at the design level.
Related Commands
REPORT ENVIRONMENT
REPORT GATE
SET GUI
SET GUi
[ON [-MAPping]
| OFf]
(Setup / LEC Mode)
Switches Conformal to the GUI mode from the non-GUI mode or to the non-GUI mode from
the GUI mode.
Tcl Command
set_gui
Parameters
This command sets global attributes that control the behavior of subsequent READ LIBRARY,
READ DESIGN, and ELABORATE DESIGN commands. Libraries and designs that have been
successfully read in and elaborated previously will not be affected by newly issued SET HDL
OPTIONS commands.
Tip: Use SET HDL OPTIONS without any options to display the current settings for SET HDL
OPTIONS.
Tcl Command
set_hdl_options
Parameters
-DEFINE <MACRO NAME> Helps the user define a macro which can work in each
READ DESIGN. For example:
Users can use SET HDL OPTION -DEFINE AAA
instead of
read design -sv -define AAA 1.sv
read design -sv -define AAA 2.sv
read design -sv -define AAA 3.sv
On the other hand, command RESET will clear these
defined macros, and command REPORT HDL OPTION
will print the defined macros.
-DFF_ASYNC_HOLD Controls how an asynchronous conditional self-
assignment is implemented for an RTL design.
By default, this option is OFF and asynchronous pins
are used to implement the gate-level design.
In some cases, a synthesizer may use asynchronous
pins for implementation instead and cause RTL and
gate-level designs non-equivalent. Setting this option
ON may help equivalence checking for such cases. This
setting applies to the entire RTL parsing.
-ERROR_OUT_POSITIONAL_ASSOCIATION_ON_LIBERTY_CELL <OFF | ON>
OFF: This is the default.
ON: When specified, the tool checks whether the design
includes one or more module instances that uses port
positional association of Liberty cells (rule check
HRC3.8a).
-FIX_PIN_DIRECTION <OFF | This changes the pin direction to the bi-directional
ON> (inout) type when an output port of a module is not
driven by any logic inside the module, or when a input
port of a module is driven by some logic inside the
module.
-FULLPATH <OFF | ON>
Records the file name's absolute path name; when files
are read in, the file source is stored in its absolute path
(opposed to a relative path or a path added by the ADD
SEARCH PATH command). Default is OFF.33
-FV_TRIMINDex <OFF | ON>
-PARSE_FILE_CMD <command>
Runs a shell command or executable file after printing
out the "Parsing file ..." message and before
Conformal parses the file during the READ LIBRARY or
READ DESIGN commands.
Each current parsing file name will be stored in an
environment variable CFM_READ_FILE before invoking
the command.
-PORTMISmatch <UNconnect | EXTend>
When the port connection widths between the module
and an instantiation do not match, this option controls
how the tool models the extra bits.
UNconnect leaves the extra bits unconnected. This is
the default.
EXTend applies zero- or sign-extending to the value,
depending on the expression signedness. See
Examples section.
-PRIMITIVE_INPUT_Conversion <LSB | LOGIC>
Specifies how the software's Verilog parser handles
multiple-bit expressions.
LSB takes the least significant bit from the multiple-bit
vector expression. This is the default for the Verilog
parser.
LOGIC treats the entire multiple-bit expression as a logic
true/false value. For example,
wire [0:5] net0;
or I00 (out, net0[0:5]);
For example:
set hdl option -synthesis_executable \
/grid/DC_INSTALL_DIR/latest/bin/dc_shell
-t
-UDP_IGN_VDD <module_name> <vdd_pin_name>
-V_TO_VD <OFF | ON> OFF: Logic compiled with -v option will be categorized
into the library space and logic compiled with -vd option
will be categorized into the design space. This is the
default.
ON: Logic compiled with -v and -vd options will be
categorized into the design space..
-VARSIZE_limit <integer_value>
Specifies the maximum size for a variable. By default,
the maximum variable size is 4194304.
For example, to increase the maximum variable size:
set hdl option -VARSIZE_limit 134217728
-VERILOG_INCLUDE_DIR <string>
Examples
The following examples use the Verilog language to show how to control index out of bound
handling. You can use similar VHDL command options to control the interpretations for the
VHDL language designs.
RTL-1
wire a;
reg [2:0] index;
reg [2:0] mem;
always @(*) mem[index] = a;
If index is greater than 2, it is out of the index range. Some synthesis tools might intentionally
interpret the RTL the same as with the following RTL-2 example:
RTL-2
wire a;
reg[2:0] index;
reg[2:0] mem;
always @(*) mem[index[1:0]] = a;
then
■ index=0 : mem[0] is assigned to the value of a
■ index=1 : mem[1] is assigned to the value of a
■ index=2 : mem[2] is assigned to the value of a
■ index=3,4,5,6,7 : mem[0], mem[1], and mem[2]are assigned to the value of 1'bx.
This interpretation assumes that out-of-bound writing will not happen, and consequently
ignores the behavior difference when index is greater than 2.
then
■ index=0 : mem[0] is assigned to the value of a
■ index=1 : mem[1] is assigned to the value of a
■ index=2 : mem[2] is assigned to the value of a
■ index=3,4,5,6,7 : mem[0], mem[1], and mem[2]will not be affected with their
current value.
Based on this interpretation, RTL-1 and RTL-2 are considered functional nonequivalent, and
consequently the implementation from RTL-2 will be nonequivalent to RTL-1.
Using the same RTL-1 and RTL-2 examples, when running the command:
set hdl options -verilog_trimindex on
The Conformal software will interpret RTL-1 as RTL-2 by ignoring index[2] in the
expression mem[index] (RTL-1). With the -verilog_trimindex on option, RTL-1 and
RTL-2 are considered equivalent.
By default, the tool leaves top.o[3] unconnected. If you use the set hdl options -
portmismatch extend command, the tool applies sign extending and connects
top.o[3] to 1'b0.
For example:
oo: out integer;
constant c1: unsigned(31 downto 0) \
:= "11000000000000000000000000000000";
oo <= conv_integer(c1);
For example,
in1: in natural; oo: out integer;
oo <= in1 * 2;
When you use the "SET HDL OPTIONS -include_src_dir off" command, search paths
are manually specified using the ADD SEARCH PATH or the +incdir+ option in the Verilog
command files. For example:
SETUP> SET HDL OPTIONS -INCLUDE_SRC_DIR OFF
SETUP> ADD SEARCH PATH common
SETUP> READ DESIGN rtl/test.v
// Conformal commands
read library -liberty LIB_CELLS.lib // read in LIB_CELL1, LIB_CELL2, LIB_CELL3
set hdl options -remove_cell lib_cell1
read design design.v
The command set hdl options -remove_cell lib_cell1 will remove the cell
instances u0 and u1 from the module design, and the resulting design after removing the
cells u0 and u1 will be equivalent to the following:
module design(...);
LIB_CELL2 u2 (...);
LIB_CELL3 u3 (...);
endmodule
Related Commands
ELABORATE DESIGN
READ DESIGN
READ LIBRARY
Tcl Command
set_hier_compare_option
Parameters
-AUTO_ANALYZE_COMPARE
Enable analyze_compare in
write_hier_compare_dofile. It also turned off the
set_datapath_option -auto.
-GOHIER_SHARED_MEMORY
Enables gohier by using shared memory. This is effective
when all workers are set as localhost. This is set with SET
PARAllel Option -workers localhost localhost.
-NOIGNORE_TOP_MERGE_CONSTRAINT
Do not ignore top-level merge commands in hierarchical
constraint.
-IGNORE_TOP_MERGE_CONSTRAINT
Ignores top-level merge commands in hierarchical constraint.
-TOP_USE_ALL_THREADS
Allows top-module comparison to perform parallel work with the
number of "worker*threads" in the command GO
HIer_compare.
Related Commands
GO HIER COMPARE
Smart LEC provides an analytic engine that can select higher quality modules for hierarchical
comparisons to minimize the overhead for module comparison. Instance selection is based
on the following design characteristics:
■ Primitive gate counts
■ RTL/netlist design
■ Datapath types
■ Boundary complexity
■ Periphery datapaths
Tcl Command
set_hier_compare_selection
Parameters
Example
The following is a sample dofile for an RTL-to-synthesized gate netlist hierarchical
comparison using smart instance selection.
Related Commands
GO HIER COMPARE
RUN HIER_COMPARE
SET IMPLEMENTATION
SET IMPlementation
<MULtiplier [-AUTO | -CSA | -WALL | -RCA | -NBW | -BKA] |
DIVider [-RPL | -BLA | -CLA | -CLA2]
[-OVERFLOW_TRUNCATE | -OVERFLOW_SATURATE | -OVERFLOW_DONTCARE]
[-ALL_div | -RTL_div | -DW_div]>
[-Both | -Golden | -Revised]
(Setup Mode)
Specifies the multiplier and divider implementations in the Golden and Revised designs.
Execute this command before READ LIBRARY and READ DESIGN.
Required Options
With this command, you must include either the multiplier or divider option; however,
Conformal permits both options, as shown below:
Tcl Command
set_implementation
Parameters
Related Command
READ DESIGN
Use this command before the READ DESIGN, READ LIBRARY, and ELABORATE DESIGN
commands to override the default instantiation depth limit. By default, the default instantiation
depth is 100.
Tcl Command
set_instantiation_depth
Parameters
Examples
The following command sets the instantiation depth to 30:
set instantiation depth 30
Note: If you do not specify a positive integer, the tool issues an Error that says the specified
number is too small. For example:
SETUP> set instantiation depth 0
// Error: The specified number 0 is too small.
Writes the transcript to a specified file. The commands and any output information write to
this file. As you review the file, identify commands by the keyword:
//Command:
When you want the Conformal software to stop writing to the log file, enter the command
without any options.
Note: If the filename you specify already exists, you must use either the -replace or
-append option. If you do not include an option, the Conformal software generates an error
message that the file exists. If you receive this message, reenter the command with either a
new filename or the appropriate option. If the filename is not writable, the software writes it to
the /tmp directory.
If you are writing the transcript to a file, you might want to turn off the screen transcript display
with the SET SCREEN DISPLAY command. (If you do not specify otherwise, the transcript
prints to the screen.)
To store log files based on the software version, use the LEC_VERSION environment variable.
For example:
set log file lec.$LEC_VERSION.log -replace
To verify the current log file setting, use the REPORT ENVIRONMENT command.
Tcl Command
set_log_file
Parameters
Related Commands
REPORT ENVIRONMENT
[-SUPPORT_RET_STRATEGY_WITH_COMPATIBLE_CTRL_AND_RET_COND_AS_ZERO_PIN
|-NO_SUPPORT_RET_STRATEGY_WITH_COMPATIBLE_CTRL_AND_RET_COND_AS_ZERO_PIN]
[-INSERT_ISO_AT_FLOATING_UNDRIVEN |
-NO_INSERT_ISO_AT_FLOATING_UNDRIVEN]
[-TRAVERSE_AON_FOR_STRATEGY_MATCHING]
[-TRAVERSE_BUF_AND_INV_FOR_STRATEGY_MATCHING]
[-EXCLUDE_SIGNALS_AS_RETENTION_ELEMENTS
[-IDENTIFY_ALIVE_POWER_DOWN_ISO_CELL <STRUCTURE | ATTRIBUTE |
ATTRIBUTE_OR_STRUCTURE>]
[-PST_SUPPORT_RANGE_VOLTAGE]
[-STANDBY_DETERMINED_BY_POWER_AND_GROUND_VOLTAGE_ONLY]
[-TRAVERSE_TERMINAL_BOUNDARY_EXCEPT_FOR_STRATEGIES |
-NO_TRAVERSE_TERMINAL_BOUNDARY_EXCEPT_FOR_STRATEGIES]
[-USE_ACTIVE_PHASE_FOR_ASYNC_CONTROL_CLAMP_VALUE]
[-USE_STRATEGY_LOCATION_AS_HIERARCHY | -
NO_USE_STRATEGY_LOCATION_AS_HIERARCHY]
[-USE_CELL_ATTRIBUTE_FOR_ASYNC_CONTROL_CLAMP_VALUE]
[-NOLP_CTRL_SIGNAL_COMPARED_PAIR | -LP_CTRL_SIGNAL_COMPARED_PAIR]
[-WITNESS_LIMIT <n>]
(Setup Mode)
Enables options to execute Low Power checks. Options differ between the CPF and 1801
flows. The syntax above describes which options are available in the CPF flow and which are
available with 1801.
For more information on these low power checks and cell types, see CHECK LOWPOWER
CELLS.
Tcl Command
set_lowpower_option
Parameters
-CONSTANT_signal
-CONSTANT_signal: Specifies if a logical constant
driving a domain interface port will be relocated to its
receiver(s)
A constant signal driven from a supply net, tie cell output
or soft/hard macro cell constant output pin or a pin with
analog attribute is not a signal that could be relocated.
A terminal boundary input port is treated as a leaf port
and the constant signal relocation stops at such ports.
NOT_LOCALIZED: The constant signal driving a domain
interface port will not be relocated. This is the default for
all analysis style.
LOCALIZED_Direct: A directly connected constant
signal (1’b0/1’b1) driving a domain interface port is
expected to be relocated to its receiver(s) during
implementation stage(s). Such directly connected
constant signal (1’b0/1’b1) will not cause crossing
violations. This does not apply for post-route analysis
style.
LOCALIZED_Propagated: A directly connected
constant signal propagating through logic gates
(including buffer and inverter) is expected to be
relocated to its receiver(s) during implementation
stage(s). Crossings related to these constant signals will
not cause crossing violations. This does not apply for
post-route analysis style.
-ENABLE_1801_HIERARCHICAL_BBOX
Enables 1801 hierarchical blackboxed block flow. This
flow enables the block UPF to be applied at the bbox
module. The block UPF should have well-defined
attributes to perform the correct analysis at the chip-
level integration. You should run CLP-Verify and clear
any 1801-HIER_BBOX_* violations before running this
flow in LP-EC.
-EXCLUDE_LOCALIZED_PATH_TYPE <NONE | TOP_PORT | MACRO_PORT |
TOP_AND_MACRO_PORT>
-NO_ADD_VIRTUAL_SWITCH_IN_SCOPE
With this option, the virtual power switch is inserted at
the scope where it was defined. This is the default.
-ADD_VIRTUAL_SWITCH_IN_SCOPE
If create_power_switch does not specify -domain,
this will insert the virtual power switch at the scope
where the switch was defined.
If create_power_switch specifies -domain, the
location and number of inserted virtual power switches
will depend on the elements of the domain and the
create_power_switch command specification:
■ If there is only one element in the domain, the virtual
switch will be inserted in that element
■ If there are multiple elements in the domain and if
the create_power_switch has no -ack_port
option, there will be one virtual switch inserted in
each element of the domain
■ If the create_power_switch has the -
ack_port option, there will be a single virtual
switch inserted at the scope where the command
was defined
-NO_ENABLE_TERMINAL_BOUNDARY_SUPPORT
Disables the terminal boundary support. This is the
default.
-ENABLE_TERMINAL_BOUNDARY_SUPPORT
Enables the terminal boundary support.
-NO_EXCLUDE_SINGLE_PWR_AND_SINGLE_GND_AT_MISSING_CSN_MACRO
Do not exclude the macro cell with a single power and a
single ground pin at
1801_SUPPLY_CSN_MISSING_FOR_MACRO check.
This is the default.
-EXCLUDE_SINGLE_PWR_AND_SINGLE_GND_AT_MISSING_CSN_MACRO
-NO_FILTER_FLOATING_UNDRIVEN_PORT_WITH_DIFF_SUPPLY_ONLY
Setting this option will not apply '-diff_supply_only
TRUE' filter to strategy elements for which the logic
driver or receiver supply set cannot be determined
because the domain boundary port is undriven or
floating. This is the default.
-FILTER_FLOATING_UNDRIVEN_PORT_WITH_DIFF_SUPPLY_ONLY
Setting this option will apply '-diff_supply_only
TRUE' filter to strategy elements for which the logic
driver or receiver supply set cannot be determined
because the domain boundary port is undriven or
floating.
-NO_GOLDEN_OVERWRITE_PHYSICAL_SUPPLY_SET_BY_SPA_FOR_BBOX
Disables -
GOLDEN_OVERWRITE_PHYSICAL_SUPPLY_SET_BY_S
PA_FOR_BBOX for the Golden design. This is the
default.
-GOLDEN_OVERWRITE_PHYSICAL_SUPPLY_SET_BY_SPA_FOR_BBOX
Disables -
REVISED_OVERWRITE_PHYSICAL_SUPPLY_SET_BY_
SPA_FOR_BBOX for the Revised design. This is the
default.
-REVISED_OVERWRITE_PHYSICAL_SUPPLY_SET_BY_SPA_FOR_BBOX
In the Revised design, the physical supply set
assignment for blackboxed instance ports will be
overwritten by the supply set specified in the power
intent using 'set_port_attribute' or
'set_related_supply_set' commands. For
blackbox inputs/inouts, the physical receiver supply will
be overwritten by the 'set_port_attribute -
receiver_supply' or 'set_related_supply_net'
setting. For blackbox outputs/inouts, the physical driver
supply will be overwritten by 'set_port_attribute -
driver_supply' or 'set_related_supply_net'
setting.
-NO_TRAVERSE_DOMAIN_BOUNDARY_FOR_ISO_ZERO_PIN_RET_MATCHING
To match the isolation cell with a zero-pin retention
strategy, the isolation cell must be placed in the same
domain as the zero-pin retention cell. This is the
default.
-TRAVERSE_DOMAIN_BOUNDARY_FOR_ISO_ZERO_PIN_RET_MATCHING
Allow crossing domain boundaries to match isolation
cell inserted for zero pin retention strategy. This option
helps to match isolation cells that are inserted in a
domain other than the domain of the zero-pin retention
cell or to match isolation cells when there are buffers
placed between isolation cell and the zero-pin retention
cell and the buffers are in a domain different than the
isolation/retention cell.
–NO_USE_SIMSTATE_FOR_STANDBY
In 1801, standby mode is supported through the
simstate argument of the add_power_state
command. With this option, the standby state will be
treated as normal ON state and the standby state
crossing checks will not be turned on. This is the
default.
-USE_SIMSTATE_FOR_STANDBY
In 1801, standby mode is supported through the
simstate argument of the add_power_state
command. With this option, the supply set is considered
to be in standby mode in a power state if all of its supply
functions are FULL_ON and the simstate is one of
following, CORRUPT_ON_ACTIVITY,
CORRUPT_ON_CHANGE,
CORRUPT_STATE_ON_ACTIVITY,
CORRUPT_STATE_ON_CHANGE. The standby state
crossing checks will also be turned on.
-EXCLUDE_SIGNALS_AS_RETENTION_ELEMENTS
1801 retention strategy applied objects include the
signal names by default based on 1801 LRM usage.
Use this option to exclude signals at the applied
elements of a retention strategy.
-INSERT_ISO_AT_FLOATING_UNDRIVEN
Isolation cells inferred by elements of set_isolation
strategy that have no logic drivers or logic receivers are
inserted. This is the default.
-TRAVERSE_AON_FOR_STRATEGY_MATCHING
Setting this option allows strategy filtering and matching
to traverse buffers and inverters that are implemented
using always-on cells, but are inserted between the
isolation or level-shifter instances and domain boundary
(traverses through the buffers and inverters as long as
no domain boundary pin is crossed).
-TRAVERSE_BUF_AND_INV_FOR_STRATEGY_MATCHING
Setting this option allows strategy filtering and matching
to traverse buffers and inverters that are not
implemented using always-on cells but are inserted
between the isolation or level shifter instances and
domain boundary (traverses through the buffers and
inverters as long as no domain boundary pin is
crossed).
-NO_INSERT_ISO_AT_FLOATING_UNDRIVEN
-TRAVERSE_TERMINAL_BOUNDARY_EXCEPT_FOR_STRATEGIES
Considers the terminal boundaries as transparent and
all supply and power state analysis are done based on
the full design. This is the default.
-NO_TRAVERSE_TERMINAL_BOUNDARY_EXCEPT_FOR_STRATEGIES
Honors the terminal boundaries and check each soft
macro scope and top scope independently.
-SUPPORT_RET_STRATEGY_WITH_COMPATIBLE_CTRL_AND_RET_COND_AS_ZERO_PIN
-NO_USE_STRATEGY_LOCATION_AS_HIERARCHY
With this option the -location in set_isolation or
set_level_shifter strategy is assumed to denote
the domain rather than hierarchy. With location denoting
the domain, the insertion of lowpower cells can be
shifted from the location specified by the strategy to any
connected net, as long as no domain boundary pin is
crossed. This is the default.
-NOLP_CTRL_SIGNAL_COMPARED_PAIR
Does not enable the feature of using probe point
compared pairs for comparing control signals of low-
power strategies. This is the default.
-LP_CTRL_SIGNAL_COMPARED_PAIR
Enables the feature of using probe point compared pairs
for comparing control signals of low-power strategies.
Users must use commands ANalyze LP_control Pair or
ADD LP_control Pair to add compared pairs of low-
power control signals.
-WITNESS_LIMIT <N> For certain rule checks, witnesses can have shared
characteristics. The option -witness_limit specifies
the maximum number of occurrences that can be
created out of a single group of similar witnesses. The
exact witness grouping criteria are rule-dependent. By
default, the witness limit is 1. If a witness limit of 0 is
specified, there is no limit: an occurrence is created for
each witness. This option takes effect during the
execution of the command that performs the rule
checks. If the witness limit is changed after the checks
are done, it's necessary to run the checks again.
Examples
Related Commands
ADD LOWPOWER CELLS
Specifies the mapping method, phase, case sensitivity, and handling for unreachable points
and blackboxes when Conformal maps the key points. With the -name option, paths of the
gates indicate some type of starting point to map key points. The system default is name
first. This default lets Conformal first map key points with the same paths, then map the
remaining unresolved key points with a mapping algorithm. All remaining unresolved key
points become unmapped points.
Use the REPORT ENVIRONMENT command to display the setting of the mapping method and
phase.
Tcl Command
set_mapping_method
Parameters
-DONOTMAP_pattern Do not map key points whose names match the specified
pattern (pattern must be provided as a regular Perl expression).
Default value is an empty string.v
-IGNORE_BBOX_UNMAPPED_FEEDTHROUGH_INPUT
Ignores the unmapped feedthrough inputs of blackboxes such
that unmapped situations for these inputs do not cause BBOX
NEQs.
-MAPPING_FILE Use the mapping file specified by SET ANALYZE OPTION -
MAPPING_FILE during mapping. This is the default.
-NOMAPPING_FILE Do not use the mapping file specified by SET ANALYZE
OPTION -MAPPING_FILE during mapping.
-MAP_UNREACH_IN_MAPPING_FILE
Maps unreachable key points specified in the mapping file.
-MEM Uses a mapping method that is compatible with memory array
structures and results in faster and more accurate memory
array element mapping and consequently more accurate
comparison, reducing the number of false errors due to
incomplete or incorrect mapping and reducing the need for
renaming rules.
This option should be set when the design to be verified is a
memory circuit.
-NAME_EFFORT Uses the specified amount of effort for key point mapping. This
option eliminates the need for simple renaming rules such as:
add renaming rule R1 "reg\[%d\]" "reg(@1)"
-golden, which maps the following Golden and Revised
design DFFs:
Golden: DFF A/B/C_reg[5]
Revised: DFF A/B/C_reg(5)
This option applies to only DFFs and DLATs.
HIgh Specifies a high effort for key point mapping.
This option is the system default.
MEdium Specifies a medium effort for key point
mapping.
LOw Specifies a low effort for key point mapping.
Related Commands
ADD NAME ALIAS
REPORT ENVIRONMENT
Specifies the MOS model names used in SPICE. You can then re-read the SPICE netlist.
When reading in SPICE netlists, the parser automatically identifies transistor model names
as PMOS and NMOS types. However, if you have models that were not defined using .MODEL
statements, the parser identifies them as ERROR. Instead of altering your SPICE file, you can
use this command.
Note: You must run this command before reading in the SPICE netlist.
Tcl Command
set_mos_model
Parameters
Splits a multibit instance name into individual instance names using a name delimiter, a group
pattern, and/or a prefix. This can facilitate the successful mapping of the individual bits for the
multibit cell.
Tcl Command
set_multibit_option
Parameters
-Delimiter <string> Specifies the name delimiter as a Perl regular expression. The
default value is "_MB_".
-GROUP <string> Specifies the name group as a Perl regular expression. It must
be in the format of
"(<pattern>)". The default value is (.*?).
-PREFIX <string> Specifies the prefix (from synthesis). The default value is
"CDN_MBIT_".
-PREPEND <string> Specifies the prepend string before the prefix as a Perl regular
expression. It must be in the format of "^(<pattern>)". The
default value is "^(.*?)".
Example
For example:
■ The SET MULTIBIT OPTION command (without any options), splits the multibit
instance name CDN_MBIT_a_reg[0]_MB_a_reg[1] into a_reg[0] and a_reg[1].
While, the multibit instance name
resolved_hier_CDN_MBIT_a_reg[0]_MB_a_reg[1] is split into
resolved_hier_a_reg[0] and resolved_hier_a_reg[1] by default.
■ The following tests how a pattern would be split:
For an original name of a_reg_MG_b_reg
Related Commands
SET MAPPING METHOD
Specifies the multiplier implementation in the Golden and Revised designs. Execute this
command before READ LIBRARY and READ DESIGN.
Tcl Command
set_multiplier_implementation
Parameters
Related Command
READ DESIGN
Specifies whether Conformal will automatically analyze multipliers when switching from
Setup to LEC mode. Additionally, use the -cdp_info option if you want Conformal to let
you know when Conformal XL will be helpful.
Tcl Command
set_multiplier_option
Parameters
Related Commands
ANALYZE DATAPATH
ANALYZE MODULE
Specifies the naming rules for an RTL or hierarchical design. Conformal uses the renaming
rule to construct the name for the design module, instance, variable, or port. Execute this
command before READ LIBRARY and READ DESIGN (note that SET NAMING RULE -
inverted_pin_extension does not have this requirement).
Each string for all of the settings must be enclosed in double quotes (" "). These double
quotes can be empty.
Use the REPORT ENVIRONMENT command to display the settings for the naming rules for the
Golden and Revised designs.
Tcl Command
set_naming_rule
Parameters
-Hierarchical_separator <string>
A character or string that specifies the hierarchical separator.
The default is "/".
Use the hierarchical separator string when matching key points
between the Golden and Revised designs. The hierarchical
separator setting has no effect on the way key points are
reported (for example, when you use the REPORT GATE
command).
-Tristate <string> A string specifies how tri-state names should be constructed.
The default is "%s_tri". Where %s denotes the tristate
variable name. The string must contain exactly one "%s".
-REGister <string> A string that specifies how register names should be
constructed. The default is "%s_reg". Where %s denotes the
register name. The string must contain exactly one "%s".
-Inverted_pin_extension <string>
A string that specifies the inverted pin extension. This option
appends the string to the Golden or Revised pin name.
For example, the Golden design has a pin named "a".
In the Revised design, it is named "a_BAR". The following
command specifies the correct name mapping:
set naming rule -inverted_pin_extension "_BAR" -golden
-MOD_PARAM
USE_ANYWAY: Compose parameterized module name with
instance parameter data regardless whether the new value is
the same as the default value or not. This is the default setting.
USE_WHEN_DIFF: Compose parameterized module name with
parameter data only if the new parameter data is different from
the default value.
USE_ALL: Apply all parameters even if instance statement does
not specify parameter setting or the new data is the same as
default values.
-NOINSTARRAY_range_reset
LEC will expand array instance into individual instance(s) and
name the instance(s) based on "-INSTANCE_Array" setting.
For the first %d in the “instance_array” setting, LEC will replace
the first "%d" with original design array instance range
declaration. This is the default.
-INSTARRAY_range_reset < ASCEND | DESCEND >
When "ASCEND" is used, LEC will replace the first "%d" with
the array index start from 0 and end with array size -1.
When "DESCEND" is used, LEC will replace the first "%d" with
the array index start from array size -1 and end with 0.
-Both The naming rule applies to both the Golden and Revised
designs. This is the default.
-Golden The naming rule applies to the Golden design alone.
-REvised The naming rule applies to the Revised design alone.
Examples
Sample Usages:
set naming rule -hierarchical_separator ":" -golden
set naming rule -register "register_%s" -revised
set naming rule -tristate "tristate_%s"
set naming rule -array "<" ">" -golden
set naming rule -instance "%L.%s" "%L[%d].%s" "%s"
Interpreting Strings
The following illustrates how LEC interprets the following parameter string to generate a
parameterized module name:
read design -sv test.v -root test -parameter -stri mystr "abc"
■ By default, LEC generates the parameterized module name as "test_mystr6382179".
■ When -STRI hex is used, LEC generate parameterized module name as
"test_mystrx616263".
■ When -STRI str is used, LEC generate parameterized module name as
"test_mystrabc".
The tool generates port names a_req, a_gnt, a_addr and a_data for module memMod.
The following command renames ports a_req, a_gnt, a_addr and a_data as \a.req,
\a.gnt, \a.addr, and \a.data respectively
set naming rule -INTerface_delimiter "." ""
\s1[2]_%s_%s%d
\s1[1]_%s_%s%d
\s1[0]_%s_%s%d
\s2[4]_%s_%s%d
\s2[3]_%s_%s%d
\s2[2]_%s_%s%d
\s2[1]_%s_%s%d
\s2[0]_%s_%s%d
■ set naming rule -instance_array "_%s_%s"
The tool produces the following error because the rule does not contain a %d . The tool
will generate the instance names using the default naming format:
// Error: Illegal INSTANCE_Array naming _%s_%s.
\3_s1_%s_%d
\2_s1_%s_%d
\1_s1_%s_%d
\0_s1_%s_%d
\4_s2_%s_%d
\3_s2_%s_%d
\2_s2_%s_%d
\1_s2_%s_%d
\0_s2_%s_%d
■ set naming rule -instance_array "_%d_%d"
The tool generates the following instance names:
\_4_%d
\_3_%d
\_2_%d
\_1_%d
\_0_%d
\_4_%d_1
\_3_%d_1
\_2_%d_1
\_1_%d_1
\_0_%d_1
Related Commands
ADD MAPPED POINTS
READ DESIGN
REPORT ENVIRONMENT
Specifies the naming style for an RTL design. Execute this command before READ DESIGN.
This command handles standard naming (where the design uses only the default Genus
synthesis attributes); it does not handle naming caused by non-default Genus synthesis
attributes (which include, but are not limited to, attributes such as inst_prefix or
hdl_generate_index_style). To handle those cases, you must also use the ADD
RENAMING RULE or SET NAMING RULE commands.
Note: If you use the dofile generated by the Genus command write_do_lec, it already
contains commands that handle standard renaming.
Tcl Command
set_naming_style
Parameters
LEC Applies the LEC naming style to the design. This is the
default.
RC Applies the RTL Compiler naming style to the design.
GENUS Applies the Genus naming style to the design.
DC Applies the Design Compiler naming style to the design.
-Both The naming style applies to both the Golden and Revised
designs. This is the default.
-Golden The naming style applies to the Golden design alone.
-REvised The naming style applies to the Revised design alone.
Examples
The following example illustrates the difference between the naming styles.
Using the LEC naming style, the instance name of the arithmetic operator will be mult_7.
Using the Genus naming style, the instance name of the arithmetic operator will be mul_7_9.
Using the DC naming style, the instance name of the arithmetic operator will be mult_7.
Related Commands
READ DESIGN
Sets the parameters for parallel processing. Some options are used for multithreaded
processing (recommended form of parallel processing), some are used for LSF-based
parallel processing, and -KEEP_DIR is used for both.
The following options are used for LSF based parallel processing only:
■ -MAX_Remote
■ -SUBMIT_COMMAND_LINE
■ -KILL_COMMAND_LINE
Tcl Command
set_parallel_option
Parameters
-SUBMIT_COMMAND_LINE <string>
Specifies the submit command interface.
The default value is:
bsub -o <logdir>/<jobnum>_LSF.log
<submit_options> <command>
The keywords <logdir>, <jobnum>, and <command> are
determined by the software.
You can specify <submit_options> with the RUN PARALLEL
COMPARE command.
-THREADS <integer>[,<integer>]
Specifies the minimum and maximum number of threads,
separated by comma. If only one number entered, this specifies
both the minimum and maximum number of threads. For
example '-threads 2' specifies two threads; '-threads 2,4'
specifies a minimum of two threads, and a maximum of four
threads.
-RESERVE_LICENSE Immediately checks out and reserves the number of licenses
required for multithreaded processing (if you specified a range
of threads, the tool looks for the minimum number of required
threads). The tool errors out if it cannot check out the required
number of licenses. The licenses are reserved until released
using the -RELEASE_LICENSE option.
Notes: This option requires that multithreading be enabled
(through the -THREADS option).
-RETRY Used with -RESERVE_LICENSE, repeat the license check until
all licenses required to support the minimum number of threads
are checked out. Press Ctrl_C to exit this procedure.
-QUEUE Use with -RESERVE_LICENSE. Puts the license request in
queue. This request will give the license when it is available.
Press Ctrl_C to exit this procedure.
-TMPDIR <string>
Examples
The following examples are for multithreaded processing only:
■ The following command sets the minimum and maximum number of threads to 3. As a
result, the subsequent COMPARE command will use 3 threads:
set_parallel_option -threads 3
compare
■ The following command specifies that LP licenses will be used during parallel
processing. Then the COMPARE -threads 3 command checks out two additional LP
licenses for parallel comparison. By default, the software checks out two additional XL
licenses.
set_parallel_option -license lp
■ The following command specifies the list of licenses to use for parallel processing. If you
have one LP and two ECO licenses, you can run parallel processing for up to four
threads:
set_parallel_option -license "lp eco"
compare -threads 4
■ If you have XL, LP, and ECO licenses, but do not know the exact usage of these licenses,
you can use all available licenses to run parallel comparison. The following command
first attempts to check out three XL licenses. If only one XL license is available, the
software checks it out and attempts to check out two LP licenses. If this succeeds, the
software runs parallel comparison using four threads with one XL license and two LP
licenses. If only one LP license is available, the software checks it out and attempts to
check out one ECO license. If this succeeds, the software runs parallel comparison with
one XL, one LP, and one ECO licenses.
set_parallel_option -license "xl lp eco"
compare -threads 4
■ The following command keeps the temporary directory created during parallel
processing:
set_parallel_option -keep_dir
■ The following command searches for an available port starting from port number 50100
set_parallel_option -starting_port 50100
■ The following command specifies that the command used to submit jobs is mybsub and
the command used to kill jobs is mybkill. By the default, the commands used to submit
and kill jobs are bsub and bkill:
set_parallel_option -submit_command_line mybsub -kill_command mybkill
■ The following command sets the minimum number of threads to 2 and maximum to 4. In
this way, the software strives to use the maximum number of threads. If this does not
succeed, it automatically reduces the number of threads according to the number of
available licenses instead of existing with an error, unless it cannot run with the minimum
number of threads:
set_parallel_option -threads 2,4
■ The following commands specify that licenses will be held during mutlithreaded
processing in hierarchical comparison to avoid frequent license check out and check in:
set_parallel_option -norelease_license
set_parallel_option -threads 4
dofile hier_compare.do
The above specifies that the parallel hierarchical comparison will use 4 threads and 4
workers from an LSF cluster.
You can mix localhost and batch in worker setting. For example:
set_parallel_option -workers batch batch localhost localhost batch localhost
================================================================================
Keep directory : NO
Multithreaded processing options:
--------------------------------------------------------------------------------
Number of threads : 0,0
Starting port : 50100
License list : SL4
Hold license : NO
Distributed parallization options:
--------------------------------------------------------------------------------
Workers : localhost localhost localhost localhost
Cluster type : LSF
Batch command : * (null)
Rsh commmand : rsh
Related Commands
SET DATAPATH OPTION
ANALYZE DATAPATH
SET PARAMETER
SET PArameter
[ <-MODule <moduleName>|-INTERface <interfaceName>>
[-Parameter [-INT |-STR|-ENUM] <paramName> <paramValue>]]
[-Golden |-Revised |-Both]
(Setup Mode)
Use this command before the READ DESIGN, READ LIBRARY, and ELABORATE DESIGN
commands to override default parameter values assigned by source files. If a command has
more than one parameter definition, Conformal uses the last parameter.
To specify multiple modules, interfaces, or parameters, you must use the corresponding
option for each module, interface, or parameter that you want to set. For example:
set parameter -mod m1 -p param1 value1 -mod m2 -p param2 value2 \
-mod m2 -p param3 value3 -p int param4 value4
Tcl Command
set_parameter
Parameters
Related Commands
ELABORATE DESIGN
READ DESIGN
Tcl Command
set_pattern_match
Parameters
-Pattern <pattern_name>
Specifies that the name of the pattern (that was read in with the
READ PATTERN command) that will apply to the module(s).
-MOdule <module_name ... >
Specifies the module(s) to apply to the pattern.
-MAPping_file <mapping_file>
Specifies the file that contains the pairs of patterns and
modules for pattern match. The format of the mapping file is
<pattern_name> <module_name>.
-Golden Sets the pattern match on the Golden design.
-Revised Sets the pattern match on the Revised design.
Related Commands
READ PATTERN
This command specifies the LEC project that will collect and consolidate various information
for multiple LEC runs.
Tcl Command
set_project_name
Parameters
Related Commands
ANALYZE PROJECT
DELETE PROJECT
Tcl Command
set_project_options
Parameters
Related Commands
DELETE PROJECT
This command adds user-specified properties to current run or user specified previous run.
Tcl Command
set_project_property
Parameters
-Run <integer> Specifies the run to which to add the property. The default
is current run.
<keyword> Specifies the name of the property to be added.
<value> Specifies the value of the property to be added.
Example
The following command specifies that the current run is the "reference" run, and sets its
property to 1. By doing so, this run is not subject to automatic removal.
set project property reference 1
For example, the SET PROJECT OPTIONS command can specify the maximum runs and
maximum memory usage for the project. When either is exceeded, the tool automatically
removes the old run directories. If you set a run's project property to 1, it is not subject to this
type of automatic removal.
Related Commands
DELETE PROJECT
Specifies whether the Conformal software automatically performs retiming analysis for
designs when switching from Setup to LEC mode. According to the structure of the designs,
the software automatically determines whether to use forward or backward pipeline retiming,
or general retiming. If sequential correspondence information is available, the software uses
general retiming except for cases where all the registers are on the PO or PI side for the
Golden or Revised design, in which case the software uses forward or backward pipeline
retiming. The analysis results enable the software to automatically resolve retiming designs.
Tip
Use the ADD MODULE ATTRIBUTE command to attach the PIPELINE_Retime
attribute to a module.
Tcl Command
set_retiming_option
Parameters
Related Commands
ADD MODULE ATTRIBUTE
ANALYZE RETIMING
Specifies the name of the root module for the Golden and Revised designs. The system
default specifies that when the design is read, Conformal automatically assigns the root
module. Thus, the SET ROOT MODULE command overrides the automatic assignment.
Use the REPORT ENVIRONMENT command to display the settings for the root module for the
Golden and Revised designs.
Tcl Command
set_root_module
Parameters
Related Commands
READ DESIGN
REPORT ENVIRONMENT
Specifies the Verilog language standard for the file extensions. When specifying -MIXvlog
with the READ DESIGN command, the file extension will be used to determine the Verilog
language standard to parse the Verilog file. The default file extensions for Verilog standards
are as follows:
■ Verilog 1995: .v95, .v95p
■ Verilog 2K: .v, .vp, .v2k
■ SystemVerilog: .sv, .svp
Tcl Command
set_rtl_type
Parameters
Examples
The following example demonstrates how to specify Verilog design standard for file
extensions.
SET RTL TYPE -V1995 .v95 .v95p .vg .gv
SET RTL TYPE -VERILOG2K .v .vp .v2k
SET RTL TYPE -SYStemverilog .sv .svp .vs
Related Commands
READ DESIGN
Filters out rules that occur in modules outside the root hierarchy. It is a means to remove
unnecessary rule reporting and focus only on the root module's hierarchy.
Use the REPORT RULE CHECK command with the -summary option to display all of the rules
and their settings and occurrences.
Tcl Command
set_rule_filter
Parameters
-ROOT_HIER_only Filters out rules that occur in modules outside the root
hierarchy.
-Golden Applies the filter to the Golden design and library. This is the
default.
-Revised Applies the filter to the Revised design and library.
Related Commands
READ DESIGN
READ LIBRARY
Specifies the rule handling when reading in the designs and libraries or exclude the specified
module, design file, library file, or rule from rule checking. Most rules are either warnings or
notes. Execute this command before READ LIBRARY and READ DESIGN.
Note: Multiple SET RULE HANDLING commands can be specified, and the effects are
cumulative.
Use the REPORT RULE CHECK command with the -summary option to display all of the rules
and their settings and occurrences.
See the Conformal Equivalence Checking User Guide for rule definitions and sample cases.
Note: The wildcard (*) represents any zero or more characters in rule names.
Tcl Command
set_rule_handling
Parameters
<rule_name* ...> Changes rule handling for the specified rules. This accepts
wildcards.
-Warning The rule handling will be a warning
message. This is the default.
-Error [-CONTinue]
The rule handling will be an error message.
The -continue option can be used on
RTL-related rules or tasks to indicate that the
program continue to run instead of erroring
out.
-Ignore The rule handling will be ignore. See
REPORT RULE CHECK to see how this
severity level affects reporting.
-Note The rule handling will be a note.
-EXCLude | -INCLude
Removes the unwanted rules. If neither of these options are
specified, all rules will be checked by default.
-EXCLude removes some rules in the specified list.
-INCLude removes all rules not in the specified list.
-MODule Removes the unwanted rules for the
specified module.
-SUBModule Also removes the unwanted rules for
submodules and decendant modules of the
specified module. Note that if a submodule
or decendant module is also part of other
module hierarchy, the rule violations will still
be reported for that module hierarchy.
-DESign_file Removes the unwanted rules for the
specified design file.
-LIB_file Removes the unwanted rules for the
specified library file.
<name* ...> Specifies the name of the module, design
file, or library file.
-LIMit <max> Limits the number of occurrences of the specified rules.
<max> is the limit after which no more occurrences will be
recorded. Changing this limit will only have effect the next time
the specified rules are checked.
-SUMMARY_only For rules with severity WARNING or lower, report the rule check
occurrences only at the end of elaboration
Examples
The following command sets the severity level of RTL7.16 from error to warning for the
Golden design:
set rule handling RTL7.16 -warning -design -golden
The following command sets the severity level of RTL7.16 from error to warning for all the
Golden design and removes RTL7.16 from the rule check for the design file top.v
set rule handling RTL7.16 -warning -exclude -design_file top.v -design -golden
The following command sets the severity level of RTL7.16 from error to warning and only
checks the specified rule RTL7.16 for the design file top.v.
set rule handling RTL7.16 -warning -include -design_file top.v -design -golden
Related Commands
READ DESIGN
READ LIBRARY
Set the elapse time limit for the specified module, hierarchical_compare and
commands. The unit of the time is second..
Tcl Command
set_runtime_limit
Parameters
-MODule Limits the runtime of LEC in the specified module. If the module
name is not specified, the runtime limit will be applied in the root
module.
-HIER_compare Distributes the total runtime limit of all the modules. The file with
the runtime limit setting, writes out after the command
write_hier_compare.
-QUICK_COMPARE When the runtime limit is reached, LEC shows the comparison
result according to the current mapping and modeling result.
This is the default.
-COMmand Sets the runtime limit for the specified command. It supports
MAP_KEY_POINTS, ANALYZE_DATAPATH, ANALYZE_ABORT,
ANALYZE_SETUP, and COMPARE.
-EACH The runtime limit is applied to each specified command.
-TOTAL The total runtime of the specified command will be limited when
the command is used multiple times.
Related Commands
DELETE RUNTIME LIMIT
Tip
If the screen display is set to off, use the SET LOG FILE command to save the
transcript to a file.
Use the REPORT ENVIRONMENT command to display the setting for the screen display. By
default, screen display is on.
Tcl Command
set_screen_display
Parameters
Related Commands
REPORT ENVIRONMENT
When you use the -AUTO option, it automatically enables the recommended Smart LEC
features.
Tcl Command
set_smartlec_option
Parameters
Related Command
Specifies options for reading the SPICE netlist design (when running the read design
-spice command).
Tcl Command
set_spice_option
Parameters
-NOKEep_InstanceX Specifies that the first character 'X' of the name of instance will
not be retained. This is the default.
-KEep_InstanceX Specifies that the first character 'X' of the name of instance will
not be retained.
Examples
Sample Dofile:
set spice option -nobulk -nobbox -addglobalpins -keep_instanceX
read design -spice library.spi -golden
abstract logic
Related Commands
ABSTRACT LOGIC
READ DESIGN
SET STATETABLE
SET STATEtable
<ON | OFf>
(Setup Mode)
Controls the global setting of the Synopsys Liberty state table support.
Note: This command must be used before READ DESIGN and READ LIBRARY.
Note: Using the READ DESIGN and READ LIBRARY command's -STATEtable option
supersedes these settings (it also supersedes the global setting).
Tcl Command
set_statetable
Parameters
Related Commands
READ DESIGN -statetable
SET SYNTHESIS_OFF_COMMAND
SET SYNTHESIS_OFF_Command
<string>
(Setup Mode)
Specifies the pragma that is used to indicate the beginning of non-synthesizable constructs
in the source code or in the generated generic netlist.
Note: If you do not run the SET_ATTR INPUT_PRAGMA_KEYWORD command prior to running
this command, the default is translate_off.
Note: If this command is run multiple times, only the last value is used.
Tcl Command
set_synthesis_off_command
Parameters
Examples
Sample Dofile:
set_attr input_pragma_keyword rtl
set synthesis_off_command turn_off
set synthesis_on_command turn_on
After running these three commands, the Conformal and VHDL parsers will recognize the
pragmas in the VHDL and Verilog Source files.
In a VHDL file, the code between -- rtl turn_off and -- rtl turn_on will not be
synthesized.
In a Verilog file, the code between // rtl turn_off and // rtl turn_on will not be
synthesized.
Related Commands
SET_ATTR INPUT_PRAGMA_KEYWORD
SET SYNTHESIS_ON_COMMAND
SET SYNTHESIS_ON_COMMAND
SET SYNTHESIS_ON_Command
<string>
(Setup Mode)
Specifies the pragma that is used to indicate the end of non synthesizeable constructs in the
source code or in the generated generic netlist.
Note: If you do not run the SET_ATTR INPUT_PRAGMA_KEYWORD command prior to running
this command, the default is translate_on.
Note: If this command is run multiple times, only the last value is used.
Tcl Command
set_synthesis_on_command
Parameters
Examples
Sample Dofile:
set_attr input_pragma_keyword rtl
set synthesis_off_command turn_off
set synthesis_on_command turn_on
After running these three commands, the Conformal and VHDL parsers will recognize the
pragmas in the VHDL and Verilog Source files.
In a VHDL file, the code between -- rtl turn_off and -- rtl turn_on will not be
synthesized.
In a Verilog file, the code between // rtl turn_off and // rtl turn_on will not be
synthesized.
Related Commands
SET_ATTR INPUT_PRAGMA_KEYWORD
SET SYNTHESIS_OFF_COMMAND
Switches system modes between the Setup mode and the LEC mode.
■ Setup mode: While in this mode, you read in the design and set all of the necessary
constraints and environment variables.
■ LEC mode: While in this mode, Conformal does the comparison and diagnosis.
When you exit the Setup mode, Conformal attempts to map all key points in the Golden and
Revised designs. A summary is given for the mapped points in the Golden and Revised
designs. An additional summary is given if Conformal identifies any unmapped key points.
Use the REPORT ENVIRONMENT command to display the current system mode.
Tcl Command
set_system_mode
Parameters
Related Command
REPORT ENVIRONMENT
REPORT TESTCASE
Sets the pin inputs of the user-defined primitive (UDP) to constant values, which are
propagated into the UDP. Some inactive entries will be removed.
The constant set to inputs simplifies the state table of the UDP, which will sometimes eliminate
some ambiguity in the UDP description.
Note: This must be used before running the READ DESIGN command.
Tcl Command
set_udp_pin
Parameters
Example
In this example, pins in1 and in2 of the UDP named udp_1 are set to 0 and 1, respectively:
set udp pin udp_1 in1 0 in2 1
Related Commands
READ DESIGN
READ LIBRARY
Specifies how Conformal handles undefined cells it encounters when reading in the Golden
and Revised designs. The system default is to give an error message if there are any
undefined cells.
Use the REPORT ENVIRONMENT command to display the settings for the undefined cells
handling for the Golden and Revised designs. Execute this command before READ LIBRARY
and READ DESIGN.
Note regarding the direction of blackbox pins: Because blackboxes are undefined, the
direction of their pins is automatically inferred from connectivities in the blackbox instance's
parent module. For example, if the net associated with pin d[31] of the blackbox instance
has a known driver (such as, the net is assigned by a continuous assignment or the net is
connected to an instance's output pin), the pin d[31] is a blackbox input pin. If no drivers are
found for the pin d[31], the pin d[31] is a blackbox output pin.
Tcl Command
set_undefined_cell
Parameters
Related Commands
ADD BLACK BOX
READ DESIGN
READ LIBRARY
REPORT ENVIRONMENT
Specifies how Conformal handles undefined ports it encounters when reading in the Golden
and Revised libraries and designs. The system default is to report an error message if
there are any undefined ports referenced by the module instance.
Use the REPORT ENVIRONMENT command to display the settings for the undefined ports
handling for the Golden and Revised designs. Execute this command before READ LIBRARY
and READ DESIGN.
Tcl Command
set_undefined_port
Parameters
Related Commands
READ DESIGN
READ LIBRARY
REPORT ENVIRONMENT
Specifies globally how Conformal treats undriven signals in the Golden and Revised designs.
The system default specifies that undriven signals are classified as high-impedance
(always driven by Z) in the Golden and Revised designs.
Use the REPORT ENVIRONMENT command to display the settings for the undriven signals for
both the Golden and Revised designs. This command has to be specified before SET
SYSTEM MODE LEC command if running flat comparison or WRITE HIER COMPARE
command if running hierarchical comparison.
Tcl Command
set_undriven_signal
Parameters
Related Command
REPORT ENVIRONMENT
Enables the usage of verification information in the current run and uses it to help optimize
verification. Verification information from the current run can only be written out (WRITE
VERIFICATION INFORMATION) when SET VERIFICATION INFORMATION is enabled.
Tcl Command
set_verification_information
Parameters
verification_information_directory
Name of the directory from which to read the verification information.
Unless any categories are enabled/disabled specifically (by the -setup
and -nosetup options), Conformal uses the hier_compare,
analyze_abort, datapath analysis, and phase categories of
information by default (described below).
-RECord Specifies the categories of second run information to be recorded for
future LEC run.
-NORECord Disables the categories of second run information to be recorded.
-SEtup Specifies the categories of verification information to use to help setup
the current LEC run.
-NOSETup Disables the usage of verification information to help setup the current
LEC run. You can disable all information or specific categories of
information.
ALL: Enable or disable all categories of information.
HIER_COMpare: Hierarchical comparison information from previously
captured verification information to avoid dynamic flattening. This
feature is described further in a web interface document titled Second
Run Optimization in Hierarchical Compare.
ANALYZE_ABOrt: Abort analysis information from previously captured
verification information to speed up the analyze abort process. This
feature is described further in a web interface document titled Second
Run Optimization for Analyze Abort.
ANALYZE_DATapath: Information from second run abort analysis. This
feature is described further in a web interface document titled Datapath
Analysis Second Run Optimization.
PHAse: Information about sequential phase inversion from the Genus
implementation information for phase mapping. This feature is described
further in a web interface document titled Verification of RTL Compiler
Synthesis with Sequential Phase Inversion.
MAPping: Mapping information from previously captured verification
information to speed up mapping process.
SEQ_CONST: Sequential constant information from previously captured
verification information to speed up sequential constant modeling
process.
SEQ_MERGE: Sequential merge information from previously captured
verification information to speed up sequential merge modeling process.
Related Command
READ IMPLEMENTATION INFORMATION
SET WATCHER
SET Watcher
[ON | OFF]
[-DIRectory <directory>]
[-RECORD <JSON>
[-LIMIT <resource name> <maximum value>]
(Setup Mode / LEC Mode)
This command launches LEC Watcher in the background for monitoring host status.
Tcl Command
set_watcher
Parameters
This command starts a web server so that you can access Conformal documentation and file
directories in a web browser. Only the latest versions of Chrome and Firefox are supported.
Tcl Command
set_web_interface
Parameters
-FILEPermission Specifies that the web interface can only access files with world
read permissions. The read permissions of the file must be
enabled for user, group, and others.
This is default.
-NOFILEPermission Specifies that the web interface can access files without
checking world readable permissions.
-PORT <integer> Specifies a different port number.
Example
The following describes how to view the web interface with file directories and documentation:
1. Start the web server for web viewing:
SETUP> set web_interface ON
//Web Interface URL is http://host.xyz.com:8090 (http://1.2.3.4:8090)
// A modern browser supporting HTML5 is required.
// File browsing is enabled. To limit access to documentation only, use the -DOCOnly option.
2. The tool returns a URL of the web interface. Copy this URL into your web browser.
The following illustrates how to view the web interface with just the documentation:
SETUP> set web_interface ON -DOCOnly
// A modern browser supporting HTML5 is required.
// Browsing is limited to documentation only.
Note: The port number is unique for each LEC run on a machine. If you try to start a server
for a port that is already in use, the tool returns a message similar to the following:
Failed to bind to port 8090: Address already in use
// Error: Web interface server cannot be created.
In this case, use the -PORT option and specify a new port number:
SETUP> set web_interface ON -port 8091
// Web Interface URL is http://hostname:8091
Specifies how Conformal treats the output behavior of multi-driven nets. The system default
for both the Golden and Revised designs specifies that multi-driven nets are treated
as a wire-AND behavior.
When you use the wire option and Conformal encounters a multi-driven net (that is, bus
contention) in a design, Conformal models this multi-driven net as TIE-X.
Note: This TIE-X is a pseudo input, not a "don't care".
Use the REPORT ENVIRONMENT command to display the settings of the wire resolution for
the Golden and Revised designs.
Tcl Command
set_wire_resolution
Parameters
Related Command
REPORT ENVIRONMENT
SET X CONVERSION
SET X COnversion
<DC | E | 0 | 1>
[-BOth | -GOlden | -REvised]
(Setup Mode)
Specifies how Conformal handles X assignments when modeling the design. It takes effect
when changing from the Setup mode to the LEC mode.
The system defaults specify that X assignments are treated as "Don't Cares" for the Golden
and "Error (E) Gates" for the Revised design. If the X assignment space of the Revised
design is within the X assignment space of the Golden design, then the E gate is marked as
an extra unmapped point (redundant gate) after comparison.
The Revised X Handling feature enhances RTL-to-RTL comparisons. It ensures that the
Revised Xs are in the Golden Don't Care space. To turn off this feature, use
set x conversion dc -revised. This feature has been available since version 4.3.
However, use this option only if you are certain that the X assignment space of the Revised
design is within the X assignment space of the Golden design; otherwise, potential errors
might be masked.
Use the REPORT ENVIRONMENT command to display the settings of the X assignment for the
Golden and Revised designs.
Tcl Command
set_x_conversion
Parameters
Related Command
REPORT ENVIRONMENT
SET XC
SET XC
(Setup Mode)
Analyzes switch and primitive drive strength to achieve the most accurate logic function
result. This technique can be applied to complex custom macros such as RAM and ROM and
is essential to accurate verification of circuits with complex layer switch nets.
SETENV
SETENV
<variable> <value>
(Setup / LEC Mode)
Tcl Command
setenv
Parameters
Examples
setenv LM_LICENSE_FILE 5280@host
Related Command
PRINTENV
SETUP NAME
SETup NAme
[-GOLden | -REVised]
[-CHANGE <instance_name> <new_instance_name>
[-TYPE <CELL|INSTANCE|PORT>]]
[-UNGROUP <instance_name>]
[-MAP_MODULE_NAME <instance_path> <new_module_name>]
[-ALIAS_MODULE_NAME <module_name> <new_module_name>]
[-MODULE <module_name>]
[-UNIQUIFY]
[-BUILD [-CASESENSITIVE]]
[-BUILD_PIN]
[-CLEAR]
[-SOURCE <file>]
[-COMMIT]
[-QUERY <hierarchical_instance_name>]
[-PROFILE]
[-LINT]
[-RENAME <string> <string>]
[-APPLY_MULTIBIT_RULE -ONTO <modules*>]
[-DUPLICATION_PATTERN <string> [<string>]]
[-NOKEEP]
[-VERBOSE [-VERBOSE]]
(Setup / LEC Mode)
SETUP NAME creates a deck to apply the naming guidance for equivalence checking. The
usage starts from -BUILD and ends with -COMMIT.
BUILD and BUILD_PIN create the naming DB from HRC DB. MAP_MODULE_NAME,
ALIAS_MODULE_NAME, and UNIQUIFY add module reference when applying the naming
conversion.
CHANGE and UNGROUP would modify the naming DB. The converted name can utilize
command SETUP_REGISTER_OPTIMIZATION, and for mapping after -COMMIT.
For the name of instance_name and instance_path, the command searches the
reference by using case-sensitive style in default and treat /|[].:_ as the same delimiter.
For example, a[3], a_3_ would point to the same thing..
Tcl Command
setup_name
Parameters
Related Command
SETUP REGISTER OPTIMIZATION
Annotate the sequential optimization information by using the name build in SETUP_NAME.
Tcl Command
setup_register_optimization
Parameters
Related Command
SETUP NAME
Searches for each blackbox instance in your design whose module name matches those in a
specified pattern list, and replaces them with new, fully-defined modules. Use this module in
conjunction with the WRITE BLACKBOX WRAPPER command.
If you enabled the automatic blackbox substitution feature using the WRITE BLACKBOX
WRAPPER -auto_substitute command, you do not need to use this command as the
models are automatically replaced.
Tcl Command
substitute_blackbox_wrapper
Parameters
Example
The following is a set of sample commands that show this and related commands in context.
Sample module:
<<< des.v>>>
module design(clk, rst, cs, wr, rd_addr, wr_addr, din, dout);
input clk, rst, cs, wr;
input [2:0] rd_addr, wr_addr;
input [4:0] din;
output[4:0] dout;
Note: This command also generates synthesis script template file dir/RUN/
synth.tcl.
4. Use the dir/RUN/synth.tcl script with your own synthesis tool to generate
dir/RUN/_DW_ram_r_w_s_dff_5_8_0.g.v.
5. Read the newly created dir/RUN/_DW_ram_r_w_s_dff_5_8_0.g.v file into the
design.
> read design -append dir/RUN/*.g.v
6. Substitute the old module of blackbox instance ram with the new module
_DW_ram_r_w_s_dff_5_8_0_DW_ram_r_w_s_dff_5_8_0_0(dir/RUN/
_DW_ram_r_w_s_dff_5_8_0.g.v:229).
> substitute blackbox wrapper DW*
Related Command
WRITE BLACKBOX WRAPPER
SYSTEM
SYStem
<string_command>
(Setup / LEC Mode)
You can substitute the exclamation mark (!) for the word System, as shown in the example
below.
Tcl Command
system
Parameters
Example
system ls
system pwd
!pwd
TCLMODE
TCLMODE
(Setup / LEC Mode)
Switches from Conformal command entry mode (VPX mode) to Tcl command entry mode.
VPX mode is the default command mode.
TCL
For more information about native Tcl commands, refer to the public Tcl manual, which is
widely available online. Conformal Tcl commands are discussed in detail in the Conformal
Equivalence Checking User Guide.
Tip
To start the Conformal software in Tcl mode without executing any initialization
script, run the following command at a UNIX system prompt:
UNIX% lec -tclmode
Tip
In the Tcl command entry mode, you can save report data to a file using the
redirection command. For example, the following command saves the gate report
data to a file named gate.out:
TCL_SETUP> report_gate -type dff > gate.out
Related Command
VPXMODE
Displays the results of the key point matching based on the user-specified renaming rules.
Use this command to obtain a quick summary of how well the key points will be mapped
based on the specified renaming rules. Test new and existing rules.
Tcl Command
test_renaming_rule
Parameters
-Design Tests the renaming rules on the entire design. This argument
instructs Conformal to display a summary of the Golden and
Revised pairs and groups and Golden and Revised single un-
grouped key points for the entire design.
-NOprint Do not display the key point pairs, un-grouped single key points,
or grouped key points. This is the default.
-Print Displays key points as follows:
Single Un-grouped single key points
Pair Key point pairs
Group Grouped key points
string A string that the renaming rule uses as an example.
-GATE_id <gate_id> Tests renaming rules on the specified gate.
-All Tests all renaming rules within the given defaults. This is the
default.
-NEw_rule <string> <string>
A new renaming rule. The first string is the pattern to be
matched; the second string is the substitution pattern.
-File <filename> Writes the results to the specified file.
-REPlace Replaces the above file, if it exists.
-MAp Tests the renaming rules on key points that will be mapped.
This is the default.
-TYpe Tests renaming rules for all key points of the specified type.
This is the default.
-NOTYpe Tests renaming rules for all key points except the specified
types.
The available types are as follows:
PI Primary Inputs
E TIE-E gates
Z TIE-Z gates
DFF D flip-flops
DLAT D-latches
CUT Artificial gates for breaking combinational
feedback loops
BBOX Blackboxes
PO Primary Outputs
-MOdule Tests the renaming rules on the modules in the design.
-PIn Tests the renaming rules on pin names of blackboxes.
-BBox <module_name> Tests the pin renaming rule on the specified blackbox module.
The default is to test all blackboxes.
-RULE_USAGE Displays the number of matches for the specified string. This
option is turned on by default.
-NORULE_USAGE Do not display the number of matches for the specified
renaming rule.
-SORTNAme When this option is used with the -print option, the results
appear in alphabetical order by name.
-Both Tests the renaming rules on both the Golden and Revised
designs. This is the default.
-Golden Tests the renaming rules on the Golden design.
-Revised Tests the renaming rules on the Revised design.
-VErbose Displays both the original key point name and the renamed key
point.
The following is sample output for the TEST RENAMING RULE command.
================================================================================
Test name mapping results
--------------------------------------------------------------------------------
Golden-Revised pair: 147
PI: 65
PO: 5
DFF: 32
DLAT: 1
BBOX: 1
Z: 43
Golden-Revised group: 1 (22 key points)
Golden single: 33
Reachable: 32
Unreachable: 1
Revised single: 2
Reachable: 1
Unreachable: 1
================================================================================
Renaming rule usages:
================================================================================
Matches Name Rename pattern
--------------------------------------------------------------------------------
32 rule1 df_reg1_reg\[%d\]
0 rule2 df_reg\[%d\]
================================================================================
The TEST RENAMING RULE command does a trial of the user-specified renaming rules on
all of the keypoints and displays the potential results of the MAP KEY POINTS command and
the number of key points the renaming rules should be able to successfully rename.
For this example, there are 147 matching key points; this indicates that the MAP KEY POINTS
command should be able to map 147 key points.
For the other areas (Golden-Revised group, Golden-single, and Revised-single), use
additional renaming rules to try and convert them into mappable key points (Golden-Revised
pair).
This section of the report displays the key points that the MAP KEY POINTS command should
be able to map given the current renaming rules. Note: In some cases, the mapping process
determines that some key points are unreachable, resulting in a mismatch between the
number reported by TEST RENAMING RULE and REPORT KEY POINTS. Where:
■ "Golden-Revised pair" refers to the total number of key points that name-match based
on the user-specified renaming rules. The key points are then listed by type (PI, PO, DFF,
DLAT, and BBOX).
■ "Golden-Revised group" refers to the number of groupings that are similar based on
functional mapping, but do not have exact matching names. This number is followed by
the total number of key points from all groups. To view the groupings, use the following
command:
test renaming rule -design -print group -file <group.log> -replace
■ "Golden-single" and "Revised-single" refers to key points that have no corresponding key
points in the other design. To view the individual key points, use the following command:
test renaming rule -design -print single -file <single.log> \ -
replace
This section of the report lists the renaming rules and the number of key points matched by
that renaming rule. Rules are listed in the order of entry; the renaming engine applies
renaming rules in the order they were entered and adds +1 to the success count when it
successfully renames a key point. Therefore, if a previous renaming rule covers a latter one,
the latter one will not be applied during mapping.
If a renaming rule is listed with zero matched key points, it means the renaming rule cannot
find the specified search pattern (either the renaming rule was entered incorrectly or previous
renaming rules changed the key point name).
Examples
■ The following command displays the summary results of the renaming rules on the
designs:
test renaming rule -design -all
■ The following command displays a list of all Golden/Revised un-grouped single key
points:
test renaming rule -design -print single
■ The following command displays a list of all Golden/Revised grouped key points:
test renaming rule -design -print group
■ The following command displays a list of all Golden/Revised pair key points:
test renaming rule -design -print pair
■ The following command writes a list of all Golden/Revised grouped key points to a file:
test renaming rule -design -print group -file group_list
■ The following command displays the summary results of the renaming rule on the
designs with a new rule:
test renaming rule -design -new_rule <string> <string>
■ The following command displays the summary results of the renaming rules applied to a
sample string:
test renaming rule <string> -all
■ The following command displays the summary results of the new renaming rule applied
to a sample string:
test renaming rule <string> -new_rule <string> <string>
Related Commands
ADD RENAMING RULE
UNIQUIFY
UNIQuify
<module_name ...> | <-ALL [-Library | -NOLibrary][-AUTO_MATCH | -
NOAUTO_MATCH]>
[-Force]
[-USE_RENaming_rules]
[-Summary | -Verbose]
[-Golden | -Revised]
(Setup Mode)
Makes the specified module, which has multiple instances, unique. This command lets you
remedy the "incompatible" instantiations warnings during hierarchical script generation. If
Conformal does not make the modules unique, they are not included in the hierarchical dofile.
Use this command after you have matched the instance hierarchies between the Golden and
Revised designs, and before any commands with pathname-based specifications.
UNIQUIFY renames modules only when complementing designs have matching instance
names and matching instance hierarchies. If this command attempts to rename a module
name, but its instance has a difference hierarchy between the Golden and Revised designs,
the renaming will fail. To ensure that the hierarchy matches between the designs, it is
recommended that you match the hierarchy between the Golden and Revised designs
(FLATTEN -MATCHHierarchy) before you use UNIQUIFY. Note that in the ECO flow, the
module and instance names should not be changed in the golden G1 netlist. Therefore, the
FLATTEN and UNIQUIFY commands should only be applied to the revised G2 netlist in that
particular use case.
Use UNIQUIFY before any commands with pathname-based specifications so that the effect
can be propagated during hierarchical constraint extraction.
should be:
SETUP> uniquify -all -nolib
Uniquified 1 instance(s) referring to module 'sub_0' in Golden
SETUP> add primary input usub_0/net -golden
SETUP> add pin constraint 0 usub_0/net -golden
When using hierarchical compare for abort resolution, this command allows you to include
more modules in the hierarchical dofile, therefore reducing the compare complexity of helping
resolve aborts.
For more information, see Hierarchical Comparison for Abort Resolution in the Conformal
Equivalence Checking User Guide.
Tcl Command
uniquify
Parameters
Example
The following command example creates a hierarchical dofile script named hier.do
containing the compare script for the submodules and the root module, then runs hierarchical
compare. This is can help in resolving aborts.
...
uniquify -all
write hier_compare dofile hier.do
run hier_compare hier do
Related Commands
RESOLVE
RUN HIER_COMPARE
USAGE
USAge
[-Benchmark]
[ | -Elapse | -Delta]
[-MIN_COMMAND_SECONDS <double>]
[-NOAuto | -Auto]
[-Remote]
[-WATCHER [-DETAILED]
[-HOST]
[-PSTACK]
[-PERIOD <period>]
[-REPEAT <times|INF>
[-CHECK <resource name> <minimum value required>]]
(Setup / LEC Mode)
Displays the total CPU run time and current memory use since you started Conformal.
To help identify and track usage, LEC automatically calls this command for commands like
WRITE HIER_COMPARE DOFILE, which can potentially have a long run time.
Tcl Command
usage
Parameters
VALIDATE CIRCUIT
VALidate CIrcuit
[-ASM | -NOASM]
[-BBOXSCRipt <filename>]
[-DOfile <filename> ...]
[-MODule <module name>]
[-POWERPIN_TO_INput | -NO_POWERPIN_TO_INput]
[-POWERPINs <pin_name 0> <pin_name 1> ... <pin_name N>]
[-PRESERVE_MODEL_OPTIONs | -NO_PRESERVE_MODEL_OPTIONs]
[-Revised | -Golden]
(Setup Mode)
Checks circuit libraries and custom blocks (when applicable), and enables equivalence
checking on the full integrated circuit design. Use this command at the integrated-circuit level
for RTL or Gate to final circuit. This application is for checking the consistency of pre-defined
libraries during design verification.
Important
Do not use this command for validating the library itself. To validate library itself, use
the VALIDATE LIBRARY command instead.
For both the Golden and Revised designs, refer to the same library so that any
inconsistencies at the library cell level will not affect the equivalence checking on design level.
After which, all the library cells under this checking will be replaced by their counterpart
reference cells.
Note: You can use this to check a verified circuit. However, you need a Conformal XL license
to diagnose logic abstraction and errors that relate to library comparisons.
Tcl Command
validate_circuit
Parameters
Tip
If there are any unexpected results, you can use this
option to revert back to the functionality of the 6.2
release and earlier.
-BBOXSCRipt <filename>
Creates a dofile with the specified name that blackboxes all
validated cells for structural verification, which is more
accurate than logical verification.
-DOfile <filename> ...
Specifies the name of the dofile that was used to verify all
custom blocks so that they can be re-checked.
If a custom module has not been verified yet, blackbox it
before running the VALIDATE CIRCUIT command.
VALIDATE CIRCUIT can check for consistency in custom
blocks, but it cannot verify custom blocks. Use Conformal
GXL to verify custom blocks.
-MODule <module name>
Validates the specified module.
By default, the software validates the root module. Use this
option to validate a module other than the root module.
Note: The software validates only the topmost library and
custom cells (that exist in the reference side) that are used by
the specified module.
-POWERPIN_TO_INput
Specifies that if there are power pins that are input/output
pins, they will be changed to input pins before validation. This
is the default.
-NO_POWERPIN_TO_INput
Specifies that power pins that are input/output pins will NOT
be changed to input pins before validation.
-POWERPINs <pin_name 0> <pin_name 1> ... <pin_name N>
Related Commands
READ DESIGN
READ LIBRARY
VALIDATE LIBRARY
VALidate LIbrary
[-ANALYZE_SEtup]
[-ASM | -NOASM]
[-NOGOLPINDir | -GOLPINDir]
[-NOSPIce | -SPIce]
[-POWERPIN_TO_INput | -NO_POWERPIN_TO_INput]
[-POWERPINs <pin_name 0> <pin_name 1> ... <pin_name N>]
[-PRESERVE_MODEL_OPTIONs | -NO_PRESERVE_MODEL_OPTIONs]
[-SKIP_EXTRA_CELL]
[-Revised | -Golden]
(Setup Mode)
Note: This requires a Conformal XL and Conformal GXL license, where noted.
Compares all top-level cells with matching names. Conformal can auto-abstract the modules
on the SPICE side before comparison using the -spice option. This application is for library
verification during library design. This command supports any combination of Verilog, Liberty,
and SPICE.
Important
To abstract SPICE modules, you must have a Conformal GXL license.
Tcl Command
validate_library
Parameters
Tip
If there are any unexpected results, you can use this
option to revert back to the functionality of the 6.2
release and earlier.
-NOGOLPINDir Do not copy the pin directions from the Golden design to the
Revised design. This is the default.
-GOLPINDir Copies the pin directions from the Golden design to the Revised
design. This is for all pins within the library cells being validated.
-NOSPIce Abstracts and validates the modules that are not SPICE. This
is the default.
Note: This option requires a Conformal GXL license.
-SPIce Abstracts and validates the SPICE modules.
Note: This option requires a Conformal GXL license.
-POWERPIN_TO_INput Specifies that if there are power pins that are input/output pins,
they will be changed to input pins before validation. This is the
default.
-NO_POWERPIN_TO_INput
Specifies that power pins that are input/output pins will NOT be
changed to input pins before validation.
-POWERPINs <pin_name 0> <pin_name 1> ... <pin_name N>
Defines names for the pin(s) that are used as extraneous power
pins, which are ignored during cell verification. For multiple
power pins, each pin name must be separated by a space.
Use the ADD PIN CONSTRAINTS command to tie power pins
to 1 and ground pins to 0.
-PRESERVE_MODEL_OPTIONs
Preserves any user-defined settings made prior to this
command. This is the default.
This option disables any flattening options that VALIDATE
LIBRARY sets by default.
-NO_PRESERVE_MODEL_OPTIONs
Do not disable any flattening options that VALIDATE LIBRARY
sets by default.
-SKIP_EXTRA_CELL Skips reporting the cells that only exist in the Golden or Revised
design.
-Revised Validates the Revised database. This is the default.
-Golden Validates the Golden database.
Related Command
VALIDATE CIRCUIT
VERSION
VERsion
(Setup / LEC Mode)
Displays the current version release number of Conformal. You can use this command after
the SET LOG FILE command so the version becomes a part of the transcript log. In this way,
you record the Conformal version that created your results. This command is also helpful
when you use the SAVE SESSION and RESTORE SESSION commands, because you must
use the same Conformal version when you restore a session.
Tcl Command
version
Related Commands
RESTORE SESSION
SAVE SESSION
VPXMODE
VPXMode
(Setup / LEC Mode)
Switches from Tcl mode to native Conformal command entry mode (VPX mode). VPX is the
default command mode.
Important
When issuing this command in the Tcl command interpreter, you must type this in
lowercase. For example:
TCL_LEC> vpxmode
Tip
In VPX mode, you can save report data to a file using the redirection command. For
example, the following command saves the gate report data to a file named
gate.out:
SETUP> report gate -type dff > gate.out
Tcl Command
vpxmode
Related Command
TCLMODE
This command generates a file that contains a wrapper for each blackbox instance in your
design whose module name matches those in the specified pattern list and generates the
scripts necessary for performing synthesis and generating the synthesized models.
You can also enable automatic blackbox substitution using the -auto_substitute option.
This option executes the synthesis executable (specified by SET HDL OPTIONS -
synthesis_executable) and automatically substitutes the blackbox models with the
synthesized models.
Tip: Instead of using the ADD NOTRANSLATE MODULES command to treat particular cells as
blackboxes, you can use the set undefined cell -black_box command prior to
reading in the design and library (through the READ DESIGN and READ LIBRARY
commands) to treat all undefined cells as blackboxes.
Tcl Command
write_blackbox_wrapper
Parameters
-DIRectory <dirname> Specifies the working directory for this command. When
this command is used, the tool creates a RUN directory
under this working directory that will contain all the files
generated by this command.
If you do not specify this option, the tool creates a
working directory called CFM_BBOX_DIR under your
current working directory. All the files will be stored under
this directory, in a subdirectory called RUN.
If you specify a project directory, by default, the working
directory CFM_BBOX_DIR is created underneath the
project directory instead.
Each time this command is used, the tool creates a new
RUN directory under the working directory (appended by
*.<integer>, where integer is the number of times
the command has been issued). For example, RUN.3.
-NOAUTO_substitute Disables automatic blackbox substitution. This is the
default. See sample flows below.
-AUTO_substitute Enables automatic blackbox substitution. With this option,
the tool automatically performs synthesis using the
corresponding synthesis script and substitutes the
blackbox models with the synthesis models from the
synthesis run.
Examples
Sample module:
<<< gol.v>>>
module design(clk, rst, cs, wr, rd_addr, wr_addr, din, dout);
input clk, rst, cs, wr;
input [2:0] rd_addr, wr_addr;
input [4:0] din;
output[4:0] dout;
The following illustrates the default flow for WRITE BLACKBOX WRAPPER (with automatic
blackbox substitution disabled):
1. Specify that Conformal treat undefined cells as blackboxes.
> set undefined cell black_box
Note: This command also generates synthesis script template file dir/RUN/
synth.tcl.
4. Use the dir/RUN/synth.tcl script with your own synthesis tool to generate
dir/RUN/_DW_ram_r_w_s_dff_5_8_0.g.v.
5. Read the newly created dir/RUN/_DW_ram_r_w_s_dff_5_8_0.g.v file into the
design.
> read design -append dir/RUN/*.g.v
6. Substitute the old module of blackbox instance ram with the new module
_DW_ram_r_w_s_dff_5_8_0_DW_ram_r_w_s_dff_5_8_0_0(dir/RUN/
_DW_ram_r_w_s_dff_5_8_0.g.v:229).
> substitute blackbox wrapper DW*
The following illustrates the flow for WRITE BLACKBOX WRAPPER with automatic blackbox
substitution enabled:
1. Specify that Conformal treat undefined cells as blackboxes.
> set undefined cell black_box
Related Command
SET HDL OPTIONS
Writes compared points information to a file, which you can use to add a specific class and
type of compared points to a compare list. This file can then be read in directly using the
DOFILE command.
Tcl Command
write_compared_points
Parameters
-SHOW_ORIG_RTL_NAMES
Writes out the DFF/DLAT compared point names without the
applied SET NAMING RULE - REGISTER <STRING> setting.
-TCLmode Use only Tcl commands in the file.
-TYpe Writes out the type of compared points. By default, the
command writes out all types.
All Writes all compared point types. This is the
default if you do not specify the -TYpe
option.
PO Writes the compared points of the primary
outputs.
DFf Writes the compared points of the D flip-
flops.
DLat Writes the compared points of the D-latches.
Bbox Writes the compared points of the
blackboxes.
Cut Writes the compared points for artificial
gates that break combinational loops.
Related Commands
DOFILE
WRITE DESIGN
WRIte DEsign
<filename>
[ | -ALL | -Module <module_name> | -BBOX_only]
[-ENABLE_BLT_IN_DW_WRITE | -DISABLE_BLT_IN_DW_WRITE]
[-GZip]
[-Library]
[-REPlace]
[-RTL]
[-SKIP_Undefined]
[-STRC_VIEW]
[-TEST_VIEW]
[-Used]
[-Golden | -REVised]
(Setup / LEC Mode)
Writes out the Golden or Revised design in Verilog format to examine how Conformal
abstracts RTL descriptions into gate-level descriptions.
Tilde: Use the tilde "~" character in the file path to replace the path to the user login home
directory.
For information on how this command handles files with encrypted/protected modules, refer
to the "IP Protection" section of the READ DESIGN command.
Tcl Command
write_design
Parameters
-Used Writes out the specified modules and all the referenced
modules, including modules in the design space.
-Golden Writes out the Golden design only. This is the default.
-REVised Writes out the Revised design only.
Related Command
READ DESIGN
This command writes the extended mapping information to a file. This file can be used to
accelerate setup and mapping in Conformal ECO or LEC second run.
Tcl Command
write_extended_mapping
Parameters
Related Commands
ANALYZE EXTENDED MAPPING
Writes out a hierarchical dofile script that verifies the two hierarchical designs starting from
the lower-level modules and progressing to the top root module. All modules not output to the
hierarchical dofile script will be flattened into their parent modules for comparison.
Use the tilde character (~) to shorten the path of the file.
This command also generates a dofile script to compare two libraries, such as a Liberty and
Verilog library. Use the -all option to write all library models to the dofile script for
comparison.
Notes:
■ The modeling options specified using the SET FLATTEN MODEL command can affect
the flattened netlists used for constraint extraction with the WRITE HIER_COMPARE
DOFILE command. For example, enabling -SEQ_CONSTANT can propagate constant
data through latches and registers, thereby extracting better quality of constraints in the
generated hierarchical dofile.
■ Hierarchical comparison is also useful in resolving aborts. See the UNIQUIFY command
for more information.
■ Running this command can result in a long run time. To help track the CPU run time and
current memory usage, LEC automatically calls the USAGE command when WRITE
HIER_COMPARE DOFILE is used.
Tcl Command
write_hier_compare_dofile
Parameters
Examples
■ The following illustrates a static hierarchical comparison; it reads in the two hierarchical
designs, writes out the hierarchical dofile script, and compares design hierarchies:
read library golden.lib -verilog -golden
read design golden.v -verilog -golden
read library revised.lib -verilog -revised
read design revised.v -verilog -revised
write hier_compare dofile hier.do -replace
dofile hier.do
■ The following reads in a synthesis library and simulation library, writes out all of the library
models, and compares library hierarchies:
read design syn.lib -liberty -golden
read design simulation.v -verilog -revised
write hier_compare dofile lib_ver.do -replace -all
dofile lib_ver.do
■ In the following command, the default compare command is replaced with two
commands during each module comparison, set compare effort low and
compare -abort_stop 1 -noneq_stop 1:
write hier_compare dofile hier.do -compare_string \
"set compare effort low; compare -abort_stop 1 -noneq_stop 1"
■ During hierarchical comparison, the logfile will contain the following messages:
// Running Module modB and modB
// Command: set root module modB -Golden
// Command: set root module modB -Revised
// Command: set module property -instance /a0/b0 -Golden
// Command: set module property -instance /a0/b0 -Revised
// Command: report black box -NOHidden
// Command: set system mode lec Applying top-level pathname-based constraints
// Command: add primary input scan_en -Golden
// Command: add pin constraints 0 scan_en -Golden End of top-level pathname-based constraints
// Processing Golden ...
// Modeling Golden ...
...
Related Commands
ADD NOBLACK BOX
ANALYZE HIER_COMPARE
READ DESIGN
READ LIBRARY
RUN HIER_COMPARE
UNIQUIFY
USAGE
WRITE LIBRARY
WRIte LIbrary
<filename>
[-GZip]
[-Module <module_name>]
[-Verilog]
[-REPlace]
[-Golden | -REVised]
(Setup / LEC Mode)
Writes out the Golden or Revised library to a Verilog file. The default is to write out the
library as functional Verilog model descriptions.
Use this command to examine how Conformal abstracts complex UDP library models.
Use the tilde character (~) to shorten the path of the file.
Tcl Command
write_library
Parameters
Related Command
READ LIBRARY
Writes the mapped point information to a file. If the comparison needs to be done at a later
time, you can use this command to accelerate the mapping process.
Tcl Command
write_mapped_points
Parameters
Related Commands
ADD MAPPED POINTS
Writes memory primitives to a file. Use this command to retrieve information for simulation.
For additional information about memory primitives, refer to the "Memory Primitive Data
Sheet" located at <install_dir>/doc/MEM_datasheet.pdf.
Use the tilde character (~) to shorten the path of the file.
Note: The wildcard (*) represents any zero or more characters in module names.
Tcl Command
write_memory_primitive
Parameters
-OPTionsdef <filename1>
Writes parameter option definitions to a separate file. This will
write the ‘define statements, which are options to available
parameters, from the memory primitives to a separate file.
-REPlace Replaces the existing file.
Related Command
READ DESIGN
Writes out a partition dofile script based on the key point names specified with the ADD
PARTITION KEY_POINT command. The number of compare iterations is based on whether
the key point names have all-pattern, one-hot, or one-cold constraints.
Use the tilde character (~) to shorten the path of the file.
Tcl Command
write_partition_dofile
Parameters
-Map <filename> Uses the specified file for key point mapping. (You must use the
WRITE MAPPED POINTS command before using this option.)
-PREPEND_String <string>
Appends any string of commands to the partition dofile script
before key point comparison for each module.
Use a semicolon (;) to separate commands.
Enclose the string of prepend commands with double quotes
(see "Examples" section below).
-Replace Replaces the existing file.
-Usage Executes the USAGE command after each comparison and at
the end of the partition dofile.
Example
write partition dofile partition.do -replace
write partition dofile ptn.do -append_string "usage" -prepend_string "report
unmapped points -notmapped" -replace
In the following command, the default compare command is replaced with two commands
during each module comparison, set compare effort low and compare
-abort_stop 1 -noneq_stop 1:
write partition dofile -compare_string "set compare effort low; compare -abort_stop
1 -noneq_stop 1"
Related Commands
ADD PARTITION KEY_POINT
Writes the rule violations into a rule file. Use this command the first time you run a session.
For later runs, exclude the violations already flagged with the read rule check -exclude
<filename> command.
Use the tilde character (~) to shorten the path of the file.
Tcl Command
write_rule_check
Parameters
Report Columns
This command generates a report listing the rule violations. For example:
Rule Type Filename Line Col Info Library Module Object
RTL6.1 57 test.v 20 22 16 0 test (null)
where:
■ Rule: Lists the rule name.
■ Type: Lists the integer value of the rule type. Each rule has a unique rule name and a
unique type.
■ Filename: Name of the file where the violation occurs.
■ Line: Line number where the violation occurs.
■ Col: Column number where the violation occurs.
■ Info: Set of internal flags.
■ Library: When 0, the rule violation is in the design space. When 1, the rule violation is in
the library space.
■ Module: Name of the module where the violation occurs.
■ Object: Text string used to display the message of the reported rule violation.
Examples
In the following example, the second report rule check will not report any rules.
read design g.v -golden
read design r.v -revised
write rule check rule.g -golden -replace
write rule check rule.r -revised -replace
read design g.v -golden -replace
read design r.v -revised -replace
report rule check -verbose -both
read rule check rule.g -exclude -golden
read rule check rule.r -exclude -revised
report rule check -verbose -both
Related Command
READ RULE CHECK
WRITE TEMPLATE
WRIte TEmplate
[-Outfile <string>]
[-show_tags]
[-list]
[tag_name ...]
(Setup / LEC Mode)
Views and writes the Conformal template scripts with the necessary commands and
attributes. To see all the available Conformal template scripts, run the command
write_template with no option
Tcl Command
write_template
Parameters
-Outfile <string> Specifies the file name to write the template script.
-show_tags Lists out all possible tags.
-list Displays all the available templates.
tag_name ... Specifies the tag to select one template; If the tag matches with
the unique template name, it will write out that template;
otherwise, it will list out all the matching templates. User then
can select the specified template to view or write out.
Writes out verification information to the specified directory. This command is enabled by the
SET VERIFICATION INFORMATION command.
Tcl Command
write_verification_information
Parameters
verification_information_directory
Writes the verification information to the specified directory.
By default, this command uses the
verification_information_directory specified by the
SET VERIFICATION INFORMATION command.
-COMpute Indicates that computation of verification information is needed.
-GOLden <label> Specifies which set of information to write out for the golden
side.
-REVised <label> Specifies which set of information to write out for the revised
side.
Example
This command can be used with READ VERIFICATION INFORMATION to compute a new
set of information that can be used to optimize new verification.
Suppose verification information for RTL versus G1 netlist is rtlg1.uvi, and verification
information for G1 versus G2 netlists is g1g2.uvi. Then, verification information that can be
used for directly verifying RTL versus G2 can be computed as:
set verification information rtlg2.uvi
read verification information rtlg1.uvi -golden rtl -revised g1
read verification information g1g2.uvi -golden g1 -revised g2
write verification information -golden rtl -revised g2 -compute
A special case is to get the information for a new verification with golden and revised netlists
swapped:
set verification information g1g2.uvi
read verification information g1g2.uvi -golden g1 -revised g2
write verification information -golden g2 -revised g1 -compute
Related Commands
READ SETUP INFORMATION
3
ECO Command Reference
This chapter describes the Encounter® Conformal® ECO commands. The commands are
presented in alphabetical order.
■ ADD ECO CUTPOINT on page 911
■ ADD ECO PIN on page 913
■ ADD SPARE CELL on page 915
■ ANALYZE ECO on page 917
■ APPLY PATCH on page 924
■ CHECK ECO SETUP on page 927
■ COMPARE ECO HIERARCHY on page 928
■ DELETE ECO CUTPOINT on page 930
■ DELETE SPARE CELL on page 932
■ OPTIMIZE PATCH on page 933
■ REPORT ECO CHANGES on page 941
■ REPORT ECO CUTPOINT on page 945
■ REPORT ECO GATEDCLOCK on page 947
■ REPORT ECO HIERARCHY on page 948
■ REPORT ECO PATCH on page 950
■ REPORT ECO PIN on page 951
■ REPORT ECO SCAN INPUT on page 952
■ REPORT ECO TESTENABLE INPUT on page 953
■ REPORT MISMATCHED PIN on page 954
Adds an ECO cutpoint. The cutpoint will be used by the ANALYZE ECO command and is
intended to help reduce the complexity of the ECO analysis by reducing the size of the ECO
patch.
Tcl Command
add_eco_cutpoint
Parameters
Example
add eco cutpoint CUT1 -GOLDEN + U30/g1 -REVISED - U13/g1
add eco cutpoint CUT2 -GOLDEN U31/g1 - U32/g2 -REVISED + U13/g1
analyze eco cutpoint
analyze eco patch.v
Related Commands
ANALYZE ECO
This command requires an ECO license and works only on the Golden design.
Adds a pin to a module. If the Revised module has extra ports, you can use this command to
add new pins to the Golden module. You should add the extra pins before running the WRITE
HIER_COMPARE DOFILE command.
Tcl Command
add_eco_pin
Parameters
Examples
■ The following command adds wr_req input port and data[15:0] input bus to module
mod_A
■ This example shows how the command's -force option affects the following design:
module top(x,y);
wire z;
endmodule
❑ The following command will error out because there is a conflict between the net z
and the new port z:
add eco pin -output top z
❑ The following command will not error out and net z will be renamed z_1:
add eco pin -output top z -FORce
Related Commands
ANALYZE ECO
Adds the spare cells or freed cells as the available cells for the OPTIMIZE PATCH command.
When using OPTIMIZE PATCH with the -usespare option, the spare cell count for each cell
type is considered. When using OPTIMIZE PATCH with the -def option, the spare cell
instances are considered for location-aware optimization.
Tcl Command
add_spare_cell
Parameters
-DEFfile <filename> Specifies the DEF filename (compressed gzip format is alo
supported). This searches for the spare cell in the DEF file. By
default, the spare cell is searched for in current hierarchy.
-FReedcell Specifies that freed cells will be used for mapping.
-SParecell <cell_instance_name*> ...
Specifies the spare cells to be added. This accepts wildcards.
-GAFiller <cell_instance_name*> ...
Specifies the gate array filler to be added. This accepts
wildcards.
Related Commands
DELETE SPARE CELL
OPTIMIZE PATCH
ANALYZE ECO
ANAlyze ECo
<filename>
[-REPlace | -APPend]
[-EFFort <HIGH | MEDIUM | ULTRA>]
[-POST_OPTImization]
[-CONE_SWAP]
[-CONNECT_ICG_TESTENABLE <AUTOmatic | MANual>]
[-CREATE_DB [R1R2 | R1G1 | R2G2]<db_filename>]
[-HIERarchical [-MODule <module name>][-ECOPIN_dofile <file_name>]]
[-IMPORT_DB <db_filename>+]
[-PLACEment_driven]
[-PRESERVE_clock | -NOADD_ICG]
[-THREADS <integer>[,<integer>]]
[-CPULIMIT <integer>]
[-USE_BUF_CHAIN_Source]
(LEC Mode)
Analyzes the ECO change in the Revised root module comparing to the Golden root module.
The logic change is written to the specified patch file, which contains the Verilog module with
the port names corresponding to the nets in the Golden design.
This command also enables the creation of the ECO cutpoint database (-create_db
option). For more information on the usage of this command, refer to the "ECO Cut Point
Flow" section of the ECO User Guide.
Note: Only the logic cone under NONEQ points are analyzed by the command.
Tcl Command
analyze_eco
Parameters
-CPULIMIT <integer> Specifies the run time limit (in seconds) for high and ultra
effort level. After the specified time limit, the effort level is
lowered to medium for the remainder of the command. The
default is value 36000.
-USE_BUF_CHAIN_SOURCE If the driver of the patch is a buffer/inverter chain, use the
source of the buffer/inverter chain as the driver for the
patch.
Use this when you need to improve the timing of the
ECOed (G3) netlist
Examples
The following illustrates the usage of the -create_db and -import_db options.
analyze eco -create_db r1r2 r1r2.db
//Creates the R1R2 database
analyze eco -create_db r1g1 r1g1.db -import_db r1r2.db
//Creates the R2G2 database and imports the R1R2 database.
analyze eco -create_db r2g2 r2g2.db -import_db r1r2.db
report eco cutpoint -auto -file cutpoint.do -import r1g1.db r2g2.db
analyze eco cutpoint
dofile cut.do
Related Commands
ADD ECO PIN
ANALYZE ECO
ANALYZE HIER_COMPARE
Analyzes the ECO cutpoints and their effect on the existing nonequivalent points. For more
information on the usage of this command, refer to the "ECO Cut Point Flow" section of the
ECO User Guide.
Note: This command is available for beta testing. The options and features described may
change prior to final release.
Tcl Command
analyze_eco_cutpoint
Parameters
None.
Related Commands
ADD ECO CUTPOINT
ANALYZE ECO
APPLY PATCH
APPly PAtch
[<module_under_ECO_name> <patch_module_name> | -AUTO]
[-KEEPHierarchy | -NOKEEPHierarchy]
[-NETnaming <format_string>]
[-INStancenaming <format_string>]
[-BBOXnaming <format_string>]
[-SEQuentialnaming <format_string>]
[ | -KEEPFREED | -TIEFREED0 | -TIEFREED1]
[-FREESCAN]
[-FREENONSCAN <0|1>]
[-STITCHSCAN]
[-SHIFTEnable <net_name> <0|1>]...
[-Golden | -Revised]
(Setup Mode)
Applies the ECO change specified in the patch module, generated by the ANALYZE ECO
command, to the module under ECO. The patched module can be written out with the WRITE
DESIGN command.
Note: The patch generated by the ANALYZE ECO command can contain unmapped
primitives.
Tcl Command
apply_patch
Parameters
<module_under_ECO_name>
Specifies the name of the module being changed for ECO.
<patch_module_name> Specifies the name of the patch module containing the ECO
changes.
-AUTO Automatically reads in and applies all patches that were created
with the ANALYZE ECO command in the current session.
-KEEPHierarchy Specifies that the ECO changes will be put in a submodule.
This is the default.
-NOKEEPHierarchy
Do not put ECO changes in a submodule.
-NETnaming <format_string>
Specifies the net naming format of the ECO nets. For example,
for eco_net_%d, the %d will be an integer that makes the net
name unique.
-INStancenaming <format_string>
Specifies the instance naming format of the ECO combinational
cells. For example, for eco_instance_%d, the %d will be an
integer that makes the instance name unique.
-BBOXnaming <format_string>
Specifies the naming format of the ECO blackboxes. For
example, eco_bbox_%s, where %s is the original blackbox
name.
-SEQuentialnaming <format_string>
Specifies the instance naming format of the ECO registers and
latches. For example, eco_%s, where %s is the original register
name.
-KEEPFREED Retains all freed instances and leaves input pins connected.
Freed instance will not be re-used for mapping the patch.
-TIEFREED0 Retains all freed instances and applies a value of '0' (tie low) to
the input pins of any freed instance.
-TIEFREED1 Retains all freed instances and applies a value of '1' (tie high) to
the input pins of any freed instance.
-FREESCAN Free up the DFFs reachable only by scan chain.
-FREENONSCAN <0|1> Do not free up the DFFs reachable only by scan chain, but tie
the non-scan related input pins of the DFFs to a constant. The
set and reset pins of the DFFs are not affected.
-STITCHSCAN Reconnect the scan chain if some DFFs are removed or some
submodule scan out connection are affected by ECO changes.
Note: In the case where DFFs are added, the newly-added
DFFs are not stitched.
-SHIFTEnable <net_name> <0|1>
Specify the scan chain is enabled when net value is 0 or 1.
Example
The following command automatically applies the ECO changes in the submodules of
modules under ECO:
apply patch -auto -keephierarchy
In addition to applying ECO changes, the following command frees up the DFFs that are
reachable only by the scan chain and reconnects the scan chain based on the given scan
chain configuration. The scan chain is enabled when test_mode and scan_enable are set.
apply patch -auto -keephierarchy -freescan -stitchscan -shiftenable test_mode 1 -
shiftenable scan_enable 1
Related Commands
OPTIMIZE PATCH
Performs ECO-related checks that will flag potential issues related to setup and offer potential
solutions early. For more information on this command and its usage, refer to the web
interface article ECO Setup Checks. To launch the web interface, use the "set web on"
command.
Tcl Command
check_eco_setup
Parameters
This command is used in the flattened ECO flow. Use this command in LEC mode, and after
running the ANALYZE HIER_COMPARE and COMPARE (complete flattened compare)
commands. This command takes the flattened compare results, along with the boundary
information, from ANALYZE HIER_COMPARE and breaks down the nonequivalent points to
their associated submodules. The flattened ECO flow eliminates any possible false
nonequivalent points that arise from the hierarchical compare process (such as boundary
optimization).
Note: The results that you get from this command might be different from the results of the
flattened comparison. For example, at the module level there might be only one
nonequivalent primary output. With the flattened compare, this same primary output might
fanout to 10 DFFs that result to 10 nonequivalent points.
Tcl Command
compare_eco_hierarchy
Parameters
Example
In the following example, COMPARE ECO HIERARCHY analyzes and breaks down the
boundaries identified by the ANALYZE HIER_COMPARE command:
setup> set flatten model -enable_analyze_hier_compare
setup> set system mode lec
lec> analyze hier_compare -dofile hier.do -constraints -FUNCTION_Pin_mapping -
eco_aware -replace
lec> add compare point -all
lec> compare
lec> compare eco hierarchy
lec> report eco hierarchy -hierarchy
lec> analyze eco patch.v -hierarchical -ecopin_dofile ecopins.do
lec> set system mode setup
lec> dofile ecopins.do
lec> apply patch -auto
Related Commands
ANALYZE HIER_COMPARE
ANALYZE ECO
Tcl Command
delete_eco_cutpoint
Parameters
Related Commands
ADD ECO CUTPOINT
ANALYZE ECO
Tcl Command
delete_eco_pin
Parameters
Related Commands
ADD ECO PIN
Deletes the spare cells or freed cells that were added with the ADD SPARE CELL command.
Tcl Command
delete_spare_cell
Parameters
Related Commands
ADD SPARE CELL
OPTIMIZE PATCH
OPTIMIZE PATCH
OPTimize PAtch
-WORKdir <working_directory>
<-LIBrary <library_file_list> | -LIBSETUPscript <tcl_script>>
[-SYNExec <synthesis_executable>]
[-SDC <sdc_file_list>]
[-VERbose]
[-NOKEEPHierarchy | -KEEPHierarchy]
[-CLEANUP]
[-AVOID <cell_name>*]
[-USE <cell_name>*]
[-NETnaming <format_string>]
[-INStancenaming <format_string>]
[-BBOXnaming <format_string>]
[-SEQuentialnaming <format_string>]
[-CAPtable <filename>]
[-USESPARE]
[-LEF <filename> ...]
[-DEF <filename> ...]
[-PLE]
[-MAPscript <filename>]
[-MMMC <mmmc_file>]
[-GAlibcell <cell_name*> ...]
[-1801 <1801_filename>]
[-CPF <cpf_filename>]
[-RELATIVE2CWD]
[-NOUSETIEcell]
[-PRELIBscript <script_name>]
[-PRESYNscript <script_name]
[-POSTSYNscript <script_name>]
[-SPLIT_non_structure <AUTO|NETLIST_ONLY|STRUCT_NETLIST_ONLY>]
[-SUPPRESS_SDCError]
[-PREMASKPHYsical [-PLACEscript <script_file_name>]]
[-ALLOW_FC_MF]
[-NOFLATTEN_SMALL]
[-ALLOWTIECELLINVersion]
[-QRCtech <filename>]
(Setup Mode)
Writes out a Genus script (cfm_eco_rc.tcl) in the working directory that will optimize the
patches and execute the script.
After OPTIMIZE PATCH successfully completes, the ECO design will be in memory and can
be written out. The optimized patches will be in the working directory.
Important
Before running this command, you must run the APPLY PATCH -keephierarchy
command.
Tcl Command
optimize_patch
Parameters
-WORKdir <working_directory>
Specifies the name of the working directory for the
optimized patches.
-LIBrary <library_file_list>
Specifies the name of the library files.
If the library name contains a relative path, the path should
be relative to the directory declared in -workdir.
Alternatively, you can use the -LIBSETUPscript option
to provide a file that specifies the libraries.
Note: Library files may also be specified in the CPF file. If
they are and the OPTIMIZE PATCH -library option is
used, both libraries will be read into Genus.
-LIBSETUPscript <tcl_script>
Specifies a library file setup script. Enables you to specify
libraries in a file rather than the -library option. If the
library name contains a relative path, the path should be
relative to the directory declared in -workdir.
-SYNExec <rc executable>
Specifies the path to the Genus or RTL Compiler
executable. If this is not specified, the software will use the
Genus command in your search path.
-SDC <sdc_file_list> Specifies the name of the SDC file(s) (compressed gzip
format is also supported).
If the SDC filename contains a relative path, the path
should be relative to the directory declared in -workdir.
Note: SDC files may also be specified in the CPF file. If
they are and the OPTIMIZE PATCH -SDC option is used,
both SDC’s will be read into Genus.
-VERbose Outputs all Genus messages. By default, the command
only outputs error messages.
-NOKEEPHierarchy Do not put ECO changes in a submodule. This is the
default.
-KEEPHierarchy Specifies that the ECO changes will be put in a
submodule.
-CLEANUP Deletes the generated files.
-AVOID <cell_name>* Avoids the specified library cells. This accepts wildcards.
When this option is used in combination with the -
USESPARE option, only the cell quantities of those cell
types not specified by -AVOID are available for mapping.
-USE <cell_name>* Uses the specified library cells. This accepts wildcards.
When this option is used in combination with the
-USESPARE option, only the cell quantities of those cell
types specified by -USE are used for mapping.
Note: The order that you specify the -AVOID and -USE
options is significant. For example:
avoids all the library cell types except NAND2 and INV2. If
these options are specified in the following order:
"-use NAND2 INV2 -avoid *"
-NETnaming <format_string>
Specifies the net naming format of the ECO nets. For
example, for eco_net_%d, the %d will be an integer that
makes the net name unique.
-INStancenaming <format_string>
Specifies the instance naming format of the ECO
combinational cells. For example, for eco_instance_%d,
the %d will be an integer that makes the instance name
unique.
-BBOXnaming <format_string>
Specifies the naming format of the ECO blackboxes. For
example, eco_bbox_%s, where %s is the original
blackbox name.
-SEQuentialnaming <format_string>
Specifies the instance naming format of the ECO registers
and latches. For example, eco_%s, where %s is the
original register name.
-CAPtable <filename>
Specifies the name of the CAP file. This option requires an
ECO GXL license.
-USESPARE Attempts to implement the ECO by mapping to spare
gates. This option requires an ECO GXL license.
-LEF <filename> ... Specifies the LEF file(s) (compressed gzip format is also
supported). This calls Genus physical synthesis to perform
location-aware spare-gate mapping.
This option requires an ECO GXL license.
-DEF <filename> ... Specifies the DEF file(s) (compressed gzip format is also
supported). This calls Genus physical synthesis to perform
location-aware spare-gate mapping.
This option requires an ECO GXL license.
-PLE Run Genus physical synthesis with LEF only. DEF is
optional.
This option requires an ECO GXL license.
-MAPscript <filename>
-PRESYNscript <script_name>
Specifies the script to run before each patch is
synthesized. The script can have two special procedures
defined in it: eco_pre_synthesis_cmd and
eco_post_synthesis_cmd. Both procedures accept
patch name as a parameter and return no value. The
procedures, if defined, are called by Genus before and
after synthesizing each patch module. The most common
use of the eco_pre_synthesis_cmd procedure is
setting attributes on the patch module. For example, this
script can contain the following lines:
# Set a root level attribute
set_attribute information_level 9 /
-POSTSYNscript <script_name>
Specifies the script to run after all patches are
synthesized.
-SPLIT_non_structure <AUTO|NETLIST_ONLY|STRUCT_NETLIST_ONLY>
AUTO: Split structural and non-structural modules into two
files and use different Genus parameter ’-netlist’ and
’-struct_netlist’ to elaborate. This is the default.
Examples
■ The following script reads in the original netlist and patch, then runs OPTIMIZE PATCH
to map and optimize the ECO changes:
read library typical.lib -liberty
read design top.gv patch1.v
apply patch mod1 mod1_eco -keephierarchy
optimize patch -workdir rc_work -library ../typical.lib
write design top.eco.gv -replace
Related Commands
APPLY PATCH
Reports the ECO changes. To report the ECO change with this command, the ECOs must
have been applied with the APPLY PATCH or OPTIMIZE DESIGN command.
Tcl Command
report_eco_changes
Parameters
-MODule <module_name>
Specifies the module to report. By default, the command
reports all nets and instances that have been added and
deleted.
-BUFFER <cell_name> Use the specified cell to replace assign statements.
-DETAIL_SEQ_REPort Report detailed information about sequential elements.
Displays a list of newly added ICG’s test-enable connection
information..
-FILE <filename> Redirects the output file.
-REPlace Replaces the file.
-SUMmary Shows a summary only. This is the default.
Related Commands
WRITE ECO DESIGN
Displays the list of ECO check violations. The ECO checks are available when the required
information is ready. Conformal ECO automatically executes ECO checks after the
commands set_system_mode lec, compare, compare_eco_hierarchy,
analyze_eco and write_hier_compare_dofile.
Note: All ECO check violations with a severity of "Ignore" are only reported with the -ignore
option.
Tcl Command
report_eco_check
Parameters
-Note Displays the ECO check violations that have a severity level of
note.
-Warning Displays the ECO check violations that have a severity level of
warning.
-Error Displays the ECO check violations that have a severity level of
error.
Related Commands
SET ECO CHECK
Reports on ECO cutpoints. For more information on the usage of this command, refer to the
"ECO Cut Point Flow" section of the ECO User Guide.
This command has three functions, it can report on added cutpoints, report on cutpoint
candidates, or report on suggested cutpoints.
Note: This command is available for beta testing. The options and features described may
change prior to final release.
Tcl Command
report_eco_cutpoint
Parameters
Related Commands
ANALYZE ECO
Tcl Command
report_eco_gatedclock
Parameters
Related Commands
ANALYZE ECO
Tcl Command
report_eco_hierarchy
Parameters
Related Commands
ANALYZE HIER_COMPARE
ANALYZE ECO
Displays a list of all user specified test-enable signals to drive the new ICGs with the SET
ECO ICG_TESTENABLE command.
Tcl Command
report_eco_icg_testenable
Related Commands
REPORT ECO ICG_TESTENABLE
Reports the ECO patch specified by the ADD ECO PATCH command.
Tcl Command
report_eco_patch
Reports the ECO pins specified by the ADD ECO PIN command.
Tcl Command
report_eco_pin
Parameters
Related Commands
ADD ECO PIN
Collects the scan input pins and reports their respective driving flops or signals.
Tcl Command
report_eco_scan_input
Parameters
Related Commands
This command collects the test-enable pins and reports their respective driving flops or
signals.
Tcl Command
report_eco_testenable_input
Parameters
Related Commands
Reports the mismatched pins between the specified modules of Golden and Revised
designs. When executed without any options, this command reports the mismatched pins
between the root module of the Golden and Revised designs.
Note: If there are any renaming rules before this command, it checks the pins after renaming.
Tcl Command
report_mismatched_pin
Parameters
-Golden <module_name>
Reports the mismatched pins between the specified modules of
the Golden design.
-Revised <module_name>
Reports the mismatched pins between the specified modules of
the Revised design.
-TYPE Reports only mismatched pins of the specified type. When
specified without a type, all types are reported.
Related Commands
ADD ECO PIN
REPORT PATHLEVELS
REPort PATHLevels
< <from_gate> <to_gate> | -NONEQ | -DIFF_pathlevels <input file> > [-
OUTputfile <filename>]
[-SOURCE]
[-NET]
[-CELLView]
[-VERbose]
[-REPlace]
[-Golden | -Revised]
(LEC Mode)
Displays the longest fan-in path depth of a gate, or between two selected gates, and saves to
a file. This command can also report the path level change for a specified fan-in of a gate in
a different run. Gates can be specified as gate ID numbers or instance paths.
Tcl Command
report_pathlevels
Parameters
<from_gate><to_gate>
Displays the longest fan-in path between the two specified
gates. Gates can be specified as gate ID numbers or instance
paths
-NONEQ Displays the longest path depth for each non-equivalent key
point.
-DIFF_pathlevels <filename>
Report path level changes for the fan-in of the specified gate.
The specified file must be the output of the REPORT
PATHLEVELS command with -outputfile option.
-OUTputfile <filename>
Outputs the report to the specified file.
-SOURCE Displays the file and line number location of the gate in the
path.
-NET Displays the corresponding net of the gate in the path.
-CELLVIEW Displays the path in instance-cell view.
-Golden Reports the specified path in the Golden design. This is the
default.
-Revised Reports the specified path in the Revised design.
Example
In the following example, REPORT PATHLEVEL is called after the compare and outputs the
report to report.log. After the patch is applied, REPORT PATHLEVEL is called again to report
the longest paths and path difference as compared to the last report.
...
compare
report pathlevels -noneq -outputfile report.log ...
set sys mode setup
apply patch
set sys mode lec
report pathlevels -diff_pathlevels report.log -output file diff.log ...
//CFMDepthDiff y6 0 1
Maximum logic path levels to destination: 1 Destination : (G) 16 PO /y6 Source
:(G)25Z/y6
//CFMDepthDiff g1/reg4/U$1 3 5
Maximum logic path levels to destination: 5 Destination : (G) 22 DFF /g1/reg4/U$1
Source :(G)8PI/in4
//CFMDepthDiff g1/reg5/U$1 3 5
Maximum logic path levels to destination: 5 Destination : (G) 23 DFF /g1/reg5/U$1
Source :(G)9PI/in5
//CFMDepthDiff y6 0 1
Maximum logic path levels to destination: 6(+5) Destination : (G) 16 PO /y6
Source:(G)25Z/y2
//CFMDepthDiff g1/reg4/U$1 3 5
Maximum logic path levels to destination: 3(-2) Destination : (G) 22 DFF /g1/reg4/
U$1 Source :(G)4PI/in4
//CFMDepthDiff g1/reg5/U$1 3 5
Maximum logic path levels to destination: 5(+0) Destination : (G) 23 DFF /g1/reg5/
U$1 Source :(G)9PI/in5
Summary Report :
==============================================
Path-Levels-Difference Total
==============================================
-2 1
0 1
+3 1
+5 1
----------------------------------------------
Related Commands
APPLY PATCH
REPORT GATE
REPORT PATH
Tcl Command
report_scan_chain
Parameters
-SE Specifies that the scan chain is enabled when the given
net value is 0 or 1. You can specify the value of this
option more than once.
-SI Specify the scan input net for the scan chain.
-SO Specify the scan output net for the scan chain.
Example
The following command reports the scan chain based on the given scan chain configuration.
The scan chain is enabled when test_mode and scan_enable are set.
report scan chain -se test_mode 1 scan_enable 1 -si scan_input -so scan_output
Related Commands
APPLY PATCH
Reports the spare cells and freed cells that were added with the ADD SPARE CELL
command.
Tcl Command
report_spare_cell
Parameters
Related Commands
APPLY PATCH
OPTIMIZE PATCH
Tcl Command
set_def_file
Parameters
No parameters.
When a new ICG is added to the patch as part of the ECO, CECO can automatically connect
it’s test-enable pin if it is constrained in Revised design. This command allows users to specify
test-enable signals to drive the new ICGs. The specified signal must be an existing signal and
constrained in the Golden design. A conflicting signal specification with the same module or
instance is not allowed.
Note that the specified signal must be a G1 signal or the command will error out.
Tcl Command
set_eco_icg_testenable
Parameters
Related Commands
ANALYZE ECO
Specifies the ECO check severity and its handling. See set_dofile_abort to see how
Conformal ECO behaves when an error message occurs. Execute this command before
set_system_mode lec.
Tcl Command
set_eco_check
Parameters
<check_name*>... Specifies the ECO check name. This accepts wildcards. Use
the command REPORT ECO CHECK -HELP to list all the ECO
checks and the default severity levels.
-Warning Changes the check severity to Warning.
-Error [-CONTinue] Changes the check severity to Error. With the -continue
option, Conformal ECO continues to run instead of erroring out.
-Note Changes the check severity to Note.
-Ignore Changes the check severity to Ignore. See report_eco_check to
see how this severity level affects reporting.
Example
The following command sets the severity level of ECO1.1 from warning to error.
set eco check ECO2.2 -error
Related Commands
REPORT ECO CHECK
Tcl Command
set_eco_option
Parameters
-FLAT Specifies that the intention is to run the Flattened ECO flow.
Setting this option executes the following commands:
SET FLATTEN MODEL -ECO
SET FLATTEN MODEL -ENABLE_ANALYZE_HIER_COMPARE
It also automatically adds the following options to the ANALYZE
HIER_COMPARE command (when -ECO_AWARE is specified):
-CONstraints
-NOEXact_pin_match
-FUNCTION_Pin_mapping
-INPUT_OUTPUT_Pin_equivalence
-THRESHOLD 0
-HIErarchical Specifies that the intention is to run the Hierarchical ECO flow.
It will execute the following commands:
SET FLATTEN MODEL -ECO
It also automatically adds the following options to the "WRITE
HIER_COMPARE DOFILE" command (when -ECO_AWARE is
specified):
-CONstraints
-NOEXact_pin_match
-FUNCTION_Pin_mapping
-INPUT_OUTPUT_Pin_equivalence
-BALANCED_EXTRACTIONS
-INStancenaming <format_string>
Specifies the instance naming format of ECO combinational cells.
For example, for eco_instance_%d, the %d will be an integer
that makes the instance name unique. Default is U%d.
-BBOXnaming <format_string>
Specifies the naming format of the ECO blackboxes. For example,
eco_bbox_%s, where %s is the original blackbox name.
-NETnaming <format_string>
Specifies the net naming format of ECO nets. For example, for
eco_net_%d, the %d will be an integer that makes the net name
unique. Default is N%d.
-PORTnaming <format_string>
Specifies the naming format for extra ports added by the ADD ECO
PIN command. For example, for eco_%s, where %s is the original
port name. Default is %s. For the default case, special characters
will be replaced by an underscore "_".
-SEQuentialnaming <format_string>
Specifies the instance naming format of the ECO registers and
latches. For example, eco_%s, where %s is the original register
name. Default is %s.
-SYNTHESIS_NAMING_style <Genus|NONGenus>
-BACKEND_NAMING_style <INNOvus|NONINNOvus>
These options will delete or keep the renaming rules with rule
name prefix eco_rename_high_fanout_ created by CECO.
These renaming rules are added by command set eco option
[-flat | -hierarchical].
When Genus and INNOVus naming style are specified, the
renaming rules are deleted. If not, the renaming rules are kept.
This is the default.
Related Commands
Reports the equivalent nets of each specified net on the other side of design. The nets can
be specified in the command or in a given file. The report will be written out to the specified
file. If no file specified, it will be written to screen.
Tcl Command
write_corresponding_nets
Parameters
Example
This command also reports inverter equivalent nets by default. In the example below, tmp[8]
in the Revised design is the inverter equivalent of n44[4] in the Golden and is reported with '-'.
LEC> write corresponding nets n44[4] -gol
// NET 1
+ (G) n44[4]
- (R) tmp[8]
+ (R) N26
Related Commands
REPORT ECO CHANGES
Generates a consolidated placement file in design exchange format (DEF) using the DEF file
from RC physical. Use this command after the OPTIMIZE PATCH command.
Tcl Command
write_eco_def
Parameters
-WORKdir <working_directory>
Specifies the name of the working directory.
-SYNExec <rc executable>
Specifies the path to the synthesis executable (Genus or RTL
Compiler). If this is not specified, the software will use the
Genus command in your search path.
-LIBrary <library_file_list>
-POSTPROCscript <script_name>
Specifies the script to run after the ECO change script (-
ECOscript <change_script>).
-VERbose Outputs all Genus messages. By default, the command only
outputs error messages.
-RELATIVE2CWD Specifies that the paths provided in other options relate to the
current working directory: not the Genus working directory.
-ALLOW_FC_MF Allows filler cells and metal fills in the design.
Filler cells and metal fills are not supported by default
because they generally can cause problems with the placer.
When you use this option, the tool will not flag these objects
and this can cause problems when you try to use the DEF
files in RC physical.
The recommended solution is to remove the filler cells and
metal fills from your DEF file before running Conformal ECO.
Example
The following illustrates how to create a DEF file using an input LEF and Verilog file:
setup> optimize patch -workdir WORK -library ../typical.lib -def ../g1.def \
-LEF ../typical.lef -sdc ../g1.sdc -placescript place.tcl -replace
setup> report eco change -script -file script.tcl -replace
setup> write eco def -workdir WORK -library ../typical.lib -LEF ../typical.lef \
-def_in ../g1.def -def_out ../g3.def -verilog_in ../g1.v -verilog_out ../g3.v
Related Commands
OPTIMIZE PATCH
Writes out the ECO netlist (note: does not write out non-ECO files) and attempts to reduce
the number of text differences between the original netlist file and the ECO netlist file. This
will reduce the number of differences reported by the UNIX diff command between the two
files.
Limitations
■ Does not work with VHDL netlists.
■ Does not work if you flatten the design during the ECO process.
■ Does not work if you uniquify the design during the ECO process.
Tcl Command
write_eco_design
Parameters
-NEWFILE [<filename_fmt>]
Writes the design into new files. The default format for the new
files is %s.eco, where %s is the original filename.
If <filename_fmt> is not specified, the default value is
%s.eco. The %s is replaced by the original file path.
Note: If <filename_fmt> does not contain %s, the ECO
design will be directly written to a specified filename without a
string replacement.
-DIR <directory_name>
Specifies the directory name to where the ECO design is
written.
-GZIPNEWfile Write out the ECO netlist in a compressed gzip format.
-REVIEWonly Reviews the changes only and does not write out the design
-BACKup [<filename_fmt>]
Creates a back up original files if using the -OVERWrite
option. The default format for the backup files is %s.bak, where
%s is the original file name.
-TIMEstamp [<user_specified_description>]
Example
■ The following is a sample script that writes out the a.v.eco and b.v.eco files after
running the Conformal ECO commands:
read design a.v b.v -golden
// ECO process
analyze eco ...
optimize patch ...
write eco design -newfile %s.eco -replace
■ The following script reads in the original netlist and patch, runs the OPTIMIZE PATCH
command to map and optimize the ECO change, and writes out the ECO netlist to
top.eco.gv.:
read library typical.lib -liberty
read design top.gv patch1.v
Related Commands
REPORT ECO CHANGES
Tcl Command
write_preserved_points
Parameters
-Dofile Specifies the name of the dofile that writes out probed points for
<dofile_name> constrained logic.
-REPlace Replaces the existing file.
Related Commands
4
Modeling Messages
This chapter lists and describes the modeling messages you encounter when the system
mode changes from Setup to LEC in the Encounter® Conformal® software.
F1
Message
Modeled multiple-driven net(s)
Description
A multi-driven net has been remodeled into Boolean logic based on how the SET WIRE
RESOLUTION command is set.
Example
Sample modeling message:
F1: Modeled multiple-driven net(s) (Occurrence: 1)
1: /n1 (and)
In this message:
■ /n1 is a multi-driven net
■ (and) indicates that SET WIRE RESOLUTION is set to AND
The following code illustrates a circuit with a net n1 that has multiple drivers u0 and u1:
not u0 (n1,a);
not u1 (n1,b);
not u2 (z,n1);
F2
Message
Inserted user cut point(s)
Description
Conformal inserted a cut point to break a combinational loop. This operation is enabled when
you use the ADD CUT POINT command.
Example
Sample modeling message:
F2: Inserted user cut point(s) (Occurrence: 1)
1: CUT /n1
In this message:
■ CUT indicates the gate type
■ /n1 indicates the net name
You get this message when you add a cut point at net n1 using the
following command:
add cut point n1 -golden
Circuit example:
mux u0 (n1,n1,d,ck);
xor u1 (q,n1);
F3
Message
Inserted system cut point(s)
Description
A cut point has been inserted automatically to break a combinational loop.
Example
Sample modeling message:
F3: Inserted system cut point(s) (Occurrence: 1)
1: MUX /u0
In this message:
■ MUX is the gate type
■ /u0 is the driver instance name
The following circuit example inserts CUT gate at the output of a MUX instance u0:
mux u0 (n1,n1,d,ck);
xor u1 (q,n1);
F3.1
Message
Inserted system cut point(s) for partially modeled library module pins
Description
A cut point has been inserted automatically to verify partially modeled library module pins.
Example
Sample modeling message:
F3.1: Added 2 cut points for partially modeled library module pins
in Golden (Occurrence: 1)
1: CUT /AAA4/BBB/DDD_lec_lpv_cut
In this message:
■ /AAA4/BBB/DDD is the partially modeled library pin and the inserted cut point is named /
AAA4/BBB/DDD_lec_lpv_cut
Associated Commands
set flatten model -library_pin_verification
F3.2
Message
Deleted redundant cut point(s)
Description
A redundant cut point has been deleted. Deleting the cut point does not form a combinational
loop.
Example
Sample modeling message:
F3.2: Deleted redundant cut point (Occurrence: 1)
1: i1[1]
In this message:
■ i1[1] is a redundant cut point and is deleted.
Associated Commands
analyze setup -cut
F3.3
Message
Removed cut point(s)
Description
A cut point has been removed.
Example
Sample modeling message:
F3.3: Removed cut point (Occurrence: 2)
1: i1[1]
2: i1[0]
In this message:
■ i1[0] and i1[1] are cut points that have been removed.
Associated Commands
analyze setup -cut
F3.4
Message
Moved cut point(s) to new location
Description
A cut point has been moved to a new location.
Example
Sample modeling message:
F3.4: Moved cut point(s) to new location (Occurrence: 1)
1: MOD_B/MOD_B_A/U$6 MOD_A/U$5/U$90
In this message:
■ A cut point is moved from the output of gate MOD_B/MOD_B_A/U$6 to the output of gate
MOD_A/U$5/U$90.
Associated Commands
analyze setup -cut
F3.5
Message
Remodeled cut point(s) to DLAT(s)
Description
A cut point has been remodeled to a DLAT. The DLAT's set and reset pins are tied to zero. Its
clock pin is tied to one and data pin is connected to the fan-in of the cut point.
Example
Sample modeling message:
F3.5: Remodeled cut point(s) to DLAT(s) (Occurrence: 1)
1: DLAT hysteresis_new/g502/SMC_I0
In this message:
■ A cut point hysteresis_new/g502/SMC_I0 is remodeled to a DLAT.
Associated Commands
analyze setup -cut
F3.6
Message
Inserted balanced cut point(s)
Description
A cut point has been inserted automatically to balance the cut points between Golden and
Revised.
Example
Sample modeling message:
F3.6: Added balanced cut points (Occurrence: 1)
1: NAND g7/U$1
In this message:
■ A balanced cut point has been inserted at the output of NAND gate g7/U$1.
Associated Commands
analyze setup -cut
F5
Message
Folded DLAT(s) into DFF(s)
Description
D-latches (DLATs) were folded into D flip-flops (DFFs). This operation is enabled when you
use the SET FLATTEN MODEL -LATCH_FOLD command, which specifies that two latches
that are in a master-slave configuration should be converted into a single DFF gate. This
operation is also affected by the SET FLATTEN MODEL -LATCH_FOLD_MASTER command.
Example
Sample modeling message:
F5: Folded DLAT(s) into DFF(s) (Occurrence: 1)
1: /l1 /l0
In this message, /l1 and /l0 are the instance names of the folded DLATs.
You would get this modeling message if you use the following command to convert two
master-slave DLATs l0 and l1 into a DFF:
set flatten model -latch_fold
Circuit example:
not u0 (ck_,ck);
DLAT l0 (n1,,1'b0,1'b0,ck_,d);
DLAT l1 (q ,,1'b0,1'b0,ck,n1);
F6
Message
Created DLAT(s) due to trireg net(s) or combinational loop(s)
Description
A DLAT was created due to trireg net or a series of buffers/inverters that were implemented
as a bus-holder.
Example
Sample modeling message:
F6: Created DLAT(s) due to trireg net(s) or combinational loop(s) (Occurrence: 1)
1: DLAT /n1 due to trireg net
This message indicates that a DLAT was created on net n1 for trireg, which is illustrated
in the following circuit example:
trireg n1;
bufif0 u0 (n1,a,s0);
bufif0 u1 (n1,b,s1);
buf u2 (z,n1);
F7
Message
Set DLAT data port(s) as ZERO due to disabled clock port(s)
Description
DLAT data ports were set to zero because there were disabled clock ports. This operation is
enabled when you use the SET FLATTEN MODEL -LATCH_FOLD command.
Example
Sample modeling message:
F7: Set DLAT data port(s) as ZERO due to disabled clock port(s) (Occurrence: 1)
1: Set DLAT 'q_reg' data port '/d' to ZERO due to disabled clock port
This message indicates that data port d of register q_reg is tied to logic ZERO because clock
port of register q_reg is always disabled (logic ZERO).
You would get this message if you issue the following command:
set flatten model -latch_fold
Circuit example:
and u0 (g,1'b0,ck);
always @(d or g)
begin
if (g)
q <= d;
end
F8
Message
Converted DLAT(s) to BUF(s) due to transparency
Description
DLATs were converted into buffers because of transparency. This operation is enabled when
you use the SET FLATTEN MODEL -LATCH_TRANSPARENT command, which specifies
that DLATs should be converted into buffers if the DLAT clock ports are always enabled.
Example
Sample modeling message:
F8: Converted DLAT(s) to BUF(s) due to transparency (Occurrence: 1)
1: DLAT /q_reg
This message indicates that a buffer was converted buf (q,d), because the clock of
register q_reg is always enabled (logic ONE).
You would get this message if you issue the following command:
set flatten model -latch_transparent
Circuit example:
or u0 (g,1'b1,ck);
always @(d or g)
begin
if (g)
q <= d;
end
F8.1
Message
Converted DLAT(s) to BUF(s) due to redundancy to DFF(s)
Description
DLAT is converted to BUF if its frontier contains only DFF(s) and DLAT(s) and it is redundant
to all of them.
Example
F8.1: Converted DLAT(s) to BUF(s) due to redundancy to DFF(s) (Occurrence: 1)
1: /q0_dlat
This message indicates that DLAT q0_dlat was converted to BUF because it was redundant
to its fanout DFF(s)/DLAT(s).
F9
Message
Removed DLAT data dependency due to redundancy
Description
Indicates that DLAT data dependencies were removed because of redundancy. This
operation is enabled when you use the SET FLATTEN MODEL -SEQ_REDUNDANT
command, which specifies that redundant fanout gates should be removed from DFFs and
DLATs.
Associated Commands
F10
Message
Removed redundant AND/NAND/OR/NOR fanin gate(s) for DFF/DLAT(s)
Description
Redundant AND/NAND/OR/NOR fan-in gates for DFFs and DLATs were removed. This
operation is enabled when you use the SET FLATTEN MODEL -SEQ_REDUNDANT
command.
Example
Sample modeling message:
F10: Removed redundant AND/NAND/OR/NOR fanin gate(s) for DFF/DLAT(s)
(Occurrence: 1)
1: Removed connection from INV /u0 to AND /u1 for DFF /f0_reg
This message indicates that the fan-in AND u1 and INV u0 gates were optimized for DFF
f0_reg due to redundant logic.
You would get this command if you issue the following command:
set flatten model -seq_redundant
Circuit example:
not u0 (rst_,rst);
and u1 (sr,set,rst_);
DFF f0_reg(q,,sr,rst,ck,d);
F11
Message
Removed redundant AND/NAND/OR/NOR fanout gate(s) for DFF/DLAT(s)
Description
Redundant AND/NAND/OR/NOR fan-out gates for DFFs and DLATs were removed. This
operation is enabled when you use the SET FLATTEN MODEL -SEQ_REDUNDANT
command.
Example
Sample modeling message:
F11: Removed redundant AND/NAND/OR/NOR fanout gate(s) for DFF/DLAT(s) (Occurrence:
1)
1: Remodeled AND /u0 for DFF /n1_reg
This message indicates that the fan-out AND gate u0 was optimized for DFF n1_reg due to
redundant logic.
You would get this command if you issue the following command:
set flatten model -seq_redundant
Circuit example:
always @(posedge ck or negedge rst )
begin
if (!rst)
n1 <= 0;
else
n1 <= d;
end
and u0 (q,n1,rst);
F12
Message
Converted DFF(s) to DLAT(s) due to disabled clock port(s)
Description
DFFs were converted into DLATs due to disabled clock ports. This operation is enabled when
you use the SET FLATTEN MODEL -DFF_TO_DLAT_ZERO, which converts a DFF to a DLAT
when the clock port is zero.
Example
Sample modeling message:
F12: Converted DFF(s) to DLAT(s) due to disabled clock port(s) (Occurrence: 1)
1: DLAT /q_reg
This message indicates DFF q_reg was converted to a DLAT because the clock of the
register is always disabled (logic ZERO).
Circuit example:
and u0 (ck1,1'b0,ck);
always @(posedge ck1)
begin
q <= d;
end
F13
Message
Converted DFF(s) to DLAT(s) due to direct feedback
Description
DFFs were converted to DLATs due to direct feedback. This operation is enabled when you
use the SET FLATTEN MODEL -DFF_TO_DLAT_FEEDBACK command, which converts a
DFF to a DLAT if the DFF's output feeds back directly to the DFF's input.
Example
Sample modeling message:
F13: Converted DFF(s) to DLAT(s) due to direct feedback
(Occurrence: 1)
1: DLAT /q_reg
This message indicates that DFF q_reg was converted to a DLAT because of direct feedback
from output q of the register to its input d.
You would get this message if you issue the following command:
set flatten model -DFF_TO_DLAT_FEEDBACK
Circuit example:
always @(posedge ck)
begin
q <= q;
end
F14
Message
Remodeled gated-clock DFF(s) or DLAT(s) to mux-feedback
Description
Gated-clock logic for DFFs or DLATs were remodeled to MUX-feedback. This operation is
enabled when you run the SET FLATTEN MODEL -GATED_CLOCK command, which
remodels gated-clock logic of the clock port of a DFF.
Example
Sample modeling message:
F14: Remodeled gated-clock DFF(s) or DLAT(s) to mux-feedback (Occurrence: 1)
1: /q_reg (DFF)
This message indicates that the de-glitch gating clock DLAT l0 and enable logic u1 for
register DFF q_reg was converted to a mux-feedback DFF.
You would get this message when issue the following command:
set flatten model -GATED_CLOCK
Circuit example:
not u0 (ck_,ck);
DLAT l0 (en,,1'b0,1'b0,ck_,ena);
and u1 (ck1,ck,en);
always @(posedge ck1)
begin
q <= d;
end
F14.1
Message
Remodeled gated-clock DFF(s) or DLAT(s) without latch to mux-feedback
Description
Conformal remodeled gated-clock logic for DFFs or DLATs without deglitching to MUX-
feedback. This operation is enabled when you use the SET FLATTEN MODEL
-GATED_CLOCK, which remodels gated-clock logic of the clock port of a DFF. This operation
might need the ADD CLOCK command to define the clock pin.
Example
Sample modeling message:
F14.1: Remodeled gated-clock DFF(s) or DLAT(s) without latch to mux-
feedback(Occurrence: 1)
1: /q_reg (DFF)
This message indicates that the gated-clocking enable logic u1 for register DFF q_reg was
converted to a mux-feedback DFF.
You get this message when you issue the following commands:
add clock 0 ck
set flatten model -GATED_CLOCK
Circuit example:
and u0 (ck1,ck,ena);
always @(posedge ck1)
begin
q <= d;
end
F16
Message
Converted DLAT(s) to MUX(s) due to clock inversion relation
Description
DLATs were converted into MUXes due to clock inversion relationships.
Example
Sample modeling message:
F16: Converted DLAT(s) to MUX(s) due to clock inversion relation (Occurrence: 1)
1: /l0
This message indicates that a dual-port DLAT l0 was converted to a MUX - mux l0
(q,d0,d1,ck) due to the clock inversion relationship on the dual-port DLAT clock ports.
Circuit example:
not u0 (ck_,ck);
DLAT l0 (q,,1'b0,1'b0,ck_,d0,ck,d1);
F17
Message
Converted DLAT(s) to BUF(s)/INV(s) due to set/reset inversion relation
Description
DLATs were converted to buffers/inverters due to set/reset inversion relationships.
Example
Sample modeling message:
F17: Converted DLAT(s) to BUF(s) due to set/reset inversion relation
(Occurrence: 1)
1: /l0
This message indicates that a DLAT l0 was converted to a buffer, buf l0 (q,a), because
of set/reset inversion relationships on asynchronous set/reset of DLAT.
Circuit example:
not u0 (a_,a);
DLAT l0 (q,,a,a_,ck,1'b0);
F18
Message
Converted DFF/DLAT(s) to ZERO/ONE
Description
Conformal converted a DFF or a DLATs to a ZERO or ONE gate. This operation is enabled
when you use the SET FLATTEN MODEL -SEQ_CONSTANT command, which converts a
DFF or DLAT to a ONE or ZERO gate if the data port is a one or zero. This operation is also
affected by the SET FLATTEN MODEL -SEQ_CONSTANT_FEEDBACK command.
Example
Sample modeling message:
F18: Converted DFF/DLAT(s) to ZERO/ONE (Occurrence: 1)
1: DFF /n1_reg (ZERO)
This message indicates that DFF n1_reg was converted to logic ZERO because data port is
tied to logic ZERO.
You would get this message if you issue the following command:
set flatten model -seq_constant
Circuit example:
always @ (posedge ck)
n1 <= 1'b0;
assign q = a | n1;
F19
Message
Merged DFF(s) or DLAT(s) in clock cones due to functional equivalence
Description
Sequentially equivalent DFFs or DLATs in clock cones were merged. This operation is
enabled when you use the SET FLATTEN MODEL -SEQ_MERGE command.
Example
Sample modeling message:
F19: Merged DFF(s) or DLAT(s) in clock cones (Occurrence: 1)
1: DFF /ck0_reg /ck1_reg
This message indicates that DFF ck0_reg and DFF ck_reg were merged into a single DFF
because the two DFFs were sequentially equivalent.
You would get this message when you issue the following command:
set flatten model -seq_merge
Circuit example:
always @ (posedge ck)
begin
ck0 <= a;
ck1 <= a;
end
F19.1
Message
Merged DFF(s) or DLAT(s) in set/reset cones due to functional equivalence
Description
Sequentially equivalent DFFs or DLATs in set/reset cones were merged. This operation is
enabled when you use the SET FLATTEN MODEL -SEQ_MERGE command
Example
Sample modeling message:
(F19.1) Merged 2 DFF/DLAT(s) in set/reset cones due to functional equivalence
This message indicates that the two DFFs or DLATs were merged because they were
functionally equivalent.
You would get this message when you issue the following command:
set flatten model -seq_merge
Circuit example:
always @ (posedge clk)
begin
set0 <= a;
set1 <= a;
end
F20
Message
Merged DFF(s) or DLAT(s)
Description
Sequentially equivalent DFFs and DLATs were merged. This operation is enabled when you
use the SET FLATTEN MODEL -ALL_SEQ_MERGE command, which merges common
groups of sequential elements into one sequential element in a logic cone of a key point.
Example
Sample modeling message:
F20: Merged DFF(s) or DLAT(s) (Occurrence: 1)
1: DFF /q0_reg /q1_reg
This message indicates that DFF q0_reg and DFF q_reg were merged into a single DFF
because the two DFFs are sequentially equivalent.
You would get this message if you use the following command:
set flatten model -all_seq_merge
Circuit example:
always @ (posedge ck)
begin
q0 <= d;
q1 <= d;
end
F21
Message
Merged DFF(s) or DLAT(s) defined by user
Description
User-defined DFFs or DLATs were merged using the ADD INSTANCE EQUIVALENCES or
REMODEL -instance_eq command.
Example
Sample modeling message:
F21: Merged DFF(s) or DLAT(s) defined by user (Occurrence: 1)
1: DFF /q0_reg /q1_reg
This message indicates that you merged two DFFs q0_reg and DFF q1_reg into a single
DFF using the following command:
add instance equivalences /q0_reg /q1_reg -golden
Circuit example:
always @ (posedge ck)
begin
q0 <= d;
q1 <= d;
end
F23
Message
Merged DFF(s) or DLAT(s) multiple ports into single port due to equivalence
Description
Multiple ports belonging to DFFs or DLATs into one single port due to equivalence were
merged.
Example
Sample modeling message:
F23: Merged DFF(s) or DLAT(s) multiple ports into single port due to equivalence
(Occurrence: 1)
1: DFF /f0
This message indicates that a dual-port DFF f0_reg with equivalent data and clock port was
merged into a single port DFF - DFF f0_reg (q,,1'b0,1'b0,ck,d).
Circuit example:
buf n0 (d0,d);
buf n1 (d1,d);
DFF f0_reg (q,,1'b0,1'b0,ck,d0,ck,d1);
F25
Message
Pipeline-retimed DFF(s) to outputs
Description
DFFs to outputs were pipeline-retimed. This operation is enabled when you use the ADD
MODULE ATTRIBUTE -PIPELINE_RETIME command, which checks specified modules for
pipeline retiming and remodels when necessary.
Example
Sample modeling messages:
Report modeling message for Revised
F25: Pipeline-retimed DFF(s) to outputs (Occurrence: 1)
1: Pipeline retimed DFF 'q_reg' to output
Report modeling message for Revised
F25: Pipeline-retimed DFF(s) to outputs (Occurrence: 2)
1: Pipeline retimed DFF 'a1_reg' to output
2: Pipeline retimed DFF 'b1_reg' to output
These messages indicate that the DFF a1_reg and DFF b1_reg performed pipeline-
retiming to the outputs.
You would get these messages if you issue the following command:
add module attribute ckt -pipeline_retime
Circuit example:
Golden:
assign n1 = a & b;
Revised:
always @(posedge ck)
begin
a1 <= a;
b1 <= b;
end
assign q = a1 & b1;
F26
Message
Merged dual-port DLAT(s) into single port DLAT(s)
Description
Dual-port DLATs were merged into single-port DLATs. This operation is enabled when you
use the SET FLATTEN MODEL -LATCH_MERGE_PORT command.
Example
Sample modeling message:
F26: Merged dual-port DLAT(s) into single port DLAT(s)
(Occurrence: 1)
1: Merged multi-port DLAT '/l0' into single port DLAT
This message indicates that dual-port DLAT "l0" was merged into a single port DLAT using
the following command:
set flatten model -latch_merge_port
Circuit example:
DLAT l0 (q,,1'b0,1'b0,ck,d0,sck,d1);
Result :
and u0 (n1,d0,ck);
and u1 (n2,d1,sck);
or u2 (din,n1,n2);
or u3 (ck_or,ck,sck);
DLAT l0 (q,,1'b0,1'b0,ck_or,din);
F27
Message
Converted internal input port(s) to inout port(s)
Description
Internal input ports were converted into inout ports because the input port does not drive any
instances.
Example
Sample modeling message:
F27: Converted internal input port(s) to inout port(s)
(Occurrence: 1)
1: port /u0/y in module AN2
This message indicates that port y of module AN2 does not drive any load.
Circuit example:
module AN2 (y,z,a,b);
input a,b,y;
output z;
and u0 (z,a,b);
buf u1 (y,a);
endmodule
AN2 u0 (y,z,a,b);
endmodule
F28
Message
Converted internal output port(s) to inout port(s)
Description
Internal output ports were converted to inout ports because the output port is not driven.
Example
Sample modeling message:
F28: Converted internal output port(s) to inout port(s)
(Occurrence: 1)
1: port /u0/a in module AN3 due to high-impedance (Z) gates
This message indicates that port a of module AN3 is not driven by any driver.
Circuit example:
module AN3 (z,a,b,c);
input b,c;
output z,a;
and u0 (z,a,b,c);
endmodule
AN3 u0 (z,a,b,c);
endmodule
F30
Message
Ignored weak device(s) due to the existence of strong device(s)
Description
Any weak devices were ignored due to the existence of a stronger device in a multiple-driven
net.
Example
Sample modeling message:
F30: Ignored weak device(s) due to the existence of strong device(s) (Occurrence: 1)
1: n1
This message indicates that a weak device buffer u0 driving net n1 was ignored due to the
existence of stronger buffer device u1 driving the same net n1.
Circuit example:
buf (weak0,weak1)u0 (n1,a);
buf u1 (n1,b);
buf u2 (z,n1);
F32
Message
Created Z gate(s) for floating net(s) and floating pin(s)
Description
Z gates were created for floating nets and floating pins.
Example
Sample modeling message:
F32: Created Z gate(s) for floating net(s) and floating pin(s) (Occurrence: 1)
1: c
Circuit example:
module ckt (z,a,b);
input a,b;
output z;
wire c;
and u0 (z,a,b,c);
endmodule
F34
Message
Convert X assignment(s) as don't care(s)
Description
X assignments were converted to "don't cares". This operation is enabled when you use the
SET X CONVERSION command.
Example
Sample modeling message:
F34: Convert X assignment(s) as don't care(s) (Occurrence: 1)
1: Converted 'X assignment' at 'N$1' be don't care
This message indicates that assignment in RTL code default: z = 1'bx is converted to
don't cares through the following command:
set x conversion DC -golden
Circuit example:
always @(a or b or sel)
begin
case (sel)
2'b01 : z = a;
2'b10 : z = b;
default : z = 1'bx;
endcase
end
F34.1
Message
Convert X assignment(s) as zero(s)
Description
X assignments were converted to zero. This operation is enabled when you use the SET X
CONVERSION command.
Example
Sample modeling message:
F34.1: Convert X assignment(s) as zero(s) (Occurrence: 1)
1: Converted X assignment 'N$1' as 0
This message indicates that X assignment in RTL code default: z = 1'bx was converted
to logic ZERO using the following command:
set x conversion 0
Circuit example:
always @(a or b or sel)
begin
case (sel)
2'b01 : z = a;
2'b10 : z = b;
default : z = 1'bx;
endcase
end
F34.2
Message
Convert X assignment(s) as one(s)
Description
X assignments were converted to one. This operation is enabled when you use the SET X
CONVERSION command.
Example
Sample modeling message:
F34.2: Convert X assignment(s) as one(s) (Occurrence: 1)
1: Converted X assignment 'N$1' as 1
This message indicates that an X assignment in the RTL code default: z = 1'bx was
converted to logic ONE using the following command:
set x conversion 1
Circuit example:
always @(a or b or sel)
begin
case (sel)
2'b01 : z = a;
2'b10 : z = b;
default : z = 1'bx;
endcase
end
F34.3
Message
Converted 1 X assignment(s) as E(s)
Description
An X assignment was converted to an error (E) gate . This operation is enabled when you use
the SET X CONVERSION command. If the X assignment space of the Revised design is
within the X assignment space of the Golden design, then the E gate is marked as an extra
unmapped point (redundant gate).
Example
Sample modeling message:
F34.2: Convert 1 X assignment(s) as E (Occurrence: 1)
1: Converted X assignment 'N$1' as E
This message indicates that an X assignment in the RTL code default: z = 1'bx was
converted to logic E using the following command:
set x conversion E
Circuit example:
always @(a or b or sel)
begin
case (sel)
2'b01 : z = a;
2'b10 : z = b;
default : z = 1'bx;
endcase
end
F36
Message
Don't care(s) added due to $constraint(s)
Description
"don't cares" were added due to $constraints.
Example
Sample modeling message:
F36: Don't care(s) added due to $constraint(s) (Occurrence: 1)
1: u0: DFF q_reg
This message indicates that constraint cstr_0 for register q_reg is added to don't cares.
Circuit example:
always @(a or b or sel)
begin
case (sel)
2'b01 : z = a;
2'b10 : z = b;
default : z = 1'bx;
endcase
end
$constraint cstr_0 ($one_hot (sel));
F36.1
Message
Detected always-on DC due to $constraint(s)
Description
Detected always-on DC gates due to $constraint(s). An always-on DC gate means that its
output is always dont-care, and that indicates the condition in $constraint(s) is always
falsified. Comparing the dont-care space to anything is equivalent. Therefore, it is abnormal
that a design has always-on DC. LEC can conclude equivalence, even for a bad
implementation. Do review the constraints to ensure correctness.
Example
Sample modeling message:
F36.1: Detected always-on DC(s) due to $constraint(s) (Occurrence: 1)
1: DC /g
In this message, the control C-pin of the DC gate "g" is always on.
F39
Message
Added output Z gate(s)
Description
Output Z gates were added. This operation is enabled by SET FLATTEN MODEL
-OUTPUT_Z, which is enabled by default.
Example
Sample modeling message:
F39: Added output Z gate(s) (Occurrence: 1)
1: /z
This message indicates that a Z gate was added at the output z using the following command:
set flatten model -output_z
Circuit example:
module ckt (z,a,sel);
input a,sel;
output z;
bufif0 u0 (z,a,sel);
endmodule
F41
Message
Converted set/reset loop(s) to data-hold(s)
Description
The Conformal software converted a data-hold function that is modeled using an
asynchronous set and an asynchronous reset functions, to a mux data-hold function
Example
Sample modeling message:
F41: Converted set/reset loop(s) to data-hold(s) (Occurrence: 1)
1: DFF 'Q_reg'
Circuit example:
assign RN = !Q & EN;
assign SET = Q & EN;
F42
Message
Unfolded DFF to latches
Description
A DFF was unfolded into two DLATs. This operation is enabled when you use the REMODEL
-UNFOLD_DFF command, which specifies that a DFF should be converted into two DLATs
that are in a master-slave configuration.
Example
Sample modeling message:
F42: Unfolded DFF to latches (Occurrence: 1)
1: /q_reg
This message indicates you converted a single DFF into a master-slave DLATs using the
following command:
remodel -unfold_dff
Circuit example:
always @(posedge ck)
q <= d;
F43
Message
Added DLATs to cut loops
Description
DLATs were added to cut combination loops.This operation is enabled by the SET FLATTEN
MODEL command.
Example
Sample modeling message:
F43: Added DLATs to cut loops (Occurrence: 1)
1: /u0
This message indicates that a DLAT was added at instance driver u0 to cut the combinational
loop using the following command:
set flatten model -loop_as_dlat
Circuit example:
mux u0 (n1,n1,d,ck);
xor u1 (q,n1);
F44
Message
Converted Z(s) to ZERO/ONE/don't care(s)
Description
One or more Z outputs were converted to ZERO, ONE, or don't care.
F45
Message
Adjusted DFF/DLAT of positive library cell(s)
Description
One or more positive library cells have a DFF or DLAT that was adjusted.
F46
Message
Converted DFF/DLAT(s) to BUF(s) by user
Description
The user-specified DFF/DLATs were converted to buffer gates. The Conformal software
performs such conversion without checking whether it preserves the functionality of the netlist
or not. Therefore, this operation could modify the functionality of the netlist.
Example
Circuit example:
not u0 (a_, a)
DLAT l0 (q, ,a, a_, ck, 1'b0)
F47
Message
Inserted DC(s) due to DFF clock/data interaction
Description
Clock or data interaction with a DFF caused one or more DCs to be inserted.
F49
Message
Removed redundant DLAT(s)
Description
Collapses serial D-latches (even when there is logic between them) into the last latch on that
clock phase. You cannot use this option with latches that have set or reset pins
Example
F49: Removed redundant DLAT(s) (Occurrence: 1)
1: /q0_reg
The following message indicates that the DLAT /q0_reg is removed from netlist. /q0_reg
is redundant with existence of /q1_reg:
Circuit example:
always @ (clk or d)
if (clk)
q0 = d;
always @ (clk or q0)
if (clk)
q1 = q0;
F50
Message
False paths(s) broken
Description
One or more false paths are broken.
F51
Message
Merged BBOXes due to common inputs
Description
Blackboxes have common inputs and are merged.
F52
Message
Removed redundant MUX fanout for DLAT(s)
Description
Redundant MUX fanouts for one or more DLATs were removed.
F53
Message
Constraints added from OVL assertion(s)
Description
One or more OVL assertion constraints were added.
F54
Message
Extracted MUX(s) from Data port of DFF(s)
Description
One or more MUX from one or more DFF data ports were extracted.
F55
Message
Disabled the sequential modeling of DFF/D-LATCH that only fan-outs to constraints
Description
One or more DFF/D-LATCH were excluded from sequential modeling because they only fan-
out to constraints.
F56
Message
Ignored power and ground pins in library module
Description
The power and ground pins of the library module will not be compared.
Example
Sample modeling message:
1: PROBE: PSUB
2: PROBE: NSUB
3: PROBE: VSS
4: PROBE: VDD
You would get this message when verifying a physical netlist. It indicates the power and
ground pins defined in the LEF file will not be compared.
F57
Message
BBOX inout-pin(s) modeled as input(s) based on LEF pin type
Description
INOUT power pins in LEF definition are modeled as inputs.
Example
Sample modeling message:
1: PROBE: VDD
2: PROBE: NSUB
3: PROBE: PSUB
You would get this message when verifying a physical netlist. It indicates the power pins
defined as INOUT in the LEF file are modeled as inputs to avoid false nonequivalence.
F59
Message
Convert set/reset functions of DFF/DLAT(s) to D/CLK due to disabled clock port(s)
Description
Set/reset functions of DFFs or DLATs with disabled clock ports are converted to data/clock,
where set/reset ports are tied zero and DFFs are converted into DLATs. This operation is
enabled by default. You can use set flatten model -nolatch_sr_to_d to turn it off.
F65.1
Message
Tied undriven signals to zero
Description
An undriven signal is tied to zero. The SET UNDRIVEN SIGNAL COMMAND sets all undriven
signals in the design.
Example
Sample modeling message:
1: /w1
F65.2
Message
Tied undriven signals to one
Description
An undriven signal is tied to one. The SET UNDRIVEN SIGNAL COMMAND sets all undriven
signals in the design.
Example
Sample modeling message:
1: /w1
F65.3
Message
Tied undriven signals to X
Description
An undriven signal is tied to X (don't care). The SET UNDRIVEN SIGNAL COMMAND sets all
undriven signals in the design.
Example
Sample modeling message:
F68
Message
Model Liberty contention condition as X
Description
Model contention condition as X to the output of the library cell. For output 'o' and contention
condition 'a', the modeled output would be a ? 1'bx : o.
F69
Message
Disabled clock for inactive port
Description
The clock of a DFF/DLAT is disabled (tied to zero) if the register's data cone is a self feedback.
Example
Sample modeling message:
In this message, the clock port of register 'q_reg' was tied to zero.
F73
Message
Transform set-dominant DFF/DLAT(s)
Description
Indicates that during auto setup the tool has analyzed and transformed unbalanced set-
dominant DFF/DLAT structures.
Example
Sample modeling message:
F73: Transform set-dominant DFF/DLAT(s) (Occurrence: 1)
1: Remodeled OR /dff1/U$3 for DFF /dff1/dff_sub
5
Tcl Command Entry Mode Support
add_to_collection
add_to_collection <base_collection>
<collection | object_list >
[-unique]
(TCL_SETUP/TCL_LEC mode)
Parameters
Example
TCL_LEC> set a [find_cfm -instance * -collection]
collection_0
TCL_LEC> set b [find_cfm -instance u* -collection]
collection_1
TCL_SETUP> set c [add_to_collection $a $b]
collection_2
TCL_SETUP> query_collection $c
pmu u_gsw u1 u_gsw u1
TCL_SETUP> set c [add_to_collection $a $b -unique]
collection_3
TCL_SETUP> query_collection $c
pmu u_gsw u1
append_to_collection
append_to_collection <var>
<collection | object_list>
[-unique]
(TCL_SETUP/TCL_LEC mode)
Parameters
Example
TCL_SETUP> set b [find -instance u* -collection]
collection_1
TCL_SETUP> append_to_collection z $b
TCL_SETUP> query_collection $z
u_gsw u1
cfm_is_gui_mode
cfm_is_gui_mode
(TCL_SETUP/TCL_LEC mode)
Checks whether the tool is in command line mode (command returns 0) or GUI mode
(command returns 1).
Parameters
None.
compare_collection
compare_collection <collection1> <collection2>
[-order_dependent]
(TCL_SETUP/TCL_LEC mode)
Description
Compares two collections. Returns a value of 0 if all the objects in both collections are the
same; returns 1 if the values in both collections are not the same.
Parameters
Example
TCL_LEC> set a [find_cfm -instance u* -collection]
collection_0
TCL_LEC> set a [find_cfm -instance ur* -collection]
collection_1
TCL_LEC> compare_collection $a $b -order_dependent
1
Notice that here it's the variable name instead of the collection name that needs to be passed
as the argument.
copy_collection
copy_collection <collection>
(TCL_SETUP/TCL_LEC mode)
Returns a copy of the specified base collection. The base collection is not changed.
Parameters
Example
TCL_LEC> copy_collection $a
collection_6
TCL_LEC> query_collection $a
/ud1 /u_iso1 /ur1 /ur2 /ur3
echo_result
echo_result [-on | -off]
(TCL_SETUP/TCL_LEC mode)
Parameters
None.
encrypt
encrypt <inputfile> <outputfile>
(TCL_SETUP/TCL_LEC mode)
Parameters
inputfile Tcl file that you want to encrypt. This file is left unchanged by
this command.
outputfile Is the output file that is the encrypted form of the input file.
exit
exit
(TCL_SETUP/TCL_LEC mode)
Ends the existing Conformal session and returns to the operating system using the native Tcl
exit command.
Parameters
None.
find
find <-Module | -Instance | -Port [-Input | -Output | -Bidir]
| -Pin [ -Input | -Output| -Bidir]
| -Net | -Gate | -Id>
[-Single]
[-HIERarchical]
<object_name>
[-EXCLIB]
[-INDESIGN]
[-LEAF]
[-Golden | -Revised | -Both]
(TCL_SETUP/TCL_LEC mode)
Returns a design database object handle or list of handles for a design object or list of objects.
The Tcl-based find and find_cfm commands are both useful for searching design
information. They can both be used to look up design objects, such as instances, ports, pins,
and nets. For gate queries, however, only the find command can be used.
Parameters
Examples
The following example shows how the return value of the command can be saved to a variable
for later reference:
set abc1 [find -instance /u1/U2]
set abc2 [find -single -instance /u1/U2]
...
get_nets [lindex $abc1 0]
get_nets $abc2
The following illustrates hierarchical name matching. For example, the first example returns
no matches, the second example returns all instances that match the hierarchical name
pattern "*/*", and the third example returns the instance that matches the name pattern
"*/x1".
find -instance */*
/u_rst_sync/RS1_reg
/u_pm/add_29_31
/u_tm/x1
/u_tm/x2
/u_tm/Iso_iso1
find_cfm
find_cfm -<object_type>
[<patterns> | <object_list> | -OF_OBJects <object_list>]
[-Filter <condition>]
[-COLlection]
[-HIERarchical]
[-HSC <hierarchical_separator>]
[-LIMit <int>]
[-REGEXP]
[-SCOPE <pathname>]
[-SENsitive | -NOSENsitive]
[-Golden | -Revised | -Both]
(TCL_SETUP/TCL_LEC mode)
Searches for the specified object and returns a design database object handle or list of
handles for a design object or list of objects. The Tcl-based find and find_cfm commands
are both useful for searching design information. They can both be used to look up design
objects, such as instances, ports, pins, and nets. The find_cfm command, however, is the
only choice for low power queries as it can also query for power intent objects, Liberty library
cells, and 1801 rule filters.
Parameters
Examples
For example, the following code uses a regular expression to find all the instances whose
name starts with RAM under the instance of DTMF_INST.
TCL_SETUP> find_cfm -instance -regexp {/DTMF_INST/RAM\w+} /DTMF_INST/
RAM_128x16_TEST_INST /DTMF_INST/RAM_256x16_TEST_INST
To view the contents of a collection, first assign the collection to a variable and use the
query_collection Tcl command to view the contents:
TCL_SETUP> set z [find -instance xL* -collection]
collection_1
TCL_SETUP> query_collection $z
xLog
Wildcards in find_cfm -pin -hierarchical do not match across hierarchical separators. In this
case, IC/I1 are two design hierarchies before the flatten command, and therefore IC*I1 will
not match it.
TCL_SETUP> find_cfm -pin -hierarchical *
/IA/A /IA/Y /IA/IB/A /IA/IB/Y /IA/IB/IC/A /IA/IB/IC/Y /IA/IB/IC/I1/A /IA/IB/IC/I1/
Y
foreach_in_collection
foreach_in_collection <var>
<collection>
<body>
(TCL_SETUP/TCL_LEC mode)
Iterate through all objects in the collection and apply the commands in the script provided as
<body>.
Parameters
Example
TCL_SETUP> foreach_in_collection y $z {puts $y}
u_gsw
u1
get_attribute
get_attribute
<object | object_list> [<-all | attribute_name>] [<var_name>]
(TCL_SETUP/TCL_LEC mode)
Parameters
<object_type> Specifies the object type. For a list of all the available object
types, use the report_tcl_attribute command.
-all Returns all attribute names with their values in a list format, as
{<attribute_name> <value> <attribute_name>
<value> ... }
<attribute_name> Specifies the name of the attribute. The default is * (wildcard).
<var_name> Specifies the name of the Tcl variable that will contain the value
of the requested attribute. If the variable does not exist in the
current scope, it is created automatically. When this option is
used, the command itself has no return value.
When a list of objects is specified, the option var_name is not
supported. For example, the following is not supported:
get_attr [find_cfm -pin {i1/din[*]}] bus_idx
var1
Examples
■ In the following example, OBJ1 is a port object. The following command returns an
attribute name of name with a value of clk1[7], an attribute name of location with a
value of test.v 41 {}, and so on:
TCL_VERIFY> get_attribute OBJ1 -all
name {clk1[7]} location {test.v 41 {}} ...
■ In the following example, the get_attribute command retrieves the value of two
attributes for object OBJ1:
TCL_VERIFY> get_attribute OBJ1 bus_width var1 bus_idx var2
■ In the following example, the get_attribute command retrieves the value for the
bus_idx variable for objects OBJ1 and OBJ2:
TCL_VERIFY> get_attribute OBJ1 OBJ2 bus_idx var1
■ The following example illustrates that this command can accept a list of objects of the
same type. For example:
get_attribute [find_cfm -instance] library
get_compare_points
get_compare_points
[-PO | -DFf| -DLat |-Bbox| -Cut] [-SIze | -SUPport]
[-EQuivalent |-INvequivalent| -NONequivalent| -ABort| -NOtcompared]
[-COunt]
(TCL_LEC mode)
Queries for multiple objects and returns a list of compare point object handles or a count of
the selected compare points. A compare point handle is a MAP_POINT object handle.
Parameters
Example
TCL_LEC> get_compare_points
(G)6(R)6 (G)7(R)7 (G)8(R)8 (G)9(R)9
get_compare_result
get_compare_result <obj_handle>
(TCL_LEC mode)
Returns compare results for the specified compare point. The key point is an object handle
of the COMPARE_POINT type. The returned result is POS_EQ, NEG_EQ, DIFF,
NOT_COMPARED, or ABORT.
Parameters
None.
Example
get_compare_result takes only arguments of the object handle type generated from the
command get_compare_point The following example illustrates how to use this
command:
TCL_LEC> set a [get_compare_points -dff]
(G)9(R)9
TCL_LEC> get_compare_result [lindex $a 0]
Equivalent
get_exit_code
get_exit_code
(TCL_SETUP/TCL_LEC mode)
Returns the run status without exiting the Conformal software. The status codes are:
Bit Condition
0 Internal Error
1 No equivalent points during comparison
2 Command error
3 Unmapped points or extra POs
4 Non-equivalent points during comparison
5 Abort or uncompared points exist during any comparisons.
6 Abort or uncompared points exist during the last comparision or hierarchical
comparison.
Note: For bits 0, and 2 through 5, once they are set to 1, they will remain at 1. For bit 1, once
it is set to 0, it will remain at 0.
Examples
■ Example Case 1:
Start Conformal and then exit immediately
Status = 2 (00010 in binary). There are no equivalent points since there was no
comparison. Thus, bit 1 is set.
■ Example Case 2:
Comparison produced a non-equivalent point, an abort point, and an equivalent point.
Status = 48 (110000 in binary). Bits 4 and 5 are set to flag the abort and non-equivalent
points.
■ Example Case 3:
Comparison produced all non-equivalent points.
Status = 18 (010010 in binary). Bits 1 and 4 are set to show two conditions: During this
get_current_module
get_current_module
(TCL_SETUP/TCL_LEC mode)
Parameters
None.
Example
TCL_LEC> get_current_module
err_detect
You can also use the related command report_modules -all to show all the available
module names.
get_fanins
get_fanins <obj_handle>
(TCL_SETUP/TCL_LEC mode)
Queries for multiple objects and returns a list of fan-in gate handles for the specified gate
object handle. The type of object handle is a FLAT_GATE.
Example
The argument of the command get_fanins is not a gate name, but the type of an object
handle, which is the 0th (first) element from a Tcl list generated from the Tcl built-in command
lindex.
get_fanouts
get_fanouts <obj_handle>
(TCL_SETUP/TCL_LEC mode)
Queries for multiple objects and returns a list of fan-out gate handles for the specified gate
object handle. The type of object handle is a FLAT_GATE.
Parameters
None.
Example
The argument of the command get_fanins is not a gate name, but the type of an object
handle, which is the 0th (first) element from a Tcl list generated from the Tcl built-in command
lindex.
get_gate_count
get_gate_count [-golden |-revised]
(TCL_SETUP/TCL_LEC mode)
Returns the gate count for the specified design. The default design is Golden.
Parameters
None.
Example
The following example illustrates how to use the command to get a gate count of the design:
TCL_LEC> get_gate_count
2116
get_gate_id
get_gate_id <obj_handle>
(TCL_SETUP/TCL_LEC mode)
Returns the gate id for the specified flattened gate object handle.
Note: The Conformal software automatically assigns ID numbers. They can differ from one
version to another. Always use ID numbers assigned by the software version you are running.
Parameters
None.
Example
The following example shows how to get the id number of the gate t[0]:
TCL_LEC> get_gate_id [lindex [find -gate {t[0]}] 0]
13
get_gate_type
get_gate_type <obj_handle>
(TCL_SETUP/TCL_LEC mode)
Returns the gate type of the specified obj_handle. The type of object handle is
FLAT_GATE.
Parameters
None.
Example
The following example shows how to get a gate's type. For hierarchical instances, use the
command report_gate first to retrieve the gate name.
TCL_LEC> report_gate /syndrm/gen_synvalid1/del_regout/q\[0\]
================================================================================
Pin-name ID (Golden) Type Tie Gate-name
================================================================================
171 DFF /syndrm/gen_synvalid1/del_regout/regout_reg[0]
------ Fanins ------------------------------------------------------------------
1: 'S' 533 ZERO /syndrm/gen_synvalid1/del_regout/N$1
2: 'R' 533 ZERO /syndrm/gen_synvalid1/del_regout/N$1
3: 'CK' 14 PI /clk
4: 'D' 2109 MUX /syndrm/gen_synvalid1/del_regout/U$1/U$1
------ Fanouts -----------------------------------------------------------------
1: 524 AND (L0) /syndrm/gen_synvalid1/dec/U$23
2: 2004 AND /syndrm/gen_synvalid1/dec/U$22
3: 2067 XOR /syndrm/gen_synvalid1/dec/U$2
================================================================================
DFF
get_handle_type
get_handle_type <obj_handle>
(TCL_SETUP/TCL_LEC mode)
Returns the object type of the specified object handle. The returned result is one of the
following strings:
■ MODULE
■ MODULE_INSTANCE
■ MODULE_PORT
■ MODULE_INSTANCE_PIN
■ MODULE_NET
■ HIERARCHY_INSTANCE
■ HIERARCHY_PORT
■ HIERARCHY_INSTANCE_PIN
■ HIERARCHY_NET
■ FLAT_GATE
■ MAP_POINT
Parameters
None.
Example
The following examples illustrates how to use this command to retrieve various handle types:
TCL_LEC> get_handle_type [lindex [find -module {syndrome_erdet}] 0]
MODULE
TCL_LEC> get_handle_type [lindex [find -gate \
{/syndrm/gen_synvalid1/del_regout/regout_reg[0]}] 0]
FLAT_GATE
TCL_LEC> get_handle_type [lindex [find -instance \
{/syndrm/gen_synvalid1/del_regout}] 0]
HIERARCHY_INSTANCE
TCL_LEC> get_handle_type [lindex [find -net /syndrm/gen_synvalid1/rst] 0]
HIERARCHY_NET
get_instances
get_instances [-all_hierarchy] <obj_handle>
(TCL_SETUP/TCL_LEC mode)
Queries for multiple objects and returns a list of instances associated with the specified object
handle.
Parameters
Example
This command takes the argument of the type of an object handle, which should be generated
by both Tcl command lindex and Conformal Tcl command find.
The following example illustrates how to list the instance that identifies itself
TCL_LEC> get_instances [lindex [find -gate \
{/syndrm/gen_synvalid1/del_regout/regout_reg[0]}] 0] \
{/syndrm/gen_synvalid1/del_regout/regout_reg[0]}
get_keypoint
get_keypoint [-golden | -revised] <obj_handle>
(TCL_SETUP/TCL_LEC mode)
Returns the key point (FLAT_GATE type) of a specified compare point. The object handle will
be a MAP_POINT type.
Parameters
Example
The following example illustrates how to get the key point from a specified pair of mapped
points
TCL_LEC> set a [get_map_points -dff]
(G)26(R)171 (G)27(R)74 (G)28(R)75 (G)29(R)76 (G)30(R)77
get_license_mode
get_license_mode
(TCL_SETUP/TCL_LEC mode)
Parameters
None.
Example
The following example illustrates how to get the license being used in the current session:
TCL_LEC> get_license_mode
Low_Power_EC
TCL_SETUP> get_license_mode
Low_Power_GXL
get_map_points
get_map_points
[-PO | -DFf| -DLat |-Bbox| -Cut] [-SIze | -SUPport]
[-EQuivalent |-INvequivalent| -NONequivalent| -ABort| -NOtcompared]
[-COunt]
(TCL_LEC mode)
Queries for multiple objects and returns a list of map point object handles or a count of the
selected map points. A map point handle is a MAP_POINT object handle.
Parameters
Example
The following example shows how to get the map points of the selected category:
TCL_LEC> get_map_point -PO
(G)24(R)24 (G)25(R)25
get_module_definition
get_module_definition <obj_handle>
(TCL_SETUP/TCL_LEC mode)
Returns a module definition for the specified object handle, where <obj_handle> is one of
the following types:
■ MODULE: define itself
■ MODULE_INSTANCE: define the module of the specified instance
■ MODULE_PORT: not applicable
■ MODULE_INSTANCE_PIN: not applicable
■ MODULE_NET: not applicable
■ HIERARCHY_INSTANCE: define the module of the specified instance in a hierarchical
context.
■ HIERARCHY_PORT: not applicable
■ HIERARCHY_INSTANCE_PIN: not applicable
■ HIERARCHY_NET: not applicable
■ FLAT_GATE: define the module of the specified flattened gate
■ MAP POINT: not applicable
Parameters
None.
Example
For modules, this command returns the definition:
TCL_LEC> get_module_definition [lindex [find -module reg_3] 0]
reg_3
For instances, this command returns the module name from which this instance is
instantiated:
TCL_LEC> get_module_definition [lindex [find -instance {/syndrm}] 0]
syndrome_erdet
get_module_instances
get_module_instances <modTclObj>
(TCL_SETUP/TCL_LEC mode)
Parameters
None.
Example
TCL_SETUP> set my_mod [find -single -module my_dlat]
my_dlat
get_names
get_names <obj_handles>
(TCL_SETUP/TCL_LEC mode)
Queries for multiple objects and returns a name or list of names for the specified object
handles.
Parameters
None.
Example
The following example illustrates how to use the commands to retrieve the names from a list
of objects
TCL_LEC> find -instance {/syndrm/gfcmult1*}
/syndrm/gfcmult1 /syndrm/gfcmult1_1 /syndrm/gfcmult1_2 /syndrm/gfcmult1_3 /syndrm/
gfcmult1_4 /syndrm/gfcmult1_5 /syndrm/gfcmult1_6 /syndrm/gfcmult1_7 /syndrm/
gfcmult1_8 /syndrm/gfcmult1_9 /syndrm/gfcmult1_10 /syndrm/gfcmult1_11 /syndrm/
gfcmult1_12 /syndrm/gfcmult1_13 /syndrm/gfcmult1_14 /syndrm/gfcmult1_15
get_nets
get_nets [-all_hierarchy] <obj_handle>
(TCL_SETUP/TCL_LEC mode)
Queries for multiple objects and returns a list of nets for the specified object handle.
Parameters
Example
User can use get_nets * to report all the nets used in the design.
The following code illustrates using the command to get a list of the nets that connects to
instance /syndrm/gfcmult1_1
TCL_LEC> get_nets [lindex [find -instance {/syndrm/gfcmult1_1}] 0]
get_parent
get_parent <obj_handle>
(TCL_SETUP/TCL_LEC mode)
Returns a handle to the parent of the specified object handle, where <obj_handle> is one
of the following types:
■ MODULE: not applicable
■ MODULE_INSTANCE: return the module that contains the specified instance
■ MODULE_PORT: return the module that contains the specified port
■ MODULE_INSTANCE_PIN: return the module that contains the specified pin
■ MODULE_NET: return the module that contains the specified net
■ HIERARCHY_INSTANCE: return the module definition of the instance
■ HIERARCHY_PORT: return the hierarchical instance that contains the specified port in a
hierarchical context
■ HIERARCHY_INSTANCE_PIN: return the hierarchical instance that contains the
specified pin in a hierarchical context
■ HIERARCHY_NET: return the hierarchical instance that contains the specified net in a
hierarchical context
■ FLAT_GATE: return the hierarchical instance that contains the specified flattened gate in
a hierarchical context
■ MAP POINT: not applicable
Parameters
None.
Example
Refer to the following example on how to get a handle to the parent of the specified object
handle
TCL_LEC> get_parent [lindex [find -instance {/syndrm/gfcmult1_1}] 0]
/syndrm
TCL_LEC> get_parent [lindex [find -net {/syndrm/gfcmult1_1/clk}] 0]
/syndrm/gfcmult1_1
get_pins
get_pins [-all_hierarchy] <obj_handle>
(TCL_SETUP/TCL_LEC mode)
Queries for multiple objects and returns a list of pins associated with the specified object
handle.
Parameters
Example
TCL_LEC> get_pins [lindex [find -instance {/syndrm/macreg}] 0]
// Command: find -instance /syndrm/macreg
{U$1/I0} {U$1/O} {U$2/I0} {U$2/O} {U$3/I0} {U$3/O} {U$4/I0} {U$4/O} {U$5/I0} {U$5/
O} {U$6/I0} {U$6/O} {U$7/I0} {U$7/O} {U$8/I0} {U$8/O} {q_reg[7]/S} {q_reg[7]/R}
{q_reg[7]/CK} {q_reg[7]/D} {q_reg[7]/Q} {q_reg[7]/QN} {q_reg[6]/S} {q_reg[6]/R}
{q_reg[6]/CK} {q_reg[6]/D} {q_reg[6]/Q} {q_reg[6]/QN} {q_reg[5]/S} {q_reg[5]/R}
{q_reg[5]/CK} {q_reg[5]/D} {q_reg[5]/Q} {q_reg[5]/QN} {q_reg[4]/S} {q_reg[4]/R}
{q_reg[4]/CK} {q_reg[4]/D} {q_reg[4]/Q} {q_reg[4]/QN} {q_reg[3]/S} {q_reg[3]/R}
{q_reg[3]/CK} {q_reg[3]/D} {q_reg[3]/Q} {q_reg[3]/QN} {q_reg[2]/S} {q_reg[2]/R}
{q_reg[2]/CK} {q_reg[2]/D} {q_reg[2]/Q} {q_reg[2]/QN} {q_reg[1]/S} {q_reg[1]/R}
{q_reg[1]/CK} {q_reg[1]/D} {q_reg[1]/Q} {q_reg[1]/QN} {q_reg[0]/S} {q_reg[0]/R}
{q_reg[0]/CK} {q_reg[0]/D} {q_reg[0]/Q} {q_reg[0]/QN}
get_ports
get_ports [-all_hierarchy] <obj_handle>
(TCL_SETUP/TCL_LEC mode)
Queries for multiple objects and returns a list of ports associated with the specified object
handle.
Parameters
Example
TCL_LEC> get_ports [lindex [find -module {reg_3}] 0]
// Command: find -module reg_3
{d[7]} {d[6]} {d[5]} {d[4]} {d[3]} {d[2]} {d[1]} {d[0]} clk {q[7]} {q[6]} {q[5]}
{q[4]} {q[3]} {q[2]} {q[1]} {q[0]}
get_primitive_type
get_primitive_type <obj_handle>
(TCL_SETUP/TCL_LEC mode)
Returns the primitive type for the specified instance object handle, where <obj_handle> is
one of the following:
■ MODULE_INSTANCE
■ HIERARCHY_INSTANCE
■ FLAT_GATE
Parameters
None.
Example
The following example illustrates how to use the command to get the gate type of the
specified gate.
TCL_LEC> report_gate /u1/x0/Q
================================================================================
Pin-name ID (Golden) Type Tie Gate-name (Library: LP_DFF)
================================================================================
9 DFF /u1/x0/U$1
------ Fanins ------------------------------------------------------------------
1: 'S' 12 ZERO /ZERO
2: 'R' 13 ZERO /ZERO
3: 'CK' 14 AND (L0) /u1/x0/U$3
4: 'D' 18 INV /u1/u0/U$1
------ Fanouts -----------------------------------------------------------------
1: 19 BUF /u1/x0/U$1/Q
================================================================================
0
TCL_LEC> get_primitive_type [lindex [find -gate /u1/x0/U\$1/Q] 0]
dff
get_project_name
get_project_name
(TCL_SETUP/TCL_LEC mode)
Parameters
None.
Example
TCL_SETUP> get_project_name
// Error: Project is not set
get_property
get_property <obj_handle> <property_type>
(TCL_SETUP/TCL_LEC mode)
Returns the property of the specified object handle. The following lists the object handle one
of the following types, with their property types and return values.
■ MODULE
Property Type: BlackBox; Return Value: YES, NO
Property Type: InLib; Return Value: YES, NO
Include the InLib property to test whether the module definition is defined in the library
space (YES) or design space (NO): that is, it tests whether the module definition is
imported by the READ LIBRARY or READ DESIGN command.
■ MODULE_INSTANCE
Property Type: Primitive; Return Value: YES, NO
Property Type: CutPoint; Return Value: YES, NO
Include the CutPoint property to test whether the module definition is a cut point: that is,
it tests whether you have run the ADD CUT POINT command on this module definition.
■ MODULE_PORT
Property Type: Direction; Return Value: INPUT, OUTPUT, BIDIR
■ MODULE_INSTANCE_PIN
Property Type: Direction; Return Value: INPUT, OUTPUT, BIDIR
■ MODULE_NET
Property Type: NetType; Return Value: TIE0, TIE1, WAND, WOR, TRI, TRI0, TRI1,
TRIAND, TRIOR, TRIREG, REG, GLOBAL, TIEX, TIEZ, WIRE
Note: GLOBAL applies to those signals that cross multiple modules (for example,
assertions).
■ HIERARCHY_INSTANCE
Property Type: BlackBox; Return Value: YES, NO
■ HIERARCHY_PORT
Property Type: Direction; Return Value: INPUT, OUTPUT, BIDIR
■ HIERARCHY_INSTANCE_PIN
Property Type: Direction; Return Value: INPUT, OUTPUT, BIDIR
■ HIERARCHY_NET
Property Type: NetType; Return Value: TIE0, TIE1, WAND, WOR, TRI, TRI0, TRI1,
TRIAND, TRIOR, TRIREG, REG, GLOBAL, TIEX, TIEZ, WIRE
Note: GLOBAL applies to those signals that cross multiple modules (for example,
assertions).
■ FLAT_GATE
Property Type: BlackBox; Return Value: YES, NO
Property Type: Golden; Return Value: YES, NO
Property Type: Revised; Return Value: YES, NO
■ MAP POINT: not applicable
Property Type: Result; Return Value: POS_EQ, NEG_EQ, DIFF, ABORT, UNKNOWN
Parameters
None.
Example
TCL_LEC> get_property [lindex [find -gate /u1/x0/U\$1/Q] 0] golden
YES
get_relative_path
get_relative_path <full_file_path>
(TCL_SETUP/TCL_LEC mode)
Returns an equivalent file path that is relative to the current working directory.
Parameters
Example
For example, assume the current working directory is /home/conformal:
TCL_LEC> pwd
/home/conformal
TCL_LEC> get_relative_path /home/conformal/foo/bar
foo/bar
TCL_LEC> get_relative_path /home/library/etc/mylib.lib
../library/etc/mylib.lib
get_root_module
get_root_module [-golden | -revised]
(TCL_SETUP/TCL_LEC mode)
Returns the name of the root module for the specified design. The default design is Golden.
Parameters
None.
Example
The following example illustrates how to look up the root module name.
TCL_LEC> get_root_module
err_detect
Furthermore, users can also use the command report_modules -all to list all the
module names on both Golden and Revised side.
get_top_module
get_top_module [-golden | -revised]
(TCL_SETUP/TCL_LEC mode)
Returns the name of the top module for the specified design. The default design is Golden.
Parameters
None.
get_unmap_points
get_unmap_points
[-PI|-PO|-DFF|-Dlat|-Bbox|-Cut|-Z]
[-INPUT][-OUTPUT]
[-Size|-SUpport]
[-Extra|-UNReachable|-NOTmapped]
[-GOLden|-REvised|-BOth]
[-COunt]
(TCL_LEC mode)
Queries for multiple objects and returns a list of unmap point object handles or a count of the
selected unmap points. An unmap point handle is a MAP_POINT object handle.
Parameters
get_version_info
get_version_info
(TCL_SETUP/TCL_LEC mode)
Returns a TCL list of the version related info, including version_num, build_date, 32 or
64 bit, host name, and platform.
Parameters
None.
help
help [command_name]
(TCL_SETUP/TCL_LEC mode)
Returns the command usage of the specified command or a list of all Conformal Tcl
commands if you do not specify a command.
Parameters
None.
index_collection
index_collection <collection> <index>
(TCL_SETUP/TCL_LEC mode)
Returns a object that exists at the specified index of the specified object collection.
Parameters
Example
The following command set returns the object that exists at the index number 2 in the object
collection referenced by $insts:
TCL_LEC> set insts [find_cfm -instance * -collection]
collection_0
TCL_LEC> set obj [index_collection $insts 2]
/ur1
ncdecrypt
ncdecrypt <input_file | -version>
(TCL_SETUP/TCL_LEC mode)
Decrypts the specified file, which was encrypted using the ncencrypt command. Writes the
contents into the buffer for the Tcl interpreter to evaluate. This command does not write out
to a file.
If the encrypted file uses a user-defined key, you must set the environment variable
NCPROTECT_KEYDB to the directory that contains the public key needed to decrypt the file
before using the ncdecrypt command.
setenv NCPROTECT_KEYDB <path>
Parameters
objtype
objtype <obj_handle>
(TCL_SETUP/TCL_LEC mode)
Returns the type of an native TCL object, for example string and list, or Conformal design
object handle type (i.e. vpxhandle).
Parameters
None.
Example
TCL_LEC> objtype [lindex [find -instance {/syndrm/gfcmult1_1}] 0]
vpxhandle
TCL_LEC> objtype a
parsedVarName
query_collection
query_collection <collection>
[-limit <integer>]
(TCL_SETUP/TCL_LEC mode)
Returns as a TCL list all or specified number of objects from a collection of objects.
Parameters
Example
Please refer to the example of sort_collection.
redirect
redirect
[-append] [-variable] <target> <command>
(TCL_SETUP/TCL_LEC mode)
Parameters
Example
Tcl command to redirect. Commands must be quoted. For example:
TCL_LEC> redirect -variable mod "report_modules -golden"
0
TCL_LEC> echo $mod
Golden:
err_detect
decode
syndrome_erdet
gfcmult_12
reg_3
gfcmult_14
gfcmult_16
gfcmult_18
gfcmult_20
gfcmult_22
gfcmult_24
gfcmult_26
gfcmult_28
gfcmult_30
gfcmult_32
gfcmult_34
gfcmult_36
gfcmult_38
gfcmult_40
gfcmult_42
strobex_rst_44
add_45
mux_46 reg_rst
remove_from_collection
remove_from_collection <collection1>
<collection2 | object_list>
[-intersect]
(TCL_SETUP/TCL_LEC mode)
Parameters
Example
TCL_LEC> set b [find_cfm -instance ur1]
/ur1
TCL_LEC> set c [remove_from_collection [find_cfm -instance * -collection] $b]
collection_2
TCL_LEC> query_collection $c
/ud1 /u_iso1 /ur2 /ur3
set_current_module
set_current_module <[which_design] module_name | obj_handle>
(TCL_SETUP/TCL_LEC mode)
Changes the current module. By default, the current module is the root module.
Parameters
Example
The following example illustrates how to use the command to reset the current module.
TCL_LEC> get_current_module
err_detect
TCL_LEC> report_modules -all
Golden design: err_detect(T) decode syndrome_erdet gfcmult_22 gfcmult_12
gfcmult_34 gfcmult_16 gfcmult_18 gfcmult_20 gfcmult_32 gfcmult_24
gfcmult_30 gfcmult_38 gfcmult_40 gfcmult_42 strobex_rst_44 gfcmult_14
gfcmult_26 gfcmult_28 gfcmult_36 add_45 mux_46 reg_3 reg_rst
Revised design: err_detect(T) add_45 reg_rst mux_46 gfcmult_12 reg_3
gfcmult_14 gfcmult_16 gfcmult_18 gfcmult_20 gfcmult_22 gfcmult_24
gfcmult_26 gfcmult_28 gfcmult_30 gfcmult_32 gfcmult_34 gfcmult_36
gfcmult_38 gfcmult_40 gfcmult_42 strobex_rst_44 syndrome_erdet decode
0
TCL_LEC> set_current_module decode
TCL_LEC> get_current_module
decode
sizeof_collection
sizeof_collection <collection>
(TCL_SETUP/TCL_LEC mode)
Parameters
Example
The following example shows how to query the size of a collection:
TCL_LEC> set insts [find_cfm -instance * -collection]
collection_0
TCL_LEC> set obj_cnt [sizeof_collection $insts]
5
sort_collection
sort_collection <collection> [-descending]
(TCL_SETUP/TCL_LEC mode)
Parameters
Example
TCL_LEC> set a [find_cfm -instance u* -collection]
collection_0
TCL_LEC> sort_collection $a
collection_1
TCL_LEC> query_collection $a
/ud1 /u_iso1 /ur1 /ur2 /ur3
tcl_set_command_name_echo
tcl_set_command_name_echo <OFF | ON>
(TCL_SETUP/TCL_LEC mode)
Turns Tcl command set (including nested Tcl commands and Tcl commands in a sourced Tcl
script/file) name echoing on or off. Default is OFF.
Parameters
None.