<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/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/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Is UICR really a full 1K flash page?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/4177/is-uicr-really-a-full-1k-flash-page</link><description>I&amp;#39;m putting some bootloader and static config data in the customer section of the UICR and I accidentally wrote to 0x1001200 and worked just fine. 
 Looking closer, it seems that UICR is actually a full 1K flash page, even though the reference manual</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 23 Oct 2014 20:20:40 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/4177/is-uicr-really-a-full-1k-flash-page" /><item><title>RE: Is UICR really a full 1K flash page?</title><link>https://devzone.nordicsemi.com/thread/14941?ContentTypeID=1</link><pubDate>Thu, 23 Oct 2014 20:20:40 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1e904e8d-5e6d-4326-b1fb-3486eb264601</guid><dc:creator>Clem Taylor</dc:creator><description>&lt;p&gt;I am only looking to store manufacturing time data. My question was if it is safe to use the full 1k and if so why does the reference manual only mention the first 256 bytes. I can really use the extra bytes, but don&amp;#39;t want to risk manfacture yield as a result.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Is UICR really a full 1K flash page?</title><link>https://devzone.nordicsemi.com/thread/14939?ContentTypeID=1</link><pubDate>Thu, 23 Oct 2014 20:07:24 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:13be0120-e16d-4330-9dac-fab6f539b492</guid><dc:creator>Clem Taylor</dc:creator><description>&lt;p&gt;Yes, the data survived a power cycle. I have not tested the full 1k range, but if to look at that region in gdb the 0xffffffffs stop after 1k.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Is UICR really a full 1K flash page?</title><link>https://devzone.nordicsemi.com/thread/14940?ContentTypeID=1</link><pubDate>Thu, 23 Oct 2014 13:06:01 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7c4f3424-e656-46e2-9e5a-247fd9b6501b</guid><dc:creator>Stefan Birnir Sverrisson</dc:creator><description>&lt;p&gt;Hi&lt;/p&gt;
&lt;p&gt;The UICR is somewhat special and does not behave as a normal flash page. You can only erase it with two commands (see nRF51 Series reference manual v2.1, NVMC chapter), nrfjprog --eraseall, which erases the UICR and the whole 256kB flash area (softdevice, application and bootloader), or with the command nrfjprog --eraseuicr, which will erase the UICR and code region 1, which is the application and the bootloader, so it is normally not convenient to use as you can not erase it unless erasing everything else.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Is UICR really a full 1K flash page?</title><link>https://devzone.nordicsemi.com/thread/14938?ContentTypeID=1</link><pubDate>Wed, 22 Oct 2014 11:01:04 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:54ea59f7-eb34-464f-ad59-49d25c71dca5</guid><dc:creator>azdem</dc:creator><description>&lt;p&gt;Have you checked whether it is really written to 0x1001200?
If some of the address bits are &amp;quot;don&amp;#39;t care&amp;quot;, it may be written to (and read from) 0x1001000 indeed...&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>