Stats

  • Locked Locked
  • Replies 3
  • Subscribers 131
  • Views 15319
  • 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

spiceIn bjt

mhowell67

Using virtuoso 6.1.4 and trying to import a CDL with the spiceIn utility.

 I get the following error returned in the log:

    Instance: Q156
    Instance has master: 'bjt' model/subtype: 'XP'

        Master Cell: 'bjt'.
        Did not find 'CMOS.bjt:symbol'.
ERROR (SPICEIN-24): Spice In did not find the symbol view of the master cell 'bjt' of the instance
'Q156' in the subcircuit 'amos_c14bg0v9'. Specify the reference library that has the symbol
view of the master cell, or use device-mapping to map 'bjt' to a different
cell.

I am using a device map file to map bjt to pnpv. This is the syntax in my map file.

devSelect := bjt pnpv
    propMatch := XP
    termOrder := C B E
    propMap := EA ae

The pnpv cell exist in CMOS library but spiceIn does not find it.

 What am I doing wrong?

  • Quek

    Hi mhowell67

    Would you please post the line in cdl netlist for Q156?

    Thanks
    Quek

  • mhowell67

     Q156 gnda gnda n32 XP $EA=16

     I actually got the SpiceIn t work.  I modified the mapping to read as follows;

    devSelect := bjt pnpv
        propMatch := Subtype XP
        termOrder := C B E
        propMap := EA ae

    Another work-around before I got the mapping to work was to copy pnpv cell into a dummy library, rename it bjt, and add the dummy library to my library reference list in spiceIn.

     

  • Quek

    Hi mhowell67

    Thanks for the reply. It is good to know that you have resolved the problem. : )

    Best regards
    Quek

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.