Quoting Tamas Rudnai <tamas.rudnai@gmail.com>:

> It depends on your needs but generally speaking you need to use a timer
> module that tells you the exact timing you need. In other words you shoul=
d
> not depend on the instruction cycles, and all you need is to make sure yo=
u
> can done the bit banging before the next tick comes... You can do this by
> interrupts or by polling the timer register, depending again what are the
> specifications and if the service routing can handle the demand (ISR coul=
d
> have a bigger overhead with all the context savings and such stuff than a
> polling...).
>
> Tamas


Ugh -- actually sounds like an overhead nightmare with either option.  =20
Not the answer I wanted to hear.  I was expecting some way to switch =20
off optimizations perhaps, and a way (such as a profiler) to figure =20
out how many instructions or clock-cycles a particular code sequence =20
takes.  Perhaps the C-compilers (which I haven't used yet) would allow =20
me access to the intermediate assembler code when it compiles it, as =20
from that I could possibly make a better determination of which is the =20
best way to handle certain timing-specific tasks.

Thanks,
-Neil.




--=20
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
.