1 / 30

EEL 3705 / 3705L Digital Logic Design

EEL 3705 / 3705L Digital Logic Design. Spring 2007 Instructor: Dr. Michael Frank Modules #90-99 (Extra Slides): Design Examples Module #94: PS/2 Serial Port Receiver and Keyboard Byte Sequence Decoder. Keyboard and Mouse Input Using the PS/2 Port.

kchannell
Download Presentation

EEL 3705 / 3705L Digital Logic Design

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. EEL 3705 / 3705LDigital Logic Design Spring 2007Instructor: Dr. Michael FrankModules #90-99 (Extra Slides): Design Examples Module #94: PS/2 Serial Port Receiverand Keyboard Byte Sequence Decoder M. Frank, EEL3705 Digital Logic, Fall 2006

  2. Keyboard and Mouse Input Using the PS/2 Port PS/2 Serial Line Receiver Circuitand Keyboard Byte Sequence Decoder M. Frank, EEL3705 Digital Logic, Fall 2006

  3. PS/2 Port Pins • From UP2 User’s Guide, p.13… M. Frank, EEL3705 Digital Logic, Fall 2006

  4. PS/2 Serial Port – Physical/Electrical Specifications • For text of specs, see http://www.computer-engineering.org/ps2protocol/ M. Frank, EEL3705 Digital Logic, Fall 2006

  5. Verifying the On-Board Port Circuitry • We check the UP2 board schematics and see that there is no port-driving circuitry between the PS/2 port and the FLEX chip • The pullup resistors for the open-drain output drivers must be implemented internally within the FLEX chip UP2 board schematics, page 6 UP2 board schematics, page 1 M. Frank, EEL3705 Digital Logic, Fall 2006

  6. PS2 Electrical Interface in Quartus • Entity ps2_port: • in example project VGA_char_RAM2 M. Frank, EEL3705 Digital Logic, Fall 2006

  7. PS/2 Serial Line Protocol • Host controls bus: • Data 1, Clock 1 • Device may transmit data • Data 1, Clock 0 • Device may not transmit data • Data 0, Clock 1 • Host requests device to send clock pulses so host may transmit data • Device generates clock pulses: • 10-16.7 kHz, 50% duty cycle • 1 data bit sent per clock cycle • Data bit is most likely to be valid in the middle of the clock’s low period • Invalid during high period • Data packet framing: • 1 start bit (always 0) • 8 data bits, LSB first • 1 parity bit (odd parity) • 1 stop bit (always 1) 0 1 0 1 0 1 0 0 0 0 1 00010101 = 1516 M. Frank, EEL3705 Digital Logic, Fall 2006

  8. Signal Decoding Strategy • Wait 20 µs after falling clock edge before sampling data bit value • Gives the best chance of being in the valid region for either slow or fast clocks • Wait until rising clock edge afterbit #11 before declaring frameis complete. Slow clock (10 kHz): 100 µs 100 µs … 50 µs 50 µs bit #0(between frames) bit #0 bit #11 bit #2 bit #1 25 µs Fast clock (16.7 kHz): • Wait 100 µs after rising clockedge before resetting bit counter 60 µs … 30 µs 30 µs bit 1 bit 2 bit 11 15 µs M. Frank, EEL3705 Digital Logic, Fall 2006

  9. PS/2 Serial Line Receiver Circuit (Byte Deframer/Deserializer) • Entity ps2_reader in VGA_char_RAM2_v6: M. Frank, EEL3705 Digital Logic, Fall 2006

  10. PS/2 Keyboard Make/Break Codes • Here are some representative examples: • From http://www.computer-engineering.org/ps2keyboard/scancodes2.html Additional undocumented variants of the normal code sequences may also be produced for certain keys, depending on whether the Num Lock key is active. M. Frank, EEL3705 Digital Logic, Fall 2006

  11. Map Between Single-Byte Make Codesand Key Cap Labels • You can use this table to quickly look up what make code is generated by a given key. M. Frank, EEL3705 Digital Logic, Fall 2006

  12. Displaying Received Bytes as ASCII Characters • Additions to top-level circuit in VGA_char_RAM2_v3 This counter keeps track of what RAM byte address (0-127) the next byte received will be written to… M. Frank, EEL3705 Digital Logic, Fall 2006

  13. Output from VGA_char_RAM2_v3 Press/release“D key” Double F016 bytes: Possible timing problem? • User typed, “donte␣rules1” M. Frank, EEL3705 Digital Logic, Fall 2006

  14. Keyboard Byte Sequence Decoder Finite State Machine Diagram M. Frank, EEL3705 Digital Logic, Fall 2006

  15. Single-Byte ASCII-based Representation of the Map 1 key make codes • This determines what character is displayed on screen by the VGA_char_ram2_v6 project when a given key is pressed. M. Frank, EEL3705 Digital Logic, Fall 2006

  16. Map from 2nd byte of 2-byte make codes to chosen ASCII representations M. Frank, EEL3705 Digital Logic, Fall 2006

  17. Circuit for Keyboard Make/Break Byte Sequence Decoder State Machine • Entity key_decoder in VGA_char_RAM2_v6 This is a good example of a design that badlyneeds to be modularizedfor better readability! View circuit inQuartus to zoom inon particular parts M. Frank, EEL3705 Digital Logic, Fall 2006

  18. Synchronous Delay Circuit • Entity delayed_pulse in VGA_char_RAM2_v6 M. Frank, EEL3705 Digital Logic, Fall 2006

  19. Relevant part of Top-Level Circuit • Byte stream is filtered through key_decoder M. Frank, EEL3705 Digital Logic, Fall 2006

  20. Output from VGA_char_RAM2_v6 • User typed, “donte␣rules1” • Output consists of the ASCII characters assigned to represent each key • Inverse video denotes key release events M. Frank, EEL3705 Digital Logic, Fall 2006

  21. Simplified State Machine Designfor key_decoder_v2 • Only three state bits are really needed: • f0 – Last byte was F016; we will output a break code. • e0 – We’re in an extended byte-code sequence, starting E016 or E116. • Use Map 2 instead of Map 1 for translating final byte of sequence. • e1 – Last byte seen (except maybe F0) was E116 • Ignore next small byte seen (14 in Pause/Break sequence) M. Frank, EEL3705 Digital Logic, Fall 2006

  22. Descriptions of All the Possible States In the below, state bits are given in the order e1e0f0: • 000 – Default state, in between byte sequences. • 001 – After 1st byte (F0) of a map 1 break code. • 010 – After E0 in an extended (map 2) sequence. • Or after E1,14 in the Pause/Break sequence. • 011 – After E0,F0 in an extended (map 2) sequence. • Or after E1,F0,14 in the Pause/Break sequence/ • 10d – (these states are not currently used) • 110 – After E1 in an extended (map 2) sequence. • 111 – After E1,F0 in an extended (map 2) sequence M. Frank, EEL3705 Digital Logic, Fall 2006

  23. State Diagram for Simplified Machine • Here is the complete state-transition diagram • for the expected code sequences • Actually, due to the don’t-cares, many other codes would also cause the specific transitions shown… • But these shouldn’t occur in practice. <80map1break <80map1make State001(1) F0 State000(0) State110(6) E1 E0 <80map2break <80map2make State010(2) 14 F0 State011(3) State111(7) F0 14 M. Frank, EEL3705 Digital Logic, Fall 2006

  24. Example State Sequence State bits are shown in the yellow columns as: e1e0f0Input bytes are in blue, output characters are B&W • User presses & releases keys: Aa Break sequencesoutlined in red RightControl PrintScreenSysRq PauseBreak “fake break” sequence from Pause/Break M. Frank, EEL3705 Digital Logic, Fall 2006

  25. Next-State Logic • Useful temporary variables: • low_byte = ~b7 (byte less than 80x); hi_byte = b7 & b6 (byte C0x or higher) • Product terms for rows of truth table: • norm_byte = ~e1 & low_byte (1st row) • 83_byte = b7 & ~b6 (2nd row) • skip_byte = e1 & low_byte (3rd row) • F0_byte = hi_byte & b4 (4th row) • E_byte = hi_byte & ~b4 (5th row) • Logic for determining the next-state bits based on the above: • e0* = e1 | (~norm_byte & (e0 | E_byte)) • Either we were just in e1 mode, or the byte just received was not a normal byte, and either we were already in E0 mode, or we just received an E0 or E1 byte. • e1* = hi_byte & (e1 | (E_byte & b0)) • The byte just seen was a high one, and either we were already in E1 mode, or we just received an E1 byte. • f0* = F0_byte • The byte just seen was an F0. M. Frank, EEL3705 Digital Logic, Fall 2006

  26. Core of key_decoder_v2 FSM M. Frank, EEL3705 Digital Logic, Fall 2006

  27. Output of VGA_char_RAM3_v5 • A large, complete 7-bit ASCII table is displayed • Including my custom control characters & associated colors. • Circuit keeps track of which keys are currently depressed • And highlights the ASCII character assigned to each in my encoding • Using inverse video • In this snapshot, user is holding down the keys “A,” “C,” “E.” • User must also have pressed the FLEX_PB1 pushbutton to clear the display initially. M. Frank, EEL3705 Digital Logic, Fall 2006

  28. Close-Up of Screen • We can see a little bit of glitching between characters, due to subtle timing issues • Could fix by pipelining, addressing warnings from timing analyzer, etc. M. Frank, EEL3705 Digital Logic, Fall 2006

  29. Modified Keymap for Text-Entry Application • Below each ASCII character in this table is the key (if any) that generates that character • in the latest version of the key_decoder. • Found in text_entry_v2 example • The white-on-black keys are the keys in map 2 • byte sequences starting with E0 or E1 • Yellow keys are those that were moved to different code points in the latest version • Done to assign keys to more commonly-used punctuation characters • Also to generate more control codes directly via function keys. M. Frank, EEL3705 Digital Logic, Fall 2006

  30. Further Ideas for Building on Key Decoder • Write a secondary decoder that translates make-break sequences into standard ASCII characters… • E.g., take as input the following event sequence… • make (left shift), make (& 7), break (& 7), break (left shift) • and produce as output the single character “&” • Write a simple text-entry application • Accept formatting characters ⌫ ↦ ↓ ↧ ↡ ↵ and translate them into appropriate cursor movements • Video games, music synthesizer (piano keyboard), etc… M. Frank, EEL3705 Digital Logic, Fall 2006

More Related