V0.3.14-pre1

New Features:

• Support for RTT (SEGGER Real Time Trace) with OpenOCD. JLink is not supported yet as you can use JLink tools. Once OpenOCD works our we can look at other gdb-servers that support RTT
  See Issue#456 for more info
• demangle is by default true. You can turn it off in launch.json

Please see the article below to see how to Install from a VSIX file. Whatever you do, do not double click on it on Windows as that will attempt to install into Visual Studio rather than VSCode

https://stackoverflow.com/questions/42017617/how-to-install-vs-code-extension-manually

V0.4.0.pre1

This will be a major release with a lot of changes and many new features. The TERMINAL area of VSCode is utilized a lot more heavily to enable bidirectional communication with the firmware. It is used for RTT, SWO and Semi-hosting.

New Features:

• Support for RTT (SEGGER Real Time Trace) with OpenOCD and JLink. See Issue#456 for more info
  • JLink RTT has a limitation that it can ONLY work with one channel (channel 0). There is another artifact with channel 0 where you may see output from a previous run at the very beginning.
• SWO console and binary decoded text data now appears in a "TERMINAL" tab instead in the "OUTPUT" tab
• All gdb-server (OpenOCD, JLink, etc.) output is also in the "TERMINAL" tab. In there you can also interact with your semihosting
• Support in debugger for Jump to Cursor, thanks to PR#417
• demangle is on by default. You can turn it off in launch.json

Please see the article below to see how to Install from a VSIX file. Whatever you do, do not double click on it on Windows as that will attempt to install into Visual Studio rather than VSCode

https://stackoverflow.com/questions/42017617/how-to-install-vs-code-extension-manually

v0.3.13

New Features:

• "external" server type now supports SWO. It works in the following way depending on "source"
  • "source": "probe" -- We do not recommend this method as there are issues with File I/O buffering causing delays and stalls, especially on Windows. Use a "socket" instead. It will use an auto-created temporary file name.
    • On Windows, it will use normal file-io
    • On Linux/Mac, it will use an OS supported FIFO which is more efficient than a normal file
  • "source": "socket" (best option if available)
    • You MUST specify the "swoPort": "[host:]port" option in the "swoConfig"
  • "source": "file", then the file specified by "swoPath" will be used. Same caveats as when"source" is "probe" but you have control over the file-name
• "openocd" server type will now use a TCP port for SWO instead of file/fifo for a more reliable connection across all platforms. Port selection is automatic. You can still use a serial port in which case, "source": "serial".
• Support for pyoocd SWO over a TCP port. You can specify the SWO source as probe. This is rather new for pyocd, so it hasn't been extensively tested.

Bug fixes and minor changes:

• Use the pyocd executable with gdbserver as first argument instead of the pyocd-gdbserver executable. This is a potentially breaking change but long overdue as the old use model has been deprecated by pyocd.
• Few other minor changes

v0.3.12-pre1

• Attempting to fix issues with not being able to set breakpoints in rust and assembly code.

Also includes:

• new binary modules for macOS for v1.53
• A new runToEntryPoint configuration property to replace runToMain allowing the actual entry point name to be configured
• A fix for SWD support on P&E Micro GDB server

V0.3.11 - Pre Release 2

More additions to the tooltips for field and register nodes

• Display the reset value for nodes in the tooltip
• Flags fields and registers as being read only and write only as appropriate in tooltips

V0.3.11 - Pre Release

New Features:

• Enable ChibiOS RTOS support for the J-Link server
• Added additional details to the the register and field level hover tooltips in the peripheral register view.

V0.3.10

This feature upgrades our VSCode dependency for the extension - as a result V0.3.10 will only support the Visual Studio Code version 1.52 and above.

Also wanted to call out the gdbPath user setting that was introduced at V0.3.8 (but not included in the changelog) - this allows users to override the complete path to GDB including the executable name - allowing the use of gdb-multiarch.

New Features:

• Added support for Linux ARM hosts (both aarch64 and armhf) to the binary modules
• Added the ability to pin certain perhiperals in the Perhiperal Register view so they remain at the top of the view. Thanks to manuargue for the PR. This provides an alterate solution to issue #370
• Added the ability to set gdbPath as an override in your launch.json file.

V0.3.8

1. New Feature:
   • Added initial support for STMicroelectronic's official ST-LINK GDB server. This server is currently only supported on Windows as we are having difficulties with getting it to run inside the visual studio environment on Linux and Windows. Also, this GDB server does not currently support SWO output through the probe. Big thanks to hwmaier for their PR that provided most of this support.
2. Issues Fixed:
   • Updated binary modules to support current versions of VS Code, fixing the support for serial based SWO output - some older versions were also removed to download size. Currently this is supported on macOS (x64), Linux (x64) and Windows (x64, x86); support for Linux AArch64 and armhf architectures is coming soon.
   • Fixed Issue #382 - GDB commands in configuration (such as postLaunchCommands) that had had quotation marks (") were not handled correctly when being passed to GDB
   • Fixed Issue #374 - Breakpoints are not cleared in GDB when exiting a debug session - this can cause issues in GDB servers like J-Link that support flash breakpoints as they would not have a chance to remove the modifications made to the flash memory to support that feature.
   • Fixed issue with not being able to properly disable function break points

V0.3.8 - Pre-release 2

Fix issues with the experimental stlink gdb server support

v0.3.8-pre

This is a pre-release of version 0.3.8

Should fix the following issues:

• Delete all breakpoints upon disconnect (this should prevent issues with flash-breakpoints corrupting flash)
• Fix issues with enabling/disabling function breakpoints
• Add initial support for the official STMicroelectronics GDB server