The converter translates IBM PC keyboard protocols to use classic keyboards with USB ports. It supports both IBM XT and AT protocols, and all of scan code set 1, 2 and 3 with one firmware.
This project is intended to integrated existent TMK XT, PS/2 and Terminal converters.
Firmware supports ATMega32u4 and ATMega32u2 by default, Teensy2 or ProMicro can be used. Wire controller pins below to keyboard signals, besides VCC and GND. This is compatible for Soarer's converter.
- Data PD0
- Clock PD1
- Reset PB6 or PB7 (For some of XT keyboards. Not needed for AT, PS/2 and Terminal)
| 5-Pin DIN | Description | Cable color | Board Pin |
|---|---|---|---|
| 1 | Clock | black | 2 |
| 2 | Data | red | 3 |
| 3 | Reset | white | 10 |
| 4 | GND | green | GND |
| 5 | +5V | yellow | VCC |
This section explains how the converter determines proper protocol and scan code set for keyboard. The converter need to do that before starting to receive and translate scan codes from keyboard.
After startup the converter sends 0xF2 command to get keyboard ID and sees how the keyboard responds to the command.
Response from keyboard:
- XT keyboard doesn't support any command and returns no response.
- AT keyboard should respond with 0xFA to the command but returns no keyboard ID.
- PS/2 keyboard should respond with 0xFA to the command, followed by keyboard ID, such as 0xAB86.
- Terminal keyboard should respond with 0xFA to the command, followed by keyboard ID, such as 0xBFBF.
Now we can discriminate the keyboard and determine suitable protocol and scan code set as described below.
- Signals from XT keyboard are recognized by XT protocol.
- Signals from AT, PS/2 and Terminal keyboard are recognized by AT protocol.
- Scan codes from XT keyboard are handled as CodeSet1.
- Scan codes from AT and PS/2 keyboard are handled as CodeSet2.
- Scan codes from Terminal keyboard are handled as CodeSet3.
The next descriptions refer to Linux, but can certainly also be applied to windows systems, in a slightly modified form. The unimap layers are configured as shown in the following pictures:
First (if not already done) install the Arduino environment to compile and flash the firmware:
sudo pacman -S arduino-avr-coreDownload the precompiled firmware from zenith-xt-usb/firmware or build it by yourself:
make clean
makeFirst of all, we should identify to which serial device the Pro Micro is connected to (normally it is /dev/ttyACM0). Connect the Pro Micro to the USB port of your computer and verify it with the list of serial devices:
ls /dev/tty*Navigate to the directory where the firmware is downloaded or compiled. Quickly connect GND + RST pins on the Pro Micro to enter the Bootloader mode and execute the following command to flash the firmware:
sudo avrdude -p atmega32u4 -P /dev/ttyACM0 -c avr109 -U flash:w:zenith_usb.hexIf you want to update the firmware you can execute the following command:
sleep 3 && sudo avrdude -p atmega32u4 -P /dev/ttyACM0 -c avr109 -U flash:w:zenith_usb.hexAfterwards you have 3 seconds to press Numpad 0 + Caps Lock to enter the Bootloader mode
To dis-/enable the piezoelectric beeper press Alt + Esc