https://devzone.nordicsemi.com/f/nordic-q-a/9805/hardfault---nrf51I&#39;m having a weird hardfault and, I can&#39;t make sense of it. Here&#39;s what I do know: nrf sdk 9.0.0; nrf51422 on a dk; I have RTC1, SPI0, and TWI1 enabled (also a uart for logging); I have the S130 enabled; Priorities seem to be good; Upon starten-USTelligent Community 13Mon, 19 Oct 2015 18:36:54 GMThttps://devzone.nordicsemi.com/thread/36352?ContentTypeID=1Mon, 19 Oct 2015 18:36:54 GMT137ad170-7792-4731-bb38-c0d22fbe4515:7f028219-b2a9-4f0e-a743-e9d5b7d101f8Beau R.<p>Thank you for the tip and the acknowledgement that my logic is sound. My link register from the stack was pointing to a instruction in disassembly for outputting characters via UART. I&#39;m going to do some more digging, I&#39;m sure I&#39;m doing something illogical somewhere. I&#39;m noticing that it&#39;s failing directly after a ble connection message receive event.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/36351?ContentTypeID=1Mon, 19 Oct 2015 16:16:19 GMT137ad170-7792-4731-bb38-c0d22fbe4515:1b10843b-20fe-42d4-acd8-027b87161ba6RK<p>That analysis seems correct. It&#39;s possible that you did jump to 0x00000002 and tried executing code which then caused a hardfault. What&#39;s at SP+0x14? That&#39;s the link register at the time of the exception, ie the return address for the last function called before whatever caused the hardfault. Perhaps that might give you a clue where you came from and how you got there.</p><div style="clear:both;"></div>