14

---

File Formats

---

• Rail Analysis Files
  • DFII Layer Map File
  • Layer Map File
• Power-Grid View Creation Files
  • DSPF Layermap File
  • LEF Layermap File
  • PGDB Layermap File

Rail Analysis Files

This section lists the rail analysis file formats.

• DFII Layer Map File
• Layer Map File

DFII Layer Map File

The APS/XPS-to-DFII layer map file provides the mapping between the layer names in the extracted view to the DFII layer names.

Multiple extraction layers can be mapped to the same DFII layer.

Sample file name: df2layermap.txt

Format:

type   extraction_layer_name dfII_layer_name

Format Description:

type specifies the type of layer; for example, metal, via, or poly.

extraction_layer_name specifies the name of the layer in the extracted view that is to be mapped to the DFII layer.

dfII_layer_name specifies the name of the DFII layer to which the extracted view layer name is being mapped.

Example:

#<type> <extraction_layer_name> <dfII_layer_name>

via    via3             Via3

metal  mt3              Metal3

via    via2_out_capind  Via2

metal  mt2              Metal2

via    via1             Via1

metal  mt1              Metal1

via    cont_ndiff       Cont

via    cont_pdiff       Cont

Layer Map File

The layer map file or map file provides the mapping between the layer names in the simulation database to those specified in the technology files (qrcTechFile and ICT file) for the EM analysis flow. It maps the layer names in the xDSPF file to the ICT layer names. It is needed under either of the following circumstances:

• When Quantus package uses the layerSetupFile, which includes the "model" keywords to define parasitic resistor model names. For example,
  

  pro_layer=M1 ext_layer=MET1 model=metal1

  In this case, the "metal1" to "M1" mapping needs to be specified in the layer map file.
  The sample command for the above in the .cdsinit file will be specified as follows:

  envSetVal("spectre.envOpts" "emLayerMap" 'string "/your-path/layermapfile")

Sample file name: contactmapfile.txt

Format:

RCX keyword   simulation DB layername  ICT keyword  technology file layername

Format Description:

RCX specifies the keyword for the simulation database.

simulation DB layername specifies the layer names in the simulation database that are to be mapped to the technology file layer names.

ICT specifies the keyword for the technology file.

technology file layername specifies the layer names in the technology file that map to those in the simulation database.

Example:

<RCX keyword> <simulation DB layername> <ICT keyword>  <technology file layername>

RCX   metal1   ICT   mt1

RCX   metal2   ICT   mt2

RCX   metal3   ICT   mt3

RCX   metal4   ICT   mt4

RCX   pl1co    ICT   poly

RCX   VIA1     ICT   via1

Power-Grid View Creation Files

This section lists the power-grid view creation file formats.

• DSPF Layermap File
• LEF Layermap File
• PGDB Layermap File

DSPF Layermap File

This layermap file contains the layer type and layer stack information for the DSPF from the top-most layer to the bottom-most layer. If this order is not followed, the PGDB will not be created.

Sample file name: layermap_dspf.txt

Format:

Layer type   Process layername

Format Description:

Layer type specifies the type of layer: metal, via, or local

Process layername specifies the name of the layer

Example:

#   Layer       Process

#   type        layername

#  ---------   ------------

    metal       m4

    via         via3

    metal       m3

    via         via2

    metal       m2

    via         via1

    metal       m1

    metal       po

    metal       mdtap

LEF Layermap File

A layer mapping file is required for the Rail Analysis library generation flow. The LEF layermap file contains the mapping information to map the layer names in the LEF file to the layer names in the technology file.

Sample file name: lefdef.layermap

Format:

type   technology_layer_name lefdef lef_layer_name

Format Description:

type specifies the type of library layer, for example, metal or via.

technology_layer_name specifies the name of the library layer to map to the LEF layer.

lefdef specifies the keyword for the LEF layer mapping.

lef_layer_name specifies the name of the LEF layer to map to the library layer.

Example:

  type    technology_layer_name      lefdef    M1

  metal    METAL_1                   lefdef    M1
  via      VIA_1                     lefdef    VIA1
  metal    METAL_2                   lefdef    M2
  via      VIA_2                     lefdef    VIA2

where “type” can be poly/via/metal/diff.

PGDB Layermap File

A layer mapping file is required for the library generation flow. The PGDB layermap file contains the mapping information to map the xDSPF layer names that are written in the simulation database to the layer names in the technology file.

Sample file name: pgdb.map

Format:

type    technology_layer_name    pgdb    xDSPF_layer_name     

Format Description:

type specifies the type of library layer. It can be poly/via/metal/diff.

technology_layer_name specifies the name of the library layer to map to the xDSPF layer name.

pgdb specifies the keyword for the xDSPF layer mapping.

xDSPF_layer_name specifies the xDSPF layer name.

Example:

type technology_layer_name pgdb xDSPF_layer_name

# ----   --------------------- ---- ---------------
  poly   POLYCIDE              pgdb    poly
  via    CONT                  pgdb    pl1co
  via    CONT                  pgdb    odCont1
  via    CONT                  pgdb    odCont2
  metal  METAL_1               pgdb    metal1
  via    VIA_1                 pgdb    VIA1
  metal  METAL_2               pgdb    metal2
  via    VIA_2                 pgdb    VIA2
  diff   OD                    pgdb    nwires
  diff   OD                    pgdb    mwires

Example:

type    technology_layer_name  pgdb    xDSPF_layer_name
diff    connectivity           pgdb    nwires
diff    connectivity           pgdb    mwires