Stats

  • Locked Locked
  • Replies 3
  • Subscribers 125
  • Views 17633
  • 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

Knowing associated TECH-FILE location

RFStuff

 Dear All,

I have installed a main stream PDK in my Cadence enviornment.

While creating a new library, I associated the techfile corresponding to this  PDK.

Is there any way to know the location of the tech file. 

The document of the PDK days that the tech file is obtained by compiling a  xxx.asc file.

 Is there any way I can know which .asc file the tech file is compiled from ?

Kind Regards,

Parents

  • When you attach to an existing tech file,  you're really attaching to the tech file in an existing library. You don't need to know where the tech file actually is. You pick the main technology library that's in the PDK - which should be documented. Provided that library is available via your cds.lib, you can pick it.

    The technology database (in IC5141) will be called techfile.cds (in IC61X it's called tech.db) and is a binary database. It lives at the root of a library.

    When you attach to a tech file, you'll only be offered the choice of libraries that contain binary technology databases within that library.

    Regards,

    Andrew.

Reply

  • When you attach to an existing tech file,  you're really attaching to the tech file in an existing library. You don't need to know where the tech file actually is. You pick the main technology library that's in the PDK - which should be documented. Provided that library is available via your cds.lib, you can pick it.

    The technology database (in IC5141) will be called techfile.cds (in IC61X it's called tech.db) and is a binary database. It lives at the root of a library.

    When you attach to a tech file, you'll only be offered the choice of libraries that contain binary technology databases within that library.

    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.