<?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>Problem Debugging when using Interrupts</title><link>https://community.arm.com/developer/tools-software/tools/f/keil-forum/38211/problem-debugging-when-using-interrupts</link><description> 
Hi 
I am using uVision 3 and i have written a source code to enable Timer
Counter 0 interrupt in at91sam7x256. 
My program compiles successfully and debugger starts well until TC0
interrupt occurs. It jumps suddenly to address 0x00000018 and so show</description><dc:language>en-US</dc:language><generator>Telligent Community 10</generator><item><title>RE: Problem Debugging when using Interrupts</title><link>https://community.arm.com/thread/55354?ContentTypeID=1</link><pubDate>Fri, 06 Feb 2009 03:59:05 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:21629c3d-fe4d-4996-a18e-57a24e53fe4b</guid><dc:creator>Tamir Michael</dc:creator><description>&lt;p&gt;&lt;p&gt;
your debugger is probably configured to load and execute the code
from RAM. but the vector table is inside internal flash...if you
remap your program to start at 0x0 - hence, remove ram.ini, remove
linker directive --entry from linker tab and adjust target window by
clicking on ROM1 checkbox and filling in 0x0 as start point - you
should be alright. and, and advised already: read the manual of
everything: your chip, uv3, the whole smack. HOW can you complain
about famous error messages if you don&amp;#39;t even understand
them?!?!?!?!?!&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Problem Debugging when using Interrupts</title><link>https://community.arm.com/thread/89549?ContentTypeID=1</link><pubDate>Fri, 06 Feb 2009 03:55:32 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:aded1fc5-8fd5-4f7f-bbed-52eae965f78a</guid><dc:creator>Christoph Franck</dc:creator><description>&lt;p&gt;&lt;p&gt;
&lt;i&gt;Jumping to 0x00000018 is normal behavior during interrupt
handling for an AT91SAM7S,&lt;/i&gt;&lt;/p&gt;

&lt;p&gt;
(and for an AT91SAM7X, too, since it has the same AIC).&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Problem Debugging when using Interrupts</title><link>https://community.arm.com/thread/55355?ContentTypeID=1</link><pubDate>Fri, 06 Feb 2009 03:50:35 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:868ae2f3-7cf9-49f1-b7b7-24ec46c6c3f2</guid><dc:creator>Christoph Franck</dc:creator><description>&lt;p&gt;&lt;p&gt;
&lt;i&gt;Do you know why debugger jumps to 0x00000018 like this?&lt;/i&gt;&lt;/p&gt;

&lt;p&gt;
Yes. If you read the chapter in the &lt;b&gt;datasheet&lt;/b&gt; of the chip
about the AIC and interrupt handling in general, you will know why,
too. And you should definitely read this chapter &lt;b&gt;yourself&lt;/b&gt; if
you plan to use interrupts on this chip.&lt;/p&gt;

&lt;p&gt;
In short: Jumping to 0x00000018 is &lt;b&gt;normal behavior&lt;/b&gt; during
interrupt handling for an AT91SAM7S, and if this causes problems with
your program, then your program is at fault.&lt;/p&gt;

&lt;p&gt;
&lt;i&gt;How could I solve that?&lt;/i&gt;&lt;/p&gt;

&lt;p&gt;
You read the appropriate chapter in the &lt;b&gt;datasheet&lt;/b&gt; of the
chip and change your program accordingly. If _any_ interrupt occurs,
the uC will first jump to 0x00000018. The code that jumps to the
appropriate interrupt handler, or a more elaborate interrupt
vectoring mechanism, must be placed there. A detailed description can
be found, as already mentioned, in the datasheet.&lt;/p&gt;

&lt;p&gt;
If you have any questions after you have read the chapter, feel
free to ask them here.&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>