I recently updated to jlink tools version 2.46g, and RTT from both JLinkExe and JLinkGDBServer appears not to work at all.
My specs:
- JLink tool version: 2.46g
- OS: Linux, Ubuntu 18.04
- JLink Adapter: JLink Plus compact
- Firmware: J-Link V10 compiled Jun 14 2019 19:25:26
- Hardware version: V10.10
- MCU: nrf52832_xxaa
- SEGGER_RTT runtime version (from SEGGER_RTT.h): 6849
- This is the version bundled with the NRF SDK (version 14.2.0)
When I start JLinkExe, it runs and connects successfully:
Code
$ JLinkExe -if swd -speed auto -device nrf52 -autoconnect 1
SEGGER J-Link Commander V6.46g (Compiled Jun 14 2019 19:36:40)
DLL version V6.46g, compiled Jun 14 2019 19:36:30
Connecting to J-Link via USB...O.K.
Firmware: J-Link V10 compiled Jun 14 2019 19:25:26
Hardware version: V10.10
S/N: 850100254
License(s): RDI, FlashBP, FlashDL, JFlash, GDB
VTref=3.438V
Device "NRF52" selected.
Connecting to target via SWD
Found SW-DP with ID 0x2BA01477
Found SW-DP with ID 0x2BA01477
Scanning AP map to find all available APs
AP[2]: Stopped AP scan as end of AP map has been reached
AP[0]: AHB-AP (IDR: 0x24770011)
AP[1]: JTAG-AP (IDR: 0x02880000)
Iterating through AP map to find AHB-AP to use
AP[0]: Core found
AP[0]: AHB-AP ROM base: 0xE00FF000
CPUID register: 0x410FC241. Implementer code: 0x41 (ARM)
Found Cortex-M4 r0p1, Little endian.
FPUnit: 6 code (BP) slots and 2 literal slots
CoreSight components:
ROMTbl[0] @ E00FF000
ROMTbl[0][0]: E000E000, CID: B105E00D, PID: 000BB00C SCS-M7
ROMTbl[0][1]: E0001000, CID: B105E00D, PID: 003BB002 DWT
ROMTbl[0][2]: E0002000, CID: B105E00D, PID: 002BB003 FPB
ROMTbl[0][3]: E0000000, CID: B105E00D, PID: 003BB001 ITM
ROMTbl[0][4]: E0040000, CID: B105900D, PID: 000BB9A1 TPIU
ROMTbl[0][5]: E0041000, CID: B105900D, PID: 000BB925 ETM
Cortex-M4 identified.
J-Link>However, I cannot attach via JLinkRTTClient or by using telnet directly:
Code
$ JLinkRTTClient
###RTT Client: ************************************************************
###RTT Client: * SEGGER Microcontroller GmbH *
###RTT Client: * Solutions for real time microcontroller applications *
###RTT Client: ************************************************************
###RTT Client: * *
###RTT Client: * (c) 2012 - 2016 SEGGER Microcontroller GmbH *
###RTT Client: * *
###RTT Client: * www.segger.com Support: support@segger.com *
###RTT Client: * *
###RTT Client: ************************************************************
###RTT Client: * *
###RTT Client: * SEGGER J-Link RTT Client Compiled Jun 14 2019 19:36:51 *
###RTT Client: * *
###RTT Client: ************************************************************
###RTT Client: -----------------------------------------------
###RTT Client: Connecting to J-Link RTT Server via localhost:19021 ........(it hangs here as long as I'll let it)
Code
$ telnet localhost:19021
telnet: could not resolve localhost:19021/telnet: Name or service not knownWith my MCU running identical firmware, and the same JLink, I can successfully get RTT output through Ozone (v2.62e).
I've not yet tried downgrading my JLink tools, but I will shortly to see if I can find the exact version this regression was introduced in.