No Debug Output and stopped APP-Timer after usage of sd_ble_gap_disconnect

[bama]

Hello,

I have a strange Problem. I have a Central Application where the Central will get a TagID via Uart and if there is a adv. from this Tag the Central will connect to the Tag.

While this connection the Central will read out some data and then the Central use the sd_ble_gap_disconnect command to disconnect from the Tag.

There is also the possibility that the Central will get a "Disconnect" command via Uart and also then the Central will use sd_ble_gap_disconnect to disconnect from the Tag.

To see if the Central is Alive the Central will send a Hearbeat message via Uart to the PC every second.

If I run the "Debug" Configuration everything went well without a problem.

But if I switch to the "Release" Configuration then I see the strange Problem.

If the central use the sd_ble_gap_disconnect alone after the central has read the data from the tag everything went well and also this uart hearteat is still send every second. Also I will see all debug outputs on the console.

But if I use the sd_ble_gap_disconnect after I have got the "Disconnect" command via Uart the central will disconnect from the Tag but I will no longer see any debug outputs on the console and also my uart heartbeat is no longer send. It looks like the used App timer is no longer working.

Bud because this happen within the Release Build I have not good chance to use the debugger to find this strange problem.

markus

[Sigurd]

bama said:

But if I switch to the "Release" Configuration then I see the strange Problem.

1) Do you still see the issue in "Release" configuration, while running a active debug session?

2) Are you using a custom board, or a development kit?

3)  What SDK version are you using ?

[bama]

1.) Yes I see it also on the "Release" Configuration while a debug session

2.) Both on a custom board and a PCA10040

3.) We use nRF5_SDK_16.0.0_98a08e2

[Sigurd]

bama said:

Yes I see it also on the "Release" Configuration while a debug session

 But then you can still use the debugger to find the issue. Do you enter the error-handler when this happens? Try to set a breakpoint at the line "app_error_fault_handler" in app_error_handler_bare() in app_error.c

[bama]

The app will not enter any error handler! And because of the Softdevice (I think) my application will enter the hard fould if I have stopped at a breakpoint and want to start again after the breakpoint. I also have tried to make a step by step debugging directly at the start of main. But there i can then see that no each line will be entered. So I think because of the optimizations within the release build the debugging is very difficult.

[Sigurd]

Could you try to set the following configuration in sdk_config.h, and see if it changes the behavior ?

#define NRF_LOG_BACKEND_RTT_ENABLED 1

#define NRF_FPRINTF_FLAG_AUTOMATIC_CR_ON_LF_ENABLED 0

#define NRF_LOG_BACKEND_UART_ENABLED 0