Subject: Re: [sv-ec] Clocking Domains
From: Steven Sharp (sharp@cadence.com)
Date: Thu Jan 30 2003 - 13:58:35 PST
>Date: Thu, 30 Jan 2003 13:34:55 -0800 (PST)
>From: "Kevin Cameron x3251" <Kevin.Cameron@nsc.com>
>The point was to create a signal that can trigger processes just before
>the clock changes - when all data should be stable - rather than to have
>a delayed process waiting for the design to stabilize after the clock
>event. My initial thought was to sort the sensitivity list somehow, but
>I think the ".new" approach works better.
But the reason the data becomes unstable when the clock changes is that
processes triggered by the clock change the data. If you trigger processes
at this .new time, the data becomes unstable then instead. Where is the
gain for this extra complexity?
Steven Sharp
sharp@cadence.com
This archive was generated by hypermail 2b28 : Thu Jan 30 2003 - 13:59:09 PST