CSCS2650 Computer Organization

PROJECT: DEBUG A PROGRAM (dap2)

OBJECTIVE

Extend our debugging infrastructure with the creation of a debugregs subroutine.

TASK

Implement a Vircon32 assembly subroutine that uses your dap0 routine. subroutine. Your task is to display the set of CPU registers (R0-R13), along with their hexadecimal contents.

No parameters need to be given to this debugging subroutine, since it will always be displaying this same range of registers.

Specifically, be sure to:

… call the subroutine debugregs or _debugregisters, and place it in your existing debug.s file so that both (and also _debugmemory from dap1) can be %include'ed as needed in debugging efforts.

Make sure it that it calls and makes use of your original _debug in the process of operation (let _debug handle the display of information).

That it is written entirely in Vircon32 assembly language, using no compiler-generated routines from the Vircon32 API (no print, no itoa)

As stated above: no parameters need to be passed in to use this routine.

Pertaining to the registers, make sure your routine preserves existing register states, so that whatever was going on before the call to debug is saved, so you can restore it upon completion).

Display registers R0-R7 in the left column, starting at or near the top left of the screen, with R8-R13 in the right column, separated by an appropriate distance.

SUBMISSION

To be successful in this project, the following criteria (or their equivalent) must be met:

  • Project must be submit on time, by the deadline.
    • Late submissions will lose 33% credit per day, with the submission window closing on the 3rd day following the deadline.
  • Processing must be correct based on input given and output requested
  • Output, if applicable, must be correct based on values input
  • Code must be nicely and consistently indented and aligned
  • Code must be consistently written, to strive for readability from having a consistent style throughout
  • Code must be commented
    • Sufficient comments explaining the point of provided logic MUST be present
  • Track/version the source code in your private semester repository
  • Submit a copy of your source code to me using the submit tool by the deadline.

SUBMIT TOOL USAGE

Let's say you have completed work on the project, and are ready to submit, you would do the following (once on LAB46, with all your data present):

lab46:~/src/SEMESTER/comporg/dap1$ make submit

You should get some sort of confirmation indicating successful submission if all went according to plan. If not, check for typos and or locational mismatches.

RUBRIC

I'll be evaluating the project based on the following criteria:

286:dap2:final tally of results (286/286)
*:dap2:submitted file called debug.s or debug.asm [26/26]
*:dap2:subroutine is called _debugregs or __debugregisters [26/26]
*:dap2:code assembles with no warnings or errors [26/26]
*:dap2:register states preserved across call [26/26]
*:dap2:calls upon original _debug to do data output [26/26]
*:dap2:output contains display of registers, contents [52/52]
*:dap2:screenshot of subroutine in action to DISCORD [26/26]
*:dap2:code contains usage instructions in comments [26/26]
*:dap2:output contains display of addresses, contents [26/26]
*:dap2:functionality is correct and to specifications [26/26]

ADDITIONALLY

  • Solutions not abiding by spirit of project will be subject to a 50% 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 or otherwise maintaining consistency in code style and presentation 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