Stats

  • Locked Locked
  • Replies 11
  • Subscribers 125
  • Views 20342
  • 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

simInfo missing. Netlisting problem

oldnick

Hi,

I'm using PVS for LVS'ing

I have some custom structures which required an addition to the ruledeck so that LVS recognised them, this works fine using the auCDL and auLVS settings in the PVS LVS (schematic input section) tool. I can LVS pretty much the whole chip using the auCDL setting, until I add the pads, something about them require the use of the createCDL setting. This is where the problem arises, when I try and LVS, I get a *Error*   Cell: xxxxx  in library: xxxxxx  is missing a simInfo.

Of course with this being a custom structure/component I've created there is no simulation info, and we have no intention of simulating the structure, we just want to verify the connections.

Ive tried setting the netlist mode to digital, but this doesn't work. I've checked that the netlist mode is digital.;

cdsGetNetlistMode()

"Digital"

I've also tried to add some terminal names to the simulation information section in the Edit CDF, but this didn't work - I wasn't 100% sure what I was doing, I added the pin name to the term order vox, and component name etc. This had no effect.

Can I copy a sim file from something else just to get it past LVS (the something else would need to only have 1 pin), Or do I have to write the shell of a simulation model or something, just to get it past this? 

Parents

  • If you normally use auCdl or auLvs, you still need to provide the simInfo for a leaf cell. This doesn't mean you're going to simulate it - the simInfo is just the part of the CDF which tells it how to netlist for a particular netlister - it's often for simulation, but not always.

    Typically you need to create a stopping view, usually with the same name as the netlister (i.e. auCdl or auLvs) which is often just a copy of the symbol. Then set up the CDF for that component and in the auCdl or auLvs simInfo define the netlist procedure and terminal list. You may be able to do this by opening the symbol view and calling this SKILL function:

    artGenerateHierSymbolCDF(geGetEditCellView())

    (I think I got the case of the function correct - I don't have the documentation to hand). That will at least give you a good start.

    Hope that helps.

    Regards,

    Andrew.

Reply

  • If you normally use auCdl or auLvs, you still need to provide the simInfo for a leaf cell. This doesn't mean you're going to simulate it - the simInfo is just the part of the CDF which tells it how to netlist for a particular netlister - it's often for simulation, but not always.

    Typically you need to create a stopping view, usually with the same name as the netlister (i.e. auCdl or auLvs) which is often just a copy of the symbol. Then set up the CDF for that component and in the auCdl or auLvs simInfo define the netlist procedure and terminal list. You may be able to do this by opening the symbol view and calling this SKILL function:

    artGenerateHierSymbolCDF(geGetEditCellView())

    (I think I got the case of the function correct - I don't have the documentation to hand). That will at least give you a good start.

    Hope that helps.

    Regards,

    Andrew.

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.