• 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. Functional Verification
  3. Verification Plan using Eplanner

Stats

  • Locked Locked
  • Replies 19
  • Subscribers 65
  • Views 20401
  • 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

Verification Plan using Eplanner

Manish Verma
Manish Verma over 16 years ago

 Hi....

 

Can anybody explain me How to map checkers(check that statement) into vplan using eplanner?

 

Thanks! 

  • Cancel
Parents
  • archive
    archive over 16 years ago
    Hi Manish,

    The easiest way is to define this in the SPECMAN_PRE_COMMANDS since the idea is the have this config before any e is loaded.

    I would have in my run script something like:

    #!/bin/sh

    SPECMAN_PRE_COMMANDS=”conf cover –collect_checks_expects=TRUE”;

    Export $SPECMAN_PRE_COMMANDS

    Specman –c “load $WORKAREA/my_test.e; conf cover –database_format=ucd –write_model=ucm; test”;

    Hope this helps!

    Ilana.
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • archive
    archive over 16 years ago
    Hi Manish,

    The easiest way is to define this in the SPECMAN_PRE_COMMANDS since the idea is the have this config before any e is loaded.

    I would have in my run script something like:

    #!/bin/sh

    SPECMAN_PRE_COMMANDS=”conf cover –collect_checks_expects=TRUE”;

    Export $SPECMAN_PRE_COMMANDS

    Specman –c “load $WORKAREA/my_test.e; conf cover –database_format=ucd –write_model=ucm; test”;

    Hope this helps!

    Ilana.
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
No Data

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