Skip to content

Releases: Marus/cortex-debug

V0.4.7-pre2

29 Sep 16:18
Compare
Choose a tag to compare
V0.4.7-pre2 Pre-release
Pre-release
  • 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

28 Sep 17:33
Compare
Choose a tag to compare
  • 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

28 Sep 22:08
Compare
Choose a tag to compare
V0.4.7-pre1 Pre-release
Pre-release
  • 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

27 Sep 15:25
Compare
Choose a tag to compare
  • 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

21 Sep 21:28
Compare
Choose a tag to compare
V0.4.5-pre3 Pre-release
Pre-release
  • 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.

V0.4.4

11 Sep 18:15
7c8e121
Compare
Choose a tag to compare

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

05 Sep 19:20
Compare
Choose a tag to compare

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

16 Aug 15:31
7fc1e9c
Compare
Choose a tag to compare

V0.4.1

11 Aug 20:33
Compare
Choose a tag to compare

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

V0.4.0

11 Aug 19:25
Compare
Choose a tag to compare

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

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