Continue to Site

Welcome to EDAboard.com

Welcome to our site! EDAboard.com is an international Electronics Discussion Forum focused on EDA software, circuits, schematics, books, theory, papers, asic, pld, 8051, DSP, Network, RF, Analog Design, PCB, Service Manuals... and a whole lot more! To participate you need to register. Registration is free. Click here to register now.

.sdc file into Innovus WARN and ERROR

Status
Not open for further replies.

EEPuppyPuppy

Junior Member level 3
Joined
Jun 14, 2018
Messages
26
Helped
0
Reputation
0
Reaction score
0
Trophy points
1
Activity points
343
I was trying to do P&R with Innovus by using the output files from Synopsys.
There are several files generated from Synopsys that are needed to be input into Innovus. One of them is the .sdc file which is generated with the command
Code:
write_sdc
However, when the .vew file which is used for mmmc comtains code reading the .sdc file
Code:
create_constraint_mode \
	 -name default \
	 -sdc_files $dbs_dir/$design.sdc
error and wranings reported:
Code:
**WARN: (TCLCMD-1013):  The SDC set_operating_conditions assertion is not supported. Please use the Innovus setOpCond command to specify library and operating condition information. Use the setAnalysisMode command to control single vs. bestCase/worstCase vs. on-chip variation timing analysis. (File DBS/fifo.sdc, Line 9).

**ERROR: (TCLCMD-290):  Could not find technology library '[lib_2_name]' (File .../[design_name].sdc, Line 11).

**ERROR: (TCLCMD-290):  Could not find technology library '[lib_3_name]' (File .../[design_name].sdc, Line 12).
The part of the code in the .sdc file that cause the problem is:
Code:
set_operating_conditions [some_setting] -library [lib_1_name]
set_wire_load_mode top
set_wire_load_model -name [some_setting] -library [lib_2_name]
set_wire_load_model -name [some_setting] -library [lib_3_name] -min
I googled a lot about this online but did not find any answers about them.

Only find one results which is for Encounter. Seems like someone got similar problems in Encounter and people suggested him to just delete all the code that causing error. The suggestions is that 'set_operation_condition' and 'set_wire_load' need to be defined in SOCE. I have not idea what SOCE is and I assume that SOCE is 'SoC Encounter' which means nothing to me since I am using Innovus right now.

1. For the WARN, I have followed the WARN suggestion to change 'set_operating_conditions' to 'setOpCond' which generated some crazier ERROR:
Code:
**ERROR: (IMPSYC-6137): Command 'setOpCond' is obsolete as the software moves to using Multi-Mode/Multi-Corner (MMMC) architecture for design import. Operating conditions must be set using the -opcond and -opcond_library options of the MMMC commands create_delay_corner and update_delay_corner. For more information on creating MMMC configurations and for a full list of design import related commands to be made obsolete, see Performing Multi-Mode Multi-Corner Timing Analysis and Optimization.
2. For the two ERROR, I have tried place the [lib_2_name], [lib_3_name] with just the lib names, the full lib path with brace. Since in the technology file, there are '.db' and '.lib' files, I tried both.
I also had other attempts:
In my .view file, I have some defination like
Code:
create_op_cond \
	 -name [name2] \
	 -library_file {[lib_2_name].lib} \
	 -[some_other_setting]
or some code like
Code:
create_library_set \
	 -name [name2_2] \
	 -timing {[lib_2_name].lib}
So I have also tried these names [name2], [name2_2]
And they all failed, reporting the same errors, cannot find the library.

Could anyone help me?
Thank you so much.
 

I was trying to do P&R with Innovus by using the output files from Synopsys.
There are several files generated from Synopsys that are needed to be input into Innovus. One of them is the .sdc file which is generated with the command
Code:
write_sdc
However, when the .vew file which is used for mmmc comtains code reading the .sdc file
Code:
create_constraint_mode \
	 -name default \
	 -sdc_files $dbs_dir/$design.sdc
error and wranings reported:
Code:
**WARN: (TCLCMD-1013):  The SDC set_operating_conditions assertion is not supported. Please use the Innovus setOpCond command to specify library and operating condition information. Use the setAnalysisMode command to control single vs. bestCase/worstCase vs. on-chip variation timing analysis. (File DBS/fifo.sdc, Line 9).

**ERROR: (TCLCMD-290):  Could not find technology library '[lib_2_name]' (File .../[design_name].sdc, Line 11).

**ERROR: (TCLCMD-290):  Could not find technology library '[lib_3_name]' (File .../[design_name].sdc, Line 12).
The part of the code in the .sdc file that cause the problem is:
Code:
set_operating_conditions [some_setting] -library [lib_1_name]
set_wire_load_mode top
set_wire_load_model -name [some_setting] -library [lib_2_name]
set_wire_load_model -name [some_setting] -library [lib_3_name] -min
I googled a lot about this online but did not find any answers about them.

Only find one results which is for Encounter. Seems like someone got similar problems in Encounter and people suggested him to just delete all the code that causing error. The suggestions is that 'set_operation_condition' and 'set_wire_load' need to be defined in SOCE. I have not idea what SOCE is and I assume that SOCE is 'SoC Encounter' which means nothing to me since I am using Innovus right now.

1. For the WARN, I have followed the WARN suggestion to change 'set_operating_conditions' to 'setOpCond' which generated some crazier ERROR:
Code:
**ERROR: (IMPSYC-6137): Command 'setOpCond' is obsolete as the software moves to using Multi-Mode/Multi-Corner (MMMC) architecture for design import. Operating conditions must be set using the -opcond and -opcond_library options of the MMMC commands create_delay_corner and update_delay_corner. For more information on creating MMMC configurations and for a full list of design import related commands to be made obsolete, see Performing Multi-Mode Multi-Corner Timing Analysis and Optimization.
2. For the two ERROR, I have tried place the [lib_2_name], [lib_3_name] with just the lib names, the full lib path with brace. Since in the technology file, there are '.db' and '.lib' files, I tried both.
I also had other attempts:
In my .view file, I have some defination like
Code:
create_op_cond \
	 -name [name2] \
	 -library_file {[lib_2_name].lib} \
	 -[some_other_setting]
or some code like
Code:
create_library_set \
	 -name [name2_2] \
	 -timing {[lib_2_name].lib}
So I have also tried these names [name2], [name2_2]
And they all failed, reporting the same errors, cannot find the library.

Could anyone help me?
Thank you so much.

SOCE = soc encounter, yes

if your errors are only related to wire load models, just remove those lines. they are important for logic synthesis, not for physical synthesis. if you need to specify operating conditions, just use the mmmc style and only the mmmc style. use the sdc file only for design stuff (clock, loads, use/dontuse cells). don't use it as a means to create analysis corners.
 

SOCE = soc encounter, yes

if your errors are only related to wire load models, just remove those lines. they are important for logic synthesis, not for physical synthesis. if you need to specify operating conditions, just use the mmmc style and only the mmmc style. use the sdc file only for design stuff (clock, loads, use/dontuse cells). don't use it as a means to create analysis corners.

Hi, NotSam. Thank you for your response. Since when I use the command 'setOpCond' it reports the error:
Code:
**ERROR: (IMPSYC-6137): Command 'setOpCond' is obsolete as the software moves to using Multi-Mode/Multi-Corner (MMMC) architecture for design import. Operating conditions must be set using the -opcond and -opcond_library options of the MMMC commands create_delay_corner and update_delay_corner. For more information on creating MMMC configurations and for a full list of design import related commands to be made obsolete, see Performing Multi-Mode Multi-Corner Timing Analysis and Optimization.
I assume that the mmmc style you were talking about is using the command 'cread_delay_corner' and 'update_delay_corner', which I have them in my .view file.
The .view file reads the .sdc file. I guess that except the operation condition setting and wire load setting part, other parts of the .sdc file are still useful. Other parts include driving cell setting, pin load setting, input delay setting, etc.
So I guess I can ignore the errors and the warns here.
 

Hi, NotSam. Thank you for your response. Since when I use the command 'setOpCond' it reports the error:
Code:
**ERROR: (IMPSYC-6137): Command 'setOpCond' is obsolete as the software moves to using Multi-Mode/Multi-Corner (MMMC) architecture for design import. Operating conditions must be set using the -opcond and -opcond_library options of the MMMC commands create_delay_corner and update_delay_corner. For more information on creating MMMC configurations and for a full list of design import related commands to be made obsolete, see Performing Multi-Mode Multi-Corner Timing Analysis and Optimization.
I assume that the mmmc style you were talking about is using the command 'cread_delay_corner' and 'update_delay_corner', which I have them in my .view file.
The .view file reads the .sdc file. I guess that except the operation condition setting and wire load setting part, other parts of the .sdc file are still useful. Other parts include driving cell setting, pin load setting, input delay setting, etc.
So I guess I can ignore the errors and the warns here.

I think so. Stick to the MMMC model. You can debug it visually using the MMMC browser. Should be very easy to spot is something is wrong.
 

Status
Not open for further replies.

Part and Inventory Search

Welcome to EDABoard.com

Sponsor

Back
Top