This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

reaching NRF_BREAKPOINT_COND; in app_error_weak.c

When adding this line to codes  from an article here control reaches 

Example used is ble_app_hrs_pca10056_s140 on nrfDK2 , sdk 17 

==================added to advertising_init and to main() both , same result occurs -=========

ble_advdata_manuf_data_t manuf_data; //Variable to hold manufaturer specific data
uint8_t data[] = "SomeData!"; //Our data to advertise
manuf_data.company_identifier = 0x0059; //Nordics company ID
manuf_data.data.p_data = data;
manuf_data.data.size = sizeof(data);

===============================================

Line 100   NRF_BREAKPOINT_COND; in app_error_weak.c

NRF_BREAKPOINT_COND;
// On assert, the system can only recover with a reset.

Parents
  • this is what it says   The value is "inherits"   "BLE_STACK_SUPPORT_REQD;BOARD_PCA10056;CONFIG_GPIO_AS_PINRESET;FLOAT_ABI_HARD;INITIALIZE_USER_SECTIONS;MBEDTLS_CONFIG_FILE="nrf_crypto_mbedtls_config.h";NO_VTOR_CONFIG;NRF52840_XXAA;NRF_CRYPTO_MAX_INSTANCE_COUNT=1;NRF_SD_BLE_API_VERSION=6;S140;SOFTDEVICE_PRESENT;SWI_DISABLE0;uECC_ENABLE_VLI_API=0;uECC_OPTIMIZATION_LEVEL=3;uECC_SQUARE_FUNC=0;uECC_SUPPORT_COMPRESSED_POINT=0;uECC_VLI_NATIVE_LITTLE_ENDIAN=1;" from project in Common configuration
    "NDEBUG" from solution in Release configuration

Reply
  • this is what it says   The value is "inherits"   "BLE_STACK_SUPPORT_REQD;BOARD_PCA10056;CONFIG_GPIO_AS_PINRESET;FLOAT_ABI_HARD;INITIALIZE_USER_SECTIONS;MBEDTLS_CONFIG_FILE="nrf_crypto_mbedtls_config.h";NO_VTOR_CONFIG;NRF52840_XXAA;NRF_CRYPTO_MAX_INSTANCE_COUNT=1;NRF_SD_BLE_API_VERSION=6;S140;SOFTDEVICE_PRESENT;SWI_DISABLE0;uECC_ENABLE_VLI_API=0;uECC_OPTIMIZATION_LEVEL=3;uECC_SQUARE_FUNC=0;uECC_SUPPORT_COMPRESSED_POINT=0;uECC_VLI_NATIVE_LITTLE_ENDIAN=1;" from project in Common configuration
    "NDEBUG" from solution in Release configuration

Children
  • added DEBUG to pre-processor definitions. Still save issue. setting a breakpoint at __WEAK void app_error_fault_handler(uint32_t id, uint32_t pc, uint32_t info)

  • Slow down - you're looking at the Release configuration, but you should make the change in the common configuration (which the release configuration inherits from).

    Furthermore, with DEBUG in place you will not need to set a breakpoint on the app_error_fault_handler.

    I am interested in seeing what your logger outputs when the error occurs, after you have enabled DEBUG in the preprocessor defines. Please do this, and share the logger's output with me.

    Best regards,
    Karl

Related