https://devzone.nordicsemi.com/f/nordic-q-a/124625/about-ncs-ble-stackI&#39;m developing a project for nRF54 using NCS. I have a question regarding the placement of the BLE protocol stack. In the previous nRF5 SDK, the protocol stack was usually stored at a fixed address, occupying about 150KB. In the new NCS, do I need toen-USTelligent Community 13Mon, 29 Sep 2025 11:33:21 GMThttps://devzone.nordicsemi.com/thread/550009?ContentTypeID=1Mon, 29 Sep 2025 11:33:21 GMT137ad170-7792-4731-bb38-c0d22fbe4515:6ce67739-c473-4a2a-8a73-7648c9a1f74dDanielNG<p>Hi,<br />I agree with Turbo. You can also use the memory report function in nRF Connect SDK to see your memory breakdown<br /><img style="max-height:240px;max-width:320px;" src="https://devzone.nordicsemi.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/4/0160.pastedimage1759144851573v1.png" alt=" " /><br />For a simple bluetooth application like the LED Button Service sample, the Bluetooth stack occupies around 47 kB of Flash and 12 kB of RAM.<br /><br />Again, your bluetooth stack size will be largely dependant on your usage/configuration.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/549879?ContentTypeID=1Fri, 26 Sep 2025 10:10:07 GMT137ad170-7792-4731-bb38-c0d22fbe4515:28f8ce51-0aac-4fa4-b871-c543cd31fcd8Turbo J<p>The new SDK has dynamic flash and RAM usage because the SD is linked in just like any other C library.</p> <p>Flash and RAM usage thus depends on how you configure your application, i.e. you have a lot more usage when both central and peripherial mode was enabled compared to pure peripherial configurations.</p><div style="clear:both;"></div>