diff --git a/docs/configuring-vscode.md b/docs/configuring-vscode.md
index 572f9933..69edf772 100644
--- a/docs/configuring-vscode.md
+++ b/docs/configuring-vscode.md
@@ -40,6 +40,7 @@ An extension called Cortex-Debug has recently been released which is designed sp
 Note: If developing on Windows, you should have `arm-none-eabi-gdb` and `openOCD` on your PATH.
 
   * Make sure you have the Firmware folder as your active folder
+  * Set `CONFIG_DEBUG=true` in the tup.config file
   * Flash the board with the newest code (starting debug session doesn't do this)
   * Debug -> Start Debugging (or press F5)
   * The processor will reset and halt.
diff --git a/docs/developer-guide.md b/docs/developer-guide.md
index dfa871b5..6f351070 100644
--- a/docs/developer-guide.md
+++ b/docs/developer-guide.md
@@ -85,7 +85,7 @@ Some instructions in this document may assume that you're using a bash command p
   * __Note 2__: 8-2018-q4-major seems to have a bug on Windows.  Please use 7-2018-q2-update.
 * [Tup](http://gittup.org/tup/index.html)
 * [GNU MCU Eclipse's Windows Build Tools](https://github.com/gnu-mcu-eclipse/windows-build-tools/releases)
-* [OpenOCD](http://gnuarmeclipse.github.io/openocd/install/). 
+* [OpenOCD](https://github.com/xpack-dev-tools/openocd-xpack/releases/). 
 * [ST-Link/V2 Drivers](http://www.st.com/web/en/catalog/tools/FM147/SC1887/PF260219)
 
 <br>
diff --git a/docs/troubleshooting.md b/docs/troubleshooting.md
index 6ba3752e..bd02b737 100644
--- a/docs/troubleshooting.md
+++ b/docs/troubleshooting.md
@@ -113,7 +113,7 @@ You can also try increasing `<axis>.controller.config.vel_limit_tolerance`. The
  * **Linux**: Type `lsusb` to list all USB devices. Verify that your ODrive is listed.
  * **Linux**: Make sure you [set up your udev rules](getting-started#downloading-and-installing-tools) correctly.
  * **Windows**: Right-click on the start menu and open "Device Manager". Verify that your ODrive is listed.
- * **Windows**: Use the [Zadig utility](http://zadig.akeo.ie/) to verify the driver is set to `libusb-win32`.
+ * **Windows**: Use the [Zadig utility](http://zadig.akeo.ie/) to verify the driver is set to `libusb-win32`. Note that there are two options listed in Zadig for Odrive: `ODrive 3.x Native Interface (Interface 2)` and `ODrive 3.x CDC Interface (Interface 0)`. Only the native interface should have `libusb-win32` while the CDC interface should use `WinUSB`.
  * Ensure that no other ODrive program is running
  * Run `odrivetools` with the `--verbose` option.
  * Run `PYUSB_DEBUG=debug odrivetools` to get even more log output.