Setting Up For RedHawk™

VERSION: V2.1-AL-RH101-17MAY2010

©2010 Apache Design Solutions

 Agenda

 Licensing, rh_setup utility

 Input Data Requirements

©2009 Apache Design Solutions

 Documentation

6/24/2010, 2 ©2010 Apache Design Solutions

 Licensing & Running RedHawk

 To run RedHawk, set the RedHawk path and license

- setenv APACHEROOT <choose the version installed on your

server>
- set path = ( $APACHEROOT/bin $path )
- setenv LM_LICENSE_FILE <To your Apache license>
- Then execute RedHawk as:
redhawk &

6/24/2010, 3 ©2010 Apache Design Solutions

 rh_setup

 Utility which simplifies setup tasks for new users –

walks you through

 Builds GSR and run command files

 Automatically finds data files if directory structure

complies with the recommended one

 Allows information to be added incrementally

6/24/2010, 4 ©2010 Apache Design Solutions

 rh_setup Utility

Proposed Dir structure User Inputs

rh_setup.pl script

RedHawk setup files

<design>.gsr run_static.tcl

6/24/2010, 5 ©2010 Apache Design Solutions

 Setting Up for rh_setup Run

 Proposed Directory Structure

Cell placement + power grid

Tech section and all macros used in the design

For power calculation

Location of ideal pwr/gnd sources

Signal nets parasitics (optional)

Apache technology file

Instance Slew/Frequency + Clocks
(optional for static)

Run directories

6/24/2010, 6 ©2010 Apache Design Solutions

 rh_setup script

rh_setup.pl [ -h gives detailed explanation]

Use GSR template with fixed data locations to populate fields easily.

6/24/2010, 7 ©2010 Apache Design Solutions

 rh_setup

 Utility Supports following analysis types

- Static IR/EM Analysis
- Dynamic Analysis
- Low Power Analysis
- CPM

 Utility Supports following modes

- Early Analysis
- Sign Off Analysis

Example usage:
rh_setup.pl -top GENERIC -vdd VDD 1.0 -vss VSS -freq 100e6

6/24/2010, 8 ©2010 Apache Design Solutions

 rh_setup (Cont’d)

Example usage:

 Case 1: If the proposed directory structure is followed

rh_setup.pl -top GENERIC –analysis static –mode sign_off_analysis -
vdd VDD 1.0 -vss VSS -freq 100e6

 Case2: If custom directory structure is followed

