NRF_BREAKPOINT_COND

[Nima64]

Hi there.
I've got some problem when advertising has start.
once I turn it on it's happened always after 3 minutes.
Hardware:
I am using nrf52832 module without any EVAL board at all.
all pins configured as output pin except RX,TX,RTC and CTS.
RX and CTS pins has been pulled-up with 4.7K Ohm resistors.
P13,P14,P15,P16 pins configured as input and internal pulled-up resistor activated to them.
P9,P10 configured as output too. but I could not see any action on those pins. (I think it's happened because of the SDK_CONFIG using those pins as a NFC)
Software:
I'm using NRF-SDK V17.0.2,V17.1.0,V15.3.0.
in CMSIS Configuration section the psb-btn-ble has been disabled to pervent any conflicting in pin configuration.
in all these versions I have same problem.
I've got this error code 0x00002006 and cannot find any mean of this.
in any cases that I am using this software I've got same problem.
even without any configurations on default SDK after 3 minutes it's stopped.
Apologies for my weak English.

[Karl Ylvisaker]

Hello,

Apologies for my weak English.

No need to apologize - I will just ask if anything is unclear! :) 

I'm using NRF-SDK V17.0.2,V17.1.0,V15.3.0.

Here you mention three different SDK versions - which is the one you are developing with?
I would always recommend using the latest if starting a new project, and if you have not already done so I would also recommend considering moving to the nRF Connect SDK since this is our newest SDK. Please see this statement regarding the future of these SDKs.


From your ticket it seems that you are encountering the NRF_BREAKPOINT_COND when stepping through the code in the debugger, is this correct?
If so, please make sure to add DEBUG in your preprocessor defines like shown in the included image:

This will make your logger output a detailed error message whenever a non-NRF_SUCCESS error code is passed to an APP_ERROR_CHECK.
Please do this, and let me know what this error message reads, and which line of code it points to in your application.

Best regards,
Karl

[Nima64]

Karl Ylvisaker said:

From your ticket it seems that you are encountering the NRF_BREAKPOINT_COND when stepping through the code in the debugger, is this correct?

I just download the code and run it through the debugger without selecting any breakpoints and never pause it during in the run code state.
And this problem happened too in normally run mode(without entering the debug mode.) 

[Karl Ylvisaker]

Nima64 said:

I just download the code and run it through the debugger without selecting any breakpoints and never pause it during in the run code state.

Yes, this is as expected if a non-NRF_SUCCESS error code is passed to an APP_ERROR_CHECK.
Please add the DEBUG define to your preprocessor defines and see what you logger outputs in this case.

Just for clarity, which example from the SDK are you trying to run?

Nima64 said:

And this problem happened too in normally run mode(without entering the debug mode.) 

Am I correct that in the normal mode you are just seeing a reset of the device?

Best regards,
Karl

[Nima64]

Karl Ylvisaker said:

Just for clarity, which example from the SDK are you trying to run?

ble_app_uart 

[Nima64]

Karl Ylvisaker said:

Just for clarity, which example from the SDK are you trying to run?

nRF5_SDK_17.1.0_ddde560

[Nima64]

Karl Ylvisaker said:

Am I correct that in the normal mode you are just seeing a reset of the device?

No. it is work correctly after turn on up to 3 minutes. after 3 minutes goes to the NRF_BREAKPOINT_COND and must hard reset. no differences between debug or normal running.

Any way it will stop working after 3 minutes. 
Thanks for your answers.

[Karl Ylvisaker]

Nima64 said:

No. it is work correctly after turn on up to 3 minutes. after 3 minutes goes to the NRF_BREAKPOINT_COND and must hard reset. no differences between debug or normal running.

Thank you for clarifying - this means that you are actually seeing the expected behavior of the sample. The expected behavior is for the ble_app_uart to call the sleep_mode_enter function when the advertising duration expires - which has the default value of 3 minutes -, which in turn triggers SYSTEM_OFF which will lead to a NRF_BREAKPOINT_COND when the debugger is connected since the CPU will not be allowed to go into actual SYSTEM_OFF when the debugger is in control of the CPU.

Please change the following define to change the time it will take before the advertising times out:
 

#define APP_ADV_DURATION                18000

Best regards,
Karl