cancel
Showing results for 
Search instead for 
Did you mean: 

J-Link: Live expression do not work after upgrade to STM32CubeIDE 2.1.0

Stefan1
Associate III

Title edited to indicate that this is specific to J-Link.


Hi,

After updating to STM32CubeIDE 2.1.0 I get the following message after starting a debug session. Live expressions do not work.

Skærmbillede 2026-03-02 092504.png

From the console:

SEGGER J-Link GDB Server V9.14a Command Line Version

JLinkARM.dll V9.14a (DLL compiled Jan 28 2026 17:11:52)

Command line: -port 2331 -s -device STM32F769NI -endian little -speed 4000 -if swd -swoport 2332 -vd -rtos C:\ST\STM32CubeIDE_1.11.2\STM32CubeIDE\plugins\com.st.stm32cube.ide.mcu.externaltools.jlink.win32_2.5.200.202601091506\tools\bin\GDBServer\RTOSPlugin_FreeRTOS.dll
-----GDB Server start settings-----
GDBInit file:                  none
GDB Server Listening port:     2331
SWO raw output listening port: 2332
Terminal I/O port:             2333
Accept remote connection:      localhost only
Generate logfile:              off
Verify download:               on
Init regs on start:            off
Silent mode:                   off
Single run mode:               on
Target connection timeout:     0 ms
------J-Link related settings------
J-Link Host interface:         USB
J-Link script:                 none
J-Link settings file:          none
------Target related settings------
Target device:                 STM32F769NI
Target device parameters:      none
Target interface:              SWD
Target interface speed:        4000kHz
Target endian:                 little

Connecting to J-Link...
J-Link is connected.
Firmware: J-Trace PRO V2 Cortex-M compiled Dec  4 2024 17:58:04
Hardware: V2.00
S/N: 752000803
Feature(s): RDI, FlashBP, FlashDL, JFlash, GDB
Checking target voltage...
Target voltage: 3.33 V
Listening on TCP/IP port 2331
Connecting to target...
Halting core...
Connected to target

 

The debug settings:

Skærmbillede 2026-03-02 102941.png

 

1 ACCEPTED SOLUTION

Accepted Solutions

Hello @Stefan1 @DKilg 

Actually, our team are aware of this issue and currently working on resolving it. (Ticket 227696 This is an internal tracking number and is not accessible or usable by customers)

Thank you,

KR, Souhaib

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.

View solution in original post

16 REPLIES 16
Andrew Neil
Super User

What version did you upgrade from ?

Presumably you did have it working in that previous version?

And other debugging stuff is working OK?

A complex system that works is invariably found to have evolved from a simple system that worked.
A complex system designed from scratch never works and cannot be patched up to make it work.
AScha.3
Super User

btw You set the core clock to 8M - really run the core at 8 MHz ?? set the real core clock here.

If you feel a post has answered your question, please click "Accept as Solution".

I upgraded from STM32CubeIDE 2.0.0

Live Expression did work before; I simply updated and then started the debugging and got the message.

I have now changed the core speed setting to 216 MHz, but the same issue remains.

Thank you for noticing.

and other debug functions still work as before ?

A complex system that works is invariably found to have evolved from a simple system that worked.
A complex system designed from scratch never works and cannot be patched up to make it work.

Expressions and Breakpoints work as usual.

Stefan1
Associate III

A reinstall did not solve the issue.

Andrew Neil
Super User

Does it work with ST-Link ?

A complex system that works is invariably found to have evolved from a simple system that worked.
A complex system designed from scratch never works and cannot be patched up to make it work.
DKilg
Associate II

Hi,

I’m experiencing the same issue after updating to STM32CubeIDE 2.1.0.

Live expressions are not working for me after the update using J-Trace PRO V3 Cortex.