• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Custom IC Design
  3. strange error message in running adexl

Stats

  • Locked Locked
  • Replies 8
  • Subscribers 125
  • Views 18857
  • 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

strange error message in running adexl

Joe Black
Joe Black over 12 years ago
 Here is the msg found in the log file (NOT spectre.out under psf. psf direcotry is empty actually).

Error* Error during netlisting of design for the point ID (0 1).
\e ("ls" 0 t nil ("*Error* ls: too many arguments (0 expected, 1 given)" ("/prj/qct/scratch/sandiego/quboz/cadence_test/adexl_hackNetlist/adexl_new/results/data/Interactive.0")))
\e

 

 it ran through with ADEL.

My cadence version is IC615_isr12

Thanks,

Joe
  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 12 years ago
    Joe,

    I already explained why this is failing, but maybe I wasn't clear enough so let me try again.

    Cadence has a function called "ls" which has been defined for many years, although is private (ie we haven't documented it and so you should not use it in your code). It accepts either no arguments or one argument and returns a list of files in the working or specified directory.

    Somewhere in the ADE code it is using this function (which is fair enough, as it is one of our functions), and is calling it with a single argument.

    Now, you've replaced our private function with your own with the same name, and it doesn't accept an optional argument, nor does it return the list of files in the directory (it will print the working directory contents in the terminal window).

    So when our code calls ls, it breaks, because it doesn't behave as the code expects.

    Now I don't know why it suddenly stopped working in ADE XL but I can imagine that maybe you used a different calculator function, or you used some different part of the functionality in ADE XL, or it loaded your modified function from the .cdsinit which it hadn't done before. But regardless of this, you're asking for trouble redefining our functions, especially if they have different semantics from the original.

    We generally advise that customer SKILL code should define functions which have a prefix, where that prefix begins with an uppercase letter, since Cadence functions either don't have a prefix or have a lowercase prefix (in general).

    So if you called your function LS you'd be ok...

    Regards,
    Andrew
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 12 years ago
    Joe,

    I already explained why this is failing, but maybe I wasn't clear enough so let me try again.

    Cadence has a function called "ls" which has been defined for many years, although is private (ie we haven't documented it and so you should not use it in your code). It accepts either no arguments or one argument and returns a list of files in the working or specified directory.

    Somewhere in the ADE code it is using this function (which is fair enough, as it is one of our functions), and is calling it with a single argument.

    Now, you've replaced our private function with your own with the same name, and it doesn't accept an optional argument, nor does it return the list of files in the directory (it will print the working directory contents in the terminal window).

    So when our code calls ls, it breaks, because it doesn't behave as the code expects.

    Now I don't know why it suddenly stopped working in ADE XL but I can imagine that maybe you used a different calculator function, or you used some different part of the functionality in ADE XL, or it loaded your modified function from the .cdsinit which it hadn't done before. But regardless of this, you're asking for trouble redefining our functions, especially if they have different semantics from the original.

    We generally advise that customer SKILL code should define functions which have a prefix, where that prefix begins with an uppercase letter, since Cadence functions either don't have a prefix or have a lowercase prefix (in general).

    So if you called your function LS you'd be ok...

    Regards,
    Andrew
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information