Stats

  • Locked Locked
  • Replies 4
  • Subscribers 65
  • Views 15336
  • 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

generate of specman (vs) randomize of systemverilog

onkarkk

Hi,

Could any one please explain me clearly steps of generate and randomize and their significance.

i.e ., in generate it is told there is pre-generate and post-generate methods i could not understand clearly why they required.

In the same way in randomize() also there are pre_randomize() and post_randomize() methods will be invoked , i didnt get sufficient clarity on their explanation .. could any 

one please clarify the significance of those methods.

Thanks in advance,

regards

Krishna Kishore 

Parents

  • If sn_help.sh isn't working, you could use the PDF version of the docs instead.
    The Specman-e reference is: <install_dir>/doc/sn_eref/sn_eref.pdf
    The generation guide: <install_dir>/doc/sn_igenuser/sn_igenuser.pdf
    User Guide: <install_dir>/doc/sn_usage/sn_usage.pdf
    etc.

    Neither pre_ or post_ methods  do anything magic, eother in SV or e. They just give you a hook to execute some code just before or just after generation. As a day-to-day user of e, you can pretty much forget about these methods - I rarely find myself needing to use them, since the constraint solver "IntelliGen" is very powerful and can do everything I ever need it to.

    I don't quite get your point about "good_crc()". If you want to use this in a constraint, you'd have to make sure the method parameters define all the fields used to calculate the crc. For example:

    keep crc_error == FALSE => crc ==  good_crc(payload);

    If you want to apply good_crc() procedurally, you need to use post_generate() as the trigger to call your method:

    post_generate() is also {
      if !crc_error { crc = good_crc(); };
    };

     

     

Reply

  • If sn_help.sh isn't working, you could use the PDF version of the docs instead.
    The Specman-e reference is: <install_dir>/doc/sn_eref/sn_eref.pdf
    The generation guide: <install_dir>/doc/sn_igenuser/sn_igenuser.pdf
    User Guide: <install_dir>/doc/sn_usage/sn_usage.pdf
    etc.

    Neither pre_ or post_ methods  do anything magic, eother in SV or e. They just give you a hook to execute some code just before or just after generation. As a day-to-day user of e, you can pretty much forget about these methods - I rarely find myself needing to use them, since the constraint solver "IntelliGen" is very powerful and can do everything I ever need it to.

    I don't quite get your point about "good_crc()". If you want to use this in a constraint, you'd have to make sure the method parameters define all the fields used to calculate the crc. For example:

    keep crc_error == FALSE => crc ==  good_crc(payload);

    If you want to apply good_crc() procedurally, you need to use post_generate() as the trigger to call your method:

    post_generate() is also {
      if !crc_error { crc = good_crc(); };
    };

     

     

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.