• 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. Digital Implementation
  3. IC5141 CDL in skipping passive devices

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 93
  • Views 13829
  • 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

IC5141 CDL in skipping passive devices

lcaley
lcaley over 12 years ago

Hello everyone, 

 I'm trying to import a CDL netlist that contains IO pads and logic into IC5141. The issue I am having is that it skips all of the passive devices within the cell. This particular cell has 3 active MOS devices, 3 diodes, and a resistor. CDL in appears to run correctly, but upon checking the schematic, only the 3 transistors are present. Below is the appropriate snippet of the CDL file, my Device Map file, and my ni.log file. I cannot see any reason for the import process to be skipping the passive devices. Please let me know if any additional information or details are needed. 

Thank you!

 P.S. I couldn't find a way to enclose the text in a code box, so please excuse the wall of text.

-----------------CDL FILE----------------------

.SUBCKT IDDBREAK VDD VSS VSSIO

*.PININFO VDD:B VSS:B VSSIO:B

RR0 VSS net40 169.876K $SUB=VDD $[RNPPO_SP] $W=500n $L=204.91u

MNM4 VDD net40 net49 VSS NA W=40e-6 L=120n M=4

MNM0 VSS VSS VDD net49 NA W=40e-6 L=120n M=12

DD2 VSSIO VSS DP 2e-11 4.2e-05 M=5

DD0 VSS VSSIO DP 2e-11 4.2e-05 M=5

DD1 VSS VDD DP 2e-11 4.2e-05 M=5

MPM0 VDD net40 VDD VDD PR W=3e-6 L=4u M=12

.ENDS

 

 

-------------------DEVICE MAP FILE-------------------------------

devMap := nfet N_11_SPHVT

propMatch := subtype NH

 

devMap := pfet P_11_SPHVT

propMatch := subtype PH

 

devMap := nfet N_25_SP

propMatch := subtype NR

 

devMap := pfet P_25_SP

propMatch := subtype PR

 

devMap := nfet N_11_SPRVT

propMatch := subtype NA

 

devMap := pfet P_11_SPRVT

propMatch := subtype PA

 

devMap := diode DIOP_SP

propMatch := subtype DP

 

devMap := diode DION_SP

propMatch := subtype DN

 

-----------------ni.log--------------------------

==========================

Subckt: IDDBREAK

==========================

 

Created the CV IDDBREAK->netlist_tmp.

 

#####################################

MOS Instance: MPM0

#####################################

 

...Searching for a valid mapping in the dev-map file...

        ...Bingo! Cell mapped to P_25_SP->symbol.

 

Now, searching for the cellview P_25_SP->symbol in ref libs...

    ...in umc65sp: Bingo! Found the master cellview: P_25_SP->symbol.

instName->'MPM0' is created.

propName->'subtype'; propVal->'PR' is created.

propName->'w'; propVal->'3E-06' is created.

propName->'l'; propVal->'4E-06' is created.

propName->'m'; propVal->'12' is created.

'D' mapped to 'D'.

The net 'VDD' of instance 'MPM0' has been connected to the terminal 'D'.

'G' mapped to 'G'.

The net 'net40' of instance 'MPM0' has been connected to the terminal 'G'.

'S' mapped to 'S'.

The net 'VDD' of instance 'MPM0' has been connected to the terminal 'S'.

'B' mapped to 'B'.

The net 'VDD' of instance 'MPM0' has been connected to the terminal 'B'.

 

#####################################

MOS Instance: MNM0

#####################################

 

...Searching for a valid mapping in the dev-map file...

        ...Bingo! Cell mapped to N_11_SPRVT->symbol.

 

Now, searching for the cellview N_11_SPRVT->symbol in ref libs...

    ...in umc65sp: Bingo! Found the master cellview: N_11_SPRVT->symbol.

instName->'MNM0' is created.

propName->'subtype'; propVal->'NA' is created.

propName->'w'; propVal->'4E-05' is created.

propName->'l'; propVal->'1.2E-07' is created.

propName->'m'; propVal->'12' is created.

'D' mapped to 'D'.

The net 'VSS' of instance 'MNM0' has been connected to the terminal 'D'.

'G' mapped to 'G'.

The net 'VSS' of instance 'MNM0' has been connected to the terminal 'G'.

'S' mapped to 'S'.

The net 'VDD' of instance 'MNM0' has been connected to the terminal 'S'.

'B' mapped to 'B'.

The net 'net49' of instance 'MNM0' has been connected to the terminal 'B'.

 

#####################################

MOS Instance: MNM4

#####################################

 

...Searching for a valid mapping in the dev-map file...

        ...Bingo! Cell mapped to N_11_SPRVT->symbol.

 

Now, searching for the cellview N_11_SPRVT->symbol in ref libs...

    ...in umc65sp: Bingo! Found the master cellview: N_11_SPRVT->symbol.

instName->'MNM4' is created.

propName->'subtype'; propVal->'NA' is created.

propName->'w'; propVal->'4E-05' is created.

propName->'l'; propVal->'1.2E-07' is created.

propName->'m'; propVal->'4' is created.

'D' mapped to 'D'.

The net 'VDD' of instance 'MNM4' has been connected to the terminal 'D'.

'G' mapped to 'G'.

The net 'net40' of instance 'MNM4' has been connected to the terminal 'G'.

'S' mapped to 'S'.

The net 'net49' of instance 'MNM4' has been connected to the terminal 'S'.

'B' mapped to 'B'.

The net 'VSS' of instance 'MNM4' has been connected to the terminal 'B'.

INFO (CDLIN-54): CDL In successfully created the schematic view IO_lib_SP_2_5V_Inline_Reg_VT.IDDBREAK::netlist. Read the log file 

'conn2sch_IDDBREAK.log' for more information.

 

 

  • Cancel
  • navi2582
    navi2582 over 12 years ago

     I think you may have to include the following at the beginning of your cdl netlist:

    .PARAM

    *.BIPOLAR
    *.RESI = 1
    *.RESVAL
    *.CAPVAL
    *.DIOPERI
    *.DIOAREA
    *.SCALE METER

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • csst
    csst over 11 years ago

    You should also add the resistor in map file


    devMap  := phyres RNPPO_SP
    termMap := PLUS PLUS MINUS MINUS SUB B

     

    • 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.

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

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