Stats

  • Locked Locked
  • Replies 3
  • Subscribers 143
  • Views 16159
  • 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 get the corner session or object in the adexl with skill

Derek WANG

Hi All

I want to retrieve the information of the corner setup in the ADEXL.

by going through the documents and Forums, I find out how to get the variables and model setup.

but I cannot get the setup of the "tests" inside the corner setup.

Does somebody know how to do it?

another relevant question is that:

from the function of ADE XL (axl*), I can get the handle of the corner.

I'd like to know how to reach the object of the corner from its handle.

As the functions of ADE L ask the object of corner as the input.

Best Regards

Yi

Parents

  • Hi Yi,

    axlGetCornersForATest() is documented (maybe it wasn't in the version you're using, but it is now). However, I understand your problem - it gives the expanded corners, which may not be what you want. I'm sure you could write some code to correlate it with what axlGetCorners() returns, but it ought to be simpler.

    There is an API to return the tests which are disabled for a particular corner, but it's private. You should contact customer support to ask for a public API for this (it's come up in a previous CCR, but the main goal of that CCR was to find the total number of simulation points, not the actual corner names - this resulted in the addition of axlGetSetupInfo() - which won't help you).

    The asi.*Corner functions are obsolete. These refer the old IC5141 corners tool which was an add on for ADE (L). I have filed a request for these to be removed from the documentation since they are of no use in IC61X because the corner mechanism is completely different.

    With ADE XL, the object handles are integers, and so you cannot use the ~> operator on them - so you must use the documented API. Even with "asi" objects (for ADE L, or for ADE XL test objects), the usage of ~> on these objects is not documented and liable to change, and you should use the documented API only in those cases.

    Kind Regards,

    Andrew.

Reply

  • Hi Yi,

    axlGetCornersForATest() is documented (maybe it wasn't in the version you're using, but it is now). However, I understand your problem - it gives the expanded corners, which may not be what you want. I'm sure you could write some code to correlate it with what axlGetCorners() returns, but it ought to be simpler.

    There is an API to return the tests which are disabled for a particular corner, but it's private. You should contact customer support to ask for a public API for this (it's come up in a previous CCR, but the main goal of that CCR was to find the total number of simulation points, not the actual corner names - this resulted in the addition of axlGetSetupInfo() - which won't help you).

    The asi.*Corner functions are obsolete. These refer the old IC5141 corners tool which was an add on for ADE (L). I have filed a request for these to be removed from the documentation since they are of no use in IC61X because the corner mechanism is completely different.

    With ADE XL, the object handles are integers, and so you cannot use the ~> operator on them - so you must use the documented API. Even with "asi" objects (for ADE L, or for ADE XL test objects), the usage of ~> on these objects is not documented and liable to change, and you should use the documented API only in those cases.

    Kind 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.