RING(1)

NAME
RING - PAD RING router

SYNOPSIS
RING source result [ stat ]

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

    -- the parameter file: source.rin
    This file consists in 5 sections: 4 for the pad placement on circuit sides, one to define the power sypply width (in lambda units).

    example:
        east () # none pad at east side.
        north (
        p_pck p_i0 p_i1
        p_i3)
        south (p_vssb p_vddb p_i2)
        width (vss 50 vdd 80)

    Separators (spaces, tabulations and new line) are allowed between instance names.

    -- east(), north(), south(), west() define the relative pad order. They use the pad instance names.

    For the north() and south() sections, the instance name declaration are from the left (first pad) to the right (last pad).

    For the east() and west() sections, the instance name declaration are from the bottom (first pad) to the top (last pad).

    Any section may be missing. It means so the revalive side has no pad, however at least one side must has one pad.

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

result defines the output filename.

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

    RING uses a pad library whose path directory is defined with the MBK_CATA_LIB(1) environment variable. It also uses a catalog filename which is defined with the MBK_CATAL_NAME(1) environment variable.
    The catalog must contain all the pad model names used in the circuit. The core model-name must not be present in the catalog.

    Part of catalog file:
        a2_y C
        high_y C
        pck_sp C
        piot_sp C
        pvssick_sp C
        ....
        pvdde_sp C
        pvddi_sp 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 :