From 9c43f8e44f379dd5f244f0bbaa3a2730d8d61276 Mon Sep 17 00:00:00 2001
From: gator96100 <jupuerzi@gmx.at>
Date: Tue, 29 Dec 2020 17:50:43 +0100
Subject: [PATCH] Updated wsl instructions

---
 .../Windows-Installation-Instructions.md      | 39 ++++++++++++-------
 1 file changed, 26 insertions(+), 13 deletions(-)

diff --git a/doc/md/Installation_Instructions/Windows-Installation-Instructions.md b/doc/md/Installation_Instructions/Windows-Installation-Instructions.md
index ea0505268..6d4477de2 100644
--- a/doc/md/Installation_Instructions/Windows-Installation-Instructions.md
+++ b/doc/md/Installation_Instructions/Windows-Installation-Instructions.md
@@ -149,18 +149,31 @@ Note that it may take a quite long time for a freshly plugged Proxmark3 to be vi
 
 Now you're ready to follow the [compilation instructions](/doc/md/Use_of_Proxmark/0_Compilation-Instructions.md).
 
-## Color text on windows 10
-In later versions of windows 10 you may be able to get color to work by setting this registry key
-```
-[HKEY_CURRENT_USER\Console]
-    "VirtualTerminalLevel"=dword:00000001
-```
-You also need to disable "use legacy console" in the cmd.exe properties, or set the following registry key
-```
-[HKEY_CURRENT_USER\Console]
-    "ForceV2"=dword:00000001
-```
-After making these changes, you will need to start a new command prompt (cmd.exe) to ensure its using the new settings.
 
-If after making these changes (and restarting proxmark3.exe) you get extra characters and no color text, set either key to 0 or enable legacy mode again (and restart the command prompt).
+## (Optional) Visual Studio Code debugging
 
+Download and install [J-Link Software and Documentation pack for Windows](https://www.segger.com/downloads/jlink/JLink_Windows.exe) 
+
+Enter WSL prompt (`wsl` or `start windows terminal`)  and from there, follow the [Linux Installation Instructions](/doc/md/Installation_Instructions/Linux-Installation-Instructions.md) for Ubuntu, summarized here below:
+
+Install dependencies
+```sh
+sudo apt-get install --no-install-recommends binutils-arm-none-eabi gdb openocd gdb-multiarch
+```
+
+The J-Link debugger requires `arm-none-eabi-gdb` which was replaced with `gdb-multiarch`. In order to use the J-Link debugger link `arm-none-eabi-gdb` to `gdb-multiarch`:
+```sh
+sudo ln -s /usr/bin/gdb-multiarch /usr/bin/arm-none-eabi-gdb
+```
+
+Setup the Visual Studio Code configuration, by going into your project folder and run:
+```sh
+./.vscode/setup.sh
+```
+
+and launch Visual Studio Code
+```sh
+code .
+```
+_note_
+Please install the recommended Visual Studio Code extensions in order for debugging to work.