<?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>processor busy after erase command</title><link>https://community.arm.com/developer/tools-software/tools/f/keil-forum/37851/processor-busy-after-erase-command</link><description> 
Hello 

 
in our sistem we have the necessity to refresh an external
Watchdog-Chip, by toggling one OUTPUT-PORT each 160ms. 
Unfortunately, that must occours also during flash-erasing (...) 
Well, our bootstrap code makes a copy of both Erase AND
Watchdog</description><dc:language>en-US</dc:language><generator>Telligent Community 10</generator><item><title>RE: processor busy after erase command</title><link>https://community.arm.com/thread/135385?ContentTypeID=1</link><pubDate>Wed, 28 May 2008 18:42:28 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:a1db7ba5-668a-443b-ad09-d2117e94a091</guid><dc:creator>Chris Wunderlich</dc:creator><description>&lt;p&gt;&lt;p&gt;
Yes&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: processor busy after erase command</title><link>https://community.arm.com/thread/124700?ContentTypeID=1</link><pubDate>Wed, 28 May 2008 05:22:00 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:d73be465-5b75-4426-b315-a991b43fdefb</guid><dc:creator>Federico Buganza</dc:creator><description>&lt;p&gt;&lt;p&gt;
I can re-formulate the question in this way:&lt;br /&gt;
during flash-erasing, is the CPU able to excute other commands
fething from PSRAM ?&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: processor busy after erase command</title><link>https://community.arm.com/thread/113972?ContentTypeID=1</link><pubDate>Wed, 28 May 2008 04:52:35 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:ce97cd6c-e867-48a7-850c-19f2caaa826a</guid><dc:creator>ImPer Westermark</dc:creator><description>&lt;p&gt;&lt;p&gt;
&amp;quot;Well, our bootstrap code makes a copy of both Erase AND
Watchdog-Manager code into PSRAM.&amp;quot;&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: processor busy after erase command</title><link>https://community.arm.com/thread/100692?ContentTypeID=1</link><pubDate>Wed, 28 May 2008 04:43:24 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:2d47fb94-c56f-470f-aca7-a2bb7e081c20</guid><dc:creator>Chris Wunderlich</dc:creator><description>&lt;p&gt;&lt;p&gt;
Where is the code to erase the flash located? If it is in the
flash (and not the sector you are erasing) then you are stalled until
this is finished as the manual states. If you need to service the WDT
while erasing the internal flash then I would think you need to
execute the erase command sequence from PSRAM or external memory.&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: processor busy after erase command</title><link>https://community.arm.com/thread/76336?ContentTypeID=1</link><pubDate>Wed, 28 May 2008 03:12:22 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:b7da7ba0-9adc-4512-91e3-c2d98d5a1d64</guid><dc:creator>Federico Buganza</dc:creator><description>&lt;p&gt;&lt;p&gt;
Hallo,&lt;/p&gt;

&lt;p&gt;
very quick!&lt;br /&gt;
yes,all interrupts are disabled using&lt;/p&gt;

&lt;p&gt;
PSW_IEN = 0;&lt;/p&gt;

&lt;p&gt;
We did not relocated the ISR table.&lt;/p&gt;

&lt;p&gt;
Maybe is the Flash-erase state machine allocated in flash as
well?&lt;/p&gt;

&lt;p&gt;
Federico&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: processor busy after erase command</title><link>https://community.arm.com/thread/51798?ContentTypeID=1</link><pubDate>Wed, 28 May 2008 03:06:47 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:ac9a5932-1f68-4444-858f-71c2976ab1a1</guid><dc:creator>ImPer Westermark</dc:creator><description>&lt;p&gt;&lt;p&gt;
Are all other interrupts disabled?&lt;/p&gt;

&lt;p&gt;
Have you relocated the interrupt table from flash to RAM?&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>