openocd | The GNU MCU Eclipse OpenOCD | Code Editor library

Cannot open source file avr/io.h (dependency of hal.h)

You appear to be using ChibiOS whhich has a file hal.h which includes halconf.h which includes mcuconf.h. Clearly you appear to have an AVR port of ChibiOS where you need STM32 or ARM Cortex-M support.

But, how VS Code can find dependencies before compiling?

The same way as the compiler/pre-processor do, by having include paths configured, parsing the project files and accounting for any externally defined (command line) macros.

I also was wondering if I should add a path for main.cpp file and other C and CPP files in the configuration file of VS Code to solve these problems?

I believe it will parse project files in any case. It only needs to find the header files included in a source file to provide context for the parsing of the sourcefile.

For debugging, I don't see any debugger in the list, though I installed openOCD and add the path in the environment variable

That is an entirely different question - post a new question for that.

Turned out that the cable I used was just a power cable which didn't support data transmission.

With a proper mini USB cable that has all 4 lines it worked right away.

I found the issue: I scale up the clock speed without switching to appropriate Flash Latency so the debugger will lose the track of program address as mentioned here, in Clocks and initial settings part: https://vjordan.info/log/fpga/first-steps-with-the-stm32f4.html

There has been a fix recently in the documentation.

As explained in this link: https://github.com/raspberrypi/pico-examples/issues/8

When setting a Raspberry Pi up as described in the Getting Started guide, two problems arise when launching the debugger:

Setting "gdbpath" in launch.json is marked as not allowed When launching the setting is ignored, and arm-none-eabi-gdb is used, which is unavailable It seems that setting "cortex-debug.gdbpath" can only be set in settings.json

So remove.

"gdbpath" : "gdb-multiarch" from launch.json and add "cortex-debug.gdbPath": "gdb-multiarch" to settings.json.

With linux you could use the USB-VendorID/ProductID to choose the config file.

You could start via a shell script like

When you connect to the target with target remote GDB asks the target for its current register state, including the $pc value. GDB does NOT (at that point) modify the remote state in any way.

When you first connected the remote reported a $pc value of 0x0. If the remote changed state for some reason, lets say, you ran something on the remote, then the $pc value might change, say to 0x08000bbe.

If you then disconnect and reconnect the remote target might still have a $pc value of 0x08000bbe which is what GDB will see.

As was mentioned in the comments, GDB is just trying to map the $pc value onto the debug information in your program. The ?? shows that GDB can't find any symbols at address 0x0. While GDB did find the symbol __c_m_sh_syscall near to address 0x08000bbe. However, this is information doesn't mean much at this point, you've not yet loaded anything onto the target, so you're not really in the function __c_m_sh_syscall, it's just the current address of the remote.

When you do the load command this is when GDB loads the executable onto the target, and writes to the $pc.

TL;DR; If your work flow is target remote then load, don't worry about the state of the target immediately after the target remote, this is just whatever random state happens to be in the target when you connect.

Assuming your Tcl code has a bit in its heart doing sendBack [eval $script], you'd change it to do this:

Your linker script

And the culprit has been found! It appears the st-util debugger (from the project mentioned above) causes an error somehow. openocd works like a charm and with that the minimal code above works.

Anyway, bug reports to write and all that...

Thank you all so much for verifying my assembler and helping me with dotting all the t's and crossing all the i's!