summaryrefslogtreecommitdiff
path: root/keyboards/1upkeyboards/sweet16v2/readme.md
diff options
context:
space:
mode:
authorziptyze <mwcordier@gmail.com>2022-10-05 17:52:18 -0400
committerGitHub <noreply@github.com>2022-10-05 22:52:18 +0100
commit6313258f23ae22943396dad7ae56a1904d5697ea (patch)
tree4735490b26df2e658ead713efd989d24459188a7 /keyboards/1upkeyboards/sweet16v2/readme.md
parent248f98bdad5c10d96649ceb5acad53cba1f513ad (diff)
Product changes to 1up lineup (#18382)
Diffstat (limited to 'keyboards/1upkeyboards/sweet16v2/readme.md')
-rw-r--r--keyboards/1upkeyboards/sweet16v2/readme.md39
1 files changed, 39 insertions, 0 deletions
diff --git a/keyboards/1upkeyboards/sweet16v2/readme.md b/keyboards/1upkeyboards/sweet16v2/readme.md
new file mode 100644
index 0000000000..e3f5859f96
--- /dev/null
+++ b/keyboards/1upkeyboards/sweet16v2/readme.md
@@ -0,0 +1,39 @@
+# sweet16v2
+
+A 4x4 macropad with RGB inswitch lighting and underglow.
+
+* Keyboard Maintainer: [ziptyze](https://github.com/ziptyze)
+* Hardware Supported: 1upkeyboards Sweet 16 v2
+* Hardware Availability: [1upkeyboards](https://1upkeyboards.com/)
+
+Make example for this keyboard using an atmel-based controller (after setting up your build environment):
+
+ make 1upkeyboards/sweet16v2/promicro:default
+
+Flashing example for this keyboard using an atmel-based controller:
+
+ make 1upkeyboards/sweet16v2/promicro:default:flash
+
+Make example for this keyboard using an rp2040-based controller (after setting up your build environment):
+
+ make 1upkeyboards/sweet16v2/kb2040:default
+
+Flashing example for this keyboard using an rp2040-based controller:
+
+ make 1upkeyboards/sweet16v2/kb2040: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 for atmel-based controllers:
+
+* **Bootmagic reset**: Hold down the key at (0,0) in the matrix (usually the top left key or Escape) and plug in the keyboard
+* **Physical reset button**: Briefly press the button on the back of the PCB - some may have pads you must short instead
+* **Keycode in layout**: Press the key mapped to `RESET` if it is available
+
+
+Enter the bootloader in 2 ways for rp2040-based controllers:
+
+* **Bootmagic reset**: Hold down the key at (0,0) in the matrix (usually the top left key or Escape) and plug in the keyboard
+* **Bootsel button**: Hold the bootsel button on controller and plug in the keyboard \ No newline at end of file