Stats

  • Locked Locked
  • Replies 2
  • Subscribers 64
  • Views 13442
  • 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

query on scope of events in e language

jaichandra

Hi

   My verification environment is in e language completely.  I want to access the events of an unit from top level sequences i build. earlier i used to accesses the events anywhere in the seqeunces using the code shown below.

wait @get_enclosing_unit(top_unit).unit1.unit2.unit3.target_unit.event_name;

Now the same code i am not able to see the events. The sequence keep waiting for the event. But the event is already generated in the target_unit. 

I am confused why it is not working now.  Any help is greatly appreciated.

- regards

  • Are you sure that the wait statement was executed before the target unit emitted the event? If you use the command "trace event target_unit.event_name" you'll see in the log every time the event is emitted. You could also put a message print-out right before your wait statement.

    If they're happening in the same time step you might consider using the "sync" statement instead of "wait", because sync can complete in the same time slot if the event was already emitted in that time slot, whereas wait needs to have been executed before the event is emitted.

    From the documentation: "The sync action is similar to the wait action, except that a wait action always requires at least one cycle of the TCM's sampling event before execution can continue. With a sync action, execution can continue in the same Specman tick."

     

  • Hi stephen,

                     Thanks for your reply. My issue is resolved. There was no problem with the code. But the issue was with the clock. The sequence driver clock was getting gated in between becasue of which the driver was not able to see the events. I changed the clock source after which the code worked fine. Thanks for you reply.

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.