<?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>UICR.BOOTLOADERADDR writing specifics</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/38625/uicr-bootloaderaddr-writing-specifics</link><description>Hi, 
 SDK documentation says &amp;quot;You cannot write to UICR.BOOTLOADERADDR when using the default J-Link target driver in IAR&amp;quot;. Some threads suggested it is only nRF51 issue, but in my experience this is true for nRF52840 - J-Link &amp;quot;write&amp;quot; to address 0x10001014</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 20 Sep 2018 05:16:28 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/38625/uicr-bootloaderaddr-writing-specifics" /><item><title>RE: UICR.BOOTLOADERADDR writing specifics</title><link>https://devzone.nordicsemi.com/thread/149536?ContentTypeID=1</link><pubDate>Thu, 20 Sep 2018 05:16:28 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c166e9fe-6ca8-408d-874e-85a8bdaa4a62</guid><dc:creator>Elkana</dc:creator><description>&lt;p&gt;Currently PE-Micro doesn&amp;#39;t support NRF52840 at all (not to mention UICR). &lt;br /&gt;Please forward it to the relevant team in NordicSemi.&lt;/p&gt;
&lt;p&gt;&lt;a href="http://www.pemicro.com/arm/device_support/NordicSemi_nRF52/nRF52/index.cfm"&gt;www.pemicro.com/.../index.cfm&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: UICR.BOOTLOADERADDR writing specifics</title><link>https://devzone.nordicsemi.com/thread/149535?ContentTypeID=1</link><pubDate>Thu, 20 Sep 2018 05:07:18 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e2bbba83-c1af-4062-a906-3c31148a3635</guid><dc:creator>Elkana</dc:creator><description>&lt;p&gt;In this case, Nordic can write a new flash loader (or board descriptor) to allow IAR writing to these addresses.&lt;br /&gt;&lt;br /&gt;You can have a look in&amp;nbsp;&lt;a href="http://supp.iar.com/FilesPublic/UPDINFO/004916/arm/doc/FlashLoaderGuide.pdf"&gt;http://supp.iar.com/FilesPublic/UPDINFO/004916/arm/doc/FlashLoaderGuide.pdf&lt;/a&gt;.&lt;br /&gt;On page 13 there is an example how to define more than 1 flash address spaces.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: UICR.BOOTLOADERADDR writing specifics</title><link>https://devzone.nordicsemi.com/thread/149216?ContentTypeID=1</link><pubDate>Tue, 18 Sep 2018 12:00:40 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e00e126d-90c0-4002-aee7-e95ca79f00cc</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;Hi&amp;nbsp;&lt;span&gt;Elkana,&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;a) The root cause of this issue is that the flash algorithm in IAR does not know that the UICR address range is flash memory, therefore it will not write to it.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;b) I do not have any experience with the&amp;nbsp;PE Micro Cyclone Pro, but I would expect that if it does not work out of the box there should be some way to configure it so that it will be able to program flash in the UICR memory range as well.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;c) It is just a matter of configuring the tools properly. The UICR is just normal flash, but you need to tell it to the programming tool.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Best regards,&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Einar&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>