When we transfair the big amound of data via RTT "port" the data is corrupted.

RE: When we transfair the big amound of data via RTT "port" the data is corrupted.

MartinBL — Mon, 05 Nov 2018 11:18:24 GMT

Hi,

Maybe these threads are relevant:

https://devzone.nordicsemi.com/f/nordic-q-a/33797/how-to-enable-blocking-log-output-with-rtt---sdk15
https://devzone.nordicsemi.com/f/nordic-q-a/22474/why-nrf_log_info-is-going-crazy/
https://devzone.nordicsemi.com/f/nordic-q-a/28113/segger_rtt_config_default_mode-blocking-app/

Your application should not hang, even if you don't have a debugger connected.

RE: When we transfair the big amound of data via RTT "port" the data is corrupted.

Boris — Sun, 21 Oct 2018 06:42:53 GMT

Thank you very much,

This helped me and works clearer although sometemes the corruptions can exist.

But the debugger disconnection disturbs me:

The application can hang only during the debugger disconnection or can hang also when it started to work without any debugger connected to it?

Can I keep the this option "SEGGER_RTT_MODE_BLOCK_IF_FIFO_FULL" for relising or I must use it for debugging only and when I relise the program for everyday usage I must return this option back to "SEGGER_RTT_MODE_NO_BLOCK_SKIP"?

RE: When we transfair the big amound of data via RTT "port" the data is corrupted.

Turbo J — Thu, 18 Oct 2018 14:45:05 GMT

Check SEGGER_RTT_Conf.h, SEGGER_RTT_MODE_DEFAULT definition.

The default SEGGER_RTT_MODE_NO_BLOCK_SKIP will throw data away once the RTT buffers are full. You can try SEGGER_RTT_MODE_BLOCK_IF_FIFO_FULL, but that may cause your application to hang when the debugger is disconnected.