Reading O value

Oh, please.....

• You have posted more than 400 lines of code.
• The code contains no useful comments whatever.
• Most of the signal names are incomprehensible.
• All the state names are meaningless.
• Many of the process sensitivity lists contain signals that they do not need.

Kindly put in the effort to isolate the problem more carefully. As part of that process, you should document your code. This documentation will help you in understanding what's going on for yourself.

If you still have a problem after you have done this, then at least you will be able to post something manageable and there is some chance that someone will try to help you.

-- Jonathan Bromley, Consultant

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

Doulos Ltd. Church Hatch, 22 Market Place, Ringwood, Hampshire, BH24 1AW, UK Tel: +44 (0)1425 471223 mail: snipped-for-privacy@doulos.com Fax: +44 (0)1425 471573 Web:

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

Jonathan, you left out a few:

• processes without names/labels
• long 'if/elsif' statements where 'case' is more appropriate
• 'Std_Logic_Arith' used instead of 'Numeric_Std'
• and finally instead of (#note 1)

This has to be the worst example of bad coding style that I've come across in a long time - LOL

#note 1 people who use tabs in source code should be hung drawn and quartered!.............. IMHO ;-)