This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

app_error_fault_handler / SDK V15.0.0 / nRF52832 Custom board / id = 0x00004001 / Blinky example / Impossible to connect

Hello,

We have a custom board based on nRF52832. The problem is that when trying to run basic example Blinky (examples\ble_peripheral\ble_app_blinky\pca10040\s132\arm5_no_packs), then impossible to connect in nRF Connect mobile: the application is visible in the list but ends in Timeout after 5 seconds when trying to connect.

Debugging: everything seems correct, all ends with err_code = 0 but after few seconds it falls into function "app_error_fault_handler" with these params:

Any idea?  (FI, our custom board works fine as an hardware peripheral, means no BLE involved)

Thanks.

Parents Reply Children
  • Hi,

    Yes, 0x12A42 is within the SoftDevice. What did you change from the first error?

    I suggest rolling back to when you got the first error, in case the second error is a consequence of not handling the first properly. The first error you got was a NRF_FAULT_ID_SDK_ERROR, and in that case, you can use the debugger to get the file, line number and return code. In most cases, this will immediately tell you what is wrong. In order to get that, information, define DEBUG for your project (Under Options for Target, select C/C++ tab and put it under Preprocessor Symbols). Your app should end up in app_error_fault_handler() from app_error_weak.c, and an instance of error_info_t  will be populated.

    The second error you got has ID 1, which is NRF_FAULT_ID_SD_ASSERT.

  • Well the final problem is that for our custom board, the external crystal might fail... by choosing option CLK_SYNTH (in sdk_config.h) solved the problem

Related