Merge pull request #8248 from PWN-GH/update_building_with_msys2

Update Building in Windows 10 or 11 with MSYS2.md

docs/development/Building in Windows 10 or 11 with MSYS2.md

@@ -1,6 +1,6 @@
 # General Info
 
-This is a guide on how to use Windows MSYS2 distribution and building platform to build iNav firmware. This environment is very simple to manage and does not require installing docker for Windows which may get in the way of VMWare or any other virtualization software you already have running for other reasons. Another benefit of this approach is that the compiler runs natively on Windows, so performance is much better than compiling in a virtual environment or a container. You can also integrate with whatever IDE you are using to make code edits and work with github, which makes the entire development and testing workflow a lot more efficient. In addition to MSYS2, this build environment also uses Arm Embedded GCC tolkit from The xPack Project, which provides many benefits over the toolkits maintained by arm.com
+This is a guide on how to use Windows MSYS2 distribution and building platform to build INAV firmware. This environment is very simple to manage and does not require installing docker for Windows which may get in the way of VMWare or any other virtualization software you already have running for other reasons. Another benefit of this approach is that the compiler runs natively on Windows, so performance is much better than compiling in a virtual environment or a container. You can also integrate with whatever IDE you are using to make code edits and work with github, which makes the entire development and testing workflow a lot more efficient. In addition to MSYS2, this build environment also uses Arm Embedded GCC tolkit from The xPack Project, which provides many benefits over the toolkits maintained by arm.com
 
 Some of those benefits are described here:
 
@@ -38,11 +38,18 @@ cd /c/Workspace
 # you can also check out your own fork here which makes contributing easier
 git clone https://github.com/iNavFlight/inav
 cd inav
-# switch to release you want or skip next 2 lines if you want latest
+```
+
+(Optional) Switch to a release instead of master
+```
 git fetch origin
-git checkout -b release_2.6.1 origin/release_2.6.1
+# on the next line, tags/5.0.0 is the release's tag, and local_5.0.0 is the name of a local branch you will create.
+# tags can be found on https://github.com/iNavFlight/inav/tags as well as the releases page
+git checkout tags/5.0.0 -b local_5.0.0
+# you can also checkout with a branch if applicable:
+# git checkout -b release_5.1.0 origin/release_5.1.0
 ```
-Now create the build and xpack directories and get the toolkit version you need for your inav version
+Now create the build and xpack directories and get the toolkit version you need for your INAV version
 ```
 mkdir build
 cd build
@@ -54,27 +61,27 @@ This will give you the version you need for any given release or master branch.
 
 https://github.com/xpack-dev-tools/arm-none-eabi-gcc-xpack/releases/
 ```
-# for version 2.6.1, version needed is 9.2.1
-wget https://github.com/xpack-dev-tools/arm-none-eabi-gcc-xpack/releases/download/v9.2.1-1.1/xpack-arm-none-eabi-gcc-9.2.1-1.1-win32-x64.zip
-unzip xpack-arm-none-eabi-gcc-9.2.1-1.1-win32-x64.zip
+# for INAV version 5.0.0, toolchain version needed is 10.2.1
+wget https://github.com/xpack-dev-tools/arm-none-eabi-gcc-xpack/releases/download/v10.2.1-1.1/xpack-arm-none-eabi-gcc-10.2.1-1.1-win32-x64.zip
+unzip xpack-arm-none-eabi-gcc-10.2.1-1.1-win32-x64.zip
 ```
 This is important, put the toolkit first before your path so that it is  picked up ahead of any other versions that may be present on your system
 ```
-export PATH=/c/Workspace/xpack/xpack-arm-none-eabi-gcc-9.2.1-1.1/bin:$PATH
+export PATH=/c/Workspace/xpack/xpack-arm-none-eabi-gcc-10.2.1-1.1/bin:$PATH
 cd /c/Workspace/inav/build
 ```
 You may need to run rm -rf * in build directory if you had any failed previous runs now run cmake
 ```
 # while inside the build directory
 cmake ..
 ```
-Once that's done you can compile the firmware for your controller
+Once that's done you can compile the firmware for your flight controller
 ```
 make DALRCF405
 ```
-To get a list of available targets in iNav, see the target src folder
-https://github.com/tednv/inav/tree/master/src/main/target
+To get a list of available targets in INAV, see the target src folder
+[https://github.com/tednv/inav/tree/master/src/main/target](https://github.com/inavflight/inav/tree/master/src/main/target)
 
 The generated hex file will be in /c/Workspace/inav/build folder
 
-At the time of writting this document, I believe this is the fastest, easiest, and most efficient Windows build environment that is available. I have used this approach several years ago and was very happy with it building iNav 2.1 and 2.2, and now I'm getting back into it so figured I would share my method
+At the time of writting this document, I believe this is the fastest, easiest, and most efficient Windows build environment that is available. I have used this approach several years ago and was very happy with it building INAV 2.1 and 2.2, and now I'm getting back into it so figured I would share my method