CLI 16 character limit?

I do agree it's likely something in the terminal programs

I'm not using the UART, I'm using putty and teraterm in telnet mode. port 19021

I'm using SDK v17.0.2

Soft device 7.2.0

Here is my sdk_config

Aha, so it is all RTT. I thought you were using PuTTY and Tera Term for UART. Then this is really strange, and I do not expect to find an explanation in sdk_config.h.

I gave this a test now, and see the same as you. Using the unmodified CLI example I see the following (erroneous) behavior:

rtt_cli:~$ rtt_cli:~$ print all a b c d e f g h i k
print all a b c
a b c

Using UART (with PuTTY) I get the expected result:

uart_cli:~$ print all a b c d e f g h i k
a b c d e f g h i k

I am not able to explain this at the moment but I will look at it again in Monday.

Aha, so it is all RTT. I thought you were using PuTTY and Tera Term for UART. Then this is really strange, and I do not expect to find an explanation in sdk_config.h.

I gave this a test now, and see the same as you. Using the unmodified CLI example I see the following (erroneous) behavior:

rtt_cli:~$ rtt_cli:~$ print all a b c d e f g h i k
print all a b c
a b c

Using UART (with PuTTY) I get the expected result:

uart_cli:~$ print all a b c d e f g h i k
a b c d e f g h i k

I am not able to explain this at the moment but I will look at it again in Monday.

Well Thats good

did you see the issue where you have to press enter twice for strings longer that 15 chars too?

found it, there IS a setting in the sdk_config:

// <o> SEGGER_RTT_CONFIG_BUFFER_SIZE_DOWN - Size of downstream buffer. 
#ifndef SEGGER_RTT_CONFIG_BUFFER_SIZE_DOWN
#define SEGGER_RTT_CONFIG_BUFFER_SIZE_DOWN 16
#endif

Change that to something bigger, I went to 32 and it all works as expected.

I suspect that the RTT viewer does a retry if the max number of characters is hit, while teraterm just throws it over the wall and hopes for the best