summaryrefslogtreecommitdiffstats
path: root/keyboards/1upkeyboards/sweet16v2/readme.md
diff options
context:
space:
mode:
authorlokher <lokher@gmail.com>2022-12-06 17:10:48 +0800
committerlokher <lokher@gmail.com>2022-12-07 15:50:49 +0800
commita336c2c5005251e4cb0f3a62ccabdb4cfccad915 (patch)
tree3c948b631a5e3b6f940dabe02fad3c7487e6f350 /keyboards/1upkeyboards/sweet16v2/readme.md
parent27fc28fd2ff52e079a5bc58d6aaea4c752420615 (diff)
Merge upstream master to 2022 Q4 breaking change
Diffstat (limited to 'keyboards/1upkeyboards/sweet16v2/readme.md')
-rw-r--r--keyboards/1upkeyboards/sweet16v2/readme.md39
1 files changed, 0 insertions, 39 deletions
diff --git a/keyboards/1upkeyboards/sweet16v2/readme.md b/keyboards/1upkeyboards/sweet16v2/readme.md
deleted file mode 100644
index e3f5859f96..0000000000
--- a/keyboards/1upkeyboards/sweet16v2/readme.md
+++ /dev/null
@@ -1,39 +0,0 @@
-# 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