error testing debugger and debugging: couldn't bind tcl to socket on port 6666: No error

[josancardenasm]

Hi all. I can't debug my code on my stm32f1xxx based board with my stlink v3. Two days ago i could do it without problems.

This is the error that i get in the testing functionality.

C:\Users\Jacar\AppData\Local\VisualGDB\EmbeddedDebugPackages\com.sysprogs.arm.openocd\bin\openocd.exe -c "gdb_port 50064" -c "telnet_port 50063" -f interface/stlink.cfg -f target/stm32f1x.cfg -c init -c "reset init" -c "echo VisualGDB_OpenOCD_Ready"
Open On-Chip Debugger 0.10.0 (2020-03-10) [https://github.com/sysprogs/openocd]
Licensed under GNU GPL v2
libusb1 09e75e98b4d9ea7909e8837b7a3f00dda4589dc3
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
Info : auto-selecting first available session transport "hla_swd". To override use 'transport select '.
Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD
Info : clock speed 1000 kHz
Info : STLINK v3 JTAG v5 API v3 SWIM v1 VID 0x0483 PID 0x374F
Info : using stlink api v3
Info : Target voltage: 3.296598
Info : Stlink adapter speed set to 1000 kHz
Info : stm32f1x.cpu: hardware has 6 breakpoints, 4 watchpoints
Info : Listening on port 50064 for gdb connections
target halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0xfffffffe msp: 0xfffffffc
VisualGDB_OpenOCD_Ready
Error: couldn't bind tcl to socket on port 6666: No error