qmk-dactyl-manuform-a/keyboard/hhkb
tmk 00e9a342df Fix 'Shift Parentheses' example 2014-04-25 11:47:02 +09:00
..
doc Fix README.md of hhkb 2013-11-30 12:33:32 +09:00
Makefile Change LUFA build options 2014-04-24 11:26:06 +09:00
Makefile.iwrap
Makefile.nodebug Add new keymap framework 2013-11-29 09:12:28 +09:00
Makefile.pjrc Add new keymap framework 2013-11-29 09:12:28 +09:00
Makefile.vusb
README.md Spellchecking keyboard README files. 2014-01-07 11:03:18 +09:00
config.h
config_iwrap.h
config_vusb.h
iwrap.txt
keymap_common.c Add new keymap framework 2013-11-29 09:12:28 +09:00
keymap_common.h Add new keymap framework 2013-11-29 09:12:28 +09:00
keymap_hasu.c Fix 'Shift Parentheses' example 2014-04-25 11:47:02 +09:00
keymap_hhkb.c Add new keymap framework 2013-11-29 09:12:28 +09:00
keymap_spacefn.c Add SpaceFN layout for HHKB 2013-11-30 12:03:19 +09:00
led.c
matrix.c
usbconfig.h

README.md

Alternative Controller for HHKB Pro

I wanted to add some features like vi cursor and mouse keys to my HHKB but its controller is not programmable and firmware source code is not open, of course. This means customizing this keyboard needs to replace original controller with programmable one.

This controller can work with HHKB Professional, Professional 2 and Type-S.

See this thread in geekhack.org.

##Features

  • Customizable keymap
  • More keymap layers(more Fn keys)
  • Mouse keys
  • USB NKRO

See README of tmk_keyboard for more.

###Pros

  • No risks: Everything is all reversible
  • No need for PCB trace patching, case cutting or any other destructive mod
  • Can keep original controller intact
  • Can change all HHKB behavior as you like

###Cons

  • Void your warranty
  • Lose USB hub function of Pro2

##DISCLAIMER I'm not a professional of electronics nor MCU programming. This may damage your HHKB. And my English writing is poor, I'm not sure I can convey my notions accurately.

##Documents See doc/HHKB.txt and files under doc/ for internal of HHKB and this controller.

##Build Firmware & Program See this document first.

Configuration

Set MCU, BOOTLOADER_SIZE and other build options in Makefile and config.h.

Build

Several version of keymap are available in advance but you are recommended to define your favorite layout yourself. Just make with KEYMAP option like:

$ make KEYMAP=[hasu|hhkb|spacefn|<name>]

Program

First, push reset button on board to start bootloader.

This command programs the controller with dfu-programmer if the tool is installed and configured properly.

$ make dfu

Or you can also use FLIP command to program. Also the tool should be installed and configured properly. FLIP GUI application is also available.

$ make flip

Use Teensy Loader if your controller is Teensy/Teensy++.

##Keymap To define your own keymap create file named keymap_<name>.c and see keymap document(you can find in top README.md) and existent keymap files.

##Hardware You have some options for hardware. Development boards with USB AVR family(ATMega32U4, AT90USB1286) like Teensy will work while MegaAVR with V-USB library is also cheaper option for DIY.

###1. TMK Alt Controller Board TMK designed Keyboard Controller Board for HHKB Pro2(KiCad project). See this post.

###2. PJRC Teensy++ 2.0 version +---------------+ | Teensy++ | | | | | HHKB pro HHKB pro2 | | ~~~~~~~~ ~~~~~~~~~ | PB0-2|------->ROW (6-8) (5-7) | PB3-5|------->COL (9-11) (8-10) | PB6|------->ENABLE (12) (11) | PE6|<-------KEY (4) (3) | PE7|------->PREV (5) (4) | | | | 5V--- (1-3) (1-2) | | GND--- (13-14) (12-13) +---------------+

###3. V-USB version See V-USB controller for HHKB