Suddenly CubeIDE doesn't run and debug mode.

YShin.5 · ‎2022-07-18

I deleted CubeIDE and reinstalled the latest version 1.10.1, but it still doesn't work. The test environment was tested with NUCLEO-G071RB with the most basic code. Even if you delete and reset the RUN and DEBUG configration by referring here and there, only the warning as shown in the figure pops up. Thank you for your help.

STMicroelectronics ST-LINK GDB server. Version 7.0.0

Starting server with the following options:

Persistent Mode: Disabled

LogFile Name: C:\Users\alko11110039\STM32CubeIDE\workspace_1.10.1\app\Debug\st-link_gdbserver_log.txt

Logging Level: 31

Listen Port Number : 61234

Status Refresh Delay: 15s

Verbose Mode: Enabled

SWD Debug: Enabled

InitWhile: Enabled

COM frequency = 4000 kHz

Target connection mode: Under reset

Reading ROM table for AP 0 @0xf0000fd0

Hardware watchpoint supported by the target

ST-LINK Firmware version : V2J40M27

Device ID: 0x460

PC: 0xffffffffe

ST-LINK device status: HALT_MODE

ST-LINK detects target voltage = 3.24 V

ST-LINK device status: HALT_MODE

ST-LINK device initialization OK

SwvSrv state change: 0 -> 1

Waiting for debugger connection...

Waiting for connection on port 61234...

Stm32Device, pollAndNotify running...

Waiting for connection on port 61235...

Accepted connection on port 61234...

Debugger connected

Waiting for debugger connection...

Waiting for connection on port 61234...

GDB session thread running

GdbSessionManager, session started: 1

GDB session terminated: Client connection lost

GdbSessionManager, session terminated: 1

GdbSrv, last session terminated, signal dispose

Stopping port 61234

Received stop for port 61234, not accepting new connections.

GdbSrv, deInit entry.

Shutting down...

GdbSessionManager, deInit entry.

GDB session disposed: 1

GdbSessionManager, deInit exit

SwvSrv deInit entry

Stopping port 61235

Stopping port 61234

Received stop for port 61235, not accepting new connections.

SwvSrv deInit exit

Stm32Device, closeDevice() entry

Stm32Device, pollAndNotify stopped

Stm32Device, closeDevice() exit

Stm32Device, deInit success

GdbSrv, deInit exit.

Exit.

Markus GIRDLAND · ‎2022-07-21

Hello there,

I tried this on two different workstations in the office but I can't seem to reproduce. Could you give more details about the steps you do in order to get this problem?

Is it only this specific project or every project?

YShin.5 · ‎2022-07-21

Thanks for your help.

Everything from example projects to development projects is included.

I installed CubeIDE on another note PC and confirmed that there was no problem during the test. Is there a problem with my note PC? I am worried about whether it will be resolved by formatting the note PC.

SSchi.4 · ‎2022-07-22

Hi,

I have the exact same error.

For me, this error came up when I did a Firmware update at my STMG071-DISCO Board.

It also happens on a firmware update of the ST-Link/v2 Debugger/Programmer. So both are not working anymore.

I still had an old STMG071-DISCO Board, which still works with its initial Firmware. I therefore wanted to downgrade the Firmware from the upgraded DISCO board back to its initial version. I downloaded the ST-Link007 V2.38.27 and programmed the DISCO board with its initial firmware. However the error still remains the same.

For everyone else, who did not yet do the firmware update, the following helped for me: Revoke the firmware upgrade request, when clicking on Debugging in the STMCubeMX IDE.

YShin.5 · ‎2022-07-24

Thanks for your help.

So, isn't there still a solution? My problem is also occurring on the PCB board for development including the STMG071-DISCO Board. Please help us for smooth development.

AScha.3 · ‎2022-08-04

Hi,

did you try the openOCD debug ? if not, try.

btw i think, i had the same problem long time ago; the simple solution was to delete a log file, that keeps some information and causing this problem. but i dont remember the name...maybe you can find it with searching.

maybe - this was it:

If after new STM32CubeIDe 1.5.0 install, debug is still KO, you can kill STLink Server process with task manager and start it manually.

To do so, In a cmd prompt window, cd to C:\Program Files (x86)\STMicroelectronics\stlink_server and run stlinkserver.exe -d with the board connected to see if he detects it.

You should see the libusb version updated to 1.0.23 and the serial number of your board.

If you see it, you can exit the window and retry to debug.

https://community.st.com/s/global-search/debug%20no%20more%20working?topicId=0TO0X000000y2j7WAA&topicName=STM32CubeIDE

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

mattias norlander · ‎2022-08-10

Did you manage to solve the issue?

Q1: Are you using ST-LINK server in combination with ST-LINK GDB server? If, so uncheck it in the debug configuration. Does it work with ST-LINK GDB server?

Q2: Did it work with OpenOCD instead?