RING(1)

NAME
ring - PAD RING router

SYNOPSIS
ring source result [ stat ]

ORIGIN
This software belongs to the ALLIANCE CAD system from the
CAO-VLSI team at MASI laboratory, University P. et M. Curie
4, place Jussieu ; 75252 PARIS Cedex 05 ; FRANCE
Fax: (33-1) 44.27.62.86 ; E-mail: cao-vlsi@masi.ibp.fr

DESCRIPTION
source defines two input files:
    -- the file describing the input netlist (MBK_IN_LO).
        example: source.al

    -- the parameter file: source.rin
    This file contains 5 sections, 4 for the sides and one for the power sypply width.

    example:
        east ()
        north (
        p_pck p_i0 p_i1
        p_i3)
        south (p_vssb p_vddb p_i2)
        width (vss 50 vdd 80)

    The separators which are allowed between instance names are spaces, tabulations and new line.

    -- east(), north(), south(), west() define the relative order of pads using the pad instance names.

    For the north() and south() sections, the declarations of instance names has to be from the left (first pad) to the right (last pad).

    For the east() and west() sections, the declarations of instance names have to be from the bottom (first pad) to the top (last pad).

    one or more sections may be absent, it means that there is no pad on theses sides, of course at least one section have to be present.

    -- the width() section is optional and describes the width of power (vdd), and ground (vss) tracks.

result defines the output file.

    This file contains the layout of the routed circuit (MBK_OUT_PH).
        example: result.ap

    RING uses a catalog file whose name is defined by the environment variable MBK_CATAL_NAME.
    The catalog must contain all the pad model names used in the circuit. The core model-name should not be in the catalog.
    RING creates automatically the corner wires when necessary.

    Example of catalog file:
        a2_y C
        high_y C
        pck_p C
        piot_p C
        po_p C
        pot_p C
        pvdde_p C
        pvddi_p C

[stat] (optional parameter) defines another output file:

    -- the statistic file: result.stat

    It contains data about length (lambdas) and area (lambdas * lambdas) in ALU1 and ALU2, for each equipotential. It describes how many vias were placed.

        example: *** STATISTIC FILE < result.stat > ***

    Equipotential list :