Genus: iSpatial (Lab Instructions)

Rapid Adoption Kit (RAK)

Product Version: Genus 22.x, Innovus 22.x and higher versions

July 2024
 Genus iSpatial: RAK

Copyright Statement

© 2024 Cadence Design Systems, Inc. Cadence and the Cadence logo are registered trademarks of
Cadence Design Systems, Inc. All others are the property of their respective holders.

This content is Cadence Confidential and for Cadence customers only. DO NOT DISTRIBUTE.

Learn more at Cadence Learning and Support Portal - https://support.cadence.com

© 2024 Cadence Design Systems, Inc. DO NOT DISTRIBUTE. Page 2
 Genus iSpatial: RAK

Contents
Purpose ....................................................................................................................... 4
1. Introduction .............................................................................................................. 5
1.1 Directory Structure ............................................................................................. 5
1.2 Tool Versions ..................................................................................................... 5
1.3 Terms and Typographic Conventions ................................................................ 5
1.4 Design ................................................................................................................ 5
1.5 LAB Sequence ................................................................................................... 6
1.6 Commands to Navigate Genus Database Design Hierarchy ............................. 6
2. LAB: Genus iSpatial Flow ........................................................................................ 7
2.1 Objective ............................................................................................................ 7
2.2 Lab Files ............................................................................................................ 7
2.3 Running the Lab ................................................................................................. 7
2.4 Understanding the Flow ..................................................................................... 7
2.4.1 Setup (Attribute Settings) ................................................................................ 8
2.4.2 Loading Libraries and Designs ........................................................................ 9
2.4.3 Running Generic Optimization and Mapping (Physical-Aware) ..................... 10
2.4.4 Run iSpatial Optimization with Unified Genus and Innovus Engines............. 11
2.4.5 Write Reports and Files for Handoff to Innovus preCTS ............................... 11
Support ...................................................................................................................... 13
Feedback ................................................................................................................... 13

Learn more at Cadence Learning and Support Portal - https://support.cadence.com

© 2024 Cadence Design Systems, Inc. DO NOT DISTRIBUTE. Page 3
 Genus iSpatial: RAK

Purpose
The purpose of this RAK is to introduce you to the Genus iSpatial flow. This flow has the
following features:
• Integrates fast timing closure with Innovus GigaPlace and GigaOpt engines.
• Provides accurate prediction of timing, area, leakage, and congestion for RTL
designers.
• DB handoff allows Innovus place_opt_design to run faster.

Learn more at Cadence Learning and Support Portal - https://support.cadence.com

© 2024 Cadence Design Systems, Inc. DO NOT DISTRIBUTE. Page 4
 Genus iSpatial: RAK

1. Introduction
In the lab exercises provided in this document, you will learn to use Genus iSpatial.
Read the Genus iSpatial: Training presentation slides and the lab instructions before
starting the labs and use them as a reference throughout the labs.

1.1 Directory Structure

In this RAK, dtmf_cadence/ contains the following directories:

• constraints/ // Contains SDC (constraints) files

• def/ // Contains the floorplan DEF file
• lab/ // Contains a lab-specified script to run the Genus iSpatial
flow
• libraries/ // Contains the standard cell libraries, LEFs, and qrcTechFile
• macro_libs/ // Contains libraries and LEFs for the macros
• rtl/ // Contains HDL files

1.2 Tool Versions

The lab has been designed with Genus 22.13 and Innovus 22.13 versions.

Some messages and log statements explained in the instructions may not appear in
different tool versions.
Note: Use the same main branches of Genus and Innovus for compatibility (for
example, Genus 22.1* with Innovus 22.1*).

1.3 Terms and Typographic Conventions

RAK Rapid Adoption Kit
DEF Design Exchange Format

Throughout the lab, anything to be typed at the command prompt is written using blue
Courier fonts.

1.4 Design
The sample testcase is a generic DTMF design and is attached with the RAK.

Learn more at Cadence Learning and Support Portal - https://support.cadence.com

© 2024 Cadence Design Systems, Inc. DO NOT DISTRIBUTE. Page 5
 Genus iSpatial: RAK

1.5 LAB Sequence

This RAK provides a lab to understand the basic flow of iSpatial synthesis using Genus.

1.6 Commands to Navigate Genus Database Design Hierarchy

In Genus, you can see the virtual directories listed below after doing the following step:

@genus:root:> vls –l

• ./ (root) // Root Directory

• commands/ // Contains commands and information for each command
• designs/ // Contains the designs for each module loaded into Genus
• flows/ // Stylus flow information
• hdl_libraries/ // Contains the VHDL architecture libraries
• libraries/ // Contains the technology libraries that have been read in
• messages/ // List of messages displayed during the Genus session
• object_types/ // Contains list of objects associated with the design
• tech/ // Contains technology-related information (for example,
vias and layers)

