All information within this article is provided "as is" and without any express or implied warranties, including, without limitation, the implied warranties of merchantibility and fitness for a particular purpose.
This article is protected under copyright law. This document may be copied only if the source, author, date, and legal information is included.
This article tries to cover every aspect of AT and PS/2 keyboards. It includes information on the low-level signals and protocol, scan codes, the command set, initialization, compatibility issues, and other miscellaneous information. Since it's closely related, I've also included information on the PC keyboard controller. All code samples involving the keyboard encoder are written in assembly for Microchip's PIC microcontrollers. All code samples related to the keyboard controller are written in x86 assembly
A History Lesson:
The most popular keyboards in use today include:
USB keyboard - Latest keyboard supported by all new computers (Macintosh and IBM/compatible). These are relatively complicated to interface and are not covered in this article.
IBM/Compatible keyboards - Also known as "AT keyboards" or "PS/2 keyboards", all modern PCs support this device. They're the easiest to interface, and are the subject of this article.
ADB keyboards - Connect to the Apple Desktop Bus of older Macintosh systems. These are not covered in this article
IBM introduced a new keyboard with each of its major desktop computer models. The original IBM PC, and later the IBM XT, used what we call the "XT keyboard." These are obsolete and differ significantly from modern keyboards; the XT keyboard is not covered in this article. Next came the IBM AT system and later the IBM PS/2. They introduced the keyboards we use today, and are the topic of this article. AT keyboards and PS/2 keyboards were very similar devices, but the PS/2 device used a smaller connector and supported a few additional features. Nonetheless, it remained backward compatible with AT systems and few of the additional features ever caught on (since software also wanted to remain backward compatible.) Below is a summary of IBM's three major keyboards.
IBM AT Keyboard (1984) - Not backward compatible with XT systems(1).
84 -101 keys
5-pin DIN connector
Bi-directional serial protocol
Uses what we now refer to as scan code set 2
Eight host-to-keyboard commands
IBM PS/2 Keyboard (1987) - Compatible with AT systems, not compatible with XT systems(1).
84 - 101 keys
6-pin mini-DIN connector
Bi-direction serial protocol
Offers optional scan code set 3
17 host-to-keyboard commands
The PS/2 keyboard was originally an extension of the AT device. It supported a few additional host-to-keyboard commands and featured a smaller connector. These were the only differences between the two devices. However, computer hardware has never been about standards as much as compatibility. For this reason, any keyboard you buy today will be compatible with PS/2 and AT systems, but it may not fully support all the features of the original devices.
Today, "AT keyboard" and "PS/2 keyboard" refers only to their connector size. Which settings/commands any given keyboard does or does not support is anyone's guess. For example, the keyboard I'm using right now has a PS/2-style connector but only fully supports seven commands, partially supports two, and merely "acknowledges" the rest. In contrast, my "Test" keyboard has an AT-style connector but supports every feature/command of the original PS/2 device (plus a few extra.) It's important you treat modern keyboards as compatible, not standard. If your design a keyboard-related device that relies on non-general features, it may work on some systems, but not on others...
Modern PS/2 (AT) compatible keyboards
Any number of keys (usually 101 or 104)
5-pin or 6-pin connector; adaptor usually included
Bi-directional serial protocol
Only scan code set 2 guaranteed.
Acknowledges all commands; may not act on all of them.
Footnote 1) XT keyboards use a completely different protocol than that used by AT and PS/2 systems, making it incompatible with the newer PCs. However, there was a transition period where some keyboard controllers supported both XT and AT (PS/2) keyboards (through a switch, jumper, or auto-sense.) Also, some keyboards were made to work on both types of systems (again, through the use of a switch or auto-sensing.) If you've owned such a PC or keyboard, don't let it fool you--XT keyboards are NOT compatible with modern computers.
Keyboards consist of a large matrix of keys, all of which are monitored by an on-board processor (called the "keyboard encoder".) The specific processor(1) varies from keyboard-to-keyboard but they all basically do the same thing: Monitor which key(s) are being pressed/released and send the appropriate data to the host. This processor takes care of all the debouncing and buffers any data in its 16-byte buffer, if needed. Your motherboard contains a "keyboard controller"(2) that is in charge of decoding all of the data received from the keyboard and informing your software of what's going on. All communication between the host and the keyboard uses an IBM protocol.
Footnote 1) Originally, IBM used the Intel 8048 microcontroller as its keyboard encoder. There are now a wide variety of keyboard encoder chips available from many different manufacturers.
Footnote 2) Originally, IBM used the Intel 8042 microcontroller as its keyboard controller. This has since been replaces with compatible devices integrated in motherboards' chipsets. The keyboard controller is covered later in this article.
Electrical Interface / Protocol:
The AT and PS/2 keyboards use the same protocol as the PS/2 mouse. Click here for detailed information on this protocol.
Your keyboard's processor spends most of its time "scanning", or monitoring, the matrix of keys. If it finds that any key is being pressed, released, or held down, the keyboard will send a packet of information known as a "scan code" to your computer. There are two different types of scan codes: "make codes"and "break codes". A make code is sent when a key is pressed or held down. A break code is sent when a key is released. Every key is assigned its own unique make code and break code so the host can determine exactly what happened to which key by looking at a single scan code. The set of make and break codes for every key comprises a "scan code set". There are three standard scan code sets, named one, two, and three. All modern keyboards default to set two.(1)
So how do you figure out what the scan codes are for each key? Unfortunately, there's no simple formula for calculating this. If you want to know what the make code or break code is for a specific key, you'll have to look it up in a table. I've composed tables for all make codes and break codes in all three scan code sets:
Scan Code Set 1 - Original XT scan code set; supported by some modern keyboards
Scan Code Set 2 - Default scan code set for all modern keyboards
Scan Code Set 3 - Optional PS/2 scan code set--rarely used
Footnote 1) Originally, the AT keyboard only supported set two, and the PS/2 keyboard would default to set two but supported all three. Most modern keyboards behave like the PS/2 device, but I have come across a few that didn't support set one, set three, or both. Also, if you've ever done any low-level PC programming, you've probably notice the keyboard controller supplies set ONE scan codes by default. This is because the keyboard controller converts all incomming scan codes to set one (this stems from retaining compatibility with software written for XT systems.) However, it's still set two scan codes being sent down the keyboard's serial line.
Make Codes, Break Codes, and Typematic Repeat:
Whenever a key is pressed, that key's make code is sent to the computer. Keep in mind that a make code only represents a key on a keyboard--it does not represent the character printed on that key. This means that there is no defined relationship between a make code and an ASCII code. It's up to the host to translate scan codes to characters or commands.
Although most set two make codes are only one-byte wide, there are a handfull of "extended keys" whose make codes are two or four bytes wide. These make codes can be identified by the fact that their first byte is E0h.
Just as a make code is sent to the computer whenever a key is pressed, a break code is sent whenever a key is released. In addition to every key having its own unique make code, they all have their own unique break code(1). Fortunately, however, you won't always have to use lookup tables to figure out a key's break code--certain relationships do exist between make codes and break codes. Most set two break codes are two bytes long where the first byte is F0h and the second byte is the make code for that key. Break codes for extended keys are usually three bytes long where the first two bytes are E0h, F0h, and the last byte is the last byte of that key's make code. As an example, I have listed below a the set two make codes and break codes for a few keys:
E0, F0, 74
E0, F0, 14
Example: What sequence of make codes and break codes should be sent to your computer for the character "G" to appear in a word processor? Since this is an upper-case letter, the sequence of events that need to take place are: press the "Shift" key, press the "G" key, release the "G" key, release the "Shift" key. The scan codes associated with these events are the following: make code for the "Shift" key (12h), make code for the "G" key (34h), break code for the "G" key(F0h,34h), break code for the "Shift" key (F0h,12h). Therefore, the data sent to your computer would be: 12h, 34h, F0h, 34h, F0h, 12h.
If you press a key, its make code is sent to the computer. When you press and hold down a key, that key becomes typematic, which means the keyboard will keep sending that key's make code until the key is released or another key is pressed. To verify this, open a text editor and hold down the "A" key. When you first press the key, the character "a" immediately appears on your screen. After a short delay, another "a" will appear followed by a whole stream of "a"s until you release the "A" key. There are two important parameters here: the typematic delay, which is the short delay between the first and second "a", and the typematic rate, which is how many characters per second will appear on your screen after the typematic delay. The typematic delay can range from 0.25 seconds to 1.00 second and the typematic rate can range from 2.0 cps (characters per second) to 30.0 cps. You may change the typematic rate and delay using the "Set Typematic Rate/Delay" (0xF3) command.
Typematic data is not buffered within the keyboard. In the case where more than one key is held down, only the last key pressed becomes typematic. Typematic repeat then stops when that key is released, even though other keys may be held down.
Footnote 1) Actually, the "Pause/Break" key does not have a break code in scan code sets one and two. When this key is pressed, its make code is sent; when it's released, it doesn't send anything. So how do you tell when this key has been released? You can't.
At power-on or software reset (see the "Reset" command) the keyboard performs a diagnostic self-test referred to as BAT (Basic Assurance Test) and loads the following default values:
Typematic delay 500 ms.
Typematic rate 10.9 cps.
Scan code set 2.
Set all keys typematic/make/break.
When entering BAT, the keyboard enables its three LED indicators, and turns them off when BAT has completed. At this time, a BAT completion code of either 0xAA (BAT successful) or 0xFC (Error) is sent to the host. This BAT completion code must be sent 500~750 milliseconds after power-on.
Many of the keyboards I've tested ignore their CLOCK and DATA lines until after the BAT completion code has been sent. Therefore, an "Inhibit" condition (CLOCK line low) may not prevent the keyboard from sending its BAT completion code.
A few notes regarding commands the host can issue to the keyboard:
The keyboard clears its output buffer when it recieves any command.
If the keyboard receives an invalid command or argument, it must respond with "resend" (0xFE).
The keyboard must not send any scancodes while processing a command.
If the keyboard is waiting for an argument byte and it instead receives a command, it should discard the previous command and process this new one.
Below are all the commands the host may send to the keyboard:
0xFF (Reset) - Keyboard responds with "ack" (0xFA), then enters "Reset" mode. (See "Reset" section.)
0xFE (Resend) - Keyboard responds by resending the last-sent byte. The exception to this is if the last-sent byte was "resend" (0xFE). If this is the case, the keyboard resends the last non-0xFE byte. This command is used by the host to indicate an error in reception.
The next six commands can be issued when the keyboard is in any mode, but it only effects the behavior of the keyboard when in "mode 3" (ie, set to scan code set 3.)
*0xFD (Set Key Type Make) - Disable break codes and typematic repeat for specified keys. Keyboard responds with "ack" (0xFA), then disables scanning (if enabled) and reads a list of keys from the host. These keys are specified by their set 3 make codes. Keyboard responds to each make code with "ack". Host terminates this list by sending an invalid set 3 make code (eg, a valid command.) The keyboard then re-enables scanning (if previously disabled).
*0xFC (Set Key Type Make/Break) - Similar to previous command, except this one only disables typematic repeat.
*0xFB (Set Key Type Typematic) - Similar to previous two, except this one only disables break codes.
*0xFA (Set All Keys Typematic/Make/Break) - Keyboard responds with "ack" (0xFA). Sets all keys to their normal setting (generate scan codes on make, break, and typematic repeat)
*0xF9 (Set All Keys Make) - Keyboard responds with "ack" (0xFA). Similar to 0xFD, except applies to all keys.
*0xF8 (Set All Keys Make/Break) - Keyboard responds with "ack" (0xFA). Similar to 0xFC, except applies to all keys.
*0xF7 (Set All Keys Typematic) - Keyboard responds with "ack" (0xFA). Similar to 0xFB, except applies to all keys.
0xF4 (Enable) - Re-enables keyboard after disabled using previous command.
0xF3 (Set Typematic Rate/Delay) - Host follows this command with one argument byte that defines the typematic rate and delay as follows:
*0xF2 (Read ID) - The keyboard responds by sending a two-byte device ID of 0xAB, 0x83. (0xAB is sent first, followed by 0x83.)
*0xF0 (Set Scan Code Set) - Keyboard responds with "ack", then reads argument byte from the host. This argument byte may be 0x01, 0x02, or 0x03 to select scan code set 1, 2, or 3, respectively. The keyboard responds to this argument byte with "ack". If the argument byte is 0x00, the keyboard responds with "ack" followed by the current scan code set.
0xEE (Echo) - The keyboard responds with "Echo" (0xEE).
0xED (Set/Reset LEDs) - The host follows this command with one argument byte, that specifies the state of the keyboard's Num Lock, Caps Lock, and Scroll Lock LEDs. This argument byte is defined as follows:
"Scroll Lock" - Scroll Lock LED off(0)/on(1)
"Num Lock" - Num Lock LED off(0)/on(1)
"Caps Lock" - Caps Lock LED off(0)/on(1)
*Originally available in PS/2 keyboards only.
Click here for keyboard/mouse routines. Source in MPASM for PIC microcontrollers.
The i8042 Keyboard Controller:
Up to this point in the article, all information has been presented from a hardware point-of-view. However, if you're writing low-level keyboard-related software for the host PC, you won't be communicating directly with the keyboard. Instead, a keyboard controller provides an interface between the keyboard and the peripheral bus. This controller takes care of all the signal-level and protocol details, as well as providing some conversion, interpretation, and handling of scan codes and commands.
An Intel 8042/compatible microcontroller is used as the PC's keyboard controller. In modern computers, this microcontroller is hidden within the motherboard's chipset, which integrates many controllers in a single package. Nonetheless, this device is still there, and the keyboard controller is still commonly referred to as "the 8042".
Depending on the motherboard, the keyboard controller may operate in one of two modes: "AT-compatible" mode, or "PS/2-compatible" mode. The latter is used if a PS/2 mouse is supported by the motherboard. If this is the case, the 8042 acts as the keyboard controller and the mouse controller. The keyboard controller auto-detects which mode it is to use according to how it's wired to the keyboard port.
The 8042 contains the following registers:
A one-byte input buffer - contains byte read from keyboard; read-only
A one-byte output buffer - contains byte to-be-written to keyboard; write-only
A one-byte status register - 8 status flags; read-only
A one-byte control register - 7 control flags; read/write
The first three registers (input, output, status) are directly accessible via ports 0x60 and 0x64. The last register (control) is read using the "Read Command Byte" command, and written using the "Write Command Byte" command. The following table shows how the peripheral ports are used to interface the 8042:
Read Input Buffer
Write Output Buffer
Read Status Register
Writing to port 0x64 doesn't write to any specific register, but sends a command for the 8042 to interpret. If the command accepts a parameter, this parameter is sent to port 0x60. Likewise, any results returned by the command may be read from port 0x60.
When describing the 8042, I may occasionally refer to its physical I/O pins. These pins are defined below:
(Note: Reading keyboard controller datasheets can be confusing--it will refer to the "input buffer" as the "output buffer" and vice versa. This makes sense from the point-of-view of someone writing firmware for the controller, but for somebody used to interfacing the controller, this can cause problems. Throughout this document, I only refer to the "input buffer" as the one containing input from the keyboard, and the "output buffer" as the one that contains output to be sent to the keyboard.)
The 8042's status flags are read from port 0x64. They contain error information, status information, and indicate whether or not data is present in the input and output buffers. The flags are defined as follows:
OBF (Output Buffer Full) - Indicates when it's okay to write to output buffer.
0: Output buffer empty - Okay to write to port 0x60
1: Output buffer full - Don't write to port 0x60
IBF (Input Buffer Full) - Indicates when input is available in the input buffer.
0: Input buffer empty - No unread input at port 0x60
1: Input buffer full - New input can be read from port 0x60
SYS (System flag) - Post reads this to determine if power-on reset, or software reset.
0: Power-up value - System is in power-on reset.
1: BAT code received - System has already beed initialized.
A2 (Address line A2) - Used internally by the keyboard controller
0: A2 = 0 - Port 0x60 was last written to
1: A2 = 1 - Port 0x64 was last written to
INH (Inhibit flag) - Indicates whether or not keyboard communication is inhibited.
0: Keyboard Clock = 0 - Keyboard is inhibited
1: Keyboard Clock = 1 - Keyboard is not inhibited
TxTO (Transmit Timeout) - Indicates keyboard isn't accepting input (kbd may not be plugged in).
0: No Error - Keyboard accepted the last byte written to it.
1: Timeout error - Keyboard didn't generate clock signals within 15 ms of "request-to-send".
RxTO (Receive Timeout) - Indicates keyboard didn't respond to a command (kbd probably broke)
0: No Error - Keyboard responded to last byte.
1: Timeout error - Keyboard didn't generate clock signals within 20 ms of command reception.
PERR (Parity Error) - Indicates communication error with keyboard (possibly noisy/loose connection)
0: No Error - Odd parity received and proper command response recieved.
1: Parity Error - Even parity received or 0xFE received as command response.
MOBF (Mouse Output Buffer Full) - Similar to OBF, except for PS/2 mouse.
0: Output buffer empty - Okay to write to auxillary device's output buffer
1: Output buffer full - Don't write to port auxillary device's output buffer
TO (General Timout) - Indicates timeout during command write or response. (Same as TxTO + RxTO.)
0: No Error - Keyboard received and responded to last command.
1: Timeout Error - See TxTO and RxTO for more information.
[EG: On my PC, the normal value of the 8042's "Status" register is 14h = 00010100b. This indicates keyboard communication is not inhibited, and the 8042 has already completed its self-test ("BAT"). The "Status" register is accessed by reading from port 64h ("IN AL, 64h")]
Reading keyboard input:
When the 8042 recieves a valid scan code from the keyboard, it is converted to its set 1 equivalent. The converted scan code is then placed in the input buffer, the IBF (Input Buffer Full) flag is set, and IRQ 1 is asserted. Furthermore, when any byte is received from the keyboard, the 8042 inhibits further reception (by pulling the "Clock" line low), so no other scan codes will be received until the input buffer is emptied.
If enabled, IRQ 1 will activate the keyboard driver, pointed to by interrupt vector 0x09. The driver reads the scan code from port 0x60, which causes the 8042 to de-assert IRQ 1 and reset the IBF flag. The scan code is then processed by the driver, which responds to special key combinations and updates an area of the system RAM reserved for keyboard input.
If you don't want to patch into interrupt 0x09, you may poll the keyboard controller for input. This is accomplished by disabling the 8042's IBF Interrupt and polling the IBF flag. This flag is set (1) when data is available in the input buffer, and is cleared (0) when data is read from the input buffer. Reading the input buffer is accomplished by reading from port 0x60, and the IBF flag is at port 0x64, bit 1. The following assembly code illustrates this:
WaitLoop: in al, 64h ; Read Status byte
and al, 10b ; Test IBF flag (Status<1>)
jz WaitLoop ; Wait for IBF = 1
in al, 60h ; Read input buffer
Writing to keyboard:
When you write to the 8042's output buffer (via port 0x60), the controller sets the OBF ("Output Buffer Full") flag and processes the data. The 8042 will send this data to the keyboard and wait for a response. If the keyboard does not accept or generate a response within a given amount of time, the appropriate timeout flag will be set (see Status register definition for more info.) If an incorrect parity bit is read, the 8042 will send the "Resend" (0xFE) command to the keyboard. If the keyboard continues to send erroneous bytes, the "Parity Error" flag is set in the Status register. If no errors occur, the response byte is placed in the input buffer, the IBF ("Input Buffer Full") flag is set, and IRQ 1 is activated, signaling the keyboard driver.
The following assembly code shows how to write to the output buffer. (Remember, after you write to the output buffer, you should use int 9h or poll port 64h to get the keyboard's response.)
WaitLoop: in al, 64h ; Read Status byte
and al, 01b ; Test OBF flag (Status<0>)
jnz WaitLoop ; Wait for OBF = 0
out 60h, cl ; Write data to output buffer
Keyboard Controller Commands:
Commands are sent to the keyboard controller by writing to port 0x64. Command parameters are written to port 0x60 after teh command is sent. Results are returned on port 0x60. Always test the OBF ("Output Buffer Full") flag before writing commands or parameters to the 8042.
0x60 (Write Command Byte) - Stores parameter as command byte. Command byte defined as follows:
INT (Input Buffer Full Interrupt) - When set, IRQ 1 is generated when data is available in the input buffer.
0: IBF Interrupt Disabled - You must poll STATUS to read input.
1: IBF Interrupt Enabled - Keyboard driver at software int 0x09 handles input.
SYS (System Flag) - Used to manually set/clear SYS flag in Status register.
0: Power-on value - Tells POST to perform power-on tests/initialization.
1: BAT code received - Tells POST to perform "warm boot" tests/initiailization.
OVR (Inhibit Override) - Overrides keyboard's "inhibit" switch on older motherboards.
0: Inhibit switch enabled - Keyboard inhibited if pin P17 is high.
1: Inhibit switch disabled - Keyboard not inhibited even if P17 = high.
_EN (Disable keyboard) - Disables/enables keyboard interface.
0: Enable - Keyboard interface enabled.
1: Disable - All keyboard communication is disabled.
XLAT (Translate Scan Codes) - Enables/disables translation to set 1 scan codes.
0: Translation disabled - Data appears at input buffer exactly as read from keyboard
1: Translation enabled - Scan codes translated to set 1 before put in input buffer
INT2 (Mouse Input Buffer Full Interrupt) - When set, IRQ 12 is generated when mouse data is available.
0: Auxillary IBF Interrupt Disabled -
1: Auxillary IBF Interrupt Enabled -
?0xA5 (Set password) - Set the new password by sending a null-terminated string of scan codes as this command's parameter.
?0xA6 (Check password) - Compares keyboard input with current password.
0xA7 (Disable mouse interface) - PS/2 mode only. Similar to "Disable keyboard interface" (0xAD) command.
0xA8 (Enable mouse interface) - PS/2 mode only. Similar to "Enable keyboard interface" (0xAE) command.
0xA9 (Mouse interface test) - Returns 0x00 if okay, 0x01 if Clock line stuck low, 0x02 if clock line stuck high, 0x03 if data line stuck low, and 0x04 if data line stuck high.
0xAA (Controller self-test) - Returns 0x55 if okay.
0xAB (Keyboard interface test) - Returns 0x00 if okay, 0x01 if Clock line stuck low, 0x02 if clock line stuck high, 0x03 if data line stuck low, and 0x04 if data line stuck high.
0xAD (Disable keyboard interface) - Sets bit 4 of command byte and disables all communication with keyboard.
0xAE (Enable keyboard interface) - Clears bit 4 of command byte and re-enables communication with keyboard.
0xAF (Get version)
0xC0 (Read input port) - Returns values on input port (see Input Port definition.)
0xC1 (Copy input port LSn) - PS/2 mode only. Copy input port's low nibble to Status register (see Input Port definition)
0xC2 (Copy input port MSn) - PS/2 mode only. Copy input port's high nibble to Status register (see Input Port definition.)
0xD0 (Read output port) - Returns values on output port (see Output Port definition.)
0xD1 (Write output port) - Write parameter to output port (see Output Port definition.)
0xD2 (Write keyboard buffer) - Parameter written to input buffer as if received from keyboard.
0xD3 (Write mouse buffer) - Parameter written to input buffer as if received from mouse.
0xD4 (Write mouse Device) - Sends parameter to the auxillary PS/2 device.
0xE0 (Read test port) - Returns values on test port (see Test Port definition.)
0xF0-0xFF (Pulse output port) - Pulses command's lower nibble onto lower nibble of output port (see Output Port definition.)
Modern Keyboard Controllers:
So far, I've only discussed the 8042 keyboard controller. Although modern keyboard controllers remain compatible with the original device, compatibility is their only requirement (and their goal.)
My motherboard's keyboard controller is a great example of this. I connected a microcontroller+LCD in parallel to my keyboard to see what data is sent by the keyboard controller. At power-up, the keyboard controller sent the "Set LED state" command to turn off all LEDs, then reads the keyboard's ID. When I tried writing data to the output buffer, I found the keyboard controller only forwards the "Set LED state" command and "Set Typematic Rate/Delay" command. It does not allow any other commands to be sent to the keyboard. However, it does emulate the keyboard's response by placing "acknowledge" (0xFA) in the input buffer when appropriate (or 0xEE in response to the "Echo" command.) Furthermore, if the keyboard sends it an erroneous byte, the keyboard controller takes care of error handling (sends the "Retry" command; if byte still erroneous; sends error code to keyboard and places error code in input buffer.)
Once again, keep in mind chipset designers are more interested in compatibility than standardization.
The following is the communication between my computer and keyboard when it boots-up. I beleive the first three commands were initiated by the keyboad controller, the next command (which enables Num lock LED) was sent by the BIOS, then the rest of the commands were sent my the OS (Win98SE). Remember, these results are specific to my computer, but it should give you a general idea as to what happens at startup.
Keyboard: AA Self-test passed ;Keyboard controller init
Host: ED Set/Reset Status Indicators
Keyboard: FA Acknowledge
Host: 00 Turn off all LEDs
Keyboard: FA Acknowledge
Host: F2 Read ID
Keyboard: FA Acknowledge
Keyboard: AB First byte of ID
Host: ED Set/Reset Status Indicators ;BIOS init
Keyboard: FA Acknowledge
Host: 02 Turn on Num Lock LED
Keyboard: FA Acknowledge
Host: F3 Set Typematic Rate/Delay ;Windows init
Keyboard: FA Acknowledge
Host: 20 500 ms / 30.0 reports/sec
Keyboard: FA Acknowledge
Host: F4 Enable
Keyboard: FA Acknowledge
Host: F3 Set Typematic Rate/delay
Keyboard: FA Acknowledge
Host: 00 250 ms / 30.0 reports/sec
Keyboard: FA Acknowledge0>1>