time for PBP statements

[sayzer]

Hi Francesc,

Here is your answer.

Check this post.

http://www.picbasic.co.uk/forum/show...ghlight=timer1



-----------------------

[fnovau]

Thanks for your answer Sayzer but the thread explains how to measure time elapsed between sentences in a program and what I 'm interested in is to know when programming with Basic how many cycles it takes for every statement I write.
-Francesc

[SteveB]

Francesc,

You might try this include file I was working on and haven't gotten a chance to post. It should be self explianatory (assuming you are carefully reading your PICs datasheet and the PBP manual.

CodeTimer

HTH,
Steve B

[sayzer]

Thanks for your answer Sayzer but the thread explains how to measure time elapsed between sentences in a program and what I 'm interested in is to know when programming with Basic how many cycles it takes for every statement I write.
-Francesc

Ok, I see.

But, my curiosity, why would you need to know that information?
A kind of HW or what?


----------------------------------------------------

[mister_e]

Thanks for your answer Sayzer but the thread explains how to measure time elapsed between sentences in a program and what I 'm interested in is to know when programming with Basic how many cycles it takes for every statement I write.
-Francesc

Impossible to know uneless you measure every single statement or a block of.

How many different IF-THEN-ELSE combination exist?
How many different HSERIN combination exist?
How many different LCDOUT combination exist?
....
nobody can answer that. So you need to measure everything. Using a internal Timer or an i/o and a scope.

Now if you add some interupts in the chain... it's quite impossible to know uneless you sim every conditions... good luck!

[Darrel Taylor]

Thanks for your answer Sayzer but the thread explains how to measure time elapsed between sentences in a program and what I 'm interested in is to know when programming with Basic how many cycles it takes for every statement I write.
-Francesc

You should take a look at the program SteveB showed in Post# 4.

It's a great little program that can tie in with "ON DEBUG", and will show the exact time of each individual line of code in your program. It's pretty cool.
<br>