J-Link RTT for easy debug prints

[jeremysf]

Not really a question, but it took me way to long to find out about J-Link RTT (i.e. j-link Real Time Terminal for easy debug printing so I thought I would mention it for future searchers on the subject.

If you have been using serial to get trace output on the dev boards and are looking for an option to get multiple channels of text output (and input!) with just a few .c files on your target device, you might want to check it out:

www.segger.com/jlink-real-time-terminal.html

Also really loving the Tag-Connect form factor for connecting my little target board to J-Link if you haven't checked it out.

[RK]

You should turn this into a blog post so more people see it in future - RTT is useful, and recent, so not a lot of people are yet using it.

I found to my delight that Crossworks, which I use for development, added RTT support recently so you get the debug output right in the debug console, it's zero work.

[Moritz]

Is there a way to easily remap the "app_trace_log"/"APPL_LOG"-calls (which are just printf) to J-Link RTT)? According to the SEGGER-Website you would just have to include the "RTT_Syscalls_KEIL.c" to remap printf, but at least in my setup this didn't work out of the box... Any ideas?

[Moritz]

Turns out that's actually quite easy. I just had to upgrade to the latest J-Link Version(currently V.4.96C) and disable "use MicroLIB" in the Keil-Project-Settings (Tab Target) to get rid of:

"Error: L6915E: Library reports error: __use_no_semihosting was requested, but a semihosting fputc was linked in"

[Stian Røed Hafskjold]

Just want to add that we now have a tutorial on this: devzone.nordicsemi.com/.../

[Lola]

future ? to use terminal in 2017 is future ? you are using Android right ? that might explain the gap in understanding UI and UX, and how they are important even if you do "tech" .