# ** Warning: /X_FF PULSE WIDTH High VIOLATION ON SET;

[cheevu]

Dear All,
when I did my timing simulation, I got the warning messages:
# ** Warning: /X_FF PULSE WIDTH High VIOLATION ON SET;
# Expected := 2.889 ns; Observed := 2 ns; At : 16641.995 ns
and
# ** Warning: /X_FF PULSE WIDTH High VIOLATION ON RST;
# Expected := 2.889 ns; Observed := 2 ns; At : 16642.098 ns

I want to know how to debug these warning.
Please help me......
Thanks

 

[Jonathan Bromley]

On Fri, 05 Oct 2007 21:28:12 -0700, cheevu <dshanmugavel@gmail.com>
wrote:

Dear All,
when I did my timing simulation, I got the warning messages:
# ** Warning: /X_FF PULSE WIDTH High VIOLATION ON SET;
# Expected := 2.889 ns; Observed := 2 ns; At : 16641.995 ns
and
# ** Warning: /X_FF PULSE WIDTH High VIOLATION ON RST;
# Expected := 2.889 ns; Observed := 2 ns; At : 16642.098 ns

I want to know how to debug these warning.
Please help me......
Thanks

Hmmmm.... Seems to me like a warning message of exemplary
clarity. Some time around 16640ns your simulation has created
set and reset pulses only 2ns wide. Is this a good idea?
Probably not. Can you debug it? I hope so, because for
certain sure I can't, seeing as I don't have any of your code.
--
Jonathan Bromley, Consultant

DOULOS - Developing Design Know-how
VHDL * Verilog * SystemC * e * Perl * Tcl/Tk * Project Services

Doulos Ltd., 22 Market Place, Ringwood, BH24 1AW, UK
jonathan.bromley@MYCOMPANY.com
http://www.MYCOMPANY.com

The contents of this message may contain personal views which
are not the views of Doulos Ltd., unless specifically stated.