reaching NRF_BREAKPOINT_COND; in app_error_weak.c

[consulting99]

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.

[consulting99]

[Karl Ylvisaker]

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

[consulting99]

[consulting99]

      NRF_LOG_ERROR("SOFTDEVICE: ASSERTION FAILED"); is the last executed line before    NRF_BREAKPOINT_COND;

[Karl Ylvisaker]

A SoftDevice assertion will happen if you hit a breakpoint during a debug session, because this halts the CPU which causes the SoftDevice to miss its timing-critical deadlines, causing the assert.
In essence, you may not use the usual debugger + multiple breakpoints in a program where the SoftDevice is enabled.

Please see my other comment, and share the complete error message so we may continue the debugging of this issue.

Best regards,
Karl