I
Igmar Palsenberg
Guest
> Processes run in parallel in both VHDL and in software.
That can only be done if :
a) You have multiple cores / processors
b) You have an OS that supports it
If either of them are not met, it all runs sequential.
I don't expect that simulation runs at fullspeed. Similar tools in software usually also have an overhead.
Hmm.. I never saw it. On the other hand : That was 15 years ago.
I personally don't like that myself.
Advise : Keep it that way
Igmar
That can only be done if :
a) You have multiple cores / processors
b) You have an OS that supports it
If either of them are not met, it all runs sequential.
In software your
process may be *hugely* complex doing many, many things in each one.
Partly that's because there is a huge overhead for setting up and
managing each process in software. In VHDL a process has no overhead in
the implementation. I'm not sure how complex process management is in
simulation. I've not heard it is a problem though. The speed problems in
simulation often come from the data structures. Integers are faster than
std_logic, et. al.
I don't expect that simulation runs at fullspeed. Similar tools in software usually also have an overhead.
I've used Altera's Max Plus II, that only had waveforms. Hooking a
real simulator up with Quartus failed for me. I might try the Xilinx
tools, see if I have better luck with them.
I've worked with Max +II. Debugging in VHDL is built in. ASSERT is a
great tool. Waveforms are for user exploration when a bug is found.
Hmm.. I never saw it. On the other hand : That was 15 years ago.
I was trying to point out there is a difference between getting
something to work, and actually understanding it. I failed at that
I've seen that many times. I've even done it when required. Sometimes
you don't have the time to "understand" something if you just need a
simple fix.
I personally don't like that myself.
BTW, I can't write PHP code. I don't even know what it is, so obviously
I'm not a monkey.![]()
Advise : Keep it that way
Igmar