Known Problems and Solutions in Virtuoso ADE Verifier
This document describes the known issues with Virtuoso® ADE Verifier and suggests the workarounds for these issues. Each issue is identified by a Cadence Change Request (CCR) number.
Related Topics
CCR 2551598: Setup Library cellviews created in the current version of Virtuoso are not compatible with earlier Virtuoso releases.
Description: When you create a Setup Library cellview, setupLib, in Virtuoso Studio IC23.1, and open it in the Setup Library assistant from an older Virtuoso release, the cellview contents are available, but the features cannot be used. Making any changes in the opened cellview view can cause Virtuoso to exit unexpectedly.
Solution: Currently, a workaround is not available.
CCR 2551597: Sync with Reference Setup does not work as expected for parametric sets in the Setup Library assistant.
Description: Consider that you create a parametric set from in the Setup Library assistant, and the drag the sweep setup that contains this parametric set to the Global Variables section of the Data View Assistant in Virtuoso ADE Assembler. This will create a reference in the Data View assistant to all the variables in the parametric set. If you modify a variable from this set in either of the assistants, the Data View assistant displays the variable name in bold. When you right-click this highlighted variable and choose Sync with Reference Setup, the variable does not update with the value in the Setup Library assistant.
Solution: Currently, a workaround is not available.
CCR 2134047: Verifier ignores verification spaces when corners or global variables are deselected in ADE Assembler and run mode is 'with SPACE'.
Description: Coverage in Verifier might show less than 100% after a simulation run when you select Local with SPACE or Batch with SPACE as the run mode. This is not correct.
When you specify a verification space for an implementation, corners or variables are set up accordingly in Verifier. However, Verifier does not check if the corners or variables are globally disabled in the corresponding maestro cellview. If the corners or variables are globally disabled, the simulation run in Verifier run does not create the expected coverage.
Solution: Check whether corners and global variables are enabled globally in ADE Assembler when applying verification spaces. To disable corners or global variables, use the individual check boxes in the Data View Assistant instead of the global check box for Corners and Variables.
CCR 1726252: Variable type tolerance and range type specs are missing in Verifier
Description: If the ADE Assembler output has a tolerance specification that has expression tolerance, expression target, or both as mentioned below:
tol (VAR("spec_value1") * 50) calcVal("constant")
Verifier cannot parse the correct minimum and maximum specification when creating requirement for this kind of output and the MinSpec and MaxSpec values are left blank.
Solution: There is no workaround available.
CCR 1463089: Assertion data is not visible for Monte Carlo simulations
Description: Currently, assertion checking for Monte Carlo implementations is not supported in Verifier.
Solution: There is no workaround available.
CCR 1509719: Implementation cellviews, whose AMS simulations are set to run in interactive mode, launch SimVision
Description: When you run an implementation cellview from Verifier, whose AMS simulation is set to start in interactive mode, the Explorer or Assembler graphical user interface does not display. However, the SimVision graphical user interface displays.
Solution: Disable the interactive mode of the AMS simulation before you run the implementation cellview from Verifier.
Return to top