<?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>Problem upgrading from NCS 2.1.0 to 2.3.0</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/102047/problem-upgrading-from-ncs-2-1-0-to-2-3-0</link><description>Having attempted to compile the BME688 sample from HomeSmartMesh/sdk-hsm-thingy53 for our custom nRF9160 board, it failed to compile for us as it uses the SENSOR_DEVICE_DT_INST_DEFINE macro, which as it turns out, was introduced in Zephyr version 3.3</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 20 Jul 2023 16:21:17 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/102047/problem-upgrading-from-ncs-2-1-0-to-2-3-0" /><item><title>RE: Problem upgrading from NCS 2.1.0 to 2.3.0</title><link>https://devzone.nordicsemi.com/thread/437531?ContentTypeID=1</link><pubDate>Thu, 20 Jul 2023 16:21:17 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:35e2f385-3f0c-44ce-b258-280ab22a12f9</guid><dc:creator>Raoul</dc:creator><description>&lt;p&gt;Hi aejoe,&lt;/p&gt;
&lt;p&gt;If I&amp;#39;ve understood you correctly, your original installation was a manual installation, correct? If so, please try the following: &lt;a href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/releases_and_maturity/developing/managing_code.html#updating-a-copy-of-the-ncs"&gt;Updating a copy of the nRF Connect SDK&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;The central difference is that you must run west update from &lt;code&gt;ncs/nrf&lt;/code&gt; (but please read the entire section).&lt;/p&gt;
&lt;p&gt;If you&amp;#39;ve always had an automatic install via the Toolchain Manager, updating should have been smooth and left in a separate directory per NCS version. If something is broken, I would recommend just removing the directory for that NCS version, and updating again.&lt;/p&gt;
&lt;p&gt;Good luck!&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Raoul&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Problem upgrading from NCS 2.1.0 to 2.3.0</title><link>https://devzone.nordicsemi.com/thread/437341?ContentTypeID=1</link><pubDate>Wed, 19 Jul 2023 15:30:40 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e1ea8689-7503-4204-890f-b889a39b2802</guid><dc:creator>aejoe</dc:creator><description>&lt;p&gt;Edit: the last ~ncs folder contents in my initial post were incorrect.&amp;nbsp; Here&amp;#39;s how it actually looks:&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;$ ls *
downloads:
ncs-toolchain-linux-x86_64-v2.3.0-20230302T121949-75e5684.tar.gz

toolchains:
v2.3.0

v2.3.0:&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;where the ~/ncs/v2.3.0 folder is the empty directory with just a single hidden empty `.west` directory in there.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>