Checkpoint LAB USB-RS232 Bedienungsanleitung

Stöbern Sie online oder laden Sie Bedienungsanleitung nach Spielsteuerung Checkpoint LAB USB-RS232 herunter. MP2 Tux Spec - Course Website Directory Benutzerhandbuch

  • Herunterladen
  • Zu meinen Handbüchern hinzufügen
  • Drucken
  • Seite
    / 4
  • Inhaltsverzeichnis
  • LESEZEICHEN
  • Bewertet. / 5. Basierend auf Kundenbewertungen
Seitenansicht 0
ECE391: Computer Systems Engineering Fall 2014
Machine Problem 2
The Tux Controller
Introduction:
This machine problem gives you several opportunities to work with software that interacts directly with devices and
must adhere to the protocols specified by those devices. Similar problems arise when one must meet software interface
specifications, but you need experience with both in order to recognize the similarities and differences. The Tux Con-
troller is that funny little game controller attached to each of the machines in the lab. It was designed and implemented
by Kevin Bassett and Mark Murphy, two students who took this class during the 2004-2005 school year, and went on
to work as lab assistants for the class.
The Tux Controller connects to the USB port of the lab machine. An FTDI “Virtual Com Port” (VCP) driver makes
the USB port appear to software as a standard (old fashioned) RS232 serial port. We can then set up QEMU so that one
of the emulated serial ports on the virtual machine maps to the emulated serial port connected to the Tux Controller.
Your tasks for the final checkpoint:
1. Enable the device driver to control the LEDs on the Tux controller
2. Enable the device driver to report when buttons are pressed and released
3. Handle device resets correctly
4. Enable control of the game using the Tux controller (support keyboard input simultaneously).
5. In the game, enable the up/down/left/right buttons on the Tux controller to do what the arrow keys do on the
keyboard, enable the A/B/C buttons to do what Insert/Home/PageUp do on the keyboard, and enable the Start
button to do what the backquote/tilde (‘’) key does on the keyboard.
Remember, the Tux driver is expected to work with ANY user-level program. This means you will not receive full
credit if you do not implement all ioctls described in this document even if the game does not make use of them.
Set up instructions:
1. Remember to use SVN or save a current version of your code as a backup.
2. You no longer need to compile the entire linux kernel, so you no longer need to boot your compiled kernel.
To prevent your compiled kernel from running, right click on “test
debug.lnk” shortcut, go to properties and
remove the -kernel ...\bzImage from the target line.
3. Enable your test machine to make use of the serial port (named COM#) corresponding to the Tux controller. To
check which COM number the Tux controller is currently connected on: Go to Start -> Devices and Printers ->
right-click on FT232R USB UART -> Hardware tab -> USB Serial Port (COM#) where # should be less than
10. If it is higher, call a TA because it will not work with QEMU. Right click on “test debug.lnk shortcut, go to
properties and add -serial COM# to the end of the target line. This connects the Windows COM# port to the
Linux ttyS0 serial port. Note: Only your test machine will be able to communicate with the Tux controller with
this setup. Although you can also add this option to your devel machine, you can only have one virtual machine
use the Tux at a time. Therefore, we recommend you use the devel machine to compile your code and the test
machine to load the kernel module and run the game.
4. Also remove the -S option from the end of the target line This option told qemu to wait until gdb was attached.
In this assignment we don’t need to start gdb until after the kernel is up and running.
Seitenansicht 0
1 2 3 4

Inhaltsverzeichnis

Seite 1 - The Tux Controller

ECE391: Computer Systems Engineering Fall 2014Machine Problem 2The Tux ControllerIntroduction:This machine problem gives you several opportunities to

Seite 2

25. When you first start your debug machine, a dialog will appear asking you for COM# Properties. The defaultvalues (Bits per second should be = 9600,

Seite 3

3control completely as a stand alone program should you try it with the full game. To interface with the game you willneed to create a new thread to t

Seite 4

4We recommend that you make use of MTCPBIOC ON and MTCP LED SET, in which case you must handle MTCP ACKand MTCP BIOC EVENT. You must also handle MTCP

Kommentare zu diesen Handbüchern

Keine Kommentare