Application starts only with connected SWD / debugger after DFU

RE: Application starts only with connected SWD / debugger after DFU

Einar Thorsrud — Wed, 11 Sep 2019 13:00:35 GMT

Hi,

You mention that you have removed all calls to SEGGER_RTT_printf(), but the fact that you use(d) directly in the first place is interesting. The RTT implementation may use semi hosting, but it is not used if you use nRF log (see line 82-84 in external\segger_rtt\SEGGER_RTT_Syscalls_KEIL.c). So if you use RTT, try using nrf_log instead of using it directly (this is the approach used by the SDK examples, including ble_app_template). What other modifications have you made? Any changes in your Makefile? You may also find relevant information in this and this thread.

RE: Application starts only with connected SWD / debugger after DFU

AbCdE — Wed, 11 Sep 2019 11:50:09 GMT

How do I know if I use semihosting? How do I turn it off?

I used the ble_app_template_pca10040_s132 as a basis. I don't necessarily need debug outputs.

RE: Application starts only with connected SWD / debugger after DFU

Einar Thorsrud — Wed, 11 Sep 2019 11:35:44 GMT

Hi,

The typical reason for an application to only run when a debugger is connected is that you use semihosting. Is that the case? It could depend on the RTT configuration or your fputc() implementation (typically which retarget.c file you have) or similar.