Stats

  • Locked Locked
  • Replies 1
  • Subscribers 125
  • Views 1880
  • 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

Using time of an assert event in ADE Assembler's output expressions

Zol

Hi everybody,

It is possible to use the time point of an assert in event driven transient simulation through the dynamic parameter option in the GUI or through a paramset file. Is there a way to access this time point in ADE's output expressions?

I've tried @MyAssert, @(MyAssert), \@MyAssert and \@(MyAssert), but it did not work οn IC6.1.8. I am not familiar with ADE's checks and assert interface, but I have used a spectre command file in the simulation files menu to define the assert.

Of course I could recreate the expressions in ADE as a workaround. I am only curious whether I can save this, to save time in the post-processing and reduce the number of items in ADE's outputs setup tab.

  • OK, here's a step-by-step process that works (I just checked):

    1. First of all, identify the assert name as it appears in the checks and asserts database (it may be MyAssert). In my case I defined one called CrossOP which was defined in the checks-and-asserts setup rather than via an include file, and it ended up called something like mylib/testpwf/CrossOP. You can do this by going to the Checks/Asserts view in the results pane and seeing what is present under the Checker Name column
    2. Then back on the Outputs Setup pane, add an output of type violations. You can then use the "..." button to create a filter for "Checker Name" LIKE "%CrossOP%" - matching your name. You can do this defining the filter like this:

      I typed in "CrossOP" as the filter name and hit the save icon. The Where was assembled by clicking on CheckerName in the Available Fields and then the left arrow to move into the Where box, and typing in the LIKE part myself.
    3. On the outputs pane, select the filter you want, then start time(s) and Min to find the time of the first occurrence of the assertion:
    4. You can then see that I have another expression which I built using the expression builder which is using that crossStart output (I gave the violation output a sensible name) - this all then works:

    I hope that's clear enough!

    Andrew

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.