<?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>Must the Soft Device be upgraded if the SDK is upgraded?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/80588/must-the-soft-device-be-upgraded-if-the-sdk-is-upgraded</link><description>With rev 3 of the nRF52840 I am looking at upgrading the SDK from 16.0.0 to 17.1.0 on my current project. 
 I have product in the field based on SDK 16.0.0 with Soft Device 7.0.1. 
 After reviewing the Soft Device and SDK release notes I&amp;#39;m left with one</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 20 Oct 2021 10:46:36 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/80588/must-the-soft-device-be-upgraded-if-the-sdk-is-upgraded" /><item><title>RE: Must the Soft Device be upgraded if the SDK is upgraded?</title><link>https://devzone.nordicsemi.com/thread/335049?ContentTypeID=1</link><pubDate>Wed, 20 Oct 2021 10:46:36 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d79e0e12-7a17-463e-8634-d2290ee507d7</guid><dc:creator>tesc</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;If you go for full SDK upgrade:&lt;br /&gt;SoftDevice s140 v7.2.0 (SDK 17) is binary compatible with s140 v7.0.1 (SDK 16). This means you can still use the same SoftDevice. See the migration document for s140 for details on what API functionality was added for v7.2.0, in the &amp;lt;nRF5 SDK v17 folder&amp;gt;\components\softdevice\s140\doc folder.&lt;/p&gt;
&lt;p&gt;If you go for only MDK upgrade:&lt;br /&gt;GCC is probably the one where it is the easiest to upgrade to a new MDK (still sticking to the same SDK version.) Get the new MDK release from our &lt;a href="https://www.nordicsemi.com/Products/Development-tools/nRF-MDK/Download#infotabs"&gt;nRF MDK download page&lt;/a&gt;, and use the files from the zip archive to replace the files distributed with the SDK in the &amp;lt;sdk folder&amp;gt;/modules/nrfx/mdk folder. If the set of c files in the MDK has changed, you may need to add additional c files to the project.&lt;/p&gt;
&lt;p&gt;Regards,&lt;br /&gt;Terje&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Must the Soft Device be upgraded if the SDK is upgraded?</title><link>https://devzone.nordicsemi.com/thread/333999?ContentTypeID=1</link><pubDate>Wed, 13 Oct 2021 15:58:58 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:006a86fb-21f5-401f-b829-c025763a9d5f</guid><dc:creator>Andrew</dc:creator><description>&lt;p&gt;I&amp;#39;m using the arm gcc toolchain. I&amp;#39;ve moved over to using VSCode and Meson/ninja for IDE and build system. I used the provided Make system as the reference when doing this.&lt;/p&gt;
&lt;p&gt;My main driver behind moving to SDK 17 is partly to support the coming rev 3 hardware, but also to be on the same SDK that is being maintained by Nordic. It&amp;#39;s pretty clear that nRF Connect SDK is where the main development is and the nRF5 SDK is in maintenance.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Must the Soft Device be upgraded if the SDK is upgraded?</title><link>https://devzone.nordicsemi.com/thread/333957?ContentTypeID=1</link><pubDate>Wed, 13 Oct 2021 13:12:13 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a944bd58-05b5-4cd6-8123-5a073ca432b6</guid><dc:creator>tesc</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;You don&amp;#39;t need to upgrade to a new SDK version in order to support the new rev 3 devices, it is enough to upgrade the MDK (delivered with the SDK, at &amp;lt;sdk root&amp;gt;/modules/nrfx/mdk). The way to do so depend on toolchain. What IDE/toolchain are you using?&lt;/p&gt;
&lt;p&gt;If you need other functionality from a later SDK version, upgrading to SDK 17.1.0 is of course also good. For that version of the SDK, the included MDK also supports the rev 3 devices. Since the SoftDevice is on the same major revision, it should be compatible, yes, if only using the old features. See release notes and migration document in e.g. &amp;lt;sdk root&amp;gt;/components/softdevice/s140/doc/ for the specific details. However if the sole purpose is to rebuild the application to be compatible with the new SoC revision then only upgrading MDK might be the better option.&lt;/p&gt;
&lt;p&gt;Regards,&lt;br /&gt;Terje&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>