<?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>Migrating from nRF5 SDK 17.1 to nRF Connect SDK while preserving FDS data (nRF52832 / nRF52833, 512 KB flash)</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/128139/migrating-from-nrf5-sdk-17-1-to-nrf-connect-sdk-while-preserving-fds-data-nrf52832-nrf52833-512-kb-flash</link><description>I recently completed a field-upgrade path from an nRF5 SDK 17.1 application (with the legacy Secure DFU bootloader) to a fresh NCS-based firmware stack, while preserving user data stored in FDS. It was easier than expected, so sharing the approach here</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 14 Nov 2017 10:43:53 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/128139/migrating-from-nrf5-sdk-17-1-to-nrf-connect-sdk-while-preserving-fds-data-nrf52832-nrf52833-512-kb-flash" /></channel></rss>