[ABANDONED] RTT doesn't work on RM48 - "RTT is not supported for this setup"

SVTechSupport · Mar 4th 2024, 10:06am

Hi,
We are developing a product with TI's RM48 processor familiy and one of the requisites is to have RTT working for debugging purposes.

We found a couple of forum posts with a lot of useful information on how to approach the problem:
- [SOLVED] How to setup JLink for background memory access of RM48L952 for real-time terminal?
- [ABANDONED] SystemView on TI RM48L952

Unfortunately, every time we try to start an RTT session we get this generic error.

We are using TI's Code Composer Studio but we'll move to IAR in the near future.

Here are some more info about our setup:

Process: C:\Program Files\SEGGER\JLink_V794i\JLinkRTTViewer.exe
Module: C:\Program Files\SEGGER\JLink_V794i\JLink_x64.dll
Version: V7.94i, compiled Feb 7 2024 17:08:52
J-Link: SEGGER J-Link V8.0, SN=(REDACTED)
J-Link Uptime: N/A (Not supported by this model)
Selected device: Debugger: RM48L9X, Internal: RM48L9X
Endian: Little
Voltage: 3.28 V
Target interface: JTAG (1000 kHz)
Host interface: USB (SN REDACTED)

For what we can see in the Wiki, all JLink models should support RTT (at least in stop mode) so we excluded the hardware incompatibility.

What could be the cause of this error?

Also, referring to this thread would it be possible to also have the JlinkScript used internally for the RM48 family?

Thank you in advance for the support!

EDIT: Added RTTViewer Log

Source Code

LOG: J-Link RTT Viewer V7.94i: Logging started.
LOG: Terminal 0 added.
LOG: Connecting to J-Link via USB...
LOG: Device "RM48L9X" selected.
LOG: ConfigTargetSettings() start
LOG: ConfigTargetSettings() end - Took 8us
LOG: InitTarget() start
LOG: TotalIRLen = 6, IRPrint = 0x01
LOG: JTAG chain detection found 1 devices:
LOG: #0 Id: 0x4B8A002F, IRLen: 06, TI ICEPick
LOG: InitTarget() end - Took 141ms
LOG: TotalIRLen = 10, IRPrint = 0x0011
LOG: JTAG chain detection found 2 devices:
LOG: #0 Id: 0x4BA00477, IRLen: 04, CoreSight JTAG-DP
LOG: #1 Id: 0x4B8A002F, IRLen: 06, TI ICEPick
LOG: DPv0 detected
LOG: CoreSight SoC-400 or earlier
LOG: AP map detection skipped. Manually configured AP map found.
LOG: AP[0]: AHB-AP (IDR: Not set)
LOG: AP[1]: APB-AP (IDR: Not set)
LOG: AP[2]: MEM-AP (IDR: Not set)
LOG: Using preconfigured AP[1] as APB-AP
LOG: AP[1]: APB-AP found
LOG: ROMTbl[0][0]: CompAddr: 80001000 CID: B105900D, PID: 007BBC14 Cortex-R4
LOG: Found Cortex-R4 r1p3
LOG: 6 code breakpoints, 2 data breakpoints
LOG: Debug architecture ARMv7.0
LOG: Data endian: little
LOG: Main ID register: 0x411FC143
LOG: TCM Type register: 0x00010001
LOG: MPU Type register: 0x00000C00
LOG: System control register:
LOG: Instruction endian: little
LOG: Level-1 instruction cache disabled
LOG: Level-1 data cache disabled
LOG: MPU disabled
LOG: Branch prediction enabled
LOG: SetupTarget() start
LOG: Executing SetupTarget()
LOG: Memory access: CPU temp. halted: https://wiki.segger.com/Memory_accesses#Legacy_stop_mode
LOG: SetupTarget() end - Took 18.6ms
LOG: RTT Viewer connected.

Display All

SEGGER - Alex · Mar 5th 2024, 7:05pm

While RTT Stop-Mode in general might be working for the J-Link you use, stop-mode support on the RM48 may require further features that are specifically needed for RTT on RM48 in general, but these are not provided by the J-Link in use.

In general, the J-Link you use is a V8 model which is pretty likely 10+ years old and has been out of support and maintenance, so there is no support, bugfixing or even analysis done on it.
If the same issue comes up with a current model, we recommend to open an official support case and we will take care.

BR
Alex

Source Code

Share