Stats

  • Locked Locked
  • Replies 1
  • Subscribers 143
  • Views 14756
  • 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

How to locate a file that is loaded using loadi?

Sheppy

Hi,

In one of the PDK we're using, somewhere in the entire chain of loading files/code, a certain file is loaded using this syntax:

loadi( "fileX.il" )

So, loadi() looks through the skillPath to find the file in one of the specified directories.

I need to locate this file in order to find a bug in one of the procedures which is in that file.

The skillPath in this particular PDK is very (very) long when I check it with getSkillPath() (it has duplicates in it, how dodgy...). I can write some code to print the location of the file:

printf( "file fileX.il is here = %s\n" car( foreach( mapcan path getSkillPath() when( isFile("fileX.il" list( path ) ) list( path ) ) ) ) )

This has one drawback: it will not show all locations if it is present at multiple locations. Removing the car() will do this trick (the %s must be swapped with %L too), although the formatting will not look nice with all double quotes.

Is there a standard SKILL function (procedure) that does the exact same thing? Procedure could be called getFilePath()...

Thanks in advance.

With kind regards,

Sjoerd

Parents

  • Hi Sjoerd,

    There's no standard function, but there is this COS solution (guess who wrote it?). Again, it only tells you the first match - the code is intended to work whether you give an absolute path, a few relative path combos or have let it find it using the SKILL path.

    Regards,

    Andrew.

Reply

  • Hi Sjoerd,

    There's no standard function, but there is this COS solution (guess who wrote it?). Again, it only tells you the first match - the code is intended to work whether you give an absolute path, a few relative path combos or have let it find it using the SKILL path.

    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.