Is that bad to call RTT functions if there is no SEGGER connected?

RE: Is that bad to call RTT functions if there is no SEGGER connected?

Sébastien Despont — Fri, 13 Nov 2015 21:14:10 GMT

Thanks you for your answer. I didn't change RTT configuration, so it should be fine.

RE: Is that bad to call RTT functions if there is no SEGGER connected?

Sébastien Despont — Fri, 13 Nov 2015 21:03:20 GMT

Thanks for your answer, can you link the RTT web page?

RE: Is that bad to call RTT functions if there is no SEGGER connected?

Bill Siever — Fri, 13 Nov 2015 21:00:37 GMT

The RTT web page says:

The developer does not have to create a special debug version and the code can stay in place in a release application.

Since the RTT routines just copy to a special block in memory they can run without the debugger connected. The final application would have slightly worse performance if it's present (a little slower; more code executed so more power consumption; RAM allocated that isn't needed).

Just to add a little more to Martijn's response: It uses non-blocking by default. The Q&A section on the RTT page (https://www.segger.com/jlink-rtt.html) mentions:

SEGGER-RTT uses non-blocking mode per default, which means it does not halt program execution if no debugger is present and J-Link is not even connected. The application program will continue to work

RE: Is that bad to call RTT functions if there is no SEGGER connected?

Martijn — Fri, 13 Nov 2015 20:56:34 GMT

It depends on what you configured.. You can configure it for trim, skip or block. In trim an skip mode it is no problem, it will continue. But in in block mode it wait until there is room, which is never... By default it is configured for trim I believe where as much data gets put into buffer as fits and skips the rest.

And yes it does use ram, rtt initialises itself the first time it is called.