CLI Example Issues

Question

I'm combing over the CLI peripheral example, but having a few problems when running the example: 
 
 The Debug Terminal in SES blacks out the test so its difficult to see commands entered or return values, unless I highlight the terminal 
 When I run the example I get the following warning that I can seem to find any documentation of "<warning> app: Logger configuration file not found." What configuration file is it referring to? 
 The example commands specified in demo_cli_cmds.c do not seem to work, nor do they seem to be enabled/registered within the main.c source code 
 The Stack Guard function seems like a good function enable in general as it helps trace Stack violations. Why isn't this enabled on most examples? Is there any downside other than slightly large image size?

I'm trying to determine whether I should use the NRF_CLI module for general development or write my own in a thread safe module. 
 
 Thanks guys.

Jakub Rzeszutko · Answer

Hi, 
 1. Please do not use SES debug terminal with CLI example. It does not handle VT100 escape codes, please use Putty instead. 
 With SES terminal you will be not able to use Tab key or meta keys... Putty configuration is available here: 
 http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.sdk5.v15.2.0/lib_cli.html?cp=4_0_0_3_10 
 I guess you are using RTT backend. In such case RTT session must be started by JLink.exe and not by SES. When you start RTT session with JLink.exe you need to disable it in SES to avoid loosing characters: 
 Project options -> Debugger -> RTT Enable (change to No) 
 2. You do not need to bother about: " <warning> app: Logger configuration file not found." First of all this shall be debug (not warning) message. Second of all we have a new feature that you can store logger settings updated in runtime in flash. This new configuration is metioned "file". 
 3. What do you mean the are not working? 
 4. Stack Guard is just a feature in the SDK, I've added a command to make it more visible for the users. I do not see any downside using it in different examples.