Stats

  • Replies 7
  • Subscribers 160
  • Views 17387
  • Members are here 0
More Content

Get info from all footprints in library

EvanShultz

I would like to write a report that gives 3D mapping info for all footprints in the library. I have written a report that works fine for all footprints on a board, so I should be able to simply swap out the list of footprints on the board with a list of footprints in the library. But I'm not sure how to do that.

getDirFiles(axlOSSlash(strcat(axlGetVariable("CDS_SITE") "//footprints"))) gives me a list of all footprints in the library, but I don't know how to access the footprint properties. The board report is as simple as symdef->prop->PKGDEF_STEP_FILE (and the other 3D model properties) for each footprint on the board, but that doesn't work with a pile of PSM files sitting out on a network folder.

Does anyone know how I can access the properties of a footprint on the network? I searched the forum and didn't find anything but I may have just not used the proper search terms. Thanks in advance for any help!

  • in reply to EvanShultz

    Nice that you succeeded to parse the information. 

    I assume you only need to run this once. If so then I suggest to copy all footprint files to a local drive. This will run much faster.

    1) you can set multiple items in the extracta option file. With axlExtractToFile() you can extract data from the current database to a ascii file. For example the ODB exporter is using this to generate several files for the actual ODB converter.

    2) I understand what the issue is, you want to sort the dra file list before you start extracta. If all of your DRA files are in 1 large directory then this is impossible without using extracta (and going through each file...) Maybe you can filter the footprints by the filename?

    The pp() is a pretty print and you can find it in the 'Cadence SKILL Development Reference'. (skdevref)

    push() is a default LISP macro. In SKILL it is actually a macro that calls cons().  So it basically does the same as a cons(), but it is shorter to write up:

    strings = cons("hello" strings)

    push("hello" strings)

    Skill > isMacro('push)  --> t
    Skill > expandMacro('push("a" x))   --> car(    (x = cons("a" x)))

    So the push uses cons() and returns the first element in the list (so the item that was added to the list)

  • regarding the documentation for ipcBeginProcess(), I just opened cdnshelp, searched for ipcBeginProcess which returned 7 results, the 1st was in 'Cadence Interprocess Communication SKILL Reference' which is in $CDSROOT/doc/skipcref

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.