Stats

  • Locked Locked
  • Replies 1
  • Subscribers 65
  • Views 15777
  • 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

Verifying Configurable RTL with JasperGold

Andrew R

Currently I am trying to verify an RTL file which is created with Parameters and Generate statements. This module is made this way so that I can be used multiple projects and adapt to the parameters that it is passed from the top level. I wanted to know if the JasperGold platform has any way to verify the module with various parameters automatically, or If I manually have to set these parameters and then verify.

Thank you.

Parents

  • Jasper will test all legal values for data, such as values on ports or registers. So if you are using parameters to configure your design's internal data, that will be tested. But Jasper doesn't dynamically change the underlying hardware itself. That is a fixed foundation on which the data moves.

    You'll need to make individual runs, each with a different hardware configuration you want to test. You can specify different TCL scripts with various settings on the analyze and elaborate commands. Or you can create different top level wrapper modules which instantiate the variations you want to test.

    Many hardware configuration possibilities don't need to be individually tested. For example, various bit widths of a data path are usually considered equivalent. You may want to make tests when the width crosses a word or byte boundary. But Jasper users don't commonly run 64 separate tests for their data path.

Reply

  • Jasper will test all legal values for data, such as values on ports or registers. So if you are using parameters to configure your design's internal data, that will be tested. But Jasper doesn't dynamically change the underlying hardware itself. That is a fixed foundation on which the data moves.

    You'll need to make individual runs, each with a different hardware configuration you want to test. You can specify different TCL scripts with various settings on the analyze and elaborate commands. Or you can create different top level wrapper modules which instantiate the variations you want to test.

    Many hardware configuration possibilities don't need to be individually tested. For example, various bit widths of a data path are usually considered equivalent. You may want to make tests when the width crosses a word or byte boundary. But Jasper users don't commonly run 64 separate tests for their data path.

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.