STM32 Nucleo-144 development board with STM32F767ZIT6 MCU, supports Arduino, ST Zio and morpho connectivity

debug and ST-LINK

18 May 2017

I compiled and successfully tested the program via mbed-cli. I exported project to eclipse IDE, than compiled successfully again Now I tried to debug the application and seems that the only way is through openocd. The configuration is the following: /media/uploads/quipu/gdb_hw_main.jpg /media/uploads/quipu/gdb_hw_debugger.jpg /media/uploads/quipu/gdb_hw_startup.jpg So, I downloaded openocd.0.10.0 for windows and tried it. I get the following error:

openocd.0.10.0 console output

c:\Program Files\openocd-0.10.0\bin-x32>
c:\Program Files\openocd-0.10.0\bin-x32>openocd.exe -f ../scripts/board/NUCLEO-F767ZI.cfg
Open On-Chip Debugger 0.10.0
Licensed under GNU GPL v2
For bug reports, read
        http://openocd.org/doc/doxygen/bugs.html
srst_only separate srst_nogate srst_open_drain connect_assert_srst
Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD
adapter speed: 2000 kHz
adapter_nsrst_delay: 100
srst_only separate srst_nogate srst_open_drain connect_assert_srst
Info : Unable to match requested speed 2000 kHz, using 1800 kHz
Info : Unable to match requested speed 2000 kHz, using 1800 kHz
Info : clock speed 1800 kHz
Info : STLINK v2 JTAG v28 API v2 SWIM v18 VID 0x0483 PID 0x374B
Info : using stlink api v2
Info : Target voltage: 3.234301
Info : STM32F767ZITx.cpu: hardware has 8 breakpoints, 4 watchpoints
Info : accepting 'gdb' connection on tcp/3333
Info : device id = 0x10006451
Warn : STM32 flash size failed, probe inaccurate - assuming 2048k flash
Info : flash size = 2048kbytes
Error: auto_probe failed
Error: Connect failed. Consider setting up a gdb-attach event for the target to prepare target for GDB connect, or use 'gdb_memory_map disable'.
Error: attempted 'gdb' connection rejected

Someone has debug successful?