<?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>BLE DFU the devices with SDK17.1 based firmware with NCS based firmware</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/105412/ble-dfu-the-devices-with-sdk17-1-based-firmware-with-ncs-based-firmware</link><description>Hi, We have some devices in field on which we have firmware which is developed using the nrf SDK17.1 now as the SDK 17.1 is End of Life, so we tried to switch the SDK . Now we are developing on the NCS. One issue is that for the field devices, Can we</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 07 Nov 2023 11:15:08 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/105412/ble-dfu-the-devices-with-sdk17-1-based-firmware-with-ncs-based-firmware" /><item><title>RE: BLE DFU the devices with SDK17.1 based firmware with NCS based firmware</title><link>https://devzone.nordicsemi.com/thread/454417?ContentTypeID=1</link><pubDate>Tue, 07 Nov 2023 11:15:08 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:17361e8e-e1cf-40e7-bb57-2ee7ec47534b</guid><dc:creator>Sarvesh</dc:creator><description>&lt;p&gt;Thanks Hung Bui, Let me check it once&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE DFU the devices with SDK17.1 based firmware with NCS based firmware</title><link>https://devzone.nordicsemi.com/thread/454391?ContentTypeID=1</link><pubDate>Tue, 07 Nov 2023 10:12:19 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8e7c08f4-28d8-4ba5-9b71-d9d83745f389</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi Sarvesh,&amp;nbsp;&lt;br /&gt;I would suggest to take a look at this ticket:&amp;nbsp;&lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/92774/hang-with-nrf5-sdk-17-1-0-bootloader-and-nrf-connect-sdk-2-1-0-application/390460"&gt;RE: Hang with nRF5 SDK 17.1.0 Bootloader and nRF Connect SDK 2.1.0 application&lt;/a&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Vidar proposed a solution to update from nRF5 SDK to nRF Connect SDK.&lt;/p&gt;
&lt;p&gt;Please be aware that you will need to modify the start address of the application so that it will start after the MBR (0x1000). Also the location of the MCUBoot is changed to the same location where the current bootloader is located.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>