CSCS2650 Computer Organization
PROJECT: btt0
OBJECTIVE
Our explorations this semester will target the Vircon32 fantasy
console, an Open Source 32-bit emulator with development toolchain.
The purpose of this project is to ensure everyone in the class gets the
latest version of Vircon32 built, installed, and running on their local
development system.
REFERENCE
Be sure to check out the Vircon32 Assembly Reference, especially its Internet Resources section to facilitate finding the needed Vircon32 archives.
TASK
Download the latest SOURCE CODE release of the Vircon32
ComputerSoftware repository (latest version as of writing is
v25.10.29). Either grab that (or any newer release), or clone the
ComputerSoftware.git repository (which should be as new or newer than
the latest release).
NOTE: If you are running a release OLDER than v25.10.29 you will want to update, as there were some important bugs resolved and updates with this release.
Please do NOT place the Vircon32 SOURCE CODE in any of existing
repository (not your SEMESTER repo, not the class repo). Place it
someplace entirely independent of version control.
Reading the provided README, go through the build process (installing
any needed supporting packages) to build Vircon32 FROM SOURCE and then
INSTALL it on your local system.
Once you have a working, installed Vircon32 (DesktopEmulator AND
DevTools), grab the "Hello, World!" C example available on lab46 as a
grabit, and test things out (build it, run the cartridge, verify it all
works).
Then, modify that "Hello, World!" C program in some meaningful way, verify it still builds, runs, and works as expected.
You will be submitting that C SOURCE file, the supporting XML file,
along with the built v32 cartridge file.
SUBMISSION CRITERIA
52:btt0:final tally of results (52/52)
*:btt0:grabit of project files before Sunday prior to due date [13/13]
*:btt0:adequate modification of source code beyond default state [13/13]
*:btt0:code compiles cleanly, cartridge builds with no errors [13/13]
*:btt0:the C SOURCE, XML, and v32 cartridge files submitted [13/13]Additionally:
- Solutions not abiding by spirit of project will be subject to a 25% overall deduction
- Solutions not utilizing descriptive why and how comments will be subject to a 25% overall deduction
- Solutions not utilizing indentation to promote scope and clarity will be subject to a 25% overall deduction
- Solutions not organized and easy to read (assume a terminal at least 90 characters wide, 40 characters tall) are subject to a 25% overall deduction