How is it possible that my app doesn't start unless I start a debug?

[puff]

I am playing with example app from this tutorial devzone.nordicsemi.com/.../ I can see the app only when I start debugging. If I just power up my custom board, it doesn't show the app in my smartphone. What do I explain such behavior? (Probably, some settings in Segger, but I can't understand, which exactly).

UPD. Could it be so that it's working in debug mode because of delays, introduced by debugger? And the absense of these delays renders in a non-working application during normal run? UPD2. I soldered on an LED to pin10 (UART config and init is commented out in my code, at least in main.c), and during debug mode my characeristic shows up simultaneousy with me LED on pin 10 (which is actually not expected). I traced it down to ble_advertising.c, line 373,

m_evt_handler(m_adv_evt);

where m_adv_evt is BLE_ADV_EVT_FAST. but I can't find, what is inside that call, and my LED seems to turn on after this line.

[Vidar Berg]

Have you updated the pinout to reflect the pinout on your board? I'm wondering if the BSP_EVENT_SLEEP (button event) could be accidentally triggered, hence causing the chip to enter system off (leads to system reset if you are in debug mode). Do you see the same behavior if you comment out the calls to sleep_mode_enter() in your code?

[Andy]

Check your sdk_config.h and make sure that

#define SEGGER_RTT_CONFIG_DEFAULT_MODE 0

is not set to 2 (Blocking mode).

[puff]

That's strange, but I don't see sdk_config.h in any dependency lists in my project, and the search for that SEGGER_RTT_CONFIG_DEFAULT_MODE thoughout the entire solution said 'no results'.

[puff]

first I commented out //err_code = bsp_btn_ble_sleep_mode_prepare(); then I commented out //err_code = sd_power_system_off(); and still got the same behaviour. I also though, that might somehow be related to buttons left in the air (neither pulled-down, nor pulled-up), so I even removed BSP_INIT_BUTTONS flag in bsp_init, but it didn't help.

[Matt]

With PCA10040 or your custom board? With SDK12? 13? 14? Just saying "it doesn't start.." is not too helpful here.