e7 < k> wrote:
> Ralf Hildebrandt wrote:
>
>> e7 wrote:
>>
>>
>>> Mike, my experience of VHDL is nil.
>>
>>> I think the free 6502 uses 15,000 cells or something, so I need
>>> something big enough to cope with that.
>>
>> Do you think, that such a big project will help you? I personally would
>> get confused.
>
> I do a lot of coding in assembler and C - so learning VHDL is
> easy enough having looked at the syntax - but need to link
> it with the real world by programming chips and try to
> understand the practical side of using VHDL, programming up
> the chips and then debugging it when it all goes horrible.
Just one thing to remember with VHDL, the key is the HDL part, thats
H=Hardware D=Descriptor L=Language.
Just FYI the V in VHDL stands for VLSI which stands for very large scale
intergration.
Avoid thinking of VHDL as code but more as a picture of the hardware you
are trying to implement. Otherwise, you'll run into all sorts of timing
problems.
One more thing, you can actually decribe hardware in C. But as with VHDL,
don't think of it as code but a description of the hardware you are trying
to implement. Personally for simple designs, I perfer to use a graphical
layout program, that way the temptations of looking at the problem like
a programmer is reduced.
--
Wing Wong.
Webpage:
http://wing.ucc.asn.au