1LVX(1)                      ALLIANCE USER COMMANDS                      LVX(1)
2
3
4

NAME

6       lvx - Logical Versus eXtracted net-list comparator
7

SYNOPSIS

9       lvx format1 format2 filename1 filename2 [ -a ] [ -u ] [ -o ] [ -f ]
10
11

ORIGIN

13       This software belongs to the  ALLIANCE CAD SYSTEM developed by the ASIM
14       team at LIP6 laboratory of Université Pierre et Marie CURIE, in  Paris,
15       France.
16
17       Web : http://asim.lip6.fr/recherche/alliance/
18       E-mail : alliance-users@asim.lip6.fr
19

DESCRIPTION

21       lvx  compares  two  gate-level  or block level net-list. The goal is to
22       compare a specification net-list (logical net-list),  the  input  to  a
23       place  and  route tool, with the physical net-list (extracted net-list)
24       obtained by the cougar(1) extractor.
25       The net-list 1 is considered as the logical net-list and net-list 2  as
26       the extracted net-list.
27       lvx is an one-level hierarchical tool:
28
29              The  two net-list are flattened, if the -f option is present, to
30              the cells contained in the catalog file. The path to the catalog
31              file  is  indicated in the MBK_CATA_LIB(1) variable for the cell
32              library, and in  the  MBK_WORK_LIB(1)  variable  with  the  name
33              MBK_CATAL_NAME(1)  for  user blocks ( catal(5) ) that are not to
34              be flattened.
35
36              For both net-list, the instances are considered as black-boxes.
37
38              The two net-list must have the same external connectors names.
39
40              The two net-list must have the same instances names.
41
42              The two net-list must have the same  signals  names  for  uncon‐
43              nected signals.
44
45              The two net-list cannot directly contain transistors.
46
47       Comparison is performed in three steps:
48
49              Compare terminals.
50
51              Compare instances.
52
53              Compare connections.
54
55              Compare unconnected signals.
56
57       If  an  error  occurs during first or second step, a message is immedi‐
58       ately displayed and the third step will not start: lvx  cannot  compare
59       connections (signals) if terminals or instances are not equivalent.
60       The  -o option allows to order connectors if the steps described before
61       have been reached successfully.  Extracted_netlist  is  then  saved  on
62       disk.  The  file  get  the  name  filename2  suffixed  by  the value of
63       MBK_OUT_LO(1) variable.
64       Routers add automatically empty feed-through cells.  These  cells  must
65       not  be  taken  into account in the comparison.  A cell that have the F
66       attribute in the catalog file ( catal (5)  )  is  considered  as  feed-
67       through  cell,  and  are deleted, in memory, from the net-list where it
68       appears.
69

OPTIONS

71       -a     Some routers generate layout with  several  physical  connectors
72              for  power  and  ground ( VDD or VSS ).  If those connectors are
73              not internally connected, they will have different indexed names
74              ( VDD1 , VDD2 etc...) in the extracted net-list.  It is possible
75              to perform reduction on those power and ground connectors before
76              comparison, using the -a option.  After reduction, each instance
77              contains only one VDD connector and one VSS  connector,  as  the
78              main figure.
79
80       -o     In  this  case, lvx produces a modified net-list (saved with the
81              name filename2 ), which is a copy of  net-list  2  with  ordered
82              connectors.   Terminals  and instance connectors are relisted in
83              the order of the models in net-list 1.  The  saved  net-list  is
84              done  with  the  MBK_OUT_LO(1)  format,  so user has to set this
85              variable before running lvx .  If he does not, default value  is
86              used, and net-list 1 could be lost if filename are identical and
87              input format same as output format.
88              If -a option is used, then the saved  net-list  is  the  reduced
89              net-list with only one VDD and one VSS .
90
91       -u     This  option  force  lvx  to check the consistency of unassigned
92              signals between the two netlists.
93
94       -f     The two net-lists are flattened to the leaf cells  contained  in
95              the  catalog  file.  Usually the extracted net-list is a flatten
96              net-list, while the logical one can be a hierarchical net-list.
97

EXAMPLES

99       With  logical_netlist   named   amd2901.vst   and   the   corresponding
100       extracted_netlist  as  amd2901.al containing multiple power connectors,
101       the command line is :
102
103              lvx vst al amd2901 amd2901 -a
104

OUTPUT FILES

106       filename2.xx        Netlist view saved when the -o option  is  present.
107                           The suffixe depend on the MBK_OUT_LO(1) environment
108                           variable.
109

ENVIRONMENT VARIABLES

111       MBK_CATA_LIB        contains the directories where the cell  librtaries
112                           are.   MBK_WORK_LIB  contains the directory path of
113                           the working directory, usually set to . (dot).
114
115       MBK_OUT_LO          contains the expected format of the netlist output.
116
117       MBK_CATAL_NAME      contains the name of the user cell catalog.
118

SEE ALSO

120       cougar(1),     MBK_OUT_LO(1),     MBK_WORK_LIB(1),     MBK_CATA_LIB(1),
121       MBK_CATAL_NAME(1), catal(5) .
122

DIAGNOSTICS

124       The  string  "_logic"  is  appended  to  the  net-list 1 and the string
125       "_extract", is appended to the net-list 2.
126
127       Two kinds of error message can occur:
128
129              A fatal error causes the program to exit.  It happens  when  one
130              of  the  net-lists is not correct, lvx cannot construct internal
131              structure for compare.
132
133              A compare error occurs when the figures are not  identical.   It
134              happens  when basic objects (instances, connectors) do not exist
135              in both net-list, or when connections (signals) do  not  connect
136              same terminals or instances in the two net-lists.
137
138       Exit code 0 is returned for identical net-lists.
139
140
141
142
143
144ASIM/LIP6                       October 1, 1997                         LVX(1)
Impressum