• 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 SKILL
  3. *Error* eval: undefined function - hiSetBindKey when running...

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 143
  • Views 4523
  • 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

*Error* eval: undefined function - hiSetBindKey when running si or strmout

alexstepanov75
alexstepanov75 over 6 years ago

Hi,

When running si or strmout I am getting error

*Error* eval: undefined function - hiSetBindKey

I understand that this function undefined when running si or strmout

The question is how I can detect which skill calls this function?

Thanks,

Alex.

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 6 years ago

    Hi Alex,

    Put this around your bindkey setting:

    when(isCallable('hiSetBindKey)
      hiSetBindKey(...)
      hiSetBindKey(...)
    )

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • alexstepanov75
    alexstepanov75 over 6 years ago in reply to Andrew Beckett

    Hi Andrew,

    The problem is that all my hiSetBindKey calls already inside when as you suggested. It is hiSetBindKey in another place like PDK skills or other tool skills loaded by virtuoso causing this error.

    So the question is it a simple way to locate it?

    I suspect it is in skill loaded by libinit.il from TSMC PDK library. So additional question is it possible to skip loading of libinit.il in si?

    Thanks!

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 6 years ago in reply to alexstepanov75

    It's potentially dangerous to skip loading of libInit.il in si because there might be a custom netlist procedure defined via that libInit.il which would then be missing. Unfortunately you can't skip them anyway (historically there was a problem where a FirstAccessLib which returned nil caused the rest not to run, but that was a mistake and was fixed).

    In order to locate it, I guess you could start virtuoso, and then (assuming you have the SKILL Development license) use:

    breakpt(hiSetBindKey)

    and then do whatever you do to trigger the library to be loaded. I don't believe TSMC normally put bindkey definitions in their libInit.il though, but maybe it's a local customisation?

    When the breakpt is triggered, you can type where() to find out the stack as to what it's doing at the time, and that may help locate it.

    Regards,

    Andrew.

    • Cancel
    • Vote Up +1 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 6 years ago in reply to alexstepanov75

    It's potentially dangerous to skip loading of libInit.il in si because there might be a custom netlist procedure defined via that libInit.il which would then be missing. Unfortunately you can't skip them anyway (historically there was a problem where a FirstAccessLib which returned nil caused the rest not to run, but that was a mistake and was fixed).

    In order to locate it, I guess you could start virtuoso, and then (assuming you have the SKILL Development license) use:

    breakpt(hiSetBindKey)

    and then do whatever you do to trigger the library to be loaded. I don't believe TSMC normally put bindkey definitions in their libInit.il though, but maybe it's a local customisation?

    When the breakpt is triggered, you can type where() to find out the stack as to what it's doing at the time, and that may help locate it.

    Regards,

    Andrew.

    • Cancel
    • Vote Up +1 Vote Down
    • Cancel
Children
  • alexstepanov75
    alexstepanov75 over 6 years ago in reply to Andrew Beckett

    Andrew,

    breakpt(hiSetBindKey) worked. As I suspected hiSetBindKey called from one of .cdn files loaded from libInit.il of PDK library.

    Thank you very much. You are very helpful, as usual :)

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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