Search the Community

Showing results for tags 'ps2'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • News
    • New Users Introduction
    • Announcements
  • Digilent Technical Forums
    • FPGA
    • Digilent Microcontroller Boards
    • Non-Digilent Microcontrollers
    • Add-on Boards
    • Scopes & Instruments
    • LabVIEW
    • FRC
    • Other
  • General Discussion
    • Project Vault
    • Learn
    • Suggestions & Feedback
    • Buy, Sell, Trade
    • Sales Questions
    • Off Topic
    • Educators
    • Technical Based Off-Topic Discussions

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 6 results

  1. Hi, I recently discovered that the wrong scan codes are sent for certain keys. This is tested with my own PS2 keyboard controller, and the same behaviour is present with the official demo: https://reference.digilentinc.com/learn/programmable-logic/tutorials/nexys-4-ddr-keyboard-demo/start I have tested two keyboards: One Logitech K120, and one Microsoft comfort curve 3000. The following behaviour is exhibited: Left arrow set 2 scancode should be: E0 6B / E0 F0 6B. Actual: 6B / F0 6B Up arrow set 2 scancode should be: E0 75 / E0 F0 75. Actual: 75 / F0 75 Down arrow set 2 scancode should be: E0 72 / E0 F0 72. Actual: 72 / F0 72 Curiously, the right arrow scancode is correct. Numpad division set 2 scancode should be: E0 4A / E0 F0 4A. Actual: 4A / F0 4A Can anyone confirm? Online Documentation for Altium Products - PS2 Keyboard Scan Codes - 2017-09-13.pdf
  2. Hi Digilent staff, and fellow forum members, Just wondering if you guys had considered making a USB HID -> PS/2 PMOD board? I was thinking of something like the circuit on the Nexys 3,4 boards which uses a PIC to convert a USB keyboard to PS/2 compatible signals. Would be handy for using newer USB keyboards/mice on PMOD socket equipped FPGA boards. PS/2 devices are becoming harder to find brand new. I (for one) would be interested in a few. Kind regards, Leslie
  3. Hi everyone any idea how I can set the PS2 power jumper to 5V ? , I have the Genesys virtex-5 board. Thank you
  4. Hi, I created a VHDL description to work with the PS2 interface of a Nexys-3 board, but I'm having a problem with the arrow keys. The right arrow key - code E0 74 - works perfectly, but strangely the other three - codes E0 75, E0 6B and E0 72 - do not! I tested with the Ctrl key - code E0 14 - and with the Alt GR - code E0 11 - and they also work perfectly. Since I was unable to understand the problem, I tried with another board - a Basys-3 - and with Vivado. The behavior was exactly the same. Then I picked up an old Spartan-3E board with a true PS2 connector and the whole arrow keys and the Ctrl and Alt GR worked perfectly (I singled these keys out because they are extended keys like the arrow keys). I'm completely puzzled! Why the same description works in a board and in the other two boards only works with certain keys? The only visible difference among the boards is that the most recent Nexys-3 and Basys-3 use an emulator to emulate PS2, while the old Spartan-3E board does not. May there be the problem? As someone already experienced the same problem? Thank you.
  5. laltarac

    Basys2 PS/2 Keyboard

    Hello. Im working on a project that requires a ps2 keyboard to communicate to the Basys2 board. Does any one have any good links that might help me get started with this. Or, maybe would someone be able to post their Verilog code , if they've done it ? It would be much appreciated Thanks Liam
  6. The PS2 Keyboard/Mouse PMOD Connector has incorrect silk screen. The labels for VE and Gnd are backwards. VE is really GND, and GND is really VE. This is the +5V external input to power mice that run off of 5V (which almost all PS/2 mice actually do run off of 5V). Swapping VE and Gnd caused me to burn my mouse. It drew about a half-amp of current and immediately smelled that lovely smell of burning electrical components. I had to purchase a second PS/2 mouse once I found out the problem. If I connect the external power opposite of the silkscreen I am able to communicate with the mouse. Can Digilent do something to make this up to me?