Add image of PCB

docs/firmware-debugging.md

@@ -65,15 +65,14 @@ Debug::Pin1::set(false); //same as ::low()
 ```
 
 The pins and pads are located on the PCB as shown here:
-![PCB header locations](./images/pcb-headers.jpg)
-
+![PCB header locations](./images/pcb-headers.png)
 
 
 ## Console output (printf debugging)
 
 You can view the console output by connecting a USB-UART cable to the TX pin of
 the debug header (next to the SWD header). The TX pin is labeled (upper-right
-pin). The bottom four pins are all GND. Settings are 115200, 8N1.
+pin). The bottom four pins are all GND. Settings are 115200, 8N1. See image above.
 
 Use `pr_dbg()`, `pr_warn()`, `pr_err()`, and `pr_trace()` for debug output. These
 require the `console/pr_dbg.hh` header.

docs/firmware-loading.md

@@ -12,6 +12,8 @@ in a section below:
 
 ### Load in RAM over SWD/JTAG
 
+![PCB header locations](./images/pcb-headers.png)
+
 This is the preferred method for active firmware development. It requires a
 JTAG programmer.
 
@@ -24,7 +26,7 @@ attach without loading.
 
 If you need to load new firmware, then do this:
 
-1) Install a jumper on `Control Expander` header that bridges the top-left pin
+1) Install a "Freeze jumper" on `Control Expander` header that bridges the top-left pin
 and the pin just to the right of it. Make sure you use the right header, it's
 the one above the Wifi header, near the `y` and `z` pots. The jumper should be
 horizontal, not vertical, on the top row of pins all the way to the left:
@@ -36,6 +38,8 @@ horizontal, not vertical, on the top row of pins all the way to the left:
            o  o  o  o
 ```
 
+See image above for reference.
+
 2) Power off and back on (full power-cycle is required).
 
 The console will show: