stuff

Author: kercre123

documents/3. Software Architecture/partitions.md

@@ -6,14 +6,20 @@ TODO
 
 ## OEM
 
+Mounts to the /factory folder. Contains calibration logs and cloud keys which are used for mTLS.
+
 ## EMR
 
-The EMR partiton (Electronic Medical Record) contains the calibration info of the robot as well as it's ESN.
+The EMR partiton (Electronic Medical Record) contains the calibration info of the robot, its ESN, its model number, and its packout status.
 
 ## boot_a and boot_b
 
 These are the boot partitions. These partitons contain a ramdisk which is loaded which will then load a system partition matching the slot ID you are in.
 
 ## system_a and system_b
 
-Vector go Beep Boop.
+The partition Vector's full Linux OS exists in, corresponding to the boot slot. Slot a = system_a. Slot b = system_b.
+
+## userdata
+
+Encrypted, mounted to /data. Used to store user information like faces, pictures, and settings.

documents/4. Operating System/os.md

@@ -2,6 +2,8 @@
 
 Vector runs on an embedded Linux image built with Yocto Jethro.
 
+This describes Vector's *original* os. WireOS (and other CFW) uses a newer version of Yocto.
+
 ## What is Yocto?
 
 Yocto is a toolkit for creating your own embedded Linux "distribution".

documents/6. Make Your Own CFW/1. prerequisites.md

@@ -8,6 +8,8 @@ Vector's software is complex and monstrous.
     -   For reference, my desktop has:
         -   Ryzen 5 5700X3D
         -   32GB 3200MHz RAM
+    -   My desktop takes ~50 minutes to build a whole OTA from a clean clone.
+        -   Takes much less time (~5 minutes) after first build.
     -   For a comfortable experience, you should have at least 16GB of RAM.
 - A Vector.
     -   You'll need something to test your code on.

documents/8. Terminology/terminology.md

@@ -4,4 +4,8 @@
     - in WireOS and Viccyware and such, the underlying OS may still be referred to as VicOS
 - CFW - Custom FirmWare
 - DDL - Digital Dream Labs
-- SLAM - Simultaneous Localization And Mapping
+- SLAM - Simultaneous Localization And Mapping
+- ESN - Electronic Serial Number
+    - e.g. 00e20145
+- QSN - Qualcomm Serial Number
+    - burned into the CPU, 10 numbers

site/3. Software Architecture/partitions.html

@@ -643,6 +643,15 @@
     </span>
   </a>
 
+</li>
+      
+        <li class="md-nav__item">
+  <a href="#userdata" class="md-nav__link">
+    <span class="md-ellipsis">
+      userdata
+    </span>
+  </a>
+  
 </li>
 
     </ul>
@@ -1240,6 +1249,15 @@
     </span>
   </a>
 
+</li>
+      
+        <li class="md-nav__item">
+  <a href="#userdata" class="md-nav__link">
+    <span class="md-ellipsis">
+      userdata
+    </span>
+  </a>
+  
 </li>
 
     </ul>
@@ -1265,12 +1283,15 @@ <h1 id="partitions">Partitions<a class="headerlink" href="#partitions" title="Pe
 <p>Vector's partition table is pretty similar to that of an Android phone, except he has a couple extra ones added by Anki.</p>
 <p>TODO</p>
 <h2 id="oem">OEM<a class="headerlink" href="#oem" title="Permanent link">&para;</a></h2>
+<p>Mounts to the /factory folder. Contains calibration logs and cloud keys which are used for mTLS.</p>
 <h2 id="emr">EMR<a class="headerlink" href="#emr" title="Permanent link">&para;</a></h2>
-<p>The EMR partiton (Electronic Medical Record) contains the calibration info of the robot as well as it's ESN.</p>
+<p>The EMR partiton (Electronic Medical Record) contains the calibration info of the robot, its ESN, its model number, and its packout status.</p>
 <h2 id="boot_a-and-boot_b">boot_a and boot_b<a class="headerlink" href="#boot_a-and-boot_b" title="Permanent link">&para;</a></h2>
 <p>These are the boot partitions. These partitons contain a ramdisk which is loaded which will then load a system partition matching the slot ID you are in.</p>
 <h2 id="system_a-and-system_b">system_a and system_b<a class="headerlink" href="#system_a-and-system_b" title="Permanent link">&para;</a></h2>
-<p>Vector go Beep Boop.</p>
+<p>The partition Vector's full Linux OS exists in, corresponding to the boot slot. Slot a = system_a. Slot b = system_b.</p>
+<h2 id="userdata">userdata<a class="headerlink" href="#userdata" title="Permanent link">&para;</a></h2>
+<p>Encrypted, mounted to /data. Used to store user information like faces, pictures, and settings.</p>
 
 
 

site/4. Operating System/os.html

@@ -1299,6 +1299,7 @@
 
 <h1 id="vectors-os">Vector's OS<a class="headerlink" href="#vectors-os" title="Permanent link">&para;</a></h1>
 <p>Vector runs on an embedded Linux image built with Yocto Jethro.</p>
+<p>This describes Vector's <em>original</em> os. WireOS (and other CFW) uses a newer version of Yocto.</p>
 <h2 id="what-is-yocto">What is Yocto?<a class="headerlink" href="#what-is-yocto" title="Permanent link">&para;</a></h2>
 <p>Yocto is a toolkit for creating your own embedded Linux "distribution".</p>
 <p>Vector does not "run Yocto Linux"!</p>

site/6. Make Your Own CFW/1. prerequisites.html

@@ -1235,6 +1235,10 @@ <h2 id="technical-requirements">Technical requirements<a class="headerlink" href
 <li>32GB 3200MHz RAM</li>
 </ul>
 </li>
+<li>My desktop takes ~50 minutes to build a whole OTA from a clean clone.<ul>
+<li>Takes much less time (~5 minutes) after first build.</li>
+</ul>
+</li>
 <li>For a comfortable experience, you should have at least 16GB of RAM.</li>
 </ul>
 </li>

site/8. Terminology/terminology.html

@@ -1158,6 +1158,14 @@ <h1 id="terminology">Terminology<a class="headerlink" href="#terminology" title=
 <li>CFW - Custom FirmWare</li>
 <li>DDL - Digital Dream Labs</li>
 <li>SLAM - Simultaneous Localization And Mapping</li>
+<li>ESN - Electronic Serial Number<ul>
+<li>e.g. 00e20145</li>
+</ul>
+</li>
+<li>QSN - Qualcomm Serial Number<ul>
+<li>burned into the CPU, 10 numbers</li>
+</ul>
+</li>
 </ul>