<?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>nRF Connect SDK Inetermediate course - lesson 1 ex 1 - debug warnings and breakpoint issues</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/126897/nrf-connect-sdk-inetermediate-course---lesson-1-ex-1---debug-warnings-and-breakpoint-issues</link><description>Working the SDK intermediate course, L1.E1. (SDK 3.2.1 / nRF54LM20A) 
 After building, I select &amp;lt;Debug&amp;gt; under Actions in VS Code. I get this popup that says &amp;quot;Debug options not enabled&amp;quot;` 
 
 I can confirm that debuging is enabled in prj.conf... 
 
 When</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 09 Feb 2026 13:20:51 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/126897/nrf-connect-sdk-inetermediate-course---lesson-1-ex-1---debug-warnings-and-breakpoint-issues" /><item><title>RE: nRF Connect SDK Inetermediate course - lesson 1 ex 1 - debug warnings and breakpoint issues</title><link>https://devzone.nordicsemi.com/thread/560660?ContentTypeID=1</link><pubDate>Mon, 09 Feb 2026 13:20:51 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:986abbe9-a52d-496b-9798-b458ddfdf357</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
[quote user=""]After building, I select &amp;lt;Debug&amp;gt; under Actions in VS Code. I get this popup that says &amp;quot;Debug options not enabled&amp;quot;`[/quote]
&lt;p&gt;This warning is generated by the nRF Connect for VS Code when the build configuration generated there does not have debug optimizations enabled. If you have set it in prj.conf or similar as in this case, you can ignore the warning. To enable debug optimization in the build configuration do that like this when generating the build configuration:&lt;/p&gt;
&lt;p&gt;&lt;img style="max-height:240px;max-width:320px;" src="https://devzone.nordicsemi.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/4/pastedimage1770642689152v1.png" alt=" " /&gt;&lt;/p&gt;
[quote user=""]&lt;p&gt;I suspect debug-oriented optimization settings are not being set correctly, which I would expect to allow breakpoints at inlines and is probably why the &amp;quot;debugging options not enabled&amp;quot; is being shown.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;[/quote]
&lt;p&gt;Using&amp;nbsp;&lt;code&gt;CONFIG_DEBUG_OPTIMIZATIONS=y&lt;/code&gt;&amp;nbsp;will pass the &amp;quot;-Og&amp;quot; to GCC, so it does not entirely&amp;nbsp;disable optimization, but sets a&amp;nbsp;compromise that is normally good&amp;nbsp;enough for debugging&amp;nbsp;while&amp;nbsp;keeping some optimization. If you need to completely&amp;nbsp;disable optimization, you should instead set&amp;nbsp;&lt;code&gt;CONFIG_NO_OPTIMIZATIONS=y&lt;/code&gt;, which disables all optimization with &amp;quot;-O0&amp;quot;.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>