diff options
author | 4pplet <4pplet@protonmail.com> | 2021-06-22 00:09:16 +0200 |
---|---|---|
committer | GitHub <noreply@github.com> | 2021-06-22 08:09:16 +1000 |
commit | d7f352de98409803d3840ccead8cd4c67e848b0d (patch) | |
tree | 8eca7120e1364d441ff67941a0d20f2d1549d2e4 /keyboards/4pplet/eagle_viper_rep/readme.md | |
parent | 19990a21a95e47dddac8d0d15e4438f34c37c786 (diff) |
Adding "Eagle Viper Rep", open sourced Eagle/Viper V2/V3 PCB (#13020)
* adding revision A
* Update keyboards/4pplet/eagle_viper_rep/rev_a/rev_a.c
Co-authored-by: Drashna Jaelre <drashna@live.com>
* Update keyboards/4pplet/eagle_viper_rep/rev_a/rev_a.c
Co-authored-by: Drashna Jaelre <drashna@live.com>
* Update keyboards/4pplet/eagle_viper_rep/rev_a/rev_a.c
Co-authored-by: Drashna Jaelre <drashna@live.com>
* Update keyboards/4pplet/eagle_viper_rep/rev_a/rev_a.h
Co-authored-by: Drashna Jaelre <drashna@live.com>
* Update keyboards/4pplet/eagle_viper_rep/rev_a/rev_a.c
Co-authored-by: Drashna Jaelre <drashna@live.com>
* Update readme.md
Adding instruction on how to enter bootloader
* adding instruction on how to enter bootloader (DFU)
adding instruction on how to enter bootloader (DFU)
* updated description
* Update keyboards/4pplet/eagle_viper_rep/rev_a/halconf.h
Co-authored-by: Nick Brassel <nick@tzarc.org>
* Update keyboards/4pplet/eagle_viper_rep/rev_a/rev_a.c
Co-authored-by: Nick Brassel <nick@tzarc.org>
* Update keyboards/4pplet/eagle_viper_rep/rev_a/config.h
Co-authored-by: Nick Brassel <nick@tzarc.org>
* Update keyboards/4pplet/eagle_viper_rep/rev_a/chconf.h
Co-authored-by: Nick Brassel <nick@tzarc.org>
* Update keyboards/4pplet/eagle_viper_rep/rev_a/chconf.h
Co-authored-by: Nick Brassel <nick@tzarc.org>
* Update keyboards/4pplet/eagle_viper_rep/keymaps/default/keymap.c
Co-authored-by: Nick Brassel <nick@tzarc.org>
* Restoring palSetLineMode for working underglow
I was experiencing the same issue as this: https://github.com/qmk/qmk_firmware/issues/12655#issuecomment-844104659
sigprof helped me resolve this issue.
* Update rev_a.c
removing palSetLineMode again, works great after rebase. Thanks!
Co-authored-by: Drashna Jaelre <drashna@live.com>
Co-authored-by: Nick Brassel <nick@tzarc.org>
Diffstat (limited to 'keyboards/4pplet/eagle_viper_rep/readme.md')
-rw-r--r-- | keyboards/4pplet/eagle_viper_rep/readme.md | 19 |
1 files changed, 19 insertions, 0 deletions
diff --git a/keyboards/4pplet/eagle_viper_rep/readme.md b/keyboards/4pplet/eagle_viper_rep/readme.md new file mode 100644 index 0000000000..76415fd6c0 --- /dev/null +++ b/keyboards/4pplet/eagle_viper_rep/readme.md @@ -0,0 +1,19 @@ +# Viper/Eagle REP Rev A + +A alternative PCB for Viper and Eagle V2 and V3 + +* Keyboard Maintainer: [4pplet](https://github.com/4pplet) +* Hardware Supported: Viper/Eagle REP Rev A + +Make example for this keyboard (after setting up your build environment): + + make 4pplet/eagle_viper_rep/rev_a:default + +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). + +How to enter bootloader (DFU): +* Press and hold the button on the keyboard (the small one on the same side as the MCU) for more than 1 second. The keyboard will then enter bootloader (DFU) mode and it's ready to flash the firmware. +* Note: If holding the button a shorter time, the keyboard will just reset. If you want to exit bootloader mode without flashing a firmware, dissconnect the keyboard from your PC and reconnect it. + +Alternative option if the firmware is already pre-flashed: +* Unplug your keyboard, hold down the Spacebar and B at the same time, plug in your keyboard and wait a second before releasing the keys. Bootmagic lite is enabled by default. |