Problems with CLI example and Segger Embedded Studio

RE: Problems with CLI example and Segger Embedded Studio

Jason Hendrix — Tue, 07 Nov 2017 13:44:02 GMT

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

RE: Problems with CLI example and Segger Embedded Studio

Jakub Rzeszutko — Tue, 07 Nov 2017 11:04:00 GMT

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.

RE: Problems with CLI example and Segger Embedded Studio

Jason Hendrix — Fri, 03 Nov 2017 16:43:39 GMT

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

RE: Problems with CLI example and Segger Embedded Studio

Jakub Rzeszutko — Fri, 03 Nov 2017 07:15:30 GMT

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.

RE: Problems with CLI example and Segger Embedded Studio

Jason Hendrix — Thu, 02 Nov 2017 16:11:05 GMT

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.

RE: Problems with CLI example and Segger Embedded Studio

Jakub Rzeszutko — Thu, 02 Nov 2017 08:44:18 GMT

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

RE: Problems with CLI example and Segger Embedded Studio

Jason Hendrix — Tue, 31 Oct 2017 19:08:35 GMT

I should note that I did see the warning in the CLI documentation against using J-Link viewer. I only brought that into the mix once i'd exhausted my options with PuTTY and the Debugger Window. I wonder if the Debugger Window (which opens automatically) is causing the same problems seen with J-Link Viewer by the writer of the CLI documentation.

RE: Problems with CLI example and Segger Embedded Studio

Jason Hendrix — Tue, 31 Oct 2017 19:06:09 GMT

That would be awesome. Appreciate it.

RE: Problems with CLI example and Segger Embedded Studio

jakub — Tue, 31 Oct 2017 18:50:23 GMT

I will be at office on Thursday. I will try to prepare something for you.

RE: Problems with CLI example and Segger Embedded Studio

Jason Hendrix — Tue, 31 Oct 2017 18:47:31 GMT

Hi Jakub, I did read the documentation; it's possible I missed something. Likely, even. Did you interfaced with the RTT interface using PuTTY? Was the Debugger Window open in SES simultaneously?
I can try the hex, but I'm running on a custom board, not the PC100040.

RE: Problems with CLI example and Segger Embedded Studio

jakub — Tue, 31 Oct 2017 18:14:40 GMT

I did and it is working fine. Did you read cli documentation? Are you able to test it with hex attached to Sdk Cli example?