rh_setup.pl -top GENERIC –analysis static
–mode sign_off_analysis
-def_files /nfs/yamuna.data/GENERIC/def/*
-lef_files /nfs/yamuna.data/GENERIC/lef/*
-lib_files /nfs/yamuna.data/GENERIC/libs/*
-vdd VDD 1.0 -vss VSS -freq 100e6

6/24/2010, 9 ©2010 Apache Design Solutions

 .lefs, .defs, .libs, .gsr, .tech, .ploc

INPUT DATA PREPARATION

6/24/2010, 10 ©2010 Apache Design Solutions

 RedHawk Input Files

.lefs Design data

Milkyway DB
.defs
Power calc
.libs RedHawk
Technology
Import Design
.tech
Design info Power Calc
.gsr
Parasitic cap Extraction
DSPF/SPEF Static / Dynamic
Slew, Timing
<design>.timing

APL files
cell.spcurrent
cell.cdev

6/24/2010, 11 ©2010 Apache Design Solutions

 Data Preparation

Design Data Characterization (APL)

DEF, LEF, Libs, Pads Current Profiles

Technology Capacitance, ESR
SPEF, STA Leakage
Package netlist Memory models
Delay/Slew

Simulation Conditions GDS Translations

Voltage Memories, IPs

Process, Temperature RDL layers
Power/Ground nets
Modes

6/24/2010, 12 ©2010 Apache Design Solutions

 RedHawk Input Files

FILE FORMATS:

1) LEF: Library Exchange Format: This is a industry standard format that has the
information related to pin description and boundaries of the blocks/instances in the
design.

2) DEF: Design Exchange Format: This contains logical and physical connectivity
between different instances and blocks in the design.

3) LIB: Synopsys Liberty file format: This has several electrical and logical properties
for a cell like: input and output pin properties, information on distributing power
among the different power pins, internal energy of the cell, cell functionality
information, etc.

4) SPEF – SIGNAL Parasitic Exchange Format: This file contains the parasitic (RC)
associated with each nets in the design.

6/24/2010, 13 ©2010 Apache Design Solutions

 Technology File (.tech)

metal <layer> {
thickness <value>
must if C and/or L extraction needed>
resistance <value>
resistance per square
EM <value>
EM current density in (current/length)
above <above a dielectric_layer_name defined in
dielectric>
must if C and/or L extraction needed and no Height
is defined
default NA
}

Use the “rhtech” utility to create the apache tech file from a STARRC-XT file
For the cadence tech file we have an utility “adsTechConverter.pl”

6/24/2010, 14 ©2010 Apache Design Solutions

 Technology File (Cont’d)

via <via_layer_name> {
width { <width> }
resistance <value>
Via resistance
The resistance is specified as it is for the via
EM <value>
Electromigration current limit for the via
UpperLayer <metal_layer_name; must>
LowerLayer <metal_layer_name; must>
}

viamodel <viamodel_name> {
<metal_layer_name> <X1> <Y1> <X2> <Y2>
<via_layer_name> <X1> <Y1> <X2> <Y2>
<metal_layer_name> <X1> <Y1> <X2> <Y2>
}

For vias, “width” or “viamodel” must be specified

6/24/2010, 15 ©2010 Apache Design Solutions

 Technology File (Cont’d)

dielectric <dname> {
constant <value; must if C and/or L extraction needed>
thickness <value defined in length unit above; must>

height <value defined in length unit above>

must if Above is not specified

above <dielectric_layer_name>
above which dielectric layer
must if Height is not specified
}

Needed for capacitance and/or inductance extraction

6/24/2010, 16 ©2010 Apache Design Solutions

 Technology File (Cont’d)
units {
capacitance 1p
ddielectric APACHE_E
inductance 1n
{
resistance 1
constant 3.9
length 1u
thickness 1.47
current 1m
Height 8.59
voltage 1
}
power 1
dielectric APACHE_D6
time 1n
{
frequency 1me
constant 3.9
}
thickness 0.6
metal metal1 {
above APACHE_D5b
Thickness 0.18
}
T 25
dielectric APACHE_D5b
Tnom 110
{
Coeff_RT1 0.00265
constant 3.9
Coeff_RT2 -2.641e-07
thickness 0.4
EM 1.509
above APACHE_D5a
EM_ADJUST 0.016
}
above ILD_B
dielectric APACHE_D5a
}
{
via via1
constant 3.9
{
thickness 1.45
Width { 0.1 }
above APACHE_D4
Resistance 1.5
}
T 25
dielectric APACHE_D4
Tnom 110
{
Coeff_RT1 0.0007815
constant 3.9
Coeff_RT2 -2.574e-06
thickness 0.25
EM 0.158
above APACHE_D3
UpperLayer metal2
}
LowerLayer metal1
}

6/24/2010, 17 ©2010 Apache Design Solutions

 Tech File – Advanced Keywords

 Most of the advanced technology keywords required

especially for 65 nm and below technologies are supported.
Example:
- ETCH_VS_WIDTH_AND_SPACING
- RHO_VS_WIDTH_AND_SPACING
- POLYNOMIAL_BASED_THICKNESS_VARIATION
- RPSQ_VS_WIDTH_AND_SPACING
- THICKNESS_VS_WIDTH_AND_SPACING
- SIDE_TANGENT
- RPV_VS_AREA

6/24/2010, 18 ©2010 Apache Design Solutions

 Identification of Voltage Sources

 Describes the source for the power and ground nets

- Can be specified through PAD_FILES keyword in GSR
- Can also import the pads using “Import pad” command

 Inside the voltage source file, we can specify the sources in different
ways
- Pad instance ( *PAD section )
> <pad_cell_name_1> [<pin_name>| <pin_name> <layer_name>]
- Pad master cell ( *PCELL section)
> <master cell name>
<x source loc> <y source loc> <layer> <P/G pad type>
- Pin location list ( *PLOC section )
> <Net name> <x coord> <y coord> <layer> <POWER | GROUND>
- Pad location with package (* PLOC_PSS )
- Pad master cell used along with package (*PAD_PSS )

 RedHawk will automatically identify the PINS from DEF if you use GSR
keyword 'ADD_PLOC_FROM_TOP_DEF 1” .

6/24/2010, 19 ©2010 Apache Design Solutions

 Identification of Voltage Sources (Cont’d)

*PCELL
DVDD12
DVSS
PASLZ55 VDD
PADLZ55 VSS

*PAD
VDD_PAD1
VSS_PAD45
PVDD1DGZ
17.5 242.0 METAL6 POWER

*PLOC
DVDD1 4905 878.85 METAL4 POWER
DVSS1 4880 938.85 METAL4 GROUND
DVDD2 4905 998.85 METAL4 POWER

6/24/2010, 20 ©2010 Apache Design Solutions

 STA Timing Information From Primetime

 Recommended for Static analysis- provides accurate

transition times and instance frequency
 Required for Dynamic – provides switching windows
 Uses Apache’s PT TCL script to dump data from PT
 Procedure:
- Load design, constraints and Link
- Set appropriate case analysis (same as normal timing sign off)

pt_shell> source pt2timing.tcl

pt_shell> getSTA *

Output STA file is <design>.timing

6/24/2010, 21 ©2010 Apache Design Solutions

 Global System Requirement File
(aka. user controls)

Apache tech lef def/gds lib spef/dspf STA

(slew/clocks)

# GSR keywords

VDD_NETS {
VDD 1.7
# RedHawk interactive commands
VDDA 3.3
import gsr GENERIC.gsr
}
setup design
…
TOGGLE_RATE 0.2

DEF_FILES {
file_16.def top
}
…
6/24/2010, 22 ©2010 Apache Design Solutions
 GSR File Overview

TECH_FILE ads.tech
LIB_FILES {
LIB_FILES {
OR <design>.libs
<path to lib file>
}
<path to lib directory> (all *.lib files in dir)
<path to custom lib file> custom
}
LEF_FILES {
LEF_FILES { OR <design>.lefs
<lef file path>/name1.lef << tech definition }
<lef file path>/name2.lef
}

DEF_FILES { OR DEF_FILES {
<def file path>/name1.def <design>.defs
<def file path>/name2.def TOP < last one to be TOP DEF }
}

6/24/2010, 23 ©2010 Apache Design Solutions

 GSR File Overview (Cont’d)

PAD_FILES {
pad file path name/name1.pad
}

GDS_CELLS {
cell_name1 <path to dir where files for cellname1
reside>
cell_name2 <path to dir where files for cellname2
reside>
}

GSC_FILE <path and name of GSC file>

6/24/2010, 24 ©2010 Apache Design Solutions

 GSR File Overview (Cont’d)

# Net switching activity

TOGGLE_RATE <value>

# Block specific toggle information Order of toggle selection

BLOCK_TOGGLE_RATE {
<block_name> <value>  VCD_FILE
...
}  INSTANCE_TOGGLE_RATE /
INSTANCE_TOGGLE_RATE_FILE
# Obtain toggle from VCD
VCD_FILE {  BLOCK_TOGGLE_RATE /
... BLOCK_TOGGLE_RATE_FILE
}
 TOGGLE_RATE
# Instance specific toggle
INSTANCE_TOGGLE_RATE {
<name of instance> <toggle rate>
}

6/24/2010, 25 ©2010 Apache Design Solutions

 GSR File Overview (Cont’d)

# Design timing information

STA_FILE {
FREQ_OF_MISSING_INSTANCES <value in Hz>
<name of design> <design timing data>  From running TCL program
}
 The frequency value that
# Dominant frequency of design captures most of the power in
FREQUENCY <value in Hz>
the design
# Input transition time
INPUT_TRANSITION <value in s>

6/24/2010, 26 ©2010 Apache Design Solutions

 GSR File Overview (Cont’d)

# Power specification
BLOCK_POWER_FOR_SCALING {
FULLCHIP <design_name/block/instance>  Fullchip or block or cell
<total power>
power can be specified
CELLTYPE <cell name> <power>
<block name> <instance name> <power>
}  Honor user provided
INSTANCE_POWER_FILE {
instance specific power
<name of file>
}

6/24/2010, 27 ©2010 Apache Design Solutions

 GSR Options for Design Report

 Keywords supported in the constraint file

# Point the constraint file to dump design – STATIC_IR
report, it currently supports dynamic – STATIC_PAD_CURRENT
simulation, static simulation, low power
simulation and power calculation – DYNAMIC_EFFVDD_TW
– DYNAMIC_MINVDD_TW
DESIGN_CONSTRAINT_FILE – DYNAMIC_MINVDD_CYC
{ – DYNAMIC_PEAK_PAD_CURRENT
constraint – RAMPUP_VOLTAGE
}
– PEAK_RUSH_CURRENT
– OFF_STATE_LEAKAGE_CURRENT

6/24/2010, 28 ©2010 Apache Design Solutions

 Sample constraint file for Design Report

6/24/2010, 29 ©2010 Apache Design Solutions

 Run Command File Overview

# Import data
import gsr GENERIC.gsr
setup design

# Calculate power
perform pwrcalc

# Power/Ground grid extraction

perform extraction -power –ground

# Lumped resistance (in Ohms)

# for package, wirebond and pads
setup package -power -r 0.005 –l 2.5 –c 5
setup package -ground -r 0.005 –l 2.5 –c 5
setup wirebond -power -r 0.01 –l 2.2 –c 1.42
setup wirebond -ground -r 0.05 –l 1.7 –c 0.2
setup pad -power -r 0.001
setup pad -ground -r 0.001

# Static IR analysis
perform analysis –static
report result

6/24/2010, 30 ©2010 Apache Design Solutions

 How to get Help!!!
 Apache Online Customer Support Center
– http://support.apache-da.com
– Email: [email protected]

6/24/2010, 31 ©2010 Apache Design Solutions

 THANK YOU !!!

6/24/2010, 32 ©2010 Apache Design Solutions