I only remember having responded ONCE to you ... and I do think no one here can give you a precise time as an answer. ( except Fernand REYNAUD's " a certain time" ... Lol )your answers.
End of File for me ...
Alain
I only remember having responded ONCE to you ... and I do think no one here can give you a precise time as an answer. ( except Fernand REYNAUD's " a certain time" ... Lol )your answers.
End of File for me ...
Alain
************************************************** ***********************
Why insist on using 32 Bits when you're not even able to deal with the first 8 ones ??? ehhhhhh ...
************************************************** ***********************
IF there is the word "Problem" in your question ...
certainly the answer is " RTFM " or " RTFDataSheet " !!!
*****************************************
The best way to get your answer is to compile the code, look at the assembly listing, and compute the time to execute one cycle from that. Then multiply it by the number of cycles the loop is expected to run. You also need to check the PIC assembly code docs to see how long it takes to execute each assembly code. I have done this a lot in order to determine how long my interrupt routines are.
Also I think some of the comments are about the fact that the code sample you gave may not run the way you expect. "A" is not defined so the WEND duration is unknown. Also, A does not change so it is not a good loop control variable.
I wonder if someone has written a program that reads assembler files and tags execution times to all the microcode.
Last edited by falingtrea; - 25th June 2008 at 21:51.
Tim Barr
Bookmarks