External SWO & new OpenOCD SWO

The "external" server type now supports SWO

OpenOCD now uses TCP ports to communicate with OpenOCD's SWO. Before it was using file IO which is unreliable (buffering) on Windows.

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

v0.3.7-pre4

• Fixed Issue #306. Support displaying more than 20 stack frames

v0.3.7-pre3

See ChangeLog for more detail

• A couple of SVD fixes. support for derivedFrom at the register level
• recover from missing addressBlock info in SVD files. Dummy peripherals we were not expecting
• Incorporate changes from PR Marus#302. This one may be important for those who are seeing incomplete variable windows.

v0.3.7-pre2

• Support for IAR produced elf files which just did not work with V0.3.6. They didn't quite work with earlier releases either. They are non-standard (kinda) compared to what gcc produced or what objdump documents.
• With the latest version of VSCode, there were too many popups coming. They are all harmless, but annoying. There were changed made to suppress these but they caused other problems.

We may just have to live with those popups (that are non-modal and disappear after a while) until we figure out how VSCode has changed. May take a while.

v0.3.7-pre1

Minor bug fix

• When runToMain was enabled there were 1-2 harmless popups when the program stopped in main. They were very frequent on Windows, less frequent on Linux and very rare if any on a Mac.

v0.3.6-pre1

Minor bug fix release

• When using multiple processors, TCP ports should be allocated consecutively, remote chance of failures avoided
• serialport binary module updated for latest Node.js/Electron
• Watch and hovers caused too many popups. Something changed in VSCode. These are now suppressed
• When runToMain was enabled, it caused a popup to appear for a failed stack trace. Again something changed in VSCode where it is requesting stack traces when program is not stopped.