Please clarify the SDK version as I mentioned in your other thread. Also, which IDE or toolchain are you using?
Assuming you use a fairly recent SDK version, the ble_app_uart and ble_app_uart_c project use Segger RTT for logging. If you use Segger Embedded Studio as IDE, that can be observed directly in the IDE. If not, you can observe the log using Segger RTT Viewer. By default the example projects are built in a release configuration. To have more debug information in the log, buld with DEBUG and DEBUG_NRF defined for the project. How do do that depends on the IDE/toolchain.
As mentioned these examples have RTT logging enabled by default, but generally the logging is controlled by sdk_config.h (you also need initialization code in your application). See Logger module for detail on logging in the nRF5 SDK.
Please clarify the SDK version as I mentioned in your other thread. Also, which IDE or toolchain are you using?
Assuming you use a fairly recent SDK version, the ble_app_uart and ble_app_uart_c project use Segger RTT for logging. If you use Segger Embedded Studio as IDE, that can be observed directly in the IDE. If not, you can observe the log using Segger RTT Viewer. By default the example projects are built in a release configuration. To have more debug information in the log, buld with DEBUG and DEBUG_NRF defined for the project. How do do that depends on the IDE/toolchain.
As mentioned these examples have RTT logging enabled by default, but generally the logging is controlled by sdk_config.h (you also need initialization code in your application). See Logger module for detail on logging in the nRF5 SDK.
