Stats

  • Locked Locked
  • Replies 4
  • Subscribers 125
  • Views 15261
  • 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 tech.db a must if I want to create a tool that scans an existing layout created by Virtuoso Layout

Sahar Afara

 Hi,

I am creating a tool that scans existing layout files created by Cadence 6.1.5 Virtuoso Layout to read the layout in OpenAccess. Is it a must that I have the tech.db file in order to run any application built with OpenAccess APIs ?

  • This is a better question for the OpenAccess forums on the Si2 website.

    Regards,

    Andrew.

  •  Thans Andrew.

    Yes, true. 

    I wanted to know what is the difference between the cds.lib and libs.def file. I am still new to Cadence and sorry if my questions seem basic.

  • lib.defs is the OpenAccess standard way of describing where libraries are. It is based on the syntax of cds.lib, but only a subset of cds.lib syntax is supported. Cadence tried for some time to keep the two in sync, but nowadays we only read the cds.lib (via a special OA plugin that can also be used in other applications; this is covered in the documentation). It's possible to generate a lib.defs from cds.lib using the library path editor (both graphically and from the command line - see "cdsLibEditor -help") if you want to use an OA executable without using the cds.lib plugin.

    Regards,

    Andrew.

  • Thank you very much for this explanation. I got a little confused by these 2 files because I generated an OA database using str2oa from a GDS file and found lib.defs. I then received a layout of H-Bridge that I need to use for my tool that only had cds.lib and wasnt sure if my conversion example from GDS was correct (although I ahd done some small traverssals using OP APIs on it).

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.