<?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>nRF5340DK - Building with VSCode</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/80167/nrf5340dk---building-with-vscode</link><description>Hello all, 
 I just found out that the nRF Connect extension for VSCode has been release, which is great news. Good job Nordic Team! I have followed the steps described in your article as well as in the Youtube tutorial and could successfully install</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 06 Oct 2021 08:35:45 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/80167/nrf5340dk---building-with-vscode" /><item><title>RE: nRF5340DK - Building with VSCode</title><link>https://devzone.nordicsemi.com/thread/332756?ContentTypeID=1</link><pubDate>Wed, 06 Oct 2021 08:35:45 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5a43b944-b361-46f8-bad5-ea849b3a6a39</guid><dc:creator>&amp;#216;ivind</dc:creator><description>&lt;p&gt;Update on the warnings disappearing:&lt;/p&gt;
&lt;p&gt;&amp;quot;It happens because the files with the warnings in doesn&amp;#39;t get re-compiled because they don&amp;#39;t have any changes. Ninja (and Make, and therefore CMake and West) only recompile files with changes, to speed up builds. But if the file doesn&amp;#39;t get recompiled, the compiler never sees the problem that generates the warning.&amp;quot;&lt;/p&gt;
&lt;p&gt;We appreciate the feedback, and this may be something we can improve the user experience on in a future update.&lt;/p&gt;
&lt;p&gt;The&amp;nbsp;flash and debug options disappearing is a known bug, and is something we are working to fix.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF5340DK - Building with VSCode</title><link>https://devzone.nordicsemi.com/thread/332232?ContentTypeID=1</link><pubDate>Sun, 03 Oct 2021 15:45:33 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1e7c5a9e-1abf-4948-95f6-03b7257d934d</guid><dc:creator>jbf12</dc:creator><description>&lt;p&gt;Hi &lt;span&gt;&lt;em&gt;&amp;Oslash;&lt;/em&gt;&lt;/span&gt;ivind,&lt;/p&gt;
&lt;p&gt;thanks for your answers. Looking forward to the feedback from your colleagues.&lt;/p&gt;
&lt;p&gt;If I may point out something else, I noticed that from time to time, some of the options from the Actions menu are missing after a pristine build. This happens randomly and not with a certain frequence.&lt;br /&gt;I did find a workaround : select another project from the Applications Menu (TestApp1) and the select again my project (TestApplication2). By doing so, all options are back in the Actions menu.&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;img src="https://devzone.nordicsemi.com/resized-image/__size/320x240/__key/communityserver-discussions-components-files/4/pastedimage1633275542667v1.png" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;Best regards.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF5340DK - Building with VSCode</title><link>https://devzone.nordicsemi.com/thread/332095?ContentTypeID=1</link><pubDate>Fri, 01 Oct 2021 09:36:14 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:65516399-339f-4e82-a916-973b451e06d8</guid><dc:creator>&amp;#216;ivind</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;1 &amp;amp; 2. These are because you set &amp;quot;Enable Debug Options&amp;quot; when creating the build configuration. You can make a new build configuration without that setting to get rid of them.&lt;/p&gt;
&lt;p&gt;3. A non-secure project consists of a non-secure image and a secure image, in this case the secure partition manager. The board is changed when building the secure image. This is intentional, and the application is still non-secure.&lt;/p&gt;
&lt;p&gt;4. I have passed this feedback along to the developers. I will update you when they respond.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>