Power Matters.

TM

Recommended CDC Signoff

Procedure
Meridian CDC Training Part 3

© 2016 Microsemi Corporation. Company Proprietary 1

Outline

 Recommended Block-Level CDC Flow

• Get the Meridian CDC Flow
• Meridian CDC Setup
• Run Structural CDC Checks
• Run Formal CDC Checks
• Lab 1

 Recommended Top-Level CDC Flow

• Get the Meridian CDC Flow
• Meridian CDC Setup
• Run Structural CDC Checks
• Partition the Top-Level Report
• Lab 2

© 2016 Microsemi Corporation. Company Proprietary Power Matters.TM 2

Outline

 Recommended Block-Level CDC Flow

• Get the Meridian CDC Flow
• Meridian CDC Setup
• Run Structural CDC Checks
• Run Formal CDC Checks
• Lab 1

 Recommended Top-Level CDC Flow

• Get the Meridian CDC Flow
• Meridian CDC Setup
• Run Structural CDC Checks
• Partition the Top-Level Report
• Lab 2

© 2016 Microsemi Corporation. Company Proprietary Power Matters.TM 3

Recommended Block-Level CDC Flow

1. Get the Meridian CDC Flow

Goal: Get tool setup, directories created, and template files in place.
• Run the following command from your block’s scripts directory to get the latest
Meridian CDC flow component. You only need to do this step once to setup the flow.
% get_icdc_comp cad_dd_01036
% ../depend/unmodified/cad_dd_01036/do_gen_cdc.pl -
top pmxx_xx_xx -mlist list/pmxx_xx_xx_rtl.mlist
<-sdc ../syn/pmxx_xx_xx_cdc.sdc> <-overwrite>
• This populates the latest CDC component, and generates the following files:
- ./Makefile (CDC flow makefile with flow control variables)
- ./cdc/user_defined_elist.elist (files to exclude/replace)
- ./cdc/user_defined_libs_file.txt (user specified .lib files for analog blocks)
- ./cdc/user_env_file.env (environment file for .env additions)
- ./cdc/case_analysis.cfg (pin/signal constraints for things like DFT)

© 2016 Microsemi Corporation. Company Proprietary Power Matters.TM 4

Recommended Block-Level CDC Flow

2. Meridian CDC Setup

Goal: Create a clean Meridian CDC environment file (.env).
• Run the following command to create an environment file:
% make create_env
• This Review/fix the generated pmxx_xx_xx.<sdc|no_sdc>.env file:
- Ensure all the clocks are being defined properly – no missing or extra clocks.
- Ensure clock associations to all pins/signals defined in the .env file are
correct.
- Reset inputs have been properly defined and associated.
• Once you are satisfied with the .env file, copy it to .base to ensure it is not overridden:
% cp ./cdc/pmxx_xx_xx.<sdc|no_sdc>.env
./cdc/pmxx_xx_xx.<sdc|no_sdc>.base.env

© 2016 Microsemi Corporation. Company Proprietary Power Matters.TM 5

Recommended Block-Level CDC Flow

3. Run Structural CDC Checks

Goal: Perform structural CDC checks and fix or waive all structural
CDC messages.
• Once you have a clean CDC environment (all setup issues have been waived or
fixed), run the following command to perform structural CDC analysis:
% make verify_cdc
The end goal is for all Errors/Warnings/Review to ultimately end up in WAIVE.
• Once the structural analysis is done, calculate the design MTBF:
- Edit ./cdc/pmxx_xx_xx.clock_freq.txt.
- Run the following command to generate pmxx_xx_xx.mtbf.xml:
% make mtbf
- Open pmxx_xx_xx.mtbf.xml in excel and copy all crossings into the MTBF
calculator spreadsheet.
- Select technology flops for all crossings to calculate the design MTBF.

© 2016 Microsemi Corporation. Company Proprietary Power Matters.TM 6

Recommended Block-Level CDC Flow

4. Run Formal CDC Checks

Goal: Perform functional/formal CDC checks and fix or waive all
functional/formal CDC messages.
• Select functional/formal checks that you want to run in GUI, and run the following
command:
% make verify_cdc_formal
Note: Formal constraints may be needed to ensure the normal mode of operation
of your design.

© 2016 Microsemi Corporation. Company Proprietary Power Matters.TM 7

Lab 1 – 45 Minutes

 Goal: get familiar with the block-level CDC workflow

 Instructions
• Change directory to lab1/eth_top/scripts
• Follow the steps in README.txt

© 2016 Microsemi Corporation. Company Proprietary Power Matters.TM 8

Outline

 Recommended Block-Level CDC Flow

• Get the Meridian CDC Flow
• Meridian CDC Setup
• Run Structural CDC Checks
• Run Formal CDC Checks
• Lab 1

 Recommended Top-Level CDC Flow

• Get the Meridian CDC Flow
• Meridian CDC Setup
• Run Structural CDC Checks
• Partition the Top-Level Report
• Lab 2

© 2016 Microsemi Corporation. Company Proprietary Power Matters.TM 9

Recommended Top-Level CDC Flow

1. Get the Meridian CDC Flow

Goal: Get tool setup, directories created, and template files in place.
• Run the following command from your block’s scripts directory to get the latest
Meridian CDC flow component. You only need to do this step once to setup the flow.
% get_icdc_comp cad_dd_01036
% ../depend/unmodified/cad_dd_01036/do_gen_cdc.pl -
top pmxx_xx_xx -mlist list/pmxx_xx_xx_rtl.mlist
<-sdc ../syn/pmxx_xx_xx_cdc.sdc> <-overwrite>
• This populates the latest CDC component, and generates the following files:
- ./Makefile (CDC flow makefile with flow control variables)
- ./cdc/user_defined_elist.elist (files to exclude/replace)
- ./cdc/user_defined_libs_file.txt (user specified .lib files for analog blocks)
- ./cdc/user_env_file.env (environment file for .env additions)
- ./cdc/case_analysis.cfg (pin/signal constraints for things like DFT)

