Break point problem

RE: Break point problem

Sangram singh — Wed, 20 Jan 2021 05:53:22 GMT

After Implementing monitor mode debugging below error is comming

Output/ble_app_uart_c_pca10040_s132 Release/Obj/JLINK_MONITOR_ISR_SES.o: In function `DebugMon_Handler':
1> D:\NORDIC\Nordic\sdk\nRF5_SDK_16.0.0\nRF5_SDK_16.0.0\examples\ble_central\ble_app_uart_c/JLINK_MONITOR_ISR_SES.s:159: undefined reference to `JLINK_MONITOR_OnEnter'
1> Output/ble_app_uart_c_pca10040_s132 Release/Obj/JLINK_MONITOR_ISR_SES.o: In function `_WaitForJLinkCmd':
1> D:\NORDIC\Nordic\sdk\nRF5_SDK_16.0.0\nRF5_SDK_16.0.0\examples\ble_central\ble_app_uart_c/JLINK_MONITOR_ISR_SES.s:183: undefined reference to `JLINK_MONITOR_OnPoll'
1> Output/ble_app_uart_c_pca10040_s132 Release/Obj/JLINK_MONITOR_ISR_SES.o: In function `_HandleRestartCPU':
1> D:\NORDIC\Nordic\sdk\nRF5_SDK_16.0.0\nRF5_SDK_16.0.0\examples\ble_central\ble_app_uart_c/JLINK_MONITOR_ISR_SES.s:228: undefined reference to `JLINK_MONITOR_OnExit'
Build failed

pls. suggest.

RE: Break point problem

Sangram singh — Wed, 20 Jan 2021 05:52:32 GMT

After Implementing monitor mode debugging below error is comming

pls. suggest.

RE: Break point problem

Sangram singh — Thu, 14 Jan 2021 10:43:31 GMT

Can we use Segger Embedded Studio V3.34 for monitor mode debugging ?

RE: Break point problem

Vidar Berg — Thu, 14 Jan 2021 07:06:56 GMT

As I have tried to explain earlier, you can't do this if you have enabled Bluetooth in your app.

RE: Break point problem

Sangram singh — Thu, 14 Jan 2021 06:17:59 GMT

when we wait approx. 30 to 40 sec at break point then Control goes to NRF_BREAKPOINT_COND ow to remove this problem

RE: Break point problem

Vidar Berg — Tue, 12 Jan 2021 10:25:39 GMT

The solution is to reset the device and start over again when you hit a breakpoint. Else you need to implement monitor mode debugging as explained here: https://github.com/NordicPlayground/j-link-monitoring-mode-debugging

RE: Break point problem

Sangram singh — Tue, 12 Jan 2021 10:22:21 GMT

yes i receive SOFTDEVICE: ASSERTION FAILED error so please give me solution

RE: Break point problem

Vidar Berg — Tue, 12 Jan 2021 09:53:40 GMT

Yes, the Softdevice will still assert if you try to resume execution after hitting a breakpoint. Did you get debug logs in the terminal after you made the changes?

RE: Break point problem

Sangram singh — Tue, 12 Jan 2021 08:54:23 GMT

After setting in sdk_config.h

1.> NRF_LOG_BACKEND_RTT_ENABLED 1

NRF_FPRINTF_FLAG_AUTOMATIC_CR_ON_LF_ENABLED 0

2.> Select the debug project configuration before building the project. This configuration sets the "DEBUG" flag .

But the same problem is comming

RE: Break point problem

Vidar Berg — Tue, 12 Jan 2021 08:12:57 GMT

Hi,

I assume you're debugging a BLE application? In that case, the error is likely reported by the Softdevice. One of the challenges when debugging with the Softdevice, or any other protocol stack with hard timing requirements for that matter, is that it will fail to meet those timing requirements if the CPU gets halted for too long. To avoid this error, you have to always make sure to reset the device after hitting a breakpoint.

Logging is also helpful. Please follow the steps below if you have not enabled it already.

Steps to enable debug logging in SES

1. Ensure you have the following configuration settings in sdk_config.h

NRF_LOG_BACKEND_RTT_ENABLED 1

NRF_FPRINTF_FLAG_AUTOMATIC_CR_ON_LF_ENABLED 0

2. Select the debug project configuration before building the project. This configuration sets the "DEBUG" flag which will make the app error handler log more error information if an error occurs.

3. Start a new debug session. The debug messages should now appear in the debug terminal window.