NECTO Studio Debugger

[innovalogica]

Hi there, I'm trying to run and debug the HDC1000 Example on a Clicker 4 with a STM32F407 MCU with NECTO Studio v18.0, C Compiler and mikroProg for STM32

I've installed the STM32CubeIDE_1.7.0 and set the mikroProg for STM32 debugger paths as follows:

C:/Users/Public/Documents/Mikroelektronika/mikroProg Suite For ARM/mikroProg Suite For ARM.exe
C:/ST/STM32CubeIDE_1.7.0/STM32CubeIDE/plugins/com.st.stm32cube.ide.mcu.externaltools.stlink-gdb-server.win32_2.0.0.202105311346/tools/bin/ST-LINK_gdbserver.exe
C:/Users/Public/Documents/Mikroelektronika/mikroProg Suite For ARM/ST-LINK_CLI.exe

When I run the debugger I get: "Failed to connect to: 127.0.0.1:61234.Failed to start debugger."

Any hint?

[filip]

Hi,

I believe my colleague has answered you regarding this issue.

Regards,
Filip.

[SSTIEVER]

I am having the same issue, what was the resolution to this issue
my paths are the same
the path for GDBserver
C:\ST\STM32CubeIDE_1.0.2\STM32CubeIDE\plugins\com.st.stm32cube.ide.mcu.externaltools.stlink-gdb-server.win32_2.0.0.202105311346\tools\bin

[SSTIEVER]

I was wondering what was the resolution? I get the same issue using the Clicker 2 for STM32 and the MikroProg. I have no issues programming but cannot enter debugger. My paths are the same as the person who started the thread

[filip]

Hi,

I believe you selected the wrong CLI. You are supposed to select the one that came with STM32CubeIDE and not the one inside mikroProg for STM32 folder.

I just tried this and it's working without any problems. I assume you blocked the gdb server access through network when it asked you for permission.
You have to allow the access in the firewall settings.
Also, just in case, I uploaded the gdb and cli files I used to Drive, you can download them and try with them.
You can download them from here:
https://drive.google.com/file/d/12tdmoe ... sp=sharing
and here:
https://drive.google.com/file/d/17W4pa4 ... sp=sharing

Regards,
Filip.