Forum Replies Created
-
Posts
-
It seems the problem is not the new BSP. I use git and reverted all changes, install the old bsp.
Compiling a new project is possible without failure.
With new OpenOCD 20200114-0-10.0 i got following Output.
What could I do to fix it?
<span>C:\Users\Daniel\AppData\Local\VisualGDB\EmbeddedDebugPackages\com.sysprogs.arm.openocd\bin\openocd.exe -c “gdb_port 58890” -c “telnet_port 58889” -f interface/stlink-v2.cfg -f C:/Users/Danny/AppData/Local/Temp/tmpD0B4.tmp -c init -c “reset init” -c “echo VisualGDB_OpenOCD_Ready”
Open On-Chip Debugger 0.10.0 (2020-01-14) [https://github.com/sysprogs/openocd]
Licensed under GNU GPL v2
libusb1 09e75e98b4d9ea7909e8837b7a3f00dda4589dc3
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
WARNING: interface/stlink-v2.cfg is deprecated, please switch to interface/stlink.cfg
Info : auto-selecting first available session transport “hla_swd”. To override use ‘transport select <transport>’.
Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD
Info : clock speed 50 kHz
Info : STLINK v2 JTAG v34 API v2 SWIM v7 VID 0x0483 PID 0x3748
Info : using stlink api v2
Info : Target voltage: 3.013368
Info : Stlink adapter speed set to 50 kHz
Info : stm32g0x.cpu: hardware has 4 breakpoints, 2 watchpoints
Info : Listening on port 58890 for gdb connections
Info : Stlink adapter speed set to 50 kHz
target halted due to debug-request, current mode: Thread
xPSR: 0xf1000000 pc: 0x08004220 msp: 0x20002000
Info : Stlink adapter speed set to 50 kHz
VisualGDB_OpenOCD_Ready
Info : Listening on port 6666 for tcl connections
Info : Listening on port 58889 for telnet connections
Info : accepting ‘gdb’ connection on tcp/58890
Info : device id = 0x10016466
Warn : Cannot identify target as a STM32 family.
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
</span>I use OPEN OCD 20191216-0.10.0 and can not debug my stm32g031K8 with a ST-Link/V2.
No chance to connect to the target.
What can I do?
Following test output:
<span>C:\Users\danny\AppData\Local\VisualGDB\EmbeddedDebugPackages\com.sysprogs.arm.openocd\bin\openocd.exe -c “gdb_port 51116” -c “telnet_port 51115” -f interface/stlink-v2.cfg -f C:/Users/Daniel/AppData/Local/Temp/tmp19CC.tmp -c init -c “reset init” -c “echo VisualGDB_OpenOCD_Ready”
Open On-Chip Debugger 0.10.0 (2019-12-16) [https://github.com/sysprogs/openocd]
Licensed under GNU GPL v2
libusb1 09e75e98b4d9ea7909e8837b7a3f00dda4589dc3
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
WARNING: interface/stlink-v2.cfg is deprecated, please switch to interface/stlink.cfg
Info : auto-selecting first available session transport “hla_swd”. To override use ‘transport select <transport>’.
Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD
Info : clock speed 50 kHz
Info : STLINK v2 JTAG v34 API v2 SWIM v7 VID 0x0483 PID 0x3748
Info : using stlink api v2
Info : Target voltage: 3.218361
Info : Stlink adapter speed set to 50 kHz
Info : stm32g0x.cpu: hardware has 4 breakpoints, 2 watchpoints
Info : Listening on port 51116 for gdb connections
Info : Stlink adapter speed set to 50 kHz
target halted due to debug-request, current mode: Thread
xPSR: 0xf1000000 pc: 0x08002d78 msp: 0x20002000
Info : Stlink adapter speed set to 50 kHz
VisualGDB_OpenOCD_Ready
Info : Listening on port 6666 for tcl connections
Info : Listening on port 51115 for telnet connections
Info : accepting ‘gdb’ connection on tcp/51116
Info : device id = 0x10016466
Warn : Cannot identify target as a STM32 family.
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
</span>Double checked it. The file exist.
Is it possible to check my VS2015 Solution?
https://1drv.ms/u/s!AspuupI-wTK0h1ZPlDPqyDqNyxBF
Hi,
here is the output
1> VisualGDB: Run “cmd.exe /c “C:\SysGCC\arm-eabi\bin\make.exe” CONFIG=Debug” in directory “C:\Users\daniel\Desktop\STM32F0Discovery\STM32F0” on local computer
1>C:\Users\daniel\Desktop\STM32F0Discovery\STM32F0\Makefile(429): warning : overriding recipe for target `Debug/system_stm32f0xx.o’
1>C:\Users\daniel\Desktop\STM32F0Discovery\STM32F0\Makefile(185): warning : ignoring old recipe for target `Debug/system_stm32f0xx.o’
1> make: *** No rule to make target../../../STM32F0Discovery/STM32F0/Src/system_stm32f0xx.c', needed byDebug/system_stm32f0xx.o’. Stop.
1> ————————————————————-
1> Command exited with code 2
1> Executable: cmd.exe
1> Arguments: /c “C:\SysGCC\arm-eabi\bin\make.exe” CONFIG=Debug
1> Directory: C:\Users\daniel\Desktop\STM32F0Discovery\STM32F0
1>VisualGDB : error : Command-line action failed
1>EXEC : error : Build has failed. See the Output window for more details.
1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.MakeFile.Targets(41,5): error MSB3073: Der Befehl “”C:\Program Files (x86)\Sysprogs\VisualGDB\\VisualGDB.exe” /build “C:\Users\daniel\Desktop\STM32F0Discovery\STM32F0\STM32F0.vcxproj” “/solution:C:\Users\daniel\Desktop\STM32F0Discovery\STM32F0\STM32F0.sln” “/config:Debug” “/platform:Win32″” wurde mit dem Code 1 beendet.
========== Erstellen: 0 erfolgreich, 1 fehlerhaft, 0 aktuell, 0 übersprungen ==========I evaluate VisualGDB today with same problem.
cubeMX v4.19.0
visualGDB 5.2
Blink project work fine on my discovery board.
Failure after build:
stm32f0xx_hal_con.h: No such file or directory
Is here anyone who can help? Otherwise VisualGDB is not a alternative because I need stm32cubemx.
Thanks
Daniel
