aboutsummaryrefslogtreecommitdiffstats
path: root/keyboards/skog/README.md
diff options
context:
space:
mode:
authorMechMerlin <30334081+mechmerlin@users.noreply.github.com>2019-09-21 11:27:53 -0700
committerDrashna Jaelre <drashna@live.com>2019-09-21 11:27:53 -0700
commitfd19795879a92287faa93eb3900ce8d10f89ace3 (patch)
tree1bc5e25ff2f52e0b1bfd4bd289b164e7a890436a /keyboards/skog/README.md
parentf069e9fc09859baf03d940b6db47e95c50a24936 (diff)
downloadfirmware-fd19795879a92287faa93eb3900ce8d10f89ace3.tar.gz
firmware-fd19795879a92287faa93eb3900ce8d10f89ace3.tar.bz2
firmware-fd19795879a92287faa93eb3900ce8d10f89ace3.zip
[Keyboard] Move more percent boards into the percent directory (#6781)
* move canoe into percent directory * update readme for new make path * move skog into percent directory * update readme for new path and new instructions * update readme * fix error in naming
Diffstat (limited to 'keyboards/skog/README.md')
-rw-r--r--keyboards/skog/README.md61
1 files changed, 0 insertions, 61 deletions
diff --git a/keyboards/skog/README.md b/keyboards/skog/README.md
deleted file mode 100644
index 51a792b6b..000000000
--- a/keyboards/skog/README.md
+++ /dev/null
@@ -1,61 +0,0 @@
-Skog TKL by Percent
-==========================
-
-Keyboard Maintainer: QMK Community
-Hardware Supported: Skog PCB
-Hardware Availability: https://geekhack.org/index.php?topic=87953.0
-
-Make example for this keyboard (after setting up your build environment):
-
- make skog:default
-
-## Setting the board to bootloader mode
-
-If you're lucky, the programming script does this automagically for you. If
-however this doesn't work for you, you need to enter the bootloader mode manually
-by plugging the keyboard in while holding the bootloader key. If you did this
-correctly the LEDs will blink and you'll be able to flash your firmware.
-
-The bootloader key is in the top-right (Pause).
-
-## Flashing
-
-ps2avr(GB) boards use an atmega32a microcontroller and a different bootloader. It is not flashable using the regular QMK methods.
-
-Windows:
-1. Download [HIDBootFlash](http://vusb.wikidot.com/project:hidbootflash).
-2. Place your keyboard into reset.
-3. Press the `Find Device` button and ensure that your keyboard is found.
-4. Press the `Open .hex File` button and locate the `.hex` file you created.
-5. Press the `Flash Device` button and wait for the process to complete.
-
-macOS:
-1. Install homebrew by typing the following:
- ```
- /usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"
- ```
-2. Install `crosspack-avr`.
- ```
- brew cask install crosspack-avr
- ```
-3. Install the following packages:
- ```
- brew install python
- brew install pyusb
- brew install --HEAD`https://raw.githubusercontent.com/robertgzr/homebrew-tap/master/bootloadhid.rb
-
-4. Place your keyboard into reset.
-5. Flash the board by typing `bootloadHID -r` followed by the path to your `.hex` file.
-
-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).
-
-## Troubleshooting
-
-From my experience, it's really hard to brick these boards. But these
-tricks have been useful when it got stuck in a weird scenario.
-
-1. Try plugging the board in while holding the bootloader key. This will force
- it to boot only the bootloader without loading the firmware. Once this is
- done, just reflash the board with the original firmware.
-2. Sometimes USB hubs can act weird, so try connecting the board directly
- to your computer or plugging/unplugging the USB hub.