Your total score for this course is calculated as follows:

• During the semester: permanent evaluation counts for 55% of the course grade.
  • Permanent evaluation: Assignments Computer Systems
  • Permanent evaluation: Projects Computer Architecture
    
  Assignments and Projects are handed in via Blackboard. Projects are evaluated during an oral defense.
• Examination period: the Theory exam counts for 25% of the course grade.
  The course material covered by the theory exam is described in this overview of what to study for the exam.
• Examination period: the practical exam together with its oral defense counts for 20% of the course grade.
  • Examination period: Practical exam (in computer lab: preparation of the design of a datapath as well as translating a high-level program to that architecture)
  • Examination period: Defense of practical exam with questions to test Computer Systems background
    
• To pass the course, you need to attend or submit every part that will be graded (if not, your grade will be "AFW" - absent). Additionally, you need to get an overall score of at least 50%, and a score of at least 40% on the theory exam, and a score of at least 40% on the practical exam, and a score of at least 40% on the year projects (architecture and systems combined). If not, your grade will be min(7, your_score). your_score is the score you would get when applying the weights given above.

• The weights of the different parts of the course remain the same as during the January session:
  • 25% theory-exam
  • 20% practical-exam
  • 40% project computer architecture during the year ("permanent evaluation")
  • 15% exercises computer systems during the year ("permanent evaluation")
  Each of these parts may have to be re-done during the Second Session.
  You do not have to (but may) re-do those (entire) parts for which you got a score of at least 50% (i.e., "partiële vrijstelling"). By "entire" we mean that exemptions will in principle not be given for sub-parts of each of the four parts of the course. You should explicitly ask for an exemption via e-mail and you will be notified via e-mail whether this request was granted.
• For the "during the year" parts, you will need to individually finish and submit (and defend) the "Computer Systems" assignments and a "Computer Architecture" project. These will be slight modifications of the original ones (see below). Deadline for these assignments is 16 August 2020 at 23:55. Submission is done via Blackboard.
• The structure of the examination remains the same. All defenses take place during the examination period.
• The examination method and the material to study for the Second Session are identical to that of the First Session. There will again be a written theory exam about both CS and CA, as well as a practical exam with oral defense on Computer Architecture. The course material covered by the theory exam is described in this overview of what to study for the exam.

All lectures (in PDF format) can be found at the URL announced in class. Before each class, the slides are last year's. By the next lecture, the slides are updated to reflect this year's changes.

In each lab session, you will be given some assignments (Computer Systems) and/or a project (Computer Architecture). All assignments are made individually, projects are solved in groups of two students.

The assignments for Computer Systems are bundled in 3 larger projects and are made individually. These projects require you to apply and combine all topics seen in the weeks before the project deadline. Projects have to be submitted to Blackboard. Every project will clearly indicate what is expected.

The projects and exercises can be found here.

In each lab session, you will work on a project in pairs of two students. Projects build on each other, to converge into a unified whole at the end of the semester. During the semester, you will be evaluated three times. At these evaluation moments, you will present your solution of the past projects by giving a demo and answering some questions. You will immediately receive feedback, which you can use to improve your solution for the following evaluations.

For every project, you submit a small report of the project you made by filling in verslag.html completely. A report typically consists of a summary of everything you implemented and an explanation of the choices you made ​​in the implementation. Again, put all your files in a tgz archive. The name of that archive consists of your last and first name, without spaces. If, for example, your name is Jan De Smedt, the file name of your archive must be DeSmedtJan.tgz.

The projects can be found here.

The HTML forms you will need for the solutions (right click, save as):

• verslag.html

You have to adapt the HTML-code manually (i.e., in notepad) to fill in the forms. A good HTML tutorial can help you with this. Remark: in the forms, the <u> element for underlining is redefined to "overline". This way, you can express NOT in Boolean algebraic expressions: e.g., NOT A OR B becomes A+B. Unfortunately, double overline is not possible. Of course, you can always use the NOT A OR B notation.

Throughout the course we will use the following tools:

• Logisim
• MARS

Both tools require java to run. The tools are installed on the lab computers.

If you would like to run a UNIX distribution on your own computer, we suggest Ubuntu. You can install Ubuntu next to your Windows using the Windows installer. After installation, you will be able to choose on startup between Windows and Ubuntu. If you would like to run Ubuntu inside your Windows, you can install Ubuntu on VirtualBox by following these steps.

In order to copy files in Windows from and to servers (e.g., between your laptop and the studento.uantwerpen.be server) you can use WinSCP. You can simply use the scp command ("secure copy") if you are using UNIX.

You can only access the studento.uantwerpen.be server from a university network or through a vpn connection (to access this page, open it after you are logged in to Blackboard).

The burden of timely submission of your work on Blackboard is on you! (late submissions are not accepted)

• Beware that Blackboard's clock may differ slightly from that on your computer. Allow a margin for submission.
• Be sure to check that your submission was actually made. Check for example under Grade Centre whether your (as yet unmarked) submission shows up.

Exercises 1: Introduction to Unix

Introduction session on Unix commands. The use of Unix Shell Commands is explained.

Material:

• Slides Introduction
• Slides Introduction to UNIX
• Assignments

Exercises 2: Regular Expressions

Introduction and assignments on Regular Expressions and the use of sed.

Material:

• Slides
• Assignments

Exercises 3: UNIX Scripting

Introduction to and assignments on UNIX Scripting.

Material:

• Slides
• Assignments

Project UNIX

Project for the UNIX part of the course.

Material:

• Project
• Example submissions

Intermezzo: vi

Material:

• Slides

Exercises 4: Data Representation

Assignments on data representation

Material:

• Slides
• Assignments
• files.py
• input.txt

Exercises 6: MIPS: Introduction

Introduction of MIPS and the use of MARS

Material:

• Slides
• Assignments
• Examples

Exercises 7: MIPS: Building your Projects' Building Blocks

Assignments on MIPS

Material:

• Slides
• Assignments

Exercises 8: MIPS: Putting your Project together

Assignments on MIPS Stacks and subroutines

Material:

• Assignments
• input_maze
• frame example
• Subroutines/Functions in MIPS

Exercises 9: MIPS: Extending your Project

Assignments on MIPS Recursion

Material:

• Assignments
• Maze layout

Second Session

The following exercises must be completed:

• Datarepresentatie: Exercises second session retake
• MIPS: werk je doolhof verder af of verbeter je code

Indien je een onvoldoende had op je oefeningen tijdens het jaar wordt er verwacht dat je beide onderdelen opnieuw instuurt.

Project 1: Gates and Wires

Introduction to Logisim and the use of gates.

Material:

• Slides
• Project assignment

Project 2: Adders

Build an 12-bit adder (ripple carry adder and carry lookahead adder).

Material:

• Slides
• Project assignment

Project 3: ALU

Build a 12-bit ALU.

Material:

• Project assignment
• ALU_GroupXX.circ
• Test_GroupXX.txt
• Test.py

Project 4: Memory

Build a register file, counter, stack, and a finite State Machine for a traffic light.

Material:

• Project assignment

Project 5: Datapath

Build a program counter and a datapath.

Material:

• Project assignment
• SD_GroupXX.circ
• Test.py
• SDTest_GroupXX.txt
• Slides

Project 6: Full Datapath

Add branch, jump and immediate instructions to the instruction set.

Material:

• Project assignment
• Test.py

Project 7: Datapath in Use

Write programs to run on your datapath.

Material:

• Project assignment

Second Session

This is a variation on the projects of the first session. The goal is to individually solve a variation of all projects, with the differences explained in the following assignment:

• Project assignment second session retake
• TestRetake.py