archifo
commented
8 months ago Finally, there indeed was a process sitting on port 6666, but not visible by windows' netstat ! There was a Powershell command to find it: $portProcessID = ( Get-NetTCPConnection -LocalPort 6666 ).OwningProcess ( Get-WmiObject win32process | Where-Object {$.ProcessID -eq $portProcessID } ).ProcessName and the to kill it Stop-Process -id $portProcessID Sorry for the disturbance.
I just managed to have all the software tooling installed on Windows 10 for my STM32F3DISCOVERY (the "F3") but when doing the final openocd test I got the following message. Any idea ? (Task manager doen't show any residual openocd process and netstat shows nobody sitting on port 6666).
C:\Users\franc>openocd -f interface/stlink.cfg -f target/stm32f3x.cfg xPack Open On-Chip Debugger 0.12.0+dev-01312-g18281b0c4-dirty (2023-09-04-22:32) Licensed under GNU GPL v2 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
Error: couldn't bind tcl to socket on port 6666: No error