<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://community.arm.com/utility/feedstylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>How can I get the running time of  my programme?</title><link>https://community.arm.com/developer/tools-software/tools/f/keil-forum/14465/how-can-i-get-the-running-time-of-my-programme</link><description> I select the Atmel 87F51RC with 24.0M clock. 
How can I get the the running time of my programme by using the keil IDE? 
 
If i can get the running time of the programme by keil, is it equal to the the real running time on the Atmel 87F51RC I selected</description><dc:language>en-US</dc:language><generator>Telligent Community 10</generator><item><title>RE: How can I get the running time of  my programme?</title><link>https://community.arm.com/thread/53906?ContentTypeID=1</link><pubDate>Wed, 17 Oct 2001 09:26:27 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:52fef3e5-5f73-4bb6-bc34-00bdba9eb002</guid><dc:creator>Jon Ward</dc:creator><description>&lt;p&gt;&lt;i&gt;is it equal to the the real running time on the Atmel 87F51RC I selected?&lt;br /&gt;
&lt;br /&gt;
If you just had simple program which runs &amp;quot;straight through&amp;quot; - without interrupts or anything - then, yes!&lt;br /&gt;
&lt;br /&gt;
But if you have interrupts (as most embedded systems do) or any other external factors which would affect the run time (eg, slow memory; unknown wait times for peripherals; execution paths dependent on external states/events) then you&amp;#39;d need to do some sort of statistical model to get realistic results from the Performance Analyser.&lt;/i&gt;&lt;br /&gt;
&lt;br /&gt;
Or, you can just look at the Secs displayed in the Registers window and see how long the whole thing took.&lt;br /&gt;
&lt;br /&gt;
That&amp;#39;s much easier and you don&amp;#39;t have to do ANY math at all!  :-)&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;Jon&lt;/b&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How can I get the running time of  my programme?</title><link>https://community.arm.com/thread/37954?ContentTypeID=1</link><pubDate>Wed, 17 Oct 2001 03:49:22 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:e456e120-b5e3-4444-9f67-b4db8d907a99</guid><dc:creator>Andrew Neil</dc:creator><description>&lt;p&gt;&lt;i&gt;How can I get the the running time of my programme by using the keil IDE?&lt;/i&gt;&lt;br /&gt;
Use the &lt;b&gt;Performance Analyser&lt;/b&gt;&lt;br /&gt;
&lt;br /&gt;
But most embedded applications don&amp;#39;t just run &amp;amp; then stop when they&amp;#39;ve finished; they just keep going for as long as the equipment in which they&amp;#39;re embedded keeps running!&lt;br /&gt;
&lt;br /&gt;
But you can still use the Performance Analyser to time a particular part of your application.&lt;br /&gt;
&lt;br /&gt;
&lt;i&gt;is it equal to the the real running time on the Atmel 87F51RC I selected?&lt;/i&gt;&lt;br /&gt;
&lt;br /&gt;
If you just had simple program which runs &amp;quot;straight through&amp;quot; - without interrupts or anything - then, yes!&lt;br /&gt;
&lt;br /&gt;
But if you have interrupts (as most embedded systems do) or any other external factors which would affect the run time (eg, slow memory; unknown wait times for peripherals; execution paths dependent on external states/events) then you&amp;#39;d need to do some sort of statistical model to get realistic results from the Performance Analyser.&lt;br /&gt;
&lt;br /&gt;
(Some) emulators can do timing analysis in your target - but you&amp;#39;d still have to ensure that you measured during a &amp;quot;realistic&amp;quot; scenario.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How can I get the running time of  my programme?</title><link>https://community.arm.com/thread/37957?ContentTypeID=1</link><pubDate>Wed, 17 Oct 2001 01:37:34 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:b317091b-51af-4708-93f1-552fadeeccca</guid><dc:creator>Christophe Champigny</dc:creator><description>&lt;p&gt;It seems to me that there is a &lt;i&gt;&lt;b&gt;states&lt;/b&gt;&lt;/i&gt; value in the register windows of the keil debugger. This states value gives the number of your 8051 cycles. The next value is &lt;i&gt;&lt;b&gt;sec&lt;/b&gt;&lt;/i&gt;, that give you the calculating time depending of your crystal value&lt;br /&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>