Stats

  • Locked Locked
  • Replies 1
  • Subscribers 125
  • Views 15315
  • 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

Number of fingers differ between schematic and layout

asta51

I am using IC 6.1.5 and I have views of standard cells (schematic and layout) which are not passing LVS (Calibre).

The issue is that in layout I have MOS with a certain number of fingers whereas the schematic have just one finger with the total width.

 Example:

 Layout:       M0 w=0.42u num_finger=2

 Schematic: M0 w=0.84u num_finger=1

For finger checking purpose, I want to update the schematics to match the layout. Is there a way to do that automatically for a whole library?

 

Thanks,

Parents

  • You'd probably have to write some SKILL code to do this. You'd probably also need to ensure that the CDF callbacks were called after making the changes (see solution 11018344 ).

    For a single schematic, if it was done using layout XL, you could do Connectivity->Update->Schematic Parameters - this would transfer the parameters from the layout devices back to the schematic. However, my guess is that has not been done here as otherwise you'd have spotted the problem before LVS.

    Often LVS rules can be set up to compare the total width, but whether you want to do that or not is up to you.

    Regards,

    Andrew.

     

Reply

  • You'd probably have to write some SKILL code to do this. You'd probably also need to ensure that the CDF callbacks were called after making the changes (see solution 11018344 ).

    For a single schematic, if it was done using layout XL, you could do Connectivity->Update->Schematic Parameters - this would transfer the parameters from the layout devices back to the schematic. However, my guess is that has not been done here as otherwise you'd have spotted the problem before LVS.

    Often LVS rules can be set up to compare the total width, but whether you want to do that or not is up to you.

    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.