<?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>An_138: what directive(s) are needed?</title><link>https://community.arm.com/developer/tools-software/tools/f/keil-forum/14894/an_138-what-directive-s-are-needed</link><description> I ported a sector erase (in C) from 1.31 to uVision 2.20a using ap note 138 (etc.). (C161O, flash 0x0 - 0x3FFFF, ram 0x80000-0x8FFFF; 16 MHz.) 
 
After entering main() and before enabling interrupts, we erase a sector and then continue with initialization</description><dc:language>en-US</dc:language><generator>Telligent Community 10</generator><item><title>RE: An_138: what directive(s) are needed?</title><link>https://community.arm.com/thread/50120?ContentTypeID=1</link><pubDate>Wed, 20 Feb 2002 08:53:31 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:b0e764c3-0ab3-4d7a-8ad8-01794a2a8ff0</guid><dc:creator>Scott deWolski</dc:creator><description>&lt;p&gt;The program I wrote using App138 worked fine using default settings.  However, the actual erase/programming modules were written in assembly to avoid having &amp;#39;C&amp;#39; casts and promotions, which the compiler does using functions sometimes (these functions will not be in the relocated code space and may be in the flash being erased/programmed).  DPP usage for nconst is also an issue.  See thread;&lt;br /&gt;
&lt;a href="http://www.keil.com/forum/docs/thread1239.asp"&gt;http://www.keil.com/forum/msgpage.asp?MsgID=4783&lt;/a&gt;&lt;br /&gt;
Best luck&lt;br /&gt;
Scott&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: An_138: what directive(s) are needed?</title><link>https://community.arm.com/thread/38412?ContentTypeID=1</link><pubDate>Tue, 19 Feb 2002 13:13:35 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:159ca71e-433c-408c-8319-125b102688f6</guid><dc:creator>Mik Kleshov</dc:creator><description>&lt;p&gt;It seems that you can&amp;#39;t debug your application using Monitor166. That&amp;#39;s very unfortunate. If there is a display in your target hardware you can print some diagnostic messages to find out at which point exactly the program crashes.&lt;br /&gt;
- Mike&lt;br /&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>