<?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>Fill of flash memory during reprogram UVision 3</title><link>https://community.arm.com/developer/tools-software/tools/f/keil-forum/21581/fill-of-flash-memory-during-reprogram-uvision-3</link><description> 
Hello, 

 
I&amp;#39;ve got some code that saves setup information to flash if the
user wants. I save a code to a memory location to let the software
know that whether setup information is available or not. If not, I
use defaults. 

 
Is there some way on the</description><dc:language>en-US</dc:language><generator>Telligent Community 10</generator><item><title>RE: Fill of flash memory during reprogram UVision 3</title><link>https://community.arm.com/thread/123782?ContentTypeID=1</link><pubDate>Fri, 20 Apr 2007 13:52:41 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:f6645f7a-3400-47eb-aac9-a1a752acfc70</guid><dc:creator>HansBernhard Broeker</dc:creator><description>&lt;p&gt;&lt;p&gt;
Any programmer software worth its salt will have a &amp;quot;full job&amp;quot; kind
of button, which runs a complete sequence of erase, blank-check,
reprogram, and possibly a verify. Use it.&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Fill of flash memory during reprogram UVision 3</title><link>https://community.arm.com/thread/112815?ContentTypeID=1</link><pubDate>Thu, 19 Apr 2007 17:03:34 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:835462de-e54c-41be-b0c7-a1e3d9a7892f</guid><dc:creator>Matthew Ryan</dc:creator><description>&lt;p&gt;&lt;p&gt;
Agreed. I have a manual erase, was looking for a button that
automatically linked it to the download. I like your idea of the ASM
code however.&lt;/p&gt;

&lt;p&gt;
Thanks,&lt;br /&gt;
Matt&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Fill of flash memory during reprogram UVision 3</title><link>https://community.arm.com/thread/99130?ContentTypeID=1</link><pubDate>Thu, 19 Apr 2007 16:56:24 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:50570f99-a200-4d20-a592-030e30998c95</guid><dc:creator>HansBernhard Broeker</dc:creator><description>&lt;p&gt;&lt;p&gt;
Wouldn&amp;#39;t your flash programming kit&amp;#39;s &amp;quot;erase device&amp;quot; handle that
already?&lt;/p&gt;

&lt;p&gt;
If you really need this, you can always write a little asm module
with a couple of&lt;/p&gt;

&lt;pre&gt;
       DB  0xff
&lt;/pre&gt;

&lt;p&gt;
at the address you want cleared, and link it with your
program.&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Fill of flash memory during reprogram UVision 3</title><link>https://community.arm.com/thread/75020?ContentTypeID=1</link><pubDate>Thu, 19 Apr 2007 11:24:29 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:5d8e7ae8-fee3-4635-b84b-5c14df2371b8</guid><dc:creator>Matthew Ryan</dc:creator><description>&lt;p&gt;&lt;p&gt;
Agreed on the checksums,etc.&lt;/p&gt;

&lt;p&gt;
The first time I get the chip, yes it&amp;#39;s blank / filled. But while
developing and burning new code (less than 8k of stuff, I&amp;#39;m storing
config up at 0x3FFF, so no worries about conflicts) then a saved
profile at 0x3FFF doesn&amp;#39;t get automatically cleared to 0xFF&amp;#39;s. So I
have to use a commmand to wipe that area, but I&amp;#39;d rather like to know
for sure that when I reprogram a chip that the configuration page
will be completely cleared (in case I forget).&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Fill of flash memory during reprogram UVision 3</title><link>https://community.arm.com/thread/50644?ContentTypeID=1</link><pubDate>Thu, 19 Apr 2007 11:15:47 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:ea4c4ca1-fcde-4902-a67d-d95ece0d9f44</guid><dc:creator>ImPer Westermark</dc:creator><description>&lt;p&gt;&lt;p&gt;
Isn&amp;#39;t your flash 0xff-filled when you receive the processor?&lt;/p&gt;

&lt;p&gt;
In that case, it should be enough to define a flag byte in the
data save area. As soon as you save configuration, you set this byte
to a value different from 0xff.&lt;/p&gt;

&lt;p&gt;
If it is dangerous for your application to run with incorrect
configuration, you should store a CRC32, MD5 or Adler-32 or similar
in the data save area, to allow you to check if the data is valid.
Avoid using a simple check-sum - they give too many false
matches!&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>