• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Custom IC Design
  3. Complete procfile/p2lvsfile syntax

Stats

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

Complete procfile/p2lvsfile syntax

ggupta85
ggupta85 over 11 years ago

Hi Friends,

I need forum's help to point me to the complete procfile/p2lvsfile syntax. I have tried searching the web and the Cadence product documentation but couldn't find a very comprehensive guide for my purpose.
Any help in this matter will be hghly regarded.

Thanks in advance!!

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 11 years ago

    This is in the documentation in your QRC or Assura. It is however obsolete and ICT should really be used instead. It used to be the format for Assura RCX, but that has long been replaced by QRC.

    In the QRC documentation (the EXT13.2 release, for example), in the Assura RCX to QRC Migration Guide, chapter 2 "Creating a Process File", it explains how to do this. This will be in your EXTXX.Y installation, if you run cdnshelp  and search for "procfile". Or you can look at <EXTinstDir>/doc/qrcxRcxMigration/qrcxRcxMigration.pdf and look at chapter 2.

    It's also in the Assura documentation for Assura RCX. This is in the "Assura Physical Verification Developers Guide", in the chapter on "Assura RCX and Capgen Setup", in Step 2 (Create a Process Description File). This is in <ASSURAHOME>/doc/assuradev/assuradev.pdf

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information