• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Custom IC Design
  3. Unified Reliability Interface for a macro model

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 125
  • Views 13898
  • 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

Unified Reliability Interface for a macro model

JulianLeander
JulianLeander over 11 years ago

Hi,

I try do design a shared library for the unified reliability interface. The model I design it for, is a macro model or uses a subckt:

 

//inline subckt modhb ( d g s b t psub )

subckt modhb ( d g s b t psub )

// Parameters: w l nrd nrs ad as pd ps

parameters ...

+ isoVoltage=50

+ extract=extracted

+ rd_lin=0

+ delta_vth=0

rpoly2 ( d d1 ) bsource r=(rd_lin/exp(-0.1))*exp(-v(d,s))*(1-1/(1+100**(v(g,s)-1)))

//

modhb ( d1 g s b ) moshb w=w l=l nrd=1-07/w nrs=1-07/w ad=ad as=as pd=pd ps=ps m=ng

// Parasitic diodes

if (extract==0) {

xdsub ( psub t ) modnimdn_ps area=((l+1-06)*(w+2.4e-06)) perimeter=(2*(l+1-06+w+1e-06))

d1 ( b t ) tubtow area=((w+2.4e-6)*(l+4.1e-6)) perim=2*((w+2.4e-6)+(l+4.1e-6))

}

model tubtow diode level=1 \

     is=...    isw=...       n=...   \

    cjo=...      m=... \

    cjsw=...     mjsw=...     fc=...     vj=...  vjsw=...  \

      eg=...     xti=...      af=1 

model moshb bsim3v3 version=...  type=n  capmod=... \

 mobmod=...  nqsmod=...  noimod=3 \

 ...

end modhb (The values are erased or changed) 

In the shared libary I get the voltages and the currents for the calculations from the terminals of the MosVar structure.

I wanted to use the uri_mode=appendage, but I get this message:

Warning(RELXP-379): There is no subckt specified to replace in URI function getNewModelName(), appendage mode will be ignored.

Expanding subckt start...

Expanding subckt completed

 

Generating aged netlist start...

Generating aged netlist completed

Note: 2 deivces are not aged:

        M0.M_subinst_01.modnm

        M1.M_subinst_01.modnm

 

I used the standard getNewModelName() as written in the Unified Reliability Interface Reference:

int nmosnmGetNewModelName( URI_Model* model, const char* name, char* newname)

{

        sprintf(newname,"% aged",name)

        return 0;

}.

My question is: How do I have to change this function or the model.scs file, that the appendage mode can be used and the devices are aged? 

Best regards,

Julian 

  • Cancel
Parents
  • Tawna
    Tawna over 11 years ago

    Hi Julian,

     Each university that has Cadence software has a University liason to Cadence.   Please contact your Department Chairperson to find out whom that person is.  They should also have a website containing that information.

    The liason can contact Customer Support on your behalf and file a Case for you.

    best regards,

    Tawna

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Tawna
    Tawna over 11 years ago

    Hi Julian,

     Each university that has Cadence software has a University liason to Cadence.   Please contact your Department Chairperson to find out whom that person is.  They should also have a website containing that information.

    The liason can contact Customer Support on your behalf and file a Case for you.

    best regards,

    Tawna

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
No Data

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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information