Stats

  • Replies 14
  • Subscribers 159
  • Views 18875
  • Members are here 0
More Content

Export libraries of all DRA files in specific directory

aricbeaver

Hi,

I would like to use SKILL to iterate through every single DRA file in a directory and export the libraries, i.e. padstacks, shapes, etc. The reason is to verify library contents during each library commit.

Would this be the proper way to do this?

1. Get the DRA file paths using getDirFiles(<directory>)

2. Open DRA file

3. Use axlShell(<command>) to open export library form

axlShell("dlib")
axlShell("setwindow form.dlib")
axlShell("FORM dlib destination export")
axlShell("FORM dlib execute")

4. Repeat 2-3 for every other DRA file

Thx,

Aric

  • Hey Dave,

    1. I need to run this from a DRA not a BRD. Can that be achieved?
    2. Looks like it is failing on axll25x300037.dra which seems like it is from the Cadence libraries and not in my BRD database.

    Can the axlGetVariableList("psmpath") be changed to just use the current design database? I think that is the problem line for my application.

    Thx,
    Aric
  • And one other thing

    3. I don't see any of the "axl" functions in either of the documentation PDFs: \doc\sklangref or \doc\sklanguser, have any idea why?

    Thx,
    Aric
  • Ignore 3. you obviously answered that in your first reply. Sorry.
  • Hi Aric, It's a different exercise to do this as dra's. It would involve stepping through and opening each dra. Are you sure that you shouldn't be using dbdoctor to do this checking?
  • Here is my concept. This doesn't have anything to do with valid Cadence files, i.e. using dbdoctor. Just to ensure each library repository commit is correct, review, and logged. Taking care of all the files (DRA/PSM/PAD/SSM/PSM..... on and on) is quite painful and knowledge of that isn't really necessary for user to know since it is all technically embedded in the DRA itself.

    1) User creates a DRA that needs to be reviewed to adhere by company standards
    2) User uploads a DRA file to web based system (like Gerrit for software) to be reviewed. Additionally schematic symbols, database properties, etc.
    3) The server then extracts the padstacks/shapes/PSM files from the DRA and also uploads them to the review system
    4) All files are then reviewed and changes suggested, DRA goes through change control process
    5) Administrator approves the change
    6) Server commits proper files to repository
Cadence Guidelines

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.