qmk_firmware/keyboards/skog/README.md

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.
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 and the make instructions for more information. Brand new to QMK? Start with our Complete Newbs Guide.

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.