RE: S130 softdevice hard fault

Vidar Berg — Mon, 27 Aug 2018 07:09:09 GMT

Either that, or in the softdevice. The processor should not be halted in the MBR region unless you have the breakpoint enabled. Have you tried to disable it?

RE: S130 softdevice hard fault

Ian — Fri, 24 Aug 2018 10:00:36 GMT

Do you mean the application occur hard fault, but is it halt here because of a breakpoint?

RE: S130 softdevice hard fault

Vidar Berg — Tue, 21 Aug 2018 12:28:34 GMT

Hi,

Looks like the CPU is halted inside the hardfault handler located in the Master boot record ( MBR - basically an interrupt forwarder) while it should have been forwarded to softdevice --> application. It is possible that SES has enabled "vector catch" and that is why the CPU gets halted in the MBR and not in the application/softdevice. While you are debugging, click on Debug in the menu bar and select Breakpoints -> Breakpoints and make sure to disable the breakpoint for the Hardfault exception.

Breakpoint view for Cortex M4

Also, do you have this function to catch softdevice assertions in your project?

/**@brief Callback function for asserts in the SoftDevice.
 *
 * @details This function will be called in case of an assert in the SoftDevice.
 *
 * @warning This handler is an example only and does not fit a final product. You need to analyze
 *          how your product is supposed to react in case of Assert.
 * @warning On assert from the SoftDevice, the system can only recover on reset.
 *
 * @param[in] line_num   Line number of the failing ASSERT call.
 * @param[in] file_name  File name of the failing ASSERT call.
 */
void assert_nrf_callback(uint16_t line_num, const uint8_t * p_file_name)
{
    app_error_handler(DEAD_BEEF, line_num, p_file_name);
}