You can enter the virtual directories listed above by using the following command:

@genus:root:> vcd <vdir>

Make sure to get back to the root directory by using the following command:

@genus:root:> vcd

Learn more at Cadence Learning and Support Portal - https://support.cadence.com

© 2024 Cadence Design Systems, Inc. DO NOT DISTRIBUTE. Page 6
 Genus iSpatial: RAK

2. LAB: Genus iSpatial Flow

The lab exercise provides the basic flow of Genus iSpatial synthesis. Commands and
descriptions are included in this manual.

2.1 Objective
Use Genus to execute a simple compile of the DTMF design:

• cd to the lab/ directory

2.2 Lab Files

This lab uses the following files:

• run.tcl: This script is created as a template for running iSpatial in the Common
UI.
• mmmc_config.tcl: Multi-Mode Multi-Corner config file
• db_handoff_to_invs.tcl: Innovus preCTS script for DB handoff
• netlist_handoff_to_invs.tcl: Innovus preCTS script for netlist handoff

2.3 Running the Lab

The following command is used to invoke Genus in the Common UI mode:

unix:> genus

You may run commands within the ‘run.tcl’ script line-by-line in the Genus session by
typing or copy/pasting, or you may run all commands in sequence using one of the
following methods:

• unix:> genus
@genus:root: > source run.tcl
OR
• unix:> genus –f run.tcl –log genus.log

2.4 Understanding the Flow

Open the run.tcl file. Go through the script and comments to understand each
command.

Learn more at Cadence Learning and Support Portal - https://support.cadence.com

© 2024 Cadence Design Systems, Inc. DO NOT DISTRIBUTE. Page 7
 Genus iSpatial: RAK

2.4.1 Setup (Attribute Settings)

1. The following three variables are used to set the design name and change the effort
levels on separate stages (syn_gen, syn_map) of the synthesis run:

i. set DESIGN dtmf_recvr_core

ii. set GEN_EFF medium
iii. set MAP_EFF high

2. The following three search path variables are set in the script to be used later to
point Genus to the directories containing the libraries, scripts, and design files:

i. set_db init_lib_search_path { \
../libraries/gsclib045_v3.5/timing \
../libraries/gsclib045_v3.5/lef \
../macro_libs }
ii. set_db init_hdl_search_path { ../rtl }
iii. set_db script_search_path { . }

3. The following attributes determine synthesis effort for each synthesis stage:

i. set_db syn_generic_effort $SYN_EFF

ii. set_db syn_map_effort $MAP_EFF

Note: You can also set the efforts directly without using vars. For example:

set_db syn_map_effort high

4. The following commands set the variables used later to create directories for saving
reports, databases, and log files:

i. set _OUTPUTS_PATH outputs

ii. set _REPORTS_PATH reports
iii. set _LOG_PATH logs

5. Set the ‘extreme’ option to set ispatial flow to run in the extreme mode

set_db opt_spatial_effort extreme

6. Set the location of the Innovus executable (this step is not needed if Innovus
executable is present in your PATH environment variable):

set_db innovus_executable <path to Innovus executable>

Learn more at Cadence Learning and Support Portal - https://support.cadence.com

© 2024 Cadence Design Systems, Inc. DO NOT DISTRIBUTE. Page 8
 Genus iSpatial: RAK

Note: If the innovus_executable attribute is not set, the following (default)

search order is used:

a) Innovus environment variable

b) PATH environment variable
c) CDS_SYNTH_ROOT environment variable

It is important that one of these be set to enable the execution of Innovus during
iSpatial optimization; otherwise, an error will occur when Genus cannot find the
executable.

7. Setting the invs_temp_dir attribute (recommended):

set_db invs_temp_dir ${_OUTPUTS_PATH}/invs_tmp_dir

This attribute creates a directory where Innovus interface files such as .sdc,
netlist, and .def are generated during syn_opt -spatial. The directory is
primarily used for debugging purposes.

Note: If this attribute is not set, the files will be generated in a temporary directory,
which will get deleted once Genus iSpatial is completed. Thus, setting the
invs_temp_dir attribute is recommended for review and debug of the iSpatial
metadata.

8. Setting power prediction attributes (optional settings if power opt is desired):

# set_db design_power_effort low; #default none

# set_db opt_leakage_to_dynamic_ratio float; #default 1.0

Note: There are power control commands that also has an impact on the power
optimization:

opt_spatial_power_driven true/false
opt_spatial_power_driven_effort none/low/high

9. Optionally, you can turn off ‘useful skew’ for iSpatial. It is recommended to set it at
the default value (true).

# set_db opt_spatial_useful_skew false; #default true

2.4.2 Loading Libraries and Designs

The commands given below load the libraries, LEF files, qrcTechFile, floorplan DEF,
and reads the HDL files and elaborates them. Libraries (.lib), constraints (SDCs),

