Stats

  • Locked Locked
  • Replies 5
  • Subscribers 90
  • Views 14100
  • 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

Is it a MUST to use capTable to do .13um design?

archive

If there is no capTable available, fe will use WLM?


Thanks.


Originally posted in cdnusers.org by pico
Parents

  • First off, welcome to the forums! Thanks for your post.

    No, cap tables are *not* a MUST. If there is no cap table available, FE will *not* use a wireload model. It will derive parasitics from actual route topologies using approximations made from whatever information is available in the technology section of your LEF file to determine resistances and capacitances.

    Whether this is sufficient to accurately model your 0.13 process depends on whether you're using FE as a prototyping tool -or- as an implementation tool. If prototyping, it may very well be sufficient. If implementation probably not.

    In general, it is always best to run with a cap table, but situations do arise where they're not available yet and we want work to proceed. Cap tables can be created using the FE command "generateCapTbl". The command takes an ICT file as input (which describes the process stack information, which usually comes from your process provider) and produces a cap table. Just thought I'd mention those details in case it wasn't clear in general where this information should come from.

    Hope this helps,
    Bob


    Originally posted in cdnusers.org by BobD
Reply

  • First off, welcome to the forums! Thanks for your post.

    No, cap tables are *not* a MUST. If there is no cap table available, FE will *not* use a wireload model. It will derive parasitics from actual route topologies using approximations made from whatever information is available in the technology section of your LEF file to determine resistances and capacitances.

    Whether this is sufficient to accurately model your 0.13 process depends on whether you're using FE as a prototyping tool -or- as an implementation tool. If prototyping, it may very well be sufficient. If implementation probably not.

    In general, it is always best to run with a cap table, but situations do arise where they're not available yet and we want work to proceed. Cap tables can be created using the FE command "generateCapTbl". The command takes an ICT file as input (which describes the process stack information, which usually comes from your process provider) and produces a cap table. Just thought I'd mention those details in case it wasn't clear in general where this information should come from.

    Hope this helps,
    Bob


    Originally posted in cdnusers.org by BobD
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.