feat: suzyq documentation

pages/suzyqboard/accessing-ccd.mdx

@@ -0,0 +1,62 @@
+---
+title: Accessing Closed Case Debugging
+description: Access Closed Case Debugging (CCD) using the SuzyQ Board
+---
+
+This information is taken from [MrChromebox's WP disabling page](https://docs.mrchromebox.tech/docs/firmware/wp/disabling.html).
+Please check it out for more information.
+
+# Step 1: Enabling Closed Case Debugging (CCD)
+
+1. Power on the device to the login screen (booted into Developer Mode).
+2. Open VT-2 terminal: press `[CTRL+ALT+F2]` (F2 is the right arrow).
+3. Login as `root`.
+4. Open the CCD: run `gsctool -a -o`.
+5. You will be prompted to press the `PP` (physical presence) button several times. On almost all devices, this means to press the power button. Opening the CCD requires you to press the `PP` button several times over a 2-3 minute period.
+6. When the open CCD process is complete, you will see a message showing `PP Done!` and the device will reboot in Normal/Verified Boot Mode.
+7. Re-enable developer mode and continue with the instructions below.
+
+# Step 2: Disabling Write Protection
+
+1. Power on the device to the login screen (booted into Developer Mode).
+2. Open VT-2 terminal: press `[CTRL+ALT+F2]` (F2 is the right arrow).
+3. Login as `root`.
+4. Plug in your SuzyQable - the USB-C end normally connects to the upper/left USB-C port.
+5. Verify the cable is connected properly:
+    Run `ls /dev/ttyUSB*`
+    The output of this command should output 3 items, `ttyUSB0`, `ttyUSB1`, and `ttyUSB2`.
+    If the 3 ttyUSB devices are not listed, try reversing the orientation of the USB-C cable, and try another port. If there is still no result, there may be a problem with your cable/adapter, or your ChromeOS device may not support connecting the cable in loopback mode as is done here. In that case, connect the USB-A end of the cable to another device and run the command from there.
+6. Run the following commands. This will disable hardware write protect.
+    - `echo "wp false" > /dev/ttyUSB0`
+    - `echo "wp false atboot" > /dev/ttyUSB0`
+7. Run `echo "ccd reset factory" > /dev/ttyUSB0`.
+    This ensures that you will be able to unbrick the device (if needed) using a SuzyQable.
+    It also disables AP RO Firmware Verification, and is mantory if flashing the firmware on a device with a Gen2 CR50 chip (aka `Ti50`).
+8. Run `gsctool -a -I` to verify the CCD is opened, and that the factory values are set.
+    The current value for all CCD flags should be set to Y/Always.
+9. Run `crossystem wpsw_cur` and verify it returns `0`.
+10. Reboot.
+
+# Disable AP RO Firmware Verification
+
+On 2023+ ChromeOS devices using a Gen2 CR50 security chip (aka `Ti50`), there is a new feature where the CR50 will verify the RO portion of the AP firmware and the state of the software write protect registers (both range and enable) at boot. If you want to flash custom firmware, you **must** use the CCD method above to disable firmware write protection, regardless if the device supports disablement via battery disconnect or a jumper as well.
+
+For more info, see the [Chromium documentation](https://www.chromium.org/chromium-os/developer-library/guides/device/ro-firmware-unlock/) on this feature.
+
+NOTE - If you disabled firmware WP via CCD and reset your CCD flags with `ccd reset factory` (as per the instructions above), you can skip this step, as `ccd reset factory` will set ` AllowUnverifiedRo` to `always`.
+
+## Step 1: Verify the device has a Ti50
+
+1. Open VT-2 terminal: press `[CTRL+ALT+F2]` (F2 is the right arrow or refresh key).
+2. Login as `root`.
+3. Run `gsctool -a -I | grep AllowUnverifiedRo`.
+4. If that command has any output, your device has a Ti50. If you get no output or an error, your device either has a Cr50 or no GSC at all.
+
+## Step 2: Disable RO verification
+
+1. Unlock the GSC by running `gsctool -a -o`.
+2. Run `gsctool -a -I AllowUnverifiedRo:always`.
+3. Press the power button when prompted.
+
+NOTE - If your device has a Ti50 and you don't disable RO verification, flashing full rom will (temporarily) brick the device.
+Check the [MrChromebox documentation](https://docs.mrchromebox.tech/docs/firmware/wp/disabling.html#recovering-a-device-bricked-due-to-ro-verification) on what to do in this case.

pages/suzyqboard/flash-firmware.mdx

@@ -0,0 +1,6 @@
+---
+title: Flashing Firmware
+description: Flash Firmware using the SuzyQ Board
+---
+
+#

pages/suzyqboard/hacking.mdx

@@ -0,0 +1,6 @@
+---
+title: Hacking
+description: General Hacking and Miscellaneous information for the SuzyQ Board
+---
+
+#

pages/suzyqboard/index.mdx

@@ -4,3 +4,30 @@ description: Learn about using the Fyra SuzyQ Board to hack your Chromebook
 ---
 
 # Introduction
+
+The SuzyQ Board is an open-source Chromebook debug board sold by Fyra Labs. It is a versatile tool for Chromebook hacking and debugging. This board works exactly like a [Google SuzyQable](https://chromium.googlesource.com/chromiumos/third_party/hdctools/+/master/docs/ccd.md#suzyq-suzyqable). Any guides or documentation you find elsewhere on using 'SuzyQables' will work with the Fyra Labs SuzyQ Board.
+
+Huge shoutout to the [Chrultrabook Project](https://docs.chrultrabook.com/) for their assistance in making this product.
+
+
+## FAQ
+
+### Does my Chromebook support using a SuzyQ Board?
+
+Please refer to [this list](https://www.chromium.org/chromium-os/developer-library/reference/development/developer-information-for-chrome-os-devices/), if your device supports Closed Case Debugging (CCD), it will support our SuzyQ Board.
+
+### Where can I purchase a SuzyQ Board?
+
+You may purchase a SuzyQ Board [on the Fyra Shop](https://fyralabs.com/FDS010).
+
+### Where are the schematics?
+
+* [Online schematics view on PCBhub](https://pcbhub.org/projects/53)
+* [GitHub repo](https://github.com/FyraLabs/suzyqboard)
+
+
+### What Does FDS010 Mean?
+
+| Fyra | Category | Product | Version | Revision |
+|------|----------|---------|---------------|---------------|
+| Fyra | Developer Tools | SuzyQ |  01 | 0 |

pages/suzyqboard/unbricking.mdx

@@ -0,0 +1,6 @@
+---
+title: Unbricking
+description: Unbrick your ChromeOS Device using the SuzyQ Board
+---
+
+#