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

My program gets stuck at NRF_BREAKPOINT_COND

Hello,

I am using a custom board that has a DSP and the Lairds BLE module BL651 that has nRF52810. I have written a simple program that sends a test data byte to the DSP and the DSP should return a response with a corresponding data. The uart_read function in DSP is a blocking function so I first run the DSP program and that will wait to receive the data from the BL651. The problem I am facing is when I run the program for BLE it directly goes and gets stuck at NRF_BREAKPOINT_COND in app_error_weak.c and hence there is no further process that occurs. The DSP still waits for the data.

Why is this happening with the BLE? I tried to debug this and when it enters the APP_ERROR_CHECK there in app_error_weak.c it gets stuck at NRF_BREAKPOINT_COND. I checked the err_code before entering APP_ERROR_CHECK and it is 0.

Please do help me with this as it is very urgent for me in my work. I am attaching the full code below.

Fullscreen
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
/**
* Copyright (c) 2014 - 2018, Nordic Semiconductor ASA
*
* All rights reserved.
*
* Redistribution and use in source and binary forms, with or without modification,
* are permitted provided that the following conditions are met:
*
* 1. Redistributions of source code must retain the above copyright notice, this
* list of conditions and the following disclaimer.
*
* 2. Redistributions in binary form, except as embedded into a Nordic
* Semiconductor ASA integrated circuit in a product or a software update for
* such product, must reproduce the above copyright notice, this list of
* conditions and the following disclaimer in the documentation and/or other
* materials provided with the distribution.
*
* 3. Neither the name of Nordic Semiconductor ASA nor the names of its
* contributors may be used to endorse or promote products derived from this
* software without specific prior written permission.
*
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

Thanks & Regards

Sudeep R J