General instructions

Computer class account

To be able to work on the class computers one must have an account. The following page allows you to open an account: pass.ttu.ee. To be able to open an account or change account information you must log in using an ID-card. You can also open an account in room ICT-410.

Working in the class

All the computers have 2 operating systems installed on them. To be able to use the tools needed for this lab, the computer must be switched to Linux operating system (manual restart helps). By default the first operation system chosen is Windows. With functional account at hand then:

  1. Type your name and password.
  2. Open a terminal window (can be found from the menu when doing right click on the desktop).
  3. Type suitable command and start working!

Checking the lab class computer operating system

To be able to log on from outside the class the computer must be in linux operating system. The change of the operating system must be done manually in the class. By default windows is booted. As everybody can restart the computers any time it is adviced to save your work continuously when accessing the class from outside network. Class status

Working outside TUT using Windows


PROXY WORKS!

To be able to work on the computer class computer from home a ssh protocol must be used along with X11 protocol. For this some programs must be installed. One set of programs can be found here.

Another and perhaps simpler guide refers using Putty and Xming environment .

Working outside TUT using other than Windows

An example for Linux users for computer lx22.

  1. Start xterm
  2. ssh -X -l username@intra.ttu.ee proksi.intra.ttu.ee
  3. Type your password
  4. ssh -X -l username@intra.ttu.ee lx22.pld.ttu.ee
  5. Type your password
  6. Start working!

Organizing work in computer class

There are three virtual drives connected to your account.

  1. Drive P - is for your own material, can be seen (by yourself) on Windows, Linux and on the web (if you log in).
  2. Drive W - consists of stuff that will be on the internet (basically your "public_html" folder). Can be seen by everybody.
  3. Drive M - lecturer material drive.

We recommend to use your "Documents" folder to store your projects. The main cause for this is that ModelSim cannot use the P-drive. Recommended is to create HDL directory to your Documents folder. In the HDL folder make a folder for every lab separately. In example: folder for lab1, folder for lab2 etc. Store the material for every lab in the appropriate folder.

Licenses

Since we have a limited number of licenses (9 for Synopsys and 25 for Mentor Graphics), please use tools only for direct simulation/synthesis. Especially when there are many students working at the same time in the lab. Close the tool (or at least stop simulation) when editing files, reading documentation, or doing something else!

Coding and coding convetion

It is higly recommended to comply with some coding rules. Not all the given codes have been accordingly edited. Therefore editing the codes based on the given rules is welcome.

  1. Comment important and functional program code. In example: --computational block
  2. Structure your code. Leave empty lines between functional blocks (this means that don't leave the line, where there's no functional block).
  3. Indent your code. To get an overview of different styles check here.
  4. Leave spaces between operands. In example: a := ( b + c ) * 3;
  5. Give labels to important concurrent statements: process, block, instance etc.
  6. Give entities, architectures, ports, constants, types, signals and variables meaningful names.

For futher reading take a look at this.

Defence of the labs

Labs must be presented both literally as a report and orally during lab hours. What is needed in the report is brought out in the next paragraph. Oral defence of the lab requires explanation and presentation of the written code and the simulation/synthesis results. Also answers to the questions of the task and any questions which the lab instructor might ask.

Lab reports

The report must have a title page. Example.

Report must contain:

  1. Description and reasoning of used solutions (up to 1 page depending on the complexity of the task).
  2. Explanation of the test bench organization and analysis of the result ( up to 1 page when testing in an essential part of the task).
  3. Simulation and/or synthesis results (waveforms, parameters, numbers, etc.).
  4. Answers to the questions in the task.
  5. Evaluation of the result(s).

Send reports to :
hardi.selg [at] ati.ttu.ee
bniazmand [at] ati.ttu.ee
siavoosh [at] ati.ttu.ee (for the 3rd lab: Pico CPU: Writing the behavioural model)