[paynterf]

I guess I don’t quite understand.  My interest in Visual GDB stems from finding that it integrates with VS2022, and specifically because there was a tutorial showing how to debug STM32 firmware.  Don’t you support your own tutorials?

 

TIA,

Frank

 

 

[paynterf]

Thanks for your reply.  Yes, I agree that the first issue I noted above is a wiring issue.  I was hoping someone familiar with that tutorial would be able to tell me what that red wire does or where it connects on the ST-LINK side.  The tutorial states that it is necessary to accomplish the ‘connect under reset’ procedure, but that doesn’t tell me how to connect it up.  Is the red wire connected to GND, +V, or some dynamic output – I can’t tell.

TIA,

Frank

 

[paynterf]

I went ahead and installed Open OCD and continued with the tutorial, but I wasn’t able to successfully upload the ‘blink’ program to the blue pill.  Here is the GDB session log.  I have also attached a screenshot showing the project settings.

 

Your VisualGDB trial expires in 30 days!
C:\Users\Frank\Documents\ArduinoData\packages\STMicroelectronics\tools\xpack-arm-none-eabi-gcc\13.2.1-1.1\bin\\arm-none-eabi-gdb –interpreter mi “C:/Users/Frank/Documents/VisualGDB/Projects/ArduinoProject1/Output/Generic_STM32F1_series/Debug/ArduinoProject1.ino.elf”
:62210: Interrupted function call.
:62210: Interrupted function call.
“monitor” command not supported by this target.
“monitor” command not supported by this target.
“monitor” command not supported by this target.
You can’t do that when your target is `exec’
The program is not being run.
Invalid thread id: 1
No registers.
Invalid thread id: 1
No registers.
Invalid thread id: 1
No registers.
Invalid thread id: 1
No registers.
The program is not being run.

Attachments:

You must be logged in to view attached files.

[Author]

Posts