Difference between revisions of "Tmk keyboard firmware"
From Makers Local 256
m (tmk) |
(pin usage) |
||
Line 8: | Line 8: | ||
* Program tmk over the bootloader | * Program tmk over the bootloader | ||
** avrdude -p atmega32u4 -P /dev/ttyACM0 -c usbasp -U flash:w:ps2_usb_lufa.hex | ** avrdude -p atmega32u4 -P /dev/ttyACM0 -c usbasp -U flash:w:ps2_usb_lufa.hex | ||
+ | |||
+ | == ps/2 cable == | ||
+ | I stole a female ps/2 port from a qcat. | ||
+ | o | o <-- Blue (clock) | ||
+ | Red (vcc) --> o | o <-- Green (gnd) | ||
+ | o o <-- Yellow (data) |
Revision as of 08:32, 11 September 2015
SparkFun atmega32u4 Breakout
So, while this board uses an atmega32u4 it has a major problem. It will always boot into the bootloader and wait for the char 'e' to be sent. So instead, I just wrote the tmk firmware over the bootloader.
- Board - https://www.sparkfun.com/products/11117
- Github - https://github.com/sparkfun/32U4_Breakout_Board
- LUFA-130303 bootloader - File:BootloaderCDC.hex.gz
- avrdude -p atmega32u4 -P /dev/ttyACM0 -c usbasp -U flash:w:BootloaderCDC.hex
- Program tmk over the bootloader
- avrdude -p atmega32u4 -P /dev/ttyACM0 -c usbasp -U flash:w:ps2_usb_lufa.hex
ps/2 cable
I stole a female ps/2 port from a qcat.
o | o <-- Blue (clock) Red (vcc) --> o | o <-- Green (gnd) o o <-- Yellow (data)