Printable View
My beef is with the overall PBP manual.
The manual is very good, but many times it does not go into enough depth, in general i think it could use more information.
I think it would be very useful to include a sheet in the PBP manual that gives you the estimated # of cycles each PBP cycle will take, and also an in depth guide to how to code to maximize speed.
well, since all application are different, statement use is different. crystal speed is different and the list is still long, they can't really give you this kind of information. If you want to have a great idea of the time your program take from 'a' to 'b' use MPLAB stop-watch.
Hi, Toalan
Your desire is accomplished by the use of PBP with MPLAB tools ...
Just take the .asm of your program ... and count cycles !!!
Or open the PBPlibs, as asm code given ... do the count for the functions.
A very little work to do ...don't you think ?
If you really are in a hurry ... why not use "C" or assembler ???
Alain