2026-02-20 8:38 AM
I'm using JetBrains CLion to debug my STM32 project, and it runs `ST-LINK_gdbserver` when debugging, and passes the "--shared" flag for other STM apps to connect into. It starts up okay, and shows "Info : default port : 7184".
I've changed my "settings.js" file in "~/.STMicroelectronics/stm32cubemonitor/" folder so that "connectionType" is "tcp" and not "p2p".
I run stm32cubemonitor, and then node-red is showing up an error of:
Cannot read properties of undefined (reading 'isTcpAvailable') (line:59)
I think this code underneath is all bundled into the distributable, so I can't debug what's actually going wrong.
The versions I have installed currently are:
ii st-stm32cubeide-2.0.0 2.0.0-26820-20251114-1348-1 amd64 IDE for STM32
ii stm32cubemonitor 1.12.0 amd64 STM32CubeMonitor helps debug a...
ii st-stlink-server 2.1.1-1 amd64 stlink tcp server to permit sev...I'm using an ST-Link/V2 ISOL
Running on Ubuntu 25.10.
Any ideas how to fix this, or where the source code is for that node-red module, or if it's a known error. Can't find any mention of this.
2026-05-08 1:57 AM
I’m having the same problem on Windows.
My version is newer: STM32CubeIDE 2.1.1.
It worked for several years using TCP, but now I’ve had to switch back to P2P.
I’ve tried running it as an administrator, reinstalling it, etc. but nothing changed
Pierre
2026-05-08 2:03 AM
@PCu1 wrote:I’m having the same (sic?) problem on Windows.
My version is newer: STM32CubeIDE 2.1.1.
But @Wol was using JetBrains CLion - not STM32CubeIDE ?
2026-05-12 2:09 AM - last edited on 2026-05-12 3:02 AM by Andrew Neil
Hello
The "isTcpAvailable" is part of the internal probe API of STM32CubeMonitor. The problem may be a race condition when the probe is loaded inside CubeMonitor.
As PCu1 says "It worked for several years using TCP, but now I’ve had to switch back to P2P.", it may me due to a change. It may be linked to the updates done in STM32CubeMonitor v1.11.0.
Can you try with the version V1.10.0 ?
Thank you
Stephane
2026-05-12 10:20 AM
hello,
I tried with the version 1.10, and it works again in tcp shared mode
As you mention, something is different with the last version.
Pierre
2026-05-13 12:48 AM
Thanks a lot for your test.
The issue should be fixed in the Q3 release. (1.13)
Stephane