...

content/assignments/dev-board/_index.md

@@ -6,10 +6,10 @@ next: assignments/dev-board/assembly
 weight: 2
 ---
 
-For this assignment you will be assembling an **EnVision DevBoard**.
+For this assignment you will be assembling an **EnVision Mini DevBoard**.
 
 This assignment is the next piece to making your own VUMeter. The DevBoard contains the microcontroller that will control the light shield.
 
-The DevBoard is _not_ as simple as the previous, and will require additional equipment. This time, you will use a **stencil** to apply **solder paste** _exactly_ on each pad.
+The DevBoard is *not* as simple as the previous, and will require additional equipment. This time, you will use a **stencil** to apply **solder paste** _exactly_ on each pad.
 
 Hope you don't have shaky hands!

content/assignments/dev-board/assembly.md

@@ -61,7 +61,7 @@ Now we will start placing our components.
 
 As you work, you can request the components you need from the TAs at the component table.
 
-To find out what you need, refer to the **B**ill **O**f **M**aterials [here](https://github.com/ECE-196/DevBoard/blob/main/BOM.xlsx).
+To find out what you need, refer to the BOM[^1] [here](https://github.com/ECE-196/DevBoard/blob/main/BOM.xlsx).
 
 Once you have a component from the B.O.M. you can see which PCB labels the component corresponds to in the _designator_ column. With tweezers,
 carefully place each component on to the labeled position on the PCB. Make sure that the components you place are centered on the pads, and be careful not
@@ -122,3 +122,5 @@ Place the connector back down, remove the heat gun, and look again at your pins
 - If your solder paste didn't turn out clean, it is much easier to just repaste. Don't try to make it work if you know you can do better.
 - Double check the BOM as you place components, while you can take components off of the paste if, it can easily cause bridging.
 - Take your time on every step, this is a very delicate process.
+
+[^1]: A **B**ill **O**f **M**aterials (BOM) is a document outlining the required components quantities and placements for a board.

content/assignments/full-stack/BLE/_index.md

@@ -0,0 +1,7 @@
+---
+title: BLE
+type: docs
+prev: assignments/full-stack/
+next: assignments/full-stack/ble/tutorial
+weight: 2
+---

content/assignments/full-stack/USB/_index.md

@@ -0,0 +1,53 @@
+---
+title: USB
+type: docs
+prev: assignments/full-stack/
+next: assignments/full-stack/usb/firmware
+weight: 1
+---
+
+Let's take a look at the hierarchy of the system we are about to design:
+
+```mermaid
+graph LR
+    subgraph "DevBoard"
+        subgraph "Front End"
+            A2(LED)
+        end
+
+        subgraph "Back End"
+            B2(Serial)
+            C2(Callbacks)
+            D2(Logic)
+        end
+
+        B2 --> C2 --> D2 --> A2
+        D2 --> B2
+    end
+
+    subgraph "Computer (Python)"
+        subgraph "Front End"
+            A1(UI)
+            B1(Alerts)
+        end
+
+        subgraph "Back End"
+            C1(Callbacks)
+            D1(Logic)
+            E1(Serial)
+        end
+
+        A1 --> C1 --> D1 <--> E1
+        D1 --> B1
+    end
+
+    B2 <--> E1
+```
+
+Now, I know this looks complicated, but we will tackle each block one by one, nice and slow.
+
+Once you are done with this, you will have a solid understanding of creating systems involving
+bidirectional communication between 2 devices, which is *super* useful for *a ton* of
+applications (including your final project).
+
+So let's get started.