<?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 v2.3.0 Migration RAM Overflow</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/101603/nrf-connect-sdk-v2-3-0-migration-ram-overflow</link><description>I am in the process of migrating from nRF Connect SDK v2.0.0 to v2.4.0. In order to isolate some of the compile errors, I did this incrementally, and found that in v2.3.0 specifically, I was getting a RAM overflow error during compilation: 
 
 The only</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 06 Jul 2023 21:02:14 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/101603/nrf-connect-sdk-v2-3-0-migration-ram-overflow" /><item><title>RE: nRF Connect SDK v2.3.0 Migration RAM Overflow</title><link>https://devzone.nordicsemi.com/thread/435085?ContentTypeID=1</link><pubDate>Thu, 06 Jul 2023 21:02:14 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:262adc1a-bc7e-43fd-ab70-11fab51909e8</guid><dc:creator>brushlow</dc:creator><description>&lt;p&gt;To anyone stuck on this issue, I found that setting a maximum allowable bluetooth connections (CONFIG_BT_MAX_CONN) allowed me to compile. I didn&amp;#39;t have this config in my hci_rpmsg.conf, and it defaults to16 which is much more than I needed. Looks like the Nordic SoftDevice RAM consumption grew enough to push the child image over the limit. &lt;/p&gt;
&lt;p&gt;Hope this helps someone&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF Connect SDK v2.3.0 Migration RAM Overflow</title><link>https://devzone.nordicsemi.com/thread/435071?ContentTypeID=1</link><pubDate>Thu, 06 Jul 2023 17:05:32 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:126c79c7-1f8f-412e-bd13-667002067ebe</guid><dc:creator>brushlow</dc:creator><description>&lt;p&gt;I dug into this more, and now understand this specifically applies to the network core child image; I can see in the correct map file where the overflow is. The configs I specified in the first post are the only ones in my hci_rpmsg.conf file. Given that, are those buffer sizes supported for the nRF340 using SoftDevice on SDK v2.3.0? Is there anything in prj.conf that would influence this? And is there anything I can do to avoid reducing these buffer sizes?&lt;/p&gt;
&lt;p&gt;Thanks for reading&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>