Learn more at Cadence Learning and Support Portal - https://support.cadence.com

© 2024 Cadence Design Systems, Inc. DO NOT DISTRIBUTE. Page 9
 Genus iSpatial: RAK

and qrcTechFile are specified in mmmc_config.tcl and will be loaded

during init_design.

1. The three search path variables mentioned earlier (refer to the point 2 under section
2.4.1 given above) are used to point Genus to the directories containing the libraries,
scripts, and design files.
2. Read mmmc_config (contains .lib, qrcTechFile, and SDC file specifications), LEF
files, and RTL files.

read_mmmc mmmc_config.tcl
read_physical -lef {gsclib045_tech.lef gsclib045_macro.lef
pllclk.lef CDK_S128x16.lef CDK_S256x16.lef CDK_R512x16.lef}
read_hdl $rtl_list

3. Elaborate, perform init_design, and check for unresolved references.

elaborate $DESIGN
init_design
check_design -unresolved

4. Read the floorplan DEF.

read_def -fuzzy_match ../def/fp.def

5. Define cost groups.

define_cost_group -name I2C -design $DESIGN

path_group -from [all_inputs] -to [all_registers] -group
I2C -name I2C

define_cost_group -name C2O -design $DESIGN

path_group -from [all_registers] -to [all_outputs] -group
C2O -name C2O

define_cost_group -name I2O -design $DESIGN

path_group -from [all_inputs] -to [all_outputs] -group I2O
-name I2O

2.4.3 Running Generic Optimization and Mapping (Physical-Aware)

Next, generic synthesis and global mapping are run, considering the physical domain.
During these steps, generic placement information is used to allow Genus to make
intelligent decisions regarding structuring and mapping.

Learn more at Cadence Learning and Support Portal - https://support.cadence.com

© 2024 Cadence Design Systems, Inc. DO NOT DISTRIBUTE. Page 10
 Genus iSpatial: RAK

syn_gen -physical
syn_map -physical

Note: Normally, you can write reports, db files, and/or netlists between these steps. The
script contains some typical commands used for writing these files. Also, you can
complete some DFT insertion (non-RTL) after syn_map (for example, connecting scan
chains) if a part of the design requires it.

2.4.4 Run iSpatial Optimization with Unified Genus and Innovus

Engines
syn_opt -spatial

Genus iSpatial calls Innovus, which places the design, optimizes it, and does a trial
route. Then, Innovus passes the design back to Genus for analysis and reporting.

Note: The iSpatial flow requires an Innovus executable when opt_spatial_effort

is set to “extreme”. It is highly recommended that you use the latest versions of
Innovus and Genus.

Note: Currently, the spatial flow runs by setting opt_spatial_effort to

“standard”.

2.4.5 Write Reports and Files for Handoff to Innovus preCTS

The following two handoff modes are available:

• DB handoff
• Netlist handoff

Netlist handoff provides added flexibility to customers who have back-end vendors that
do not accept a placed DB.

write_reports -directory $_REPORTS_PATH -tag final

# write handoff DB for INVS prects

write_db -common \\
${_OUTPUTS_PATH}/final_db/${DESIGN}

# OR write netlist handoff files for INVS prects

write_netlist $DESIGN > final_netlist

Supplementary information: Innovus commands for loading and placing the design in
preCTS for both DB and netlist handoffs are as follows:

Learn more at Cadence Learning and Support Portal - https://support.cadence.com

© 2024 Cadence Design Systems, Inc. DO NOT DISTRIBUTE. Page 11
 Genus iSpatial: RAK

DB handoff:

read_db ${_OUTPUTS_PATH}/final_db/${DESIGN}
time_design -report_only

# execute prects optimization

place_opt_design

Netlist handoff:

# load only specific files from Genus

read_mmmc <mmmc_config.tcl>
read_physical -lef <LEF files>
read_netlist ${_OUTPUTS_PATH}/final_netlist/${DESIGN}.v
init_design
# execute prects optimization
place_opt_design

Note: Only the DB handoff passes the placement forward to Innovus. DB contains
information that tells Innovus that a full place_opt_design is not required; so, DO
NOT use the -incremental switch when running Innovus place_opt_design in
either handoff modes.

Learn more at Cadence Learning and Support Portal - https://support.cadence.com

© 2024 Cadence Design Systems, Inc. DO NOT DISTRIBUTE. Page 12
 Genus iSpatial: RAK

Support
Cadence Support Portal provides access to support resources, including an extensive
knowledge base, access to software updates for Cadence products, and the ability to
interact with Cadence Customer Support. Visit https://support.cadence.com.

Feedback
Email comments, questions, and suggestions to [email protected].

Learn more at Cadence Learning and Support Portal - https://support.cadence.com

© 2024 Cadence Design Systems, Inc. DO NOT DISTRIBUTE. Page 13