• 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. How to retrieve variables and outputs for multiple test...

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 143
  • Views 6555
  • 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 retrieve variables and outputs for multiple test benches in ADE maestro view

mschw
mschw over 2 years ago

Hello everyone,

I tried to apply the script CCSRetrieveVarfromMaestro provided on Cadence Support .

Unfortunately, the function does not print the contents of the ADE view to the CIW.
CCSRetrieveVarfromMaestro("testlib" "testcell" "maestro")
"--------------------------------------------------- "
"Extracing the local and sweep design varialbes ... "
"----------------------------------------- "
"Extracing the global design varialbes ... "
"Extracing the design varialbes is completed...

When I open the view graphically in the Assembler, everything works as expected:

CCSRetrieveVarfromMaestro("testlib" "testcell" "maestro")
INFO (ASSEMBLER-9072): The 'testlib/testcell/maestro' cellview is already open in the 'a' mode. It will not be opened again.
"--------------------------------------------------- "
"Extracing the local and sweep design varialbes ... "
Testbench: "resdiv"
local/sweep variable "R0" = "1k"
local/sweep variable "R1" = "1k"
Output from "resdiv"
("V_I" nil "V_O" nil "V_O_swp")
Testbench: "lowpass"
Output from "lowpass"
("v_O_sin" nil "v_I_sin" nil "v_O_ac" "v_O_ac_dB" "v_O_ac_phase")
"----------------------------------------- "
"Extracing the global design varialbes ... "
Global Variable "R0" = "1k"
Global Variable "R1" = "1k"
"Extracing the design varialbes is completed... "

The problem seems to be that the 3rd line in the function
list_setup=maeGetSetup()
returns a different result in these two cases.

I modified the script by changing the 3rd line to
list_setup=maeGetSetup(?session mySession)
but unfortunately that did not change anything.

Currently, I'm using ISR 31.

What do I need to add to the script that the script behaves correctly, even if I do not open the view graphically?

Many thanks!

Regards,
Matthias

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 2 years ago

    Matthias,

    Initially I was offended by the spelling mistakes in the code in that article, and also it's not a particularly clean implementation so I rewrote it (not entirely - I kept the output formatting broadly similar). I've passed that along via a request to update the article (it's not my article) - so the updated code should appear shortly on the support site.

    However, I tried what you did with the code as-is, and it worked OK. It's not obvious why it would be failing - the best route would be to contact customer support (maybe the new version I wrote will fix the problem?)

    Andrew

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

    Matthias,

    The article has now been updated, by the way.

    Regards,

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • mschw
    mschw over 2 years ago in reply to Andrew Beckett

    Dear Andrew,

    thanks for spending your time in updating the article.

    However, even the new implementation fails to print the contents to the CIW.

    It seems that the project I'm currently working on is not setup properly.
    I went back to an older project - there everything works as expected.

    I will have a closer look on the project setup before I contact customer support.

    Many thanks!

    Regards,
    Matthias

    • 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