1S2R(1) ALLIANCE USER COMMANDS S2R(1)
2
6 s2r - Process mapping from symbolic layout to physical layout
7
9 s2r [-tc1rv] source [result]
10
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 Web : http://asim.lip6.fr/recherche/alliance/
18 E-mail : alliance-users@asim.lip6.fr
19
21 The goal of s2r is to perform the translation from the symbolic layout
22 to physical layout for the foundry. s2r uses a technolgy file whose
23 name is defined by the environnement variable RDS_TECHNO_NAME.
24 Some cells, like I/O pads, are specific to a given foundry. In the
25 symbolic methodology, these cells are phantom cells. It means that
26 only their abutment box and and connectors are present. s2r wil sub‐
27 stitute physical cells to the symbolic phamtom cells. Beware, this
28 implies that the manufacturer cells must be modified by hand to ensure
29 the abutment box is a symbolic grid step multiple, and that the real
30 connectors are centered on symbolic grid.
31 In order for the replacement to work well, the physicals cells must
32 have the abutment box lower left corner at coordinate (0,0) The name of
33 cells to be replaced are written in the catalog file with the G
34 attribute, see catal(5) for details on that file. See also ring(1) for
35 more on pads. Output can be generated in either cif or gds formats, to
36 fit the manufacturer requirements.
37 Mainly two kinds of users are concerned with s2r :
39 experts they should be able to parametrize the technology
41 file for a new process technology file is
42 described in techno(5).
43 designers they are not directly concerned with the target
45 process, but need to be able to compute real
46 capacitances for simulation.
47 The source argument is the name of the symbolic layout file to be
49 translated. The optional result argument indicates the name to be
50 given to the real layout output. This name is also the name of the top
51 level model of the layout hierarchy. If result name is omitted, then
52 source name is used.
53 Six environment variables must be set for proper usage of s2r, all of
55 them having default values, thus ensuring the possibility of using it
56 ``as it is''.
57 MBK_IN_PH The input format for symbolic layout is given by
59 this environment variable. The possible values
60 are cp, ap. Default is cp. See MBK_IN_PH(1) for
61 details.
62 MBK_CATA_LIB Sets the directories that are to be searched thru
64 for reading files. The searching mechanism first
65 look in MBK_WORK_LIB(1) MBK_WORK_LIB defines the
66 path where the generated file is saved. Make sure
67 the write permissions are set up correctly, other‐
68 wise no save will occur.
69 MBK_CATAL_NAME This indicates the name of the catalog file used
71 for pad substitution. For the appropriate syntax
72 of this file, see catal(5).
73 RDS_IN Defines the format to be used as input for cell
75 substitution. The available ones are cif and gds
76 (default one). The cells to be parsed must not
77 containt 45 degrees wires. If an unknown layer is
78 encountered, the entire cell will be skipped.
79 RDS_OUT Gives the format of the output file. This may be
81 either cif or gds (default is gds).
82 RDS_TECHNO_NAME This points to the technology file to be used for
84 symbolic to real translation. This file is in
85 general shared between all the designers. it is
86 the full path name to the file location, with the
87 extension.
88
90 Without option, s2r should produce a layout that fits for the foundry.
91 Nevertheless, its behaviour can be modified when invoked with the fol‐
92 lowing options:
93 -t Suppress the denotching phase. s2r performs gap
95 filling, denotching in order to avoid DRC errors.
96 This operation is time consuming. It is mandatory
97 for the foundry but not really useful for capaci‐
98 tance evaluation.
99 -c Deletes connectors and node names at all hierarchy
101 level. Theses objects link the physical view and
102 the logical view of a chip. If simulation is to
103 be done after physical mapping, connectors must
104 appear, so that the extractors and simulators can
105 use them. This must not be used when preparing a
106 final layout for the foundry.
107 For the factory, the top level connectors are for‐
108 bidden, since they do not represent any physical
109 reality.
110 -1 Creates the top level cell with the instances as
112 black boxes. This may be useful for hierarchical
113 extractors, since the file size may be greatly
114 reduced.
115 -r does not replace black boxes. Cells flagged with
117 the G attribute in the catal(5) file will not be
118 replaced by their equivalent layout loaded from
119 disk.
120 -v verbose mode on.
122
126 You should first have a correct execution environment :
127 It is recommended to put it in the ``.cshrc'' file if in c
128 shell, as in the example below.
129 setenv MBK_IN_PH ap
131 setenv MBK_WORK_LIB ~fred/mbk/layout
132 setenv MBK_CATA_LIB ~franck/s2r:/alliance/cells
133 setenv MBK_CATAL_NAME catalog
134 setenv RDS_TECHNO_NAME /labo/etc/prol15.rds
135 setenv RDS_IN gds
136 setenv RDS_OUT gds
137 s2r -c na2_y
138 This invocation will produce the cell na2_y from the standard
139 cell library in real layout, without connectors, scotches if
140 needed, in gds format.
141
143 mbk(1), ring(1), MBK_IN_PH(1), MBK_CATA_LIB(1), MBK_WORK_LIB(1),
144 MBK_CATAL_NAME(1), RDS_IN(1), RDS_OUT(1), RDS_TECHNO_NAME(1),
145 techno(5), catal(5).
146
149 The actual version of the gds parser and driver doesn't translate nei‐
150 ther connectors, nor node names. If an extraction on s2r output is
151 needed, cif format will create the connectors using cif extension 4X,
152 and the node names with 4N.
153ASIM/LIP6 October 1, 1997 S2R(1)