Checkpoint LAB USB-RS232 Spécifications

ECE391: Computer Systems Engineering Spring 2015Machine Problem 2Checkpoint 1: Monday, March 2, 7pmCheckpoint 2: Monday, March 9, 7pmDevice, Data, and

level programs such as the game. You must implement the following ioctls for your device abstraction:TUX INIT Takes no argume nts. Initializes any var

110 1 0 00 0 1 0X XXC ALBUDRXX XS7 0120That is, the fir st byte will have the value MTCP POLL OK, the second and third will contain active-lowbit masks

adjacent levels look different (you can reuse so me colors if you want, but you can’t h ave just one). You can also makethem glow, chang e with the nu

This machine problem gives you several o pportu nities for working with da ta layout in memory and for tr ansformingdata from one form to another. Mos

assert.c Suppor t for assertions and cleanups as design and debugging aids.blocks.s Graphic block images of the maze, the player, fruits, etc.input.c

Each pixel in mode X is represented by a on e -byte color value. Although only 256 colors are available in mode X, theactual color space is 18-bit, wi

The game defines a two-dimensional world of pixels, an d the screen at any time shows a region of that world. Themaze world is never f ully constructed

The next question is the size of the build buffer. If we can limit the size of the maze world, we can allocate a buildbuffer large enough to hold any

easy p la c e to start. The main difficulty is for you to understand bo th how mode X maps pixels and how the abstractionsin modex.c work, so try to re

the USB port appear to software as a standard (old fashioned) RS232 serial port. We can then set up QEMU so that oneof the emulated serial ports on th

Building the Driver:The mp2/module directory contains a framework for the driver you will be implementing for the Tux controller. Amodule is similar t