Problems with CLI example and Segger Embedded Studio

[Jason Hendrix]

Hi, I'm working on a custom board based on the nRF52832. I'm developing on Win 8.1 using the latest version of SES and a J-Link Plus. SDK version 14.1. I've modifed the CLI example to run on my HW. My app doesn't interface with UART, only RTT. I'm having a terrible time interfacing with it, however. Segger opens a Debug Window by default. The output on this window is nearly perfect, but input is doubled up on the display, e.g. ccllii__ssttaattss. However, the command sent to the app is valid. I've tried opening a PuTTY connection, but that appears to be conflicting with the Debugger Window, even if I close the debugger window. J-Link Viewer works a little better, but is also conflicting with the Debug Window.

Has anyone had any success interfacing with the CLI over RTT using Segger Embedded Studio? I will appreciate any suggestions. Thanks.

[Jakub Rzeszutko]

Hi,

It seems we have a small problem here with SES. You cannot use PuTTY because SES terminal will "steal" some characters sometimes... The same problem is with J-Link Viewer.

So in this case you need to stick with SES Debug Terminal only.

I found a way to avoid doubled characters unfortunately SES terminal does not interpret ASCII escape codes. As a result you will be not able to use following keys: arrows, tab, backspace and delete.

nrf_cli.c

[Jason Hendrix]

Thanks for the help. I agree completely. I would be interested in how you eliminated the double characters if you can share. I just got approval at the Segger forum today, so I'll post some questions or requests over there.

[Jakub Rzeszutko]

Replace nrf_cli.c with the one attached in my post (above). Next in SDK config please set parameter NRF_CLI_ECHO_STATUS to false. Now in SES debug terminal you will not see doubled characters.

I just realized that "echo" command was not correctly implemented in SDK14.1. It will be fixed in 14.2.

[Jason Hendrix]

Thanks guys. With that new file, my problem with doubled characters on the SES Debug Terminal is solved. I've started a thread in the Segger Forums about the Debug Window/PuTTY conflict: forum.segger.com/index.php

[Jakub Rzeszutko]

According to SEGGER forum in order to use PuTTY and avoid data grabbing by SES debug window you need to: Project settings->Debug->Debugger->RTT Enable-> Set to No. I have tested it and it is working fine.

[Jason Hendrix]

Agreed. Works for me too. Thanks for the help.