<?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>ULINK: Programming devices with write protection</title><link>https://community.arm.com/developer/tools-software/tools/f/keil-forum/26279/ulink-programming-devices-with-write-protection</link><description> 
I have a hex file that contains a bootloader and an application
image along with flash option data to write protect the bootloader.
In order to be able to program the write protection I have added the
&amp;quot;STM32F10x Flash Options&amp;quot; programming algorithm</description><dc:language>en-US</dc:language><generator>Telligent Community 10</generator><item><title>RE: ULINK: Programming devices with write protection</title><link>https://community.arm.com/thread/58963?ContentTypeID=1</link><pubDate>Thu, 09 Dec 2010 07:02:16 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:c6214ddc-1002-4013-b1f8-3f3ee51fea61</guid><dc:creator>Michael RigbyJones</dc:creator><description>&lt;p&gt;&lt;p&gt;
Forgot to add - if the two project solution really is the only way
to go, how do I stop the &amp;quot;Erase failed&amp;quot; dialog box popping up during
the first chip erase operation?&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>