© 2016 Microsemi Corporation. Company Proprietary Power Matters.TM 10

Recommended Top-Level CDC Flow

2. Meridian CDC Setup

Goal: Create a clean Meridian CDC environment file (.env).
• Run the following command to create an environment file:
% make create_env
• This Review/fix the generated pmxx_xx_xx.<sdc|no_sdc>.env file:
- Ensure all the clocks are being defined properly – no missing or extra clocks.
- Ensure clock associations to all pins/signals defined in the .env file are
correct.
- Reset inputs have been properly defined and associated.
• Once you are satisfied with the .env file, copy it to .base to ensure it is not overridden:
% cp ./cdc/pmxx_xx_xx.<sdc|no_sdc>.env
./cdc/pmxx_xx_xx.<sdc|no_sdc>.base.env

© 2016 Microsemi Corporation. Company Proprietary Power Matters.TM 11

Recommended Top-Level CDC Flow

3. Run Structural CDC Checks

Goal: Perform structural CDC checks and fix or waive all structural
CDC messages.
• At top-level, shelling should be enabled to shell out block-level warnings/errors. In
your Makefile, use the following variables:
USE_SHELL_MODULES=1
SHELL_MODULES_LIST=“A B C“
USE_SHELL_INSTANCES=1
SHELL_INSTANCES_LIST="A B C"
• Once you have a clean CDC environment (all setup issues have been waived or
fixed), run the following command to perform structural CDC analysis:
% make verify_cdc
At device-level, shelling should filter out all lower-level messages. Analyze the
remaining top-level interconnect warnings/errors.
The end goal is for all Errors/Warnings/Review to ultimately end up in WAIVE.
• At device-level, it is not required to calculate design MTBF.

© 2016 Microsemi Corporation. Company Proprietary Power Matters.TM 12

Recommended Top-Level CDC Flow
4. Partition the Top-Level CDC Report
Goal: Partition the top-level structural CDC report and work with
SubSystem designers to fix or waive all structural CDC messages.
• Partition the top-level report using View Criteria:
You will need to create separate View Criteria reports for different error/warning
categories for each sub-system block.
• Have the SS designers to analyze their block’s View Criteria reports. They can
remotely access the reports by running:
% make debug_cdc
Note: In their workspaces, they need to get the Meridian CDC flow (see step 1),
copy your Makefile, and edit to enable the following variables:
REMOTE_DEBUG=1
REMOTE_WORKSPACE=
• Once SS designers finish, integrate all SS results back into the main top-level CDC
environment.

© 2016 Microsemi Corporation. Company Proprietary Power Matters.TM 13

Lab 2 – 45 Minutes

 Goal: get familiar with the top-level CDC workflow

 Instructions
• Change directory to lab2/eth_top/scripts
• Follow the steps in README.txt

© 2016 Microsemi Corporation. Company Proprietary Power Matters.TM 14

Rev DATE Initials Description
===================================================================================================================
1 2016-03-22 HC Initial creation based on TSB CDC training.

Microsemi Corporation (MSCC) offers a comprehensive portfolio of semiconductor and system solutions for
communications, defense & security, aerospace and industrial markets. Products include high-performance and radiation-
hardened analog mixed-signal integrated circuits, FPGAs, SoCs and ASICs; power management products; timing and
synchronization devices and precise time solutions, setting the world's standard for time; voice processing devices; RF
solutions; discrete components; enterprise storage and communication solutions, security technologies and scalable anti-
tamper products; Ethernet solutions; Power-over-Ethernet ICs and midspans; as well as custom design capabilities and
services. Microsemi is headquartered in Aliso Viejo, Calif., and has approximately 4,800 employees globally.
Learn more at www.microsemi.com

Microsemi Corporate Headquarters
One Enterprise, Aliso Viejo, CA 92656 USA
Within the USA: +1 (800) 713-4113
Outside the USA: +1 (949) 380-6100
Sales: +1 (949) 380-6136
Fax: +1 (949) 215-4996
email: sales.support@microsemi.com
www.microsemi.com
Microsemi makes no warranty, representation, or guarantee regarding the information contained herein or the suitability of its products and services for any
particular purpose, nor does Microsemi assume any liability whatsoever arising out of the application or use of any product or circuit. The products sold
hereunder and any other products sold by Microsemi have been subject to limited testing and should not be used in conjunction with mission-critical
equipment or applications. Any performance specifications are believed to be reliable but are not verified, and Buyer must conduct and complete all
performance and other testing of the products, alone and together with, or installed in, any end-products. Buyer shall not rely on any data and performance
specifications or parameters provided by Microsemi. It is the Buyer’s responsibility to independently determine suitability of any products and to test and
verify the same. The information provided by Microsemi hereunder is provided “as is, where is” and with all faults, and the entire risk associated with such
information is entirely with the Buyer. Microsemi does not grant, explicitly or implicitly, to any party any patent rights, licenses, or any other IP rights,
whether with regard to such information itself or anything described by such information. Information provided in this document is proprietary to Microsemi,
and Microsemi reserves the right to make any changes to the information in this document or to any products and services at any time without notice.
©2016 Microsemi Corporation. All rights reserved. Microsemi and the Microsemi logo are registered trademarks of Microsemi Corporation. All other
trademarks and service marks are the property of their respective owners. TM
© 2016 Microsemi Corporation. Company Proprietary Power Matters. 15