Stats

Locked Locked
Replies 1
Subscribers 124
Views 13506
Members are here 0

This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

OSS netlisting inherited gnd problem

Dear all,

we are having a strange issue when netlising our design with the OSS netlister (via runams command-line).

Some of the inherited grounds nets are being strangely netliested. For instance, an inherited net that should be netlisted as \vss! ; is being netlisted as \vss_vss! ; that is, its name is being duplicated. This causes elaboration errors.

Here's what we see:

// Verilog-AMS netlist generated by the AMS netlister, version 5.10.41.500.6.149.

// Cadence Design Systems, Inc.

(* cds_ams_schematic *)

module and2_2 ( x,a,b );

output x; input a; input b;

wire (*

integer inh_conn_prop_name = "vdd";

integer inh_conn_def_value

= "cds_globals.\\vdd! ";

\vdd! ;

wire (*

integer inh_conn_prop_name = "vss";

integer inh_conn_def_value

= "cds_globals.\\vss! ";

\vss! ;

\nmos #(.ad(( max(1.120 , 0.7) * 0.805 )), .nrd(( 0.28 / 1.120 )), .vds("2.5"),

.pd(( 2.0 * ( max(1.120 , 0.7) + 0.805 ) )), .w(1.120), .lpe(0), .as(( max(1.120 , 0.7) * 0.805 )),

.nrs(( 0.28 / 1.120 )), .np(1), .ps(( 2.0 * ( max(1.120 , 0.7) + 0.805 ) )),

.l(0.28)) (*

integer library_binding = "smos8mv_ams";

N53 ( x,

nnet6, \vss! , \vss! );

\nmos #(.ad(( max(0.630 , 0.7) * 0.805 )), .nrd(( 0.28 / 0.630 )), .vds("2.5"),

.pd(( 2.0 * ( max(0.630 , 0.7) + 0.805 ) )), .w(0.630), .lpe(0), .as(( max(0.630 , 0.7) * 0.805 )),

.nrs(( 0.28 / 0.630 )), .np(1), .ps(( 2.0 * ( max(0.630 , 0.7) + 0.805 ) )),

.l(0.28)) (*

------------------------------------

using runams (OSS NETLISTER), FOR THE SAME “AND2_2”, I got a different format netlist, which gave ncelab errors.

2) ---------------------

module and2_2 (x, a, b);

output x;

input a, b;

wire (*

integer inh_conn_prop_name = "vdd";

integer inh_conn_def_value = "cds_globals.\\vdd! ";*)

cdsNet1;

wire (*

integer inh_conn_prop_name = "vss";

integer inh_conn_def_value = "cds_globals.\\vss! ";*)

cdsNet0;

wire (*

integer inh_conn_prop_name = "vss";

integer inh_conn_def_value = "cds_globals.\\vss! ";

\vss_vss! ;

\nmos #(.l(0.28), .w(1.120), .as("(max((1.120),0.7)*0.805)"),

.ps("(2.0*(max((1.120),0.7)+0.805))"),

.ad("(max((1.120),0.7)*0.805)"),

.pd("(2.0*(max((1.120),0.7)+0.805))"), .nrd("(0.28/(1.120))"),

.nrs("(0.28/(1.120))"), .lpe(0), .np(1), .vds(2.5)) N53 (x, nnet6

, cdsNet0, \vss_vss! );

So the cdsNet1, cdsNet0, \vss_vss! Are all the ncelab errors.

Any ideas?

thanks for your support.

Andrew Beckett over 11 years ago

Please contact customer support - I think we'll need to look at the data. I didn't do any searching to see if I could find this, and there isn't any opportunity to really fix the software (the last hotfix, 5.10.41.500.6.151 was released over 2.5 years ago), but maybe we can identify something unusual about the data and provide a workaround.
Kind Regards,
Andrew.
Cancel
Vote Up 0 Vote Down

Cancel

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.