Hello,
With the latest release of the extension (3.6.4), the pre-release version (based on bundle manager) was moved to be the official release, thus making CLT obsolete.
My original launch file (based on CLT) does not work anymore, it included a Debug script, an Attach script, and a build+flash-only script.
To create a compatible launch file, I used the preset script - "STM32Cube: STM32 Launch ST-Link GDB Server" by using vscode's "create a launch.json file" option.
This does work for debugging, but creates a few issues-
a. Doe's not contain an "Attach" option - I could not find any help on the options for configuring the "stlinkgdbtarget" script type.
b. The "Memory Inspector" which is part of the extension pack, does not work anymore with the generated launch file. I get a "No debugger attached" while debugging.
c. The vscode reset debug button does not reset the core anymore - it re-flashes the device.
Can anyone help me create a launch file that will contain these features based on the new "stlinkgdbtarget" or some other script type?
It's pretty annoying that the pre-release was pushed to release, while it removes some useful features and also does not include a separate release for the "cube" CLI.
