https://devzone.nordicsemi.com/f/nordic-q-a/103989/update-to-4-2-0-versionHi Nordic team, I am using VS code and I upgraded from 2.4.1 to 2.4.2 (SDK version). Now I have a problem with my debugging process, but &quot;build&quot; and &quot;flash&quot; are working correctly. Could you help me with some advice? It sends me to the &quot;cpu_idle.Sen-USTelligent Community 13Fri, 22 Sep 2023 00:11:41 GMThttps://devzone.nordicsemi.com/thread/447167?ContentTypeID=1Fri, 22 Sep 2023 00:11:41 GMT137ad170-7792-4731-bb38-c0d22fbe4515:265b0aa6-29d1-433b-b6c4-251eec2482b1Raoul<p>Hi Tania!</p> <p>I don&#39;t think that this is due to any update to the SDK (but I might be wrong), but perhaps an update to our <a href="https://nrfconnect.github.io/vscode-nrf-connect/index.html">VS Code Extension</a>.</p> <p>In any case, you can always decide where the debugger stops by setting breakpoints. See the VS Code docs on this: <a href="https://code.visualstudio.com/docs/editor/debugging#_breakpoints">https://code.visualstudio.com/docs/editor/debugging#_breakpoints</a></p> <p>Wherever you place a breakpoint, an instruction will be added such that the debugger stops there and waits for your input. So you could place one at the start of main(), or wherever you like within main().</p> <p>Best regards,</p> <p>Raoul</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/446959?ContentTypeID=1Wed, 20 Sep 2023 23:53:55 GMT137ad170-7792-4731-bb38-c0d22fbe4515:750a4388-8e87-4e04-a7e0-9d0b73855679Tania V<p>Sorry, from 2.4.1 to 2.4.2</p><div style="clear:both;"></div>