Update to use VSCode for PlatformIO (in addition to Atom)

[aufdenkampe]

Presently only discusses Atom for PlatformIO.
Add advice and info for how to install and work with VSCode, to support both.

[aufdenkampe]

Here is the list of issues that we had with RPBCWD workshop participants Installing PlatformIO for Atom.

• Uncaught channel closed error, but this was fixed by Jan 25 with platformio-atom-ide-terminal 2.9.0. See assertion failed!, atom 1.31.2 x64 platformio/platformio-atom-ide-terminal#613
• Assertion Failed! Error when trying to run Serial Monitor. See Assertion Failed! Windows10 Pro platformio/platformio-atom-ide-terminal#571 (comment)
• There appear to be other related issues that may have been related to the ones above, and seem to have been fixed in early March with platformio-atom-ide-terminal 2.9.1 and making sure that Python 2.7.x is installed rather than Python 3.6.x. See Blinking cursor/no output: Terminal is not responding platformio/platformio-atom-ide-terminal#668 (comment)

The short story is that these might have all been fixed.

[aufdenkampe]

Our workaround in December was to have people use VSCode. However, there were also a couple of additional things that we needed to learn:

• Changing Serial Monitor baud rates can't be done through the IDE, but rather requires a new line in the PlatformIO.ini file. See:
  • https://docs.platformio.org/en/latest/ide/vscode.html#serial-port-monitor and
  • https://docs.platformio.org/en/latest/projectconf/section_env_monitor.html#projectconf-monitor-speed
• Don't install the Arduino plugin, as it will interfere with PlatformIO

It seems there were a few other config issues, but I can't remember.

[aufdenkampe]

Added new sections in Episode 4 in March that mostly covers above.

[aufdenkampe]

I think 8c7d8f8 finalizes this short list. We can create a future issue if we want to provide greater support for VSCode.