expand on make your own section

Author: kercre123

documents/2. Available CFW/RainbOS.md documents/2. Available CFW/5. RainbOS.mddocuments/2. Available CFW/RainbOS.md renamed to documents/2. Available CFW/5. RainbOS.md

@@ -14,12 +14,12 @@ RainbOS is based off of [WireOS,] (https://github.com/os-vector/wire-os) but wit
   - Anki had an old feature in prototype firmware where Vector would request to "Play BlackJack?" You could chose to start a game of BlackJack with Vector by saying yes, or decide to disapoint Vector with a no. Sadly, this feature was taken out before Vector's release. GamingTime added it back, and it is no fully functional once again.
 - Many more small changes, which you can checkout on the [RainbOS Repository.] (https://github.com/gamingtimevr/new-victor)
 - MORE TO COME IN THE FUTURE!
-  -RainbOS is a work-in-progress! As GamingTime's skills and understandings grow, so will the features of RainbOS. Stay tuned for the future!
+  - RainbOS is a work-in-progress! As GamingTime's skills and understandings grow, so will the features of RainbOS. Stay tuned for the future!
 
-  ## Where to Find
+## Where to Find
 
-  You can find all RainbOS related things on its GitHub repository, "https://github.com/gamingtimevr/new-victor"
+You can find all RainbOS related things on its GitHub repository, "https://github.com/gamingtimevr/new-victor"
 
-  You can find all GamingTime realted stuff on his GitHub account, "https://github.com/gamingtimevr" or his Discord, @gamingtimevr.
+You can find all GamingTime realted stuff on his GitHub account, "https://github.com/gamingtimevr" or his Discord, @gamingtimevr.
 
-  YOU CAN FIND INSTALLATION INSTRUCTIONS ON THE GITHUB REPOSITROY'S README. WEBSITE SOON.
+YOU CAN FIND INSTALLATION INSTRUCTIONS ON THE GITHUB REPOSITROY'S README. WEBSITE SOON.

documents/6. Make Your Own CFW/2. forking.md

@@ -4,21 +4,17 @@ Fork wire-os and its submodules.
 
 ## How
 
-- Fork these repos. When choosing names, just replace the `wire-os` parts with the name you desire:
+1. Fork these repos. When choosing names, just replace the `wire-os` parts with the name you desire:
     -   [wire-os](https://github.com/os-vector/wire-os)
     -   [wire-os-victor](https://github.com/os-vector/wire-os-victor)
     -   [wire-os-externals](https://github.com/os-vector/wire-os-externals)
-
-- Let's say, for example, we called it `diode-os`, and our GitHub username is diode123. Run in a Linux terminal:
-
-```
+2. Let's say, for example, we called it `diode-os`, and our GitHub username is diode123. Now we have diode123/diode-os, diode123/diode-os-victor, and diode123/diode-os-externals. Run in a Linux terminal:
+```bash
 cd ~
 git clone https://github.com/diode123/diode-os --recursive
 ```
-
-- Replace the wire-os-victor submodule with yours:
-
-```
+3. Replace the wire-os-victor submodule with yours:
+```bash
 cd diode-os
 git rm -f anki/victor
 rm -rf anki/victor .git/modules/anki/victor
@@ -27,5 +23,15 @@ git submodule add https://github.com/diode123/diode-os-victor anki/victor
 git commit -m "new submodule"
 git push
 ```
-
-- You have successfully created diodeOS.
+4. Clone diode-os-victor separately and replace the EXTERNALS submodule.
+```bash
+cd ~
+git clone https://github.com/diode123/diode-os-victor --recursive
+cd wire-os-victor
+git rm -f EXTERNALS
+rm -rf EXTERNALS
+git commit -m "remove externals"
+git submodule add https://github.com/diode123/diode-os-externals EXTERNALS
+git commit -m "update externals"
+git push
+```

documents/6. Make Your Own CFW/3. how.md

@@ -1,12 +1,46 @@
 # How to Develop
 
-The majority of your changes will probably be in the /anki folder, which is built from diode-os-victor.
+Here, we will perform two steps in one: learning how to make modifications to the code, and how to change the final screen in CCIS which describes what the builds are.
 
-## Set up your dev environment
+## What IDE should I use?
 
-You should have two folders: diode-os-victor and diode-os.
+Anki tended to use Visual Studio Code - just use that.
 
-Do NOT just make all of you changes in diode-os/anki/victor, despite it being the same repo. `diode-os-victor` can be built standalone, and deployed to a robot with `rsync`. These builds should not end up in a Yocto environment.
+## What OS should I use?
 
-TODO
+An M-series Macs, or an x86_64 Linux PC - toolchains are only available for these platforms.
 
+## Let's make a modification!
+
+1. Open up the diode-os-victor folder in VSCode.
+2. Open up `animProcess/src/cozmoAnim/faceDisplay/faceInfoScreenManager.cpp`
+3. Modify lines 69-72 to match the details of your new CFW.
+4. Open a terminal and run `cd ~/diode-os-victor`
+5. Build the code by running this: `./build/build-v.sh`
+
+## Deploy
+
+When you deploy code to a robot, his /anki folder gets replaced. This can be done on a laptop (reference: Ryzen 7840U, 16GB RAM). You do not need to build a whole OTA every time you want to test a change. ./build/build.sh just builds a /anki folder.
+
+1. Open a terminal and `cd ~/diode-os-victor`
+2. Echo your robot's IP address to robot_ip.txt: `echo "192.168.1.50" > robot_ip.txt`
+3. Run: `curl -o robot_sshkey https://github.com/kercre123/unlocking-vector/raw/refs/heads/main/ssh_root_key`
+4. Deploy: `./build/deploy-v.sh`
+
+## Build an OTA with your change
+
+1. Run `cd ~/diode-os`
+2. Update the submodule: 
+```bash
+cd anki/victor
+git pull origin main
+cd ../../
+git add .
+git commit -m "vp"
+git push
+```
+3. Build:
+```bash
+./build/build.sh -bt dev -v 1
+```
+4. Your OTA will be at: ./_build/vicos-3.0.1.1d.ota.