[sv-ec] FW: [sv-ac] clocking block trrigger, global clocking

From: Bresticker, Shalom <shalom.bresticker@intel.com>
Date: Thu Apr 28 2011 - 10:02:58 PDT

From: owner-sv-ac@eda.org [mailto:owner-sv-ac@eda.org] On Behalf Of Eduard Cerny
Sent: Thursday, April 28, 2011 7:57 PM
To: 'sv-ac@eda-stds.org'
Subject: [sv-ac] clocking block trrigger, global clocking

Hi,

i find clocking events a little confusing in the LRM:

on page 291, 14.13, it says:
Upon processing its specified clocking event, a clocking block shall update its sampled values before triggering
the event associated with the clocking block name. This event shall be triggered in the Observed
region.

on page 289, 14.10, it says:

The clocking event of a clocking block is available directly by using the clocking block name, regardless of
the actual clocking event used to declare the clocking block.
For example:
clocking dram @(posedge phi1);
inout data;
output negedge #1 address;
endclocking
The clocking event of the dram clocking block can be used to wait for that particular event:
@( dram );
The above statement is equivalent to @(posedge phi1).

How can it be equivalent if one triggers in the active region and the other in the observed region?

How the will $global_clock trigger? In observed region? Does it matter where since assertions execute in observed regardless? Updates of checker variables?

thanks,
ed

--
This message has been scanned for viruses and
dangerous content by MailScanner<http://www.mailscanner.info/>, and is
believed to be clean.
---------------------------------------------------------------------
Intel Israel (74) Limited
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
Received on Thu Apr 28 10:03:46 2011

This archive was generated by hypermail 2.1.8 : Thu Apr 28 2011 - 10:03:55 PDT