right way to log SEGGER RTT output into file

RE: right way to log SEGGER RTT output into file

Collin — Tue, 15 May 2018 20:02:50 GMT

Sorry to necro, but for any future readers, I use J-link RTT Viewer and hit F5 (Logging>Start Terminal Logging). It has never lost data, and puts a nice header at the top of the log file. Also, RTT viewer allows you to see ~40 lines of text as it comes through. This seems to be best solution for viewing, logging, and sending commands.

RE: right way to log SEGGER RTT output into file

Jørgen Holmefjord — Mon, 09 Apr 2018 08:11:16 GMT

Calling NRF_LOG_FLUSH() after every line makes no sense, then you might as well turn off deferred logging. You should consider increasing the buffer size, and changing the config NRF_LOG_ALLOW_OVERFLOW, to make sure the buffer is not overwritten.

RE: right way to log SEGGER RTT output into file

MattFL — Fri, 06 Apr 2018 16:43:50 GMT

It seems that if the data comes faster than it can be dumped to the console, then NRF_LOG_INFO() will skip it. The fix for me was the NRF_LOG_FLUSH() after every line. This makes it much slower, but nothing is lost.

RE: right way to log SEGGER RTT output into file

Jakub Rzeszutko — Fri, 08 Dec 2017 06:33:57 GMT

Just a comment to discussion.

It is possible to use PuTTY and not loose any data but RTT session must be started by JLink.exe not by JLink Viewer.

RE: right way to log SEGGER RTT output into file

pmeilleur — Thu, 07 Dec 2017 22:41:21 GMT

I wanted to share the most reliable and efficient method I found, which also allows using the excellent Log Viewer Log4View. Simply create and launch 2 distinct batch files, open Log4view and start debugging!

The first batch file starts the JLINK Commander that reliably connects (and reconnects) to a target, buffers and make log output available through telnet. Rename as "jlinkcommander.bat" and start it once only;

REM this is to start JLINK Commander, that collects log stuff and make it available through telnet port 19021
"C:\Program Files (x86)\SEGGER\JLink_V510d\JLink.exe" -device NRF52832_XXAA -if SWD -speed 4000 -autoconnect 1

Then the 2nd batch file can be killed and restarted as desired to "cut" the log file, and store the previous log as an archive, which can be usefull for later reference. I called it "jlink_startlog.bat" :

REM this script renames current log file, if any, to date-time format
REM then move all logs to subfolder archive
REM then starts a telnet receiver to localhost + stores output to a local file
REM this file can then be read through Log4View (file receiver, log format = pattern, %m (dump all directly)
REM Log4View could also be configured to track formatting like  UniversalTime (runtime in ms) log source, etc..
@echo off
echo wscript.echo year(date) ^& "-" ^& right(100+month(date),2) ^& "-" ^& right(100+day(date),2)^& "@" ^& right(100+hour(time),2) ^& "-" ^& right(100+minute(time),2) > "%temp%\dateparts.vbs"
for /f "tokens=1 delims=" %%a in ('cscript //nologo "%temp%\dateparts.vbs"') do set yyyymmddhhmm=%%a
echo Now you can use this in your filename: %yyyymmddhhmm%
@echo on

if EXIST rtt_debug.log (
REN rtt_debug.log "%yyyymmddhhmm% - rtt_debug.log"
)

move %~dp0\*.log %~dp0\archive

telnet localhost 19021 -f rtt_debug.log

Finally I recommend viewing the log output using Log4View. Simply configure a File Receiver, using the pattern %s to output the whole file content. You can also standardize the output format of all your NRF_LOG to feed the uptime in millisecond, the log source, the severity, etc.

[31761132] RFN0 >> [ForcedRxLoad] ignore (mode_site)
[31761134] RFN0 >> [RxProcessRun] <<< scan >>> FreqBandIsmRxDefaultOverride
[31770625] MODEM>> RX (12)
[31770626] MODEM>> 0000: C3 00 00 06 6B 17 01 00 00 00 7D EE -- -- -- -- 
[31770627] MODEM>> [ATRspProcess] app -> h_OnIpTunnelDataReceived (12)

RE: right way to log SEGGER RTT output into file

Jørgen Holmefjord — Tue, 15 Nov 2016 12:22:47 GMT

From your code you log using SEGGER_RTT_WriteString(0,buffer);, but in your RTT output window, you have selected index 1. You should select index 0 to use the RTT logger.

RE: right way to log SEGGER RTT output into file

makouda — Wed, 09 Nov 2016 09:55:44 GMT

should I use SEGGER_RTT or nrf_log to log into file with jlink?

RE: right way to log SEGGER RTT output into file

makouda — Wed, 09 Nov 2016 09:38:32 GMT

I really couldn't log into file, do you open RTT Viewer or RTT logger. when I use RTT Viewer, it print eveytthing on screeen but when I use RTT loger I receive nothing, as you can see in the question above

RE: right way to log SEGGER RTT output into file

Wojtek — Tue, 08 Nov 2016 14:46:08 GMT

To be honest, I don't now. But I also find PuTTy a bit slow. I would advise you to try other telnet client

RE: right way to log SEGGER RTT output into file

makouda — Tue, 08 Nov 2016 14:38:35 GMT

@Wojtek I tried your solution and it seems to work, but I miss data (lot of data), not all data are forwarded to puyy, RTT viewer still print some data (data which is missed by putty) and this is a great issue. what kind of configurations should I perform to be sure that all data are forwarded to Putty

RE: right way to log SEGGER RTT output into file

Jørgen Holmefjord — Fri, 04 Nov 2016 15:32:15 GMT

On my Windows 7 system, the log-file was stored in %LOCALAPPDATA%\VirtualStore\Program Files (x86)\SEGGER\JLink_Vxxxx\. Just search for the name you specified for the file, to locate it. I used SEGGER_RTT_WriteString(0, "Hello World!\n"), an this worked well.

RE: right way to log SEGGER RTT output into file

makouda — Fri, 04 Nov 2016 15:11:00 GMT

I used SEGGER_RTT_printf(1, "%d \n", x_raw); to send data on channel1. but where can I find the output file? I cant find it anywhere on jlink path

RE: right way to log SEGGER RTT output into file

Wojtek — Fri, 04 Nov 2016 14:29:56 GMT

Open RTT viewer, next open PuTTY (or another preffered telnet client), select telnet, localhost:19021, and log as you would normally do in putty.

RE: right way to log SEGGER RTT output into file

Jørgen Holmefjord — Fri, 04 Nov 2016 14:26:02 GMT

You can use J-Link RTT Logger to store data from Up-Channel 1 to a file. RTT Logger is part of the J-Link Software and Documentation Pack.

RE: right way to log SEGGER RTT output into file

Alex — Fri, 04 Nov 2016 14:04:08 GMT

One of the options, although a bit expensive, is to buy J-Link SDK