V0.4.8-pre4

• Store register/peripheral settings in the appropriate folder instead of the first folder
• Kill gdb-server if the user kills/exits gdb without using the proper disconnect/Stop buttons/process/commands
• VSCode was terminating Cortex-Debug before it was done. st-util exit behavior was also not clean as it did not exit on a disconnect.
• Preliminary support for data watchpoints
• SVD now can allow no merge of consecutive addresses with a -1 specified for svdAddrGapThreshold. This will make peripheral updates very slow but certain devices may need this option.
• You can now save the output of a gdb-server into a text file by specifying cortex-debug.dbgServerLogfile in User/Workspace settings. This will save output from the servers from all sessions (not just the recent ones). This is primarily for debugging and for users when submitting issues.
• Pathnames for gdb-servers can be OS specific. For instance cortex-debug.openocdPath can be suffixed with one of .linux, .osx or .windows. For instance cortex-debug.openocdPath.windows is used only on Windows and if that is missing, it will default looking for cortex-debug.openocdPath`.
• SWO output can now be logged (saved) to a file just like RTT output

Please see the article below for Install instructions for a VSIX file. 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.8.pre3

• Store register/peripheral settings in the appropriate folder instead of the first folder of a Workspace
• Kill gdb-server if the user kills/exits gdb without using the proper disconnect/Stop buttons/process/commands
• VSCode was terminating Cortex-Debug before it was done. st-util exit behavior was also not clean as it did not exit on a disconnect.

Please see the article below for Install instructions for a VSIX file. 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.8-pre2

• Kill gdb-server if the user kills/exits gdb without using the proper disconnect/Stop buttons/process/commands
• VSCode was terminating Cortex-Debug before it was done. st-util exit behavior was also not clean as it did not exit on a disconnect.

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

• Fixed a regression for STLink gdbserver. It was in fact accidentally working in prior releases. The real bug is now fixed. Issue #494
• We may have finally found a way to exit OpenOCD without having to kill it and OpenOCD not hanging around after the session ends. This is of course dependent on OpenOCD behaving as documented. Thanks to #482 and @bohdan-tymkiv for a solution
• Timestamps for RTT and SWO have been standardized to be of the form [ISO-Date-Time, +NNNNNNms] where the first part is the date/time of day and the NNNNNNms is the number of milliseconds elapsed since the debug session began.
• timestamp is now an option for SWO console decoders. Default is false. A timestamp is output only when a newline is received or a timeout of 5 seconds

V0.4.7-pre3

• Fixed a regression for STLink gdbserver. It was in fact accidentally working in prior releases. The real bug is now fixed
• We may have finally found a way to exit OpenOCD without having to kill it and OpenOCD not hanging around after the session ends. This is of course dependent on OpenOCD behaving as documented. Thanks to #482 and @bohdan-tymkiv for a solution
• Timestamps for RTT and SWO have been standardized to be of the form [ISO-Date-Time, +NNNNNNms] where the first part is the date/time of day and the NNNNNNms is the number of milliseconds elapsed since the debug session began.
• timestamp is now an option for SWO console decoders. Default is false. A timestamp is output only when a newline is received or a timeout of 5 seconds

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

• Fixed a regression for STLink gdbserver. It was in fact accidentally working in prior releases. The real bug is now fixed
• We may have finally found a way to exit OpenOCD without having to kill it and OpenOCD not hanging around after the session ends. This is of course dependent on OpenOCD behaving as documented. Thanks to #482 and @bohdan-tymkiv for a solution

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.6

• Bugfix: Issue #493 In the previous release, we were trying to end OpenOCD using a SIGINT first and then SIGTERM. The way VSCode works, this did not work in production releases. Reverting back to the previous method of just using SIGTERM. Unfortunately. Still looking for a better method to end OpenOCD.

V0.4.7-pre1

• Fixed a regression for STLink gdbserver. It was in fact accidentally working in prior releases. The real bug is now fixed

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.5

• Support for resume/suspend after Launch/Attach. With new UI features added to VSCode, the Stop button (after Launch) can now also be used for a Disconnect using keyboard shortcuts. The reverse is true when using an Attach type session. But this requires co-operation from the gdb-server to comply. Certain versions of OpenOCD do comply, JLink always seems to resume (see issue $481). Provided the gdb-server cooperates, the expected behavior now when you end a debug session is:
  • Stop will leave the program in a halted state
  • Disconnect will let the program continue
• You can now have RTT console output lines contain a timestamp. Use the timestamp option for the RTT decoder. Default is false (no timestamp)
• Issues #482 addressed for JLink. It always cleanly exits on it own. OpenOCD is still an issue where it has to be killed which once in a blue moon does not seem to work.
• Integrated PR #480 -- creates .vscode director if it doesn't exist for saving register/peripheral states.
• PRs #489, #490, #488, #478 submitted by @trond-snekvik merged. They fix issues and enhances your experience with Cortex-Debug in various ways. Thank you @trond-snekvik

V0.4.5-pre3

• Support for resume/suspend after Launch/Attach. With new features added to VSCode, the Stop button (after Launch) can now also be used for a Disconnect using keyboard shortcuts. The reverse is true when using an Attach type session. But this requires co-operation from the gdb-server to comply. Certain versions of OpenOCD do comply, JLink always seems to resume.
• Issues #482 and #481 partially addressed
• Integrated PR #480 -- creates .vscode director if it doesn't exist for saving register/peripheral states.