A friend told me about a problem compiling ktl in Debian Squeeze
He has automake 1.11 and had this error:
$ make -f Makefile.cvs
This Makefile is only for the CVS repository
This will be deleted before making the distribution
*** YOU'RE USING automake (GNU automake) 1.11.
*** KDE requires automa
Ok... i think now pic simulation work quite better, the simulation run in
two diferent ways:
-When runed from the circuit button (play), simulation goes at real time for
a 20 MHz compiled pic code, registers are not updated, breakpoints doesn't
have effect, it's just like powering the pic.
-When
> Maybe Alan knows: how is the time in simulation managed?
Not really...
The code was a real mess. The current preferred method is
Simulator::time(). This will read the current linear element clock for you.
There is kindof a problem though because if a subcircuit has analog
elements it will
Hello again
Using flowcode I'm performing a right-rotation on variable x on a P16F84.
Port A TRIS is 0001 and port B TRIS is . x is set to 1 before
the initial rotation.
I have the chip's out pins hooked up to LEDs in a circuit in ktechlab. I'm
writing x to port B, the value of whic
2009/9/16 Zoltan Padrah
> Yes. the logic update is done as you've written.
>
> What do you mean by unstable? Ktechlab crashes or just outputs garbage?
>
Unstable perhaps is not the proper word... i mean irregular periods, i tried
with a simple toggle led pic program at 1 Hz.
Logic update at 5e6
Yes. the logic update is done as you've written.
What do you mean by unstable? Ktechlab crashes or just outputs garbage?
Also I don't understand how to reproduce the problem. Set the logic update
timer to 5e6 and then?
Maybe Alan knows: how is the time in simulation managed? We should provide
th
I't looks to me that logic update rate (then gpsim processors) is actually
1e6, then 1 MHz.. is this correct?
What is the actual behaivor of logic update rates?
i think the qtimer is at 1KHz, but the loops inside every call aren't
sinchonized... i mean: logic updates are done 1e6 times/Sec, but no
