Stats

  • Locked Locked
  • Replies 2
  • Subscribers 63
  • Views 15989
  • 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

LEC debug points report generation ???

aperla

LEC between rtl and netlist

i have black boxed all the logic blocks. 

assue there is no logic between inputs to till black boxes.

now i wanted to generate the report for each failed point with respect to inputs

please help

thanks

 

  • For each non-equivalent point (and a blackbox is considered as 1 point), you can generate a diagnosis report for it with "diagnose" command.

    i.e.

    LEC> diagnose top/A/B/C/u_sram -golden

    When it's a blackbox, LEC will diagnose and report each and every input pins which are non-equivalent.

     Here's the description of "diagnose" command.

     SYNTAX
           DIAgnose
           <<gate_id> | <instance_pathname> | <pin_pathname>
             [-Golden | -Revised]
             [-SUPport]
             [-MERge]
             [-NUm <integer>]
            | -SUMmary [integer][-SOrt <SUpport | SIze>]
            |[-NOneq]>
            [-GROup]
            [-VERBose]
           (LEC Mode)

    DESCRIPTION
           Runs diagnosis on a specified compared point. Specify the compared
           point by its gate identification number, instance path, or a pin path.
           Use this command to determine why the software identified nonequiva-
           lence between compared points.

           The diagnosis displays all of the non-corresponding support key points
           with a list of all likely error candidates from the Revised design. The
           list organizes likelihood in descending order with 1.00 being the
           greatest possible error candidate.

           Use the REPORT ENVIRONMENT command to display the maximum diagnosis
           candidates setting.

           Note: The syntax above assumes you are diagnosing mapped compare points
           (where you only need to specify one compare point). When you are diag-
           nosing instance/sequential merge nonequivalence, you must specify two
           compare points.

    PARAMETERS
           <gate_id>       Diagnoses the specified gate.

                           Note: ID numbers can differ from one version of Confor-
                           mal to another. Always use the full path in dofiles and
                           any time you rerun a design with a different Conformal
                           version.

           <instance_pathname>
                           Diagnoses the specified instance path.
     ...

  •  SYNTAX
           DIAgnose
           <<gate_id> | <instance_pathname> | <pin_pathname>
             [-Golden | -Revised]
             [-SUPport]
             [-MERge]

    I don't understand this part



    ________
    sogold - founder gia ca phe hom nay and gia ca phe noi dia 

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.