Can't see log messages and errors in Debug mode SES IDE

[MikeLemon]

Hello, 

I'm quite a beginner programming with the NRF52 and all and while trying to debug any example and view the log and error messages I simply can't see it anywhere(Debug Terminal is white empty) and RTT is enabled is sdk_config.h 

How do you view it?

Also is it possible to get an explanation about how debugging this chip work sins I understood debugging doesn't work with BLE but the logs are used instead with RTT and CLI(which is unclear why other then the RTT method to debug the CLI exists)

[Susheel Nuguru]

Hi MikeLemon,

Which application(example) are you trying to run ?

I can understand that for the beginners it can a bit confusing. If you have enabled the RTT in sdk_config.h you need to also enable NRF_LOG_ENABLED bit for the log feature to compile in your application. RTT is only selected as a backend only if you have enabled NRF_LOG_ENABLED by setting it to 1.

I did not quite understand your question regarding CLI, can you please explain what confuses you regarding RTT and CLI?

RTT is only used for logging. 

CLI is a Command Line Interface you can use to interact with your device .

[MikeLemon]

Hi, 

So after enabling everything in the SDK after debugging any example that includes that debugging element I just manage to see a "Debug Window" that is just blank So my question is what other setting regardless the SDK in the SES IDE you have to change/enable in order to make it work?

Also is the "Debug Window" the only window in SES you are suppose to view this message?

[Susheel Nuguru]

I believe that you enabled the logs in sdk_config.h "NRF_LOG_ENABLED" to 1 and also set the backend to RTT (not UART)

You also need to go to the project settings in SES and in the debugger tab, you need to set "Yes" to "Show logs to debug window". Then all your logs are captured by SES in debug window. You see logs only when you run your application in debug mode.

The other option is NOT to configure the SES to capture the logs like above, but instead use JLink RTT viewer to sniff for the RTT logs.

Remember that you cannot have both JLink RTT Viewer and SES debug window working in parallel.