<?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>Seconds Auxiliary Interrupt</title><link>https://community.arm.com/developer/tools-software/tools/f/keil-forum/23627/seconds-auxiliary-interrupt</link><description> 
I have set my system timers to generate interrupts at 10Hz (MSINT)
and 1HZ (SECINT). The millisecond interrupt is triggered immediately
after reset but the seconds interrupt takes some time before it
starts to trigger (about 15s). After that it triggers</description><dc:language>en-US</dc:language><generator>Telligent Community 10</generator><item><title>RE: Seconds Auxiliary Interrupt</title><link>https://community.arm.com/thread/100472?ContentTypeID=1</link><pubDate>Mon, 07 Apr 2008 14:31:24 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:48481c34-bc81-4507-96e8-85ad4d254630</guid><dc:creator>ImPer Westermark</dc:creator><description>&lt;p&gt;&lt;p&gt;
This isn&amp;#39;t a chip I have worked with.&lt;/p&gt;

&lt;p&gt;
However, a common way for a timer to generate an interrupt is by
having a timer match register. If the timer counter is _exactly_ the
value of the match register, the timer may (depending on
configuration) generate an interrupt, and/or reset the counter (for
repetitive use) and/or just stop the counter.&lt;/p&gt;

&lt;p&gt;
If you have a 32-bit counter configured in a way that the match
register will match and auto-reset at a low value, you could manage
to configure the timer so that the counter value has already passed
the match value when you program the timer.&lt;/p&gt;

&lt;p&gt;
In that case, you will have to wait the full 32-bit counting range
until it turns around before the match register gets a second chance.
If implementing the same thing in software, delays are normally
implemented with a &amp;gt;= test, to maximize the &amp;quot;self-healing&amp;quot; of the
software. If you have a timer with exact-match, there will not be any
such self-healing and depending on prescaler settings, it could take
a very, very long time until an overflow happens and the timer starts
to tick with the normal time intervals.&lt;/p&gt;

&lt;p&gt;
Are you sure that both timers are stopped (and in a reset
condition) before you start them?&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Seconds Auxiliary Interrupt</title><link>https://community.arm.com/thread/76161?ContentTypeID=1</link><pubDate>Mon, 07 Apr 2008 11:07:03 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:34ebcb37-215d-488e-a958-59b4cee35855</guid><dc:creator>Paul Marley</dc:creator><description>&lt;p&gt;&lt;p&gt;
TI&amp;#39;s MSC1210Y5&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Seconds Auxiliary Interrupt</title><link>https://community.arm.com/thread/49665?ContentTypeID=1</link><pubDate>Mon, 07 Apr 2008 11:03:13 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:af103dea-5b3e-4b75-be81-fc312af43919</guid><dc:creator>Neil Kurzmam</dc:creator><description>&lt;p&gt;&lt;p&gt;
What chip?&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>