V0.4.4

See ChangeLog for details. Lots of new features
https://github.com/Marus/cortex-debug/blob/master/CHANGELOG.md#v044

• Reset button
• Run without Debugging
• Auto-continue
• etc.

V0.4.3

V0.4.3

• Registers (CPU and Peripheral) now indicate with a highlighted value, which ones changed since last update. Other windows don't track changed values since they are managed by VSCode and no API avaibale.
• Line-based Breakpoints now visually indicate which line a breakpoint is actually set when different from what was requested. Normal VSCode behavior is to revert back to the original line when debug session ends.
• Perhpieral update will try to update as much as possible instead of bailing entire peripheral update after a single memory read failure. Failed reads are now indicated with 0xffffffff

V0.4.2

Please see https://github.com/Marus/cortex-debug/blob/master/CHANGELOG.md for details

V0.4.1

The clearSearch option was not working as intended. Affects OpenOCD users more than others.

V0.4.0

It is a BIG one. Please see the following for details of this release

https://github.com/Marus/cortex-debug/blob/master/CHANGELOG.md

V0.4.0.pre2

• Support for RTT (SEGGER Real Time Trace) with OpenOCD and JLink. See Issue#456 for more info
  • You can plot RTT data just like you could with SWO. The setup in launch.json is identical. See this comment
  • Channel sharing: You can use the same RTT channels in multiple ways. Corte-Debug reads the channel data from OpenOCD/JLink once and distributes to all subscribers (terminals & graphs). For instance, you can plot a channel and also look at its binary data in a terminal. Just use two decoders with the same channel (actually called port) number.
  • JLink RTT has a limitation that it can ONLY work with one channel (channel 0). There is another artifact with RTT channels where you may see output from a previous run at the very beginning.
  • The default polling interval in OpenOCD is 100 ms. If you are outputting more frequently, try lowering the interval in launch.json. 10ms seems more acceptable as a tradeoff between creating bus traffic and not losing/blocking data. If nothing changes, then OpenOCD does do much even if the interval is small.
• 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
• A change in this pre-release, you will see some debug information in the gdb-server console. You will also see messages output by the extension that are not part of the actual output in bright magenta. This will happen in all terminals (RTT, SWO and console)
• WARNING: The Adapter Output window in the OUTPUT tab will go away. Replaced by the 'gdb-server' in the TERMINAL tab.

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.14-pre2

New Features:

• Support for RTT (SEGGER RealTimeTrace) 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). We are not sure why yet. There is another artifact with channel 0 where you may see output from a previous run at the very beginning.
• 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.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