qmk_firmware

QMK firmware for my keyboards (Corne, Sweep Ferris) and trackball (Ploopy Adept)
Log | Files | Refs | Submodules | LICENSE

readme.md (3185B)


      1 # alt34
      2 
      3 ![alt34](https://i.imgur.com/GDv0dL0h.png)
      4 
      5 alt34 was designed as a minimalistic, 'no frills' workhorse keyboard with focus on efficiency and ergonomics.
      6 This breaks down into the following priorities in the design:
      7 
      8 * Keyboard Maintainer: [Tommy Alatalo](https://github.com/altosys)
      9 * Hardware Supported: 
     10    * Compact 34 key split layout with two thumb keys per hand
     11    * Orthogonal layout with a somewhat aggressive column stagger
     12    * Compatibility with standard controllers (Elite-C, Pro Micro etc.)
     13    * Cherry MX switch support
     14    * Kailh hotswap socket support
     15    * Tenting puck support
     16 
     17 ## Hardware
     18 
     19 A bill of materials for building alt34 is found in [the alt34 git repo](https://gitlab.com/altosys/alt34)
     20 
     21 ## Bootloader
     22 
     23 Enter the bootloader in 3 ways:
     24 
     25 * **Bootmagic reset**: Hold down the key at (0,0) in the matrix (usually the top left key or Escape) and plug in the keyboard
     26 * **Physical reset jumper**: Briefly short the pads just below the TRRS connector on the PCB
     27 * **Keycode in layout**: Press the key mapped to `QK_BOOT` if it is available
     28 
     29 Latest updates and information for alt34 is found at https://gitlab.com/altosys/alt34
     30 
     31 ## Build Guide
     32 
     33 There is no dedicated build guide for alt34. If you are a novice builder and need guidance then suggested reading would be build guides for the Corne keyboard (aka. crkbd), they will cover the usual installation of the controller, diodes and hotswap sockets, which is essentially all there is to assembling the alt34.
     34 
     35 ## Flashing QMK Firmware
     36 
     37 Set up your build environment according to the QMK documentation, then after cloning the `qmk_firmware` repository you can run the below commands in the repo root to build and flash the firmware onto your controller.
     38 
     39 Note that this method enables `EE_HANDS` mode which allows you to connect the USB cable to either half of alt34 when using the keyboard.
     40 
     41 
     42 Flash `EE_HANDS` to the left hand half, this updates the persistent EEPROM storage along with the firmware.
     43 Run the below command and then set the board into bootloader mode by bridging the reset pads below the TRRS connector with a paper clip or similar.
     44 ```
     45 make alt34/rev1:default:dfu-split-left
     46 ```
     47 
     48 Do the same for the right hand side:
     49 ```
     50 make alt34/rev1:default:dfu-split-right
     51 ```
     52 
     53 Now you should be able to connect the USB cable to either side of the split and it should work the same.
     54 
     55 For any further changes it is enough to flash only the firmware and not the EEPROM:
     56 ```
     57 make alt34/rev1:default:flash
     58 ```
     59 
     60 It is still recommended to do this for both sides of the split when updating keymaps etc.
     61 
     62 **Note I:** the above examples are using an Elite-C controller with an `atmel-dfu` bootloader, adjust this according to your own hardware.
     63 
     64 **Note II:** the included keymap is rudimentary, the recommended layout to use with alt34 is `miryoku`, see the [miryoku docs](https://github.com/manna-harbour/miryoku) for instructions.
     65 
     66 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).