Stats

  • Locked Locked
  • Replies 4
  • Subscribers 64
  • Views 16252
  • 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

pre_body() and post_body() from virt-seq

archive

Hi there,

I implemented my objection handling "raise_objection" in pre_body() and "drop_objection" in post_body() so I don't have to worry about the test stopping during some sequence. When I "do" my sequences from a sve virtual_seq, the pre_body() and post_body() functions are not called whereas when I "do" my sequences from the MAIN eVC sequence, both are called.

Is this intended behaviour?

My workaround currently is calling pre_body() as first statement in body() itself and post_body at the very end.
The fact that calling them works tells me, that they are present.

Shouldn't they be called automatically by the virtual sequence before and after the body() section?

greetings


Originally posted in cdnusers.org by SomeDude
Parents

  • Hi,

    In this case i you can implement the objection mechanism by raising the TEST_DONE objection from the virtual sequence pre_body() and dropping it from the virtual sequence post_body().

    Hope this will help to you.

    --
    Regards,
    Gaurav Patel
    ASIC Engineer
    eInfochips.
    www.einfochips.com


    Originally posted in cdnusers.org by er_gauravpatel
Reply

  • Hi,

    In this case i you can implement the objection mechanism by raising the TEST_DONE objection from the virtual sequence pre_body() and dropping it from the virtual sequence post_body().

    Hope this will help to you.

    --
    Regards,
    Gaurav Patel
    ASIC Engineer
    eInfochips.
    www.einfochips.com


    Originally posted in cdnusers.org by er_gauravpatel
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.