2026-05-31 6:25 PM
STM32CubeIDE
Version: 2.1.1
Build: 28236_20260312_0043 (UTC)
How can I make sense of this ?
TMicroelectronics ST-LINK GDB server. Version 7.13.0
Copyright (c) 2026, STMicroelectronics. All rights reserved.
Starting server with the following options:
Persistent Mode : Disabled
Logging Level : 1
Listen Port Number : 61234
Status Refresh Delay : 15s
Verbose Mode : Disabled
SWD Debug : Enabled
Waiting for debugger connection...
Debugger connected
Waiting for debugger connection...
Debugger connected
Waiting for debugger connection...
-------------------------------------------------------------------
STM32CubeProgrammer v2.22.0
-------------------------------------------------------------------
Log output file: /tmp/STM32CubeProgrammer_Xj0e11.log
Error: Unable to connect to the target device, Access port is not valid.
Encountered Error when opening /home/soham/st/stm32cubeide_2.1.1/plugins/com.st.stm32cube.ide.mcu.externaltools.cubeprogrammer.linux64_2.2.400.202601091506/tools/bin/STM32_Programmer_CLI
Shutting down...
Exit.
I have added the "monitor flash mass_erase" to starter as explained in this thread,
I have set the boot switches into dev mode 0011:
2026-05-31 7:58 PM
Hi @maths ,
Have you followed this tutorial: Modify, rebuild and reload the firmware - stm32mpu ?
We’re moving the ST Community to a new platform to give you a better and more reliable community experience.