summaryrefslogtreecommitdiff
path: root/keyboards/enviousdesign/delirium/readme.md
diff options
context:
space:
mode:
Diffstat (limited to 'keyboards/enviousdesign/delirium/readme.md')
-rw-r--r--keyboards/enviousdesign/delirium/readme.md32
1 files changed, 32 insertions, 0 deletions
diff --git a/keyboards/enviousdesign/delirium/readme.md b/keyboards/enviousdesign/delirium/readme.md
new file mode 100644
index 0000000000..157a960303
--- /dev/null
+++ b/keyboards/enviousdesign/delirium/readme.md
@@ -0,0 +1,32 @@
+# EnvKB DELIRIUM
+
+![Image of EnvKB TKL PCB](https://i.imgur.com/a7UaS4mh.png)
+
+A low cost standard TKL design which takes inspiration from the CFTKB Mysterium. All versions are designed for reference Pi Picos.
+
+* Keyboard Maintainer: [Envious-Data](https://github.com/envious-data)
+* Hardware Supported:
+ * Delirium Prototype (`tkl/rev0`)
+ * Delirium (`tkl/rev1`)
+ * Delirium RGB (`tkl/rgb`)
+* Hardware Availability: [Mechboards](https://mechboards.co.uk/products/envkb-delirium-tkl-kit), [GitHub](https://github.com/Envious-Data/Env-KB)
+
+Make example for this keyboard (after setting up your build environment):
+
+ make enviousdesign/tkl/rgb:default
+
+Flashing example for this keyboard:
+
+ make enviousdesign/tkl/rgb:default:flash
+
+See the [build environment setup](https://docs.qmk.fm/#/getting_started_build_tools) and the [make instructions](https://docs.qmk.fm/#/getting_started_make_guide) for more information. Brand new to QMK? Start with our [Complete Newbs Guide](https://docs.qmk.fm/#/newbs).
+
+## Bootloader
+
+Enter the bootloader in 3 ways:
+
+* **Bootmagic reset**: Hold down the top left key and plug in the keyboard. This will also clear the emulated EEPROM, so it is a good first step if the keyboard is misbehaving.
+* **Physical reset**: Hold down the `BOOTSEL` button on the Pi Pico, then either plug the board in or press the `RESET` button.
+* **Keycode in layout**: Press the key mapped to `QK_BOOT`. In the pre-supplied keymaps it is on the second layer, replacing the Esc key.
+
+After entering the bootloader through one of the three methods above, the keyboard will appear as a USB mass storage device named `RPI-RP2`. If the CLI is unable to find this device, the compiled `.uf2` file can be manually copied to it. The keyboard will reboot on completion with the new firmware loaded.