Stats

  • Locked Locked
  • Replies 4
  • Subscribers 129
  • Views 5231
  • 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

Unbound pin error from Assura LVS after P&R

bjbit

Hi,

When I do Assura LVS on the layout I got from P&R Encounter, the "unbound pins" error appears in the report. As the attached picture shows, the net marked as green color in both schematic and layout looks matching well. But it seems LVS cannot specify the pin ports from the instance of the standard cell layout? Can I ignore this error and trust that schematic and layout actually match? Thanks in advance.

Best regard, 

  • Hi bjbit

    I think it is better to troubleshoot the error so that you can get lvs match. The error looks strange. Assura seems to be reporting. You should check the sdb and ldb netlists in the run directory to see why Assura is reporting pin errors.

    terminal>vldbToCdl design.sdb > design.sdb.ascii

    The above cmd will convert the binary netlist to ascii format.

    Best regards
    Quek

  • Check if your layout pins are in the correct format
    to get properly recognized by your Assura LVS.
    If you exchange the data from Encounter to Virtuoso in GDSII
    format your pins are most likely only defined as labels over the
    interconnects. This may work for a LVS run on GSDII layout basis,
    but probably not for a LVS on the Virtuoso layout database.

    If this is the case you can try the utility ‘Create Pins From Labels’,
    to get the pins in the proper form.
    From the layout window ‘Tools -> Create Pins From Labels’.

    Bernd

  • Sorry guys I should have posted a update that I already figured this out. The encounter automatically adds net names on label layers, and Assura LVS treats them as pins, which caused pin mismatch. Thanks all the same. Best regards,
  • Hi bjbit, 

    I have encountered the same problem. How could you solve this back then? 

    Regards. 

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.