https://devzone.nordicsemi.com/f/nordic-q-a/50825/hardfault-debugDuring the firmware running, there will be a HardFault_Handler error occasionally. Is there any way to locate the error source? Is there any good way to catch the hardware exception? Thanks!en-USTelligent Community 13Mon, 12 Aug 2019 07:04:11 GMThttps://devzone.nordicsemi.com/thread/203474?ContentTypeID=1Mon, 12 Aug 2019 07:04:11 GMT137ad170-7792-4731-bb38-c0d22fbe4515:3abaefcc-aab1-4181-b95b-fffee903d286AndreasF<p>Hi.</p> <p>You are running the APP timer with a higher IRQ priority than the SoftDevice, which is not allowed.</p> <p>Best regards,</p> <p>Andreas</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/203253?ContentTypeID=1Fri, 09 Aug 2019 10:05:18 GMT137ad170-7792-4731-bb38-c0d22fbe4515:8eb37524-66cd-4c1d-9d94-5a996ef005f2Hansome<p><span>APP_TIMER_CONFIG_IRQ_PRIORITY = 6 is normal</span></p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/203252?ContentTypeID=1Fri, 09 Aug 2019 10:04:46 GMT137ad170-7792-4731-bb38-c0d22fbe4515:d9709da2-7b77-4823-83c6-4ecbba6136d4Hansome<p>While setting APP_TIMER_CONFIG_IRQ_PRIORITY = 2, execute sd_ble_gap_conn_param_update will cause HardFault.<br />While setting APP_TIMER_CONFIG_IRQ_PRIORITY = 2, it is normal.<br />Why?</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/203230?ContentTypeID=1Fri, 09 Aug 2019 08:20:57 GMT137ad170-7792-4731-bb38-c0d22fbe4515:954312b5-3a12-45c6-8365-7bbc4beb43a3AndreasF<p>Hi, to quick summarize:</p> <p>You have to find the stack pointer (SP) value at r13, as you can see that that is the location of the stack pointer in Cortex M4:</p> <p><img alt=" " src="https://devzone.nordicsemi.com/resized-image/__size/755x550/__key/support-attachments/beef5d1b77644c448dabff31668f3a47-0999fdb329e34453bc77027e5d655d31/pastedimage1565338658864v1.png" /></p> <p>You then have to add 0x18 to the stack pointer value, and this will give you the program counter (PC) value that cause the error.</p> <p><img alt=" " src="https://devzone.nordicsemi.com/resized-image/__size/714x310/__key/support-attachments/beef5d1b77644c448dabff31668f3a47-0999fdb329e34453bc77027e5d655d31/pastedimage1565338741891v2.png" /></p> <p>Best regards,</p> <p>Andreas</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/203220?ContentTypeID=1Fri, 09 Aug 2019 07:46:07 GMT137ad170-7792-4731-bb38-c0d22fbe4515:90f3a775-5e63-4eb5-9dce-47e59509db04Hansome<p>Based on MDK5.25,&nbsp;nRF5_SDK_15.3.0_59ac345, and open DEBUG macro, and -O0</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/203219?ContentTypeID=1Fri, 09 Aug 2019 07:45:18 GMT137ad170-7792-4731-bb38-c0d22fbe4515:674b6134-6659-47fe-b9bd-1fd8167e79beAndreasF<p>Hi.</p> <p>Can you take a look at<a href="https://stackoverflow.com/questions/53253652/debugging-a-hard-fault-in-arm-cortex-m4"> this page</a> on StackOverflow?</p> <p>Best regards,</p> <p>Andreas</p><div style="clear:both;"></div>