I'm trying to run RTT viewer and RTT logger on a Raspberry Pi 3 (Raspbian). The target is a nRF52832, using J-Link Ultra. I'm able to run RTTViewer on a Windows 10 system with the same hardware. But when I use the ARM host version of JLink tools, I'm unable to get RTT logger working. There also doesn't seem to be a plain RTT Viewer CLI tool, just the logger, which I haven't been able to get working. Note that I'm able to use the Raspberry Pi to erase and flash .hex files onto the nRF52, so the JLink and Nordic microcontroller works and is connected fine. But RTTlogger tool does not function correctly. See the attached screen shots and annotation.
On my windows 10 machine, I have to use V6.32i of RTT Viewer, the latest versions don't work for my Windows 10 setup. So I tried several older versions of the ARM host JLink CLI tools on the Raspberry Pi. But all of them failed to capture RTT output. I've tried V6.46 (screen shot below), V6.46i, and V6.32i of the ARM Host JLink tools.
Link to tool:
(segger.com/downloads/jlink#J-L…twareAndDocumentationPack)
EDIT: Just closing in the loop for future readers. I was able to figure out my issue. The RTT tool for ARM linux isn't smart enough to figure out which channel/terminal to use for the target. The Windows version of RTTViewer figures that out automatically so I never had to pay attention to which channel I was using. The tip is to run your target on a Windows (or maybe x86-hosted Linux machine), using the much better RTTViewer there. Watch the log for which terminal you're using. Then use the screen shot below to explicitly input the terminal. Specifically, I entered "0" when prompted for terminal, and "SWD" when prompted for interface. If the tool doesn't know what target to use, you can go back to the Windows version of J-Flash's UI, and enter the same text shown in the target dropdown selection corresponding to your micro.
Eric
On my windows 10 machine, I have to use V6.32i of RTT Viewer, the latest versions don't work for my Windows 10 setup. So I tried several older versions of the ARM host JLink CLI tools on the Raspberry Pi. But all of them failed to capture RTT output. I've tried V6.46 (screen shot below), V6.46i, and V6.32i of the ARM Host JLink tools.
Link to tool:
(segger.com/downloads/jlink#J-L…twareAndDocumentationPack)
EDIT: Just closing in the loop for future readers. I was able to figure out my issue. The RTT tool for ARM linux isn't smart enough to figure out which channel/terminal to use for the target. The Windows version of RTTViewer figures that out automatically so I never had to pay attention to which channel I was using. The tip is to run your target on a Windows (or maybe x86-hosted Linux machine), using the much better RTTViewer there. Watch the log for which terminal you're using. Then use the screen shot below to explicitly input the terminal. Specifically, I entered "0" when prompted for terminal, and "SWD" when prompted for interface. If the tool doesn't know what target to use, you can go back to the Windows version of J-Flash's UI, and enter the same text shown in the target dropdown selection corresponding to your micro.
Eric