<?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>Unable to build when enabling CONFIG_DEBUG on nRF5340 platforms in NCS 2.6.1</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/114558/unable-to-build-when-enabling-config_debug-on-nrf5340-platforms-in-ncs-2-6-1</link><description>I&amp;#39;m trying to debug on the Thingy:53 platform using an Nordic DK as the J-Link intermediate. However, with NCS 2.6.1, adding ` CONFIG_DEBUG=y` to the project configuration causes the network core binary to be way too big for flash (see output below).</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 10 Sep 2024 13:44:07 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/114558/unable-to-build-when-enabling-config_debug-on-nrf5340-platforms-in-ncs-2-6-1" /><item><title>RE: Unable to build when enabling CONFIG_DEBUG on nRF5340 platforms in NCS 2.6.1</title><link>https://devzone.nordicsemi.com/thread/501956?ContentTypeID=1</link><pubDate>Tue, 10 Sep 2024 13:44:07 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1f89d991-fc43-4170-b67f-427d841ec0d1</guid><dc:creator>Susheel Nuguru</dc:creator><description>[quote user="Anthony W"]I wanted to make sure a flag is enabled only for the parent image, is there a way to specify that in the build? It seems like CONFIG_DEBUG=y is turning on other flags which aren&amp;#39;t disabled by specifying CONFIG_DEBUG=n in the network core&amp;#39;s child image. Unless I&amp;#39;m just misunderstanding exactly what&amp;#39;s going on.[/quote]
&lt;p&gt;Yeah, the dependencies are crazy here. If you want to make sure you want to disable something, put that config value to be disabled in your prj.conf and see that it does not generate any warnings of being overwritten in the compile log. If there are warnings saying that your config in prj.conf is overwritten, then it will also give you the dependency that made it so.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Unable to build when enabling CONFIG_DEBUG on nRF5340 platforms in NCS 2.6.1</title><link>https://devzone.nordicsemi.com/thread/501789?ContentTypeID=1</link><pubDate>Mon, 09 Sep 2024 16:08:47 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:63acd9a4-c168-4df6-868d-664f1cc1cdb1</guid><dc:creator>Anthony W</dc:creator><description>&lt;p&gt;I&amp;#39;m using the Thingy:53 specifically to test with the sensors already on the device, so it&amp;#39;s convenient to occasionally be able to debug on the device itself, I assume that was the intent.&lt;/p&gt;
&lt;p&gt;However, good point about building without TFM. I didn&amp;#39;t know what that was or that it should just be disabled, but that&amp;#39;s easy enough to do and works fine, thanks.&lt;/p&gt;
&lt;p&gt;But in the event using the T-FM was necessary, or if there was ever a case for some other reason I wanted to make sure a flag is enabled only for the parent image, is there a way to specify that in the build? It seems like CONFIG_DEBUG=y is turning on other flags which aren&amp;#39;t disabled by specifying CONFIG_DEBUG=n in the network core&amp;#39;s child image. Unless I&amp;#39;m just misunderstanding exactly what&amp;#39;s going on.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Unable to build when enabling CONFIG_DEBUG on nRF5340 platforms in NCS 2.6.1</title><link>https://devzone.nordicsemi.com/thread/501745?ContentTypeID=1</link><pubDate>Mon, 09 Sep 2024 12:52:56 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:da20d300-8d91-4d4e-afcb-fecb2b820e5f</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;it looks like Thingy:53 applications are mostly built without the TFM support and we have not tested anything with non secure support. Is it a necessity that you need to use Thingy:53? Can&amp;#39;t you use the DK if are trying to evaluate some sample?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>