VScode Debug with Ozone path issuehttps://devzone.nordicsemi.com/f/nordic-q-a/96460/vscode-debug-with-ozone-path-issuehello I am now checking nrf connect SDK, nrf5340 DK&#39;s basic operation in VScode IDE environment. A problem occurred while checking the operation of the DK board by calling the following example. &quot;C:\ncs\v2.2.99-dev3\nrf\samples\bluetooth\peripheral_uarten-USTelligent Community 13Mon, 13 Feb 2023 06:40:16 GMTRE: VScode Debug with Ozone path issuehttps://devzone.nordicsemi.com/thread/409484?ContentTypeID=1Mon, 13 Feb 2023 06:40:16 GMT137ad170-7792-4731-bb38-c0d22fbe4515:6c49e62a-1c59-477d-a0d5-2b7c89d711adJohn Lee<p>hi</p> <p>reinstalling all configurations fixed the problem<br />thank you</p><div style="clear:both;"></div>RE: VScode Debug with Ozone path issuehttps://devzone.nordicsemi.com/thread/409388?ContentTypeID=1Fri, 10 Feb 2023 14:44:49 GMT137ad170-7792-4731-bb38-c0d22fbe4515:3a19d037-3dd6-41a4-a9c9-2979ac113215&#216;ivind<p>Hi,</p> <p>I will see if I can replicate this and get back to you.</p> <p>It works properly in v2.2.0?</p> <p>Did you install the toolchain through the Toolchain Manager? If yes, have you tried closing VSCode, opening the command line from the Toolchain Manager and running &quot;west update&quot;?</p><div style="clear:both;"></div>