How do variables get synthesized in this case?

Jacko wrote:

or maybe just process() which would appear to be a useless process
template.

My favorite is
process(reset, clock)


-- Mike Treseler
 
On 23 Mar, 17:47, Andy <jonesa...@comcast.net> wrote:
On Mar 19, 10:03 am, Jacko <jackokr...@gmail.com> wrote:



Nothing!! nibzB.vhd not yet available will have the seperate D_I and
D_O and correct sensitivity to them. From my minimum state change
prospective.

cheers jacko

http://nibz.googlecode.com

If you simulated nibzA.vhd, you would see what the difference between
simulation and synthesis is WRT the following simplification of your
example:

process(smelly) is
begin
  fart <= smelly;
  nose <= fn(fart);
end process;

The combinatorial processes in nibzA.vhd exhibit this mistake a few
times too.

Andy
Yes, I have not ignored the warnings, they are still there. The fact
that sythesis in Quartus II 8.0 seems to not use the simulation
understanding is of small education on such a design.

On a large design, the power density limits of a material
semiconductor may be exceeded by such differing 'easy' sythesis vs.
'lazy' simulation outcomes.

So process(all) should be augmented with process(enough) or some such
suitable enumeration generic ting.

or maybe just process() which would appear to be a useless process
template.

cheers jacko

a.k.a. doc sith (dark side pesant revolutionary front :)
 

Welcome to EDABoard.com

Sponsor

Back
Top