<?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>Bootloader DFU SDK11 to SDK12</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/17218/bootloader-dfu-sdk11-to-sdk12</link><description>Hi 
 I&amp;#39;m upgrading from SDK11 to SDK12 on the nrf52 and part of that is the secure bootloader. I&amp;#39;ve created a new bootloader and have this working with the new softdevice (s132 3.0.0). 
 Now, updating devices with the old SDK11 bootloader are a problem</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Sun, 19 May 2019 09:30:10 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/17218/bootloader-dfu-sdk11-to-sdk12" /><item><title>RE: Bootloader DFU SDK11 to SDK12</title><link>https://devzone.nordicsemi.com/thread/187741?ContentTypeID=1</link><pubDate>Sun, 19 May 2019 09:30:10 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b87a8a14-411f-48b9-b19c-4456e13baf59</guid><dc:creator>Corey</dc:creator><description>&lt;p&gt;The link is invalid.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Bootloader DFU SDK11 to SDK12</title><link>https://devzone.nordicsemi.com/thread/66150?ContentTypeID=1</link><pubDate>Thu, 06 Jul 2017 07:09:27 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d502eabb-07af-4d95-8cd2-f412b37c1005</guid><dc:creator>sosse</dc:creator><description>&lt;p&gt;Here is much simple way to secure your bootloader without changing ROM/RAM size. It works on nrf51822 with 16k RAM. Very lightweight (compare nordic provided one based on ECC).
Here is link. &lt;a href="https://github.com/CHAKAK/bootloader_secure_custom"&gt;https://github.com/CHAKAK/bootloader_secure_custom&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Bootloader DFU SDK11 to SDK12</title><link>https://devzone.nordicsemi.com/thread/66149?ContentTypeID=1</link><pubDate>Mon, 03 Apr 2017 11:39:00 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:de79d3cb-cfd9-454b-b810-21dab952f7b2</guid><dc:creator>Raj</dc:creator><description>&lt;p&gt;@Bjørn Spockeli: I created new question and the link is &lt;a href="https://devzone.nordicsemi.com/question/125639/update-from-sdk1100-to-sdk1202-through-dfu/"&gt;devzone.nordicsemi.com/.../&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Bootloader DFU SDK11 to SDK12</title><link>https://devzone.nordicsemi.com/thread/66148?ContentTypeID=1</link><pubDate>Mon, 03 Apr 2017 11:30:47 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5e69e498-1a65-4e1d-ae87-1272d1781ea2</guid><dc:creator>bjorn-spockeli</dc:creator><description>&lt;p&gt;Ok, I have made a bootloader based on SDK v11.0.0 thats compatible with both v1.0.0 and v2.0.x.  Could you create a new question with your first comment as the question and post the link here? Then I will answer that question and attach the bootloader project.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Bootloader DFU SDK11 to SDK12</title><link>https://devzone.nordicsemi.com/thread/66147?ContentTypeID=1</link><pubDate>Mon, 03 Apr 2017 10:49:47 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ccd4deac-9738-419a-ad59-f03f1ddd1f9a</guid><dc:creator>Raj</dc:creator><description>&lt;p&gt;Bjørn Spockeli: I shifted SDK12.0.0 secure bootloader start address to 0x39c00 same as start address of singing bootloader in SDk11.0.0.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Bootloader DFU SDK11 to SDK12</title><link>https://devzone.nordicsemi.com/thread/66146?ContentTypeID=1</link><pubDate>Mon, 03 Apr 2017 10:32:00 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:79668712-758f-4642-93c8-06dc41fc1802</guid><dc:creator>bjorn-spockeli</dc:creator><description>&lt;p&gt;@RajKumar: Ok, the solution above is only possible if you have allocated 24kb to the bootloader from SDK v11.0.0 when it was flashed to the nRF51822. If not, then its not possible update the bootloader start address without re-flashing the chip using a programmer.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Bootloader DFU SDK11 to SDK12</title><link>https://devzone.nordicsemi.com/thread/66145?ContentTypeID=1</link><pubDate>Mon, 03 Apr 2017 10:11:56 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e00fad43-2eb2-4a58-a5af-c185e5b42691</guid><dc:creator>Raj</dc:creator><description>&lt;p&gt;@Bjørn Spockel:we are using nRF51822 with s130v2.0.0 with SDK11.0.0 and want to update to s130 v2.0.1&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Bootloader DFU SDK11 to SDK12</title><link>https://devzone.nordicsemi.com/thread/66144?ContentTypeID=1</link><pubDate>Mon, 03 Apr 2017 09:39:21 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3987b060-1740-4f61-a58c-54ef6d442bec</guid><dc:creator>bjorn-spockeli</dc:creator><description>&lt;p&gt;@Rajkumar: We have shrunk the size of the secure bootloader as much as possible and I do not recommend trying to reduce the size of the secure bootloader further. My suggestion would be to do the updates separately,i.e. bootloader first and then SoftDevice, by creating a bootloader that is compatible with both the SoftDevice versions used by SDK v11.0.0 and SDK v12.2.0. I assume that you&amp;#39;re using the nRF51822 with S130 v1.0.0 with SDK v11.0.0 and want to update to S130 v2.0.1?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Bootloader DFU SDK11 to SDK12</title><link>https://devzone.nordicsemi.com/thread/66143?ContentTypeID=1</link><pubDate>Fri, 31 Mar 2017 13:35:05 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e3cd5c60-c5ec-45c1-8479-4100101c90dd</guid><dc:creator>Raj</dc:creator><description>&lt;p&gt;Hi Bjorn, we have custom boards with sdk11 already sold out now we need to update those boards from sdk11 to sdk12.2. so we are planing to update sd+bl image. The present sdk11 firmwares have app preserve data of 3 code pages i.e(0xc00) finally we have bank0+bank1 size is 120kb but when we create a zip file sdk12.2+secure_bootloader almost the size is 123kb. Is their any possibility to reduce the code size of secure bootloader.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Bootloader DFU SDK11 to SDK12</title><link>https://devzone.nordicsemi.com/thread/66142?ContentTypeID=1</link><pubDate>Fri, 28 Oct 2016 13:14:08 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3ae600b9-a33b-4b92-a30c-b3d2865bd177</guid><dc:creator>bjorn-spockeli</dc:creator><description>&lt;p&gt;As you correctly stated, we introduced a new secure bootloader in SDK v12.0.0 which allow you to sign the firmware images. However, this bootloader is considerably larger[~24kB) compared to the legacy bootloader(~15kB), which means that it is not possible to update from the legacy to the secure bootloader unless the size bootloader region was initially set to 24kB. This is becaue the bootloader address that is stored in a UICR register. The register cannot be rewritten without erasing all the other UICR registers on the device.&lt;/p&gt;
&lt;p&gt;Best regards&lt;/p&gt;
&lt;p&gt;Bjørn&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>