Stats

  • Locked Locked
  • Replies 4
  • Subscribers 125
  • Views 15907
  • 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

Assembler Run Plan: enforcing runs to sequence correctly

Cra1g

Hi,

I am using Virtuoso IC6.1.7-64b.500.13 and have my testbenches and tests in Maestro views.

I have a two run run plan:

Run.0:  a calibration routine: Test = "calibrate_delay"

Output of interest: "cal_value_decimal"

Run.1: second calibration routine based on the result of the first test, passing it into a global variable using a calcval expression:

Global variables:

cal_stored = calcVal("cal_value_decimal" "calibrate_delay" ?run "Run.0")

The problem is that I can always see that both tests run concurrently and the correct value for cal_stored from Run.0 is not captured in Run.1

How can i best stage runs in my runplan?

Thanks in advance!

Craig

  • ++ A few further comments, I wrote this post based on my efforts yesterday where it was running the plan, but not picking up the correct value.

    Today:

    I re-created my run plan (Run.0 and Run.1) and this time I cannot run it at all, as it has detected a dependency between the runs which it didn't complain about yesterday:

    "Message 9080: cannot simulate Run.1 because it depends on run " that does not exist correct the dependency and re simulate the run"

    I have also tried to put in place a workaround for the concurrency issue from Run.0 and Run.1, where I generate a specific value in an output at the end of Run.0 which I wanted to be used to trigger Run.1.

    But the options I saw yesterday for adding run conditions no longer pick up any tests or outputs for me to select and trigger on.

  • in reply to Cra1g

    Hi Craig,

     Reg the ADE Assembler Message 9080 check whether in the Add/Edit Run Conditions form you have entered a blank condition. If so, remove it using the X icon.

    If you still see the issue you described in the beginning then perhaps you should file a ticket on the support site or give some more details of how your Run Plan looks like. 

    I cannot see a problem using calcVal() in the RunPlan. After creating my Run Plan similar to yours, Run.0 and Run.1 run in series and the correct value is propagated from Run.0 to Run.1.

    Regards,

    Dimitra

  • in reply to Dimitra Papazoglou

    Hi Dimitra,

    Thanks for you fast response.

    -I have fixed the error message, the problem was as you described there.

    -I have been able to sequence the run plans with a dummy pass criterion to stage the tests, so that's all good now.

    -Im still getting the wrong values from the calcval though, ill have one more stab at it then maybe raise a ticket.

    Some related question(s):

    If I don't tick any of the Global Variables in a particular Run Plan test, should that test pick up the local variables as defined for that test in ADE Explorer?

    Can I mix and match between overriding test variables via globals and leaving some variables as default from the ADE Explorer setup?

    Thanks for your help!

  • in reply to Cra1g

    Hi Craig,

    Cra1g said:
    If I don't tick any of the Global Variables in a particular Run Plan test, should that test pick up the local variables as defined for that test in ADE Explorer?

    Yes. If the Global variable is disabled in Run.x then the local value is used.

    Cra1g said:
    Can I mix and match between overriding test variables via globals and leaving some variables as default from the ADE Explorer setup?

    Yes you can. In Run.x make sure the Global Variables box is enabled. There, enable the variables you want to keep as globals and disable those you want to be local.

    You can confirm the above by adding expression ' VAR("variableName") ' as output and then run the Run Plan.

    Regards,

    Dimitra

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.