[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
This commit is contained in:
parent
f069e9fc09
commit
fd19795879
@ -1,5 +1,4 @@
|
||||
CANOE
|
||||
========
|
||||
# Canoe
|
||||
|
||||
A 65% keyboard with some RGB
|
||||
|
||||
@ -9,7 +8,7 @@ Hardware Availability: https://geekhack.org/index.php?topic=92418.0
|
||||
|
||||
Make example for this keyboard (after setting up your build environment):
|
||||
|
||||
make canoe:default
|
||||
make percent/canoe:default
|
||||
|
||||
Flashing
|
||||
|
||||
@ -33,12 +32,13 @@ macOS:
|
||||
```
|
||||
3. Install the following packages:
|
||||
```
|
||||
brew install python
|
||||
pip install pyusb
|
||||
brew install python3
|
||||
pip3 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 [build environment setup](https://docs.qmk.fm/#/getting_started_build_tools) then the [make instructions](https://docs.qmk.fm/#/getting_started_make_guide) for more information.
|
||||
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).
|
@ -1,5 +1,4 @@
|
||||
Skog TKL by Percent
|
||||
==========================
|
||||
# Skog TKL
|
||||
|
||||
Keyboard Maintainer: QMK Community
|
||||
Hardware Supported: Skog PCB
|
||||
@ -7,21 +6,14 @@ Hardware Availability: https://geekhack.org/index.php?topic=87953.0
|
||||
|
||||
Make example for this keyboard (after setting up your build environment):
|
||||
|
||||
make skog:default
|
||||
make percent/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
|
||||
Flashing
|
||||
|
||||
ps2avr(GB) boards use an atmega32a microcontroller and a different bootloader. It is not flashable using the regular QMK methods.
|
||||
|
||||
**Reset Key:** Hold down the key located at `K00`, commonly programmed as Pause while plugging in the keyboard.
|
||||
|
||||
Windows:
|
||||
1. Download [HIDBootFlash](http://vusb.wikidot.com/project:hidbootflash).
|
||||
2. Place your keyboard into reset.
|
||||
@ -40,22 +32,14 @@ macOS:
|
||||
```
|
||||
3. Install the following packages:
|
||||
```
|
||||
brew install python
|
||||
brew install pyusb
|
||||
brew install --HEAD`https://raw.githubusercontent.com/robertgzr/homebrew-tap/master/bootloadhid.rb
|
||||
brew install python3
|
||||
pip3 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.
|
||||
|
||||
**Please Note:** You will need to use the `EEP_RST` keycode first, followed by unplugging/replugging the board to get RGB underglow effects to work.
|
||||
|
||||
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.
|
Loading…
Reference in New Issue
Block a user