https://devzone.nordicsemi.com/f/nordic-q-a/73066/softdevice-separate-from-sdk-example-built-binariesDo the examples in the SDK folder like ble_nus have their binaries with softdevice already? I&#39;m a newbie in Nordic and using the BLE NUS example with nRF52-DK to learn as well as SDK 15. I can connect to the BLE chip using my smartphone and send dataen-USTelligent Community 13Tue, 23 Mar 2021 14:53:55 GMThttps://devzone.nordicsemi.com/thread/301491?ContentTypeID=1Tue, 23 Mar 2021 14:53:55 GMT137ad170-7792-4731-bb38-c0d22fbe4515:c903181e-999e-417d-a844-b5efc2e6a79daabitria<p>Thanks for the answer.&nbsp; That somehow clarifies my doubts.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/301121?ContentTypeID=1Mon, 22 Mar 2021 07:59:55 GMT137ad170-7792-4731-bb38-c0d22fbe4515:cb298800-dd42-4984-972a-9bfa1438bc1dEinar Thorsrud<p>Hi,</p> <p>The prebuilt binaries (residing in folders called &quot;hex&quot; within each example folder) are merged with the correct SoftDevice for apps that need it in order to make it easier to use them. Also, of you are building an example in SES and programming from there, the SoftDevice will also be automatically programmed together with your application. With other IDEs that is typically not the case though, and in those cases you will have to program the SoftDevice yourself.</p> <p>If needed you can easily see if the SoftDevice is included or not by opening a hex file in <a href="https://infocenter.nordicsemi.com/index.jsp?topic=%2Fug_nc_programmer%2FUG%2Fnrf_connect_programmer%2Fncp_introduction.html">nRF Connect programmer</a> and see which memory regions it contains data for.</p><div style="clear:both;"></div>