On Sat, 4 Jul 2009 06:57:32 +0800
steve <[email protected]> wrote:

> [snip]
>
> But my main issue was the double/triple clocking of a variable that
> was only supposed to clock once on a signal transition. It of course
> is controlled by the only signal i could not investigate.
>
> [snip 2: snip returns]
>

This is a bit outside of your original request, but "a variable that
was only supposed to clock once on a signal transition" sounds AWFULLY
a lot like the classic rookie mistake of using data signals to clock
things, rather than running everything off of a system clock and just
synchronizing the data.

That sort of thing leads to situations that a) don't show up in
simulation and b) are murderously difficult to try to hunt down.

--
Rob Gaddi, Highland Technology
Email address is currently out of order