RTT Viewer doesn't always work

RE: RTT Viewer doesn't always work

pmeilleur — Thu, 07 Dec 2017 22:39:50 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: RTT Viewer doesn't always work

JohnBrown — Thu, 26 May 2016 16:49:33 GMT

Do you have more than one Segger connected? Not that I've touched a Nordic chip for months, but I seem to remember that the serial number question only arose when I had a J-link connected to the board under development AND a Nordic dongle plugged into the PC.

RE: RTT Viewer doesn't always work

Christopher — Thu, 26 May 2016 15:30:29 GMT

I use the J-Link RTT client (JLinkRTTClient.exe) in console mode which automatically reconnects and not the J-Link RTT Viewer.

You should also keep your Segger tools updated to the latest version. use this link to downalod the latest tools: www.segger.com/jlink-software.html

RE: RTT Viewer doesn't always work

JohnBrown — Wed, 21 Oct 2015 09:55:40 GMT

Thanks. I have realised that reset (from Eclipse using nnrjprog) DOES seem to work, but pin reset, which I have been using, as I believe it turns debug mode off, does NOT work in conjunction with RTT Viewer. So am I only supposed to be able to use RTT Viewer when in debug mode? Maybe it's been my problem all along...

RE: RTT Viewer doesn't always work

MartinBL — Wed, 21 Oct 2015 09:25:27 GMT

Hi. Maybe this is relevant? How should I reset my device when using RTT?

RE: RTT Viewer doesn't always work

JohnBrown — Wed, 21 Oct 2015 08:43:26 GMT

"Upgraded" to 5.02d. GCC moans about Segger's use of char for array subscripts. Changed to unsigned char, seems to work. Yes, it remembers the serial number now, but I still have to click on the tickbox that says "serial number", Shame there isn't a setting for this.

If anyone from Segger ever looks at this forum, the ability to perform a reset from RTT Viewer would be really useful.

RE: RTT Viewer doesn't always work

kirkus — Tue, 20 Oct 2015 21:18:45 GMT

I also had reliability issues - until upgrading to 5.02d of both the Segger software and the RTT source code. That combo has been rock-solid for me (with a powered USB hub) for the nRF51/52 OB J-Link as well as my J-Link EDU. I just checked RTT Viewer 5.02d and it remembered the serial number.