<?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>LPC2468 timer behavior - transition drom boot to application</title><link>https://community.arm.com/developer/tools-software/tools/f/keil-forum/24703/lpc2468-timer-behavior---transition-drom-boot-to-application</link><description> 
Hello, 
I wrote a bootloader that works just fine in doing IAP, jumping to
application etc. 
I do have one big problem though: the bootloader uses timer 1 to
drive a LED. unless I disable that timer, the application usage of
timer 1 is incorrect, namely</description><dc:language>en-US</dc:language><generator>Telligent Community 10</generator><item><title>RE: LPC2468 timer behavior - transition drom boot to application</title><link>https://community.arm.com/thread/101580?ContentTypeID=1</link><pubDate>Mon, 26 Jan 2009 04:44:27 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:372e8b94-1627-4682-b5fb-bcc325512ce9</guid><dc:creator>Tamir Michael</dc:creator><description>&lt;p&gt;&lt;p&gt;
I have to get used to 32 bit counters; the STR9&amp;#39;s counters are 16
bit!&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: LPC2468 timer behavior - transition drom boot to application</title><link>https://community.arm.com/thread/89532?ContentTypeID=1</link><pubDate>Mon, 26 Jan 2009 03:23:48 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:af1d6b63-d0aa-49d6-acbe-3b0a7ff6b7b0</guid><dc:creator>Tamir Michael</dc:creator><description>&lt;p&gt;&lt;p&gt;
thanks Per; I thought it might something like that. executing&lt;/p&gt;

&lt;pre&gt;
T1TCR = 2 ;
&lt;/pre&gt;

&lt;p&gt;
(holding the timer in reset until the application reconfigures it)
seems to solve the problem. this pqrticular timer is free running, no
interrupts involved (but they are remapped, of course).&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: LPC2468 timer behavior - transition drom boot to application</title><link>https://community.arm.com/thread/55264?ContentTypeID=1</link><pubDate>Mon, 26 Jan 2009 03:10:58 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:229638fb-eec5-4842-9d5c-b491eb00bdbe</guid><dc:creator>ImPer Westermark</dc:creator><description>&lt;p&gt;&lt;p&gt;
Maybe the application is reinitializing the clock just when the
timer passes its &amp;quot;exact match&amp;quot;, resulting in the match to be
lost.&lt;/p&gt;

&lt;p&gt;
Then, you maybe have to wait for a full 2^32 ticks until the timer
once more reaches the match condition until the application sees the
first match interrupt.&lt;/p&gt;

&lt;p&gt;
Interrupt handover of a enabled device between a boot loader and
an application is really problematic and very much chip-specific.&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>