https://devzone.nordicsemi.com/f/nordic-q-a/123088/makefile-does-not-produce-runnable-code-ses-doesHi all I have a project that I developed with SDK 17.0.2 in Segger Embedded Studio. It works well, but now I would like to add a GitHub Runner to compile it every time I push something to my main branch. For that, I want to build a Makefile, so it canen-USTelligent Community 13Sat, 19 Jul 2025 20:56:59 GMThttps://devzone.nordicsemi.com/thread/542929?ContentTypeID=1Sat, 19 Jul 2025 20:56:59 GMT137ad170-7792-4731-bb38-c0d22fbe4515:5ddb240f-b5a8-4d27-bbc7-27bb8866a422fuesel<p>After looking at this for days, of course I find the solution some hours after posting here.&nbsp;</p> <p>The problem lies in this line in the linker script:</p> <p>RAM (rwx) :&nbsp; ORIGIN = 0x20002288, LENGTH = 0xdd90</p> <p>This defines the RAM start and size. Adding these two numbers together:&nbsp;<span>0x20002288 + 0xdd90 =&nbsp;</span><span>0x20010018. However, according to the product specifications&nbsp;<a id="" href="https://docs.nordicsemi.com/bundle/ps_nrf52832/page/memory.html">https://docs.nordicsemi.com/bundle/ps_nrf52832/page/memory.html</a>&nbsp;the maximum allowed RAM size is 0x20010000. The correct length is calculated as such: 0x20010000 -&nbsp;0x20002288 =&nbsp;</span>0xdd78. Correcting this value gives the following line:</p> <p><span>RAM (rwx) :&nbsp; ORIGIN = 0x20002288, LENGTH = 0xdd78</span></p> <p><span>I do not understand why this worked in SES, but it did. And it did not work using a Makefile - as it should.</span></p><div style="clear:both;"></div>