lunduniversity.lu.se

Computer Science

Faculty of Engineering, LTH

Denna sida på svenska This page in English

Assignments

Read the lab description before the lab starts.

Sample Data

You can generate your own data sequences using this Java program.

Here are some pre-generated sequences: n10_gcd71.txtn30_gcd3.txt,n50_gcd6211.txtn70_gcd128.txtn100_gcd587.txt 

There are a number of ways to send the data to your system through a serial via a terminal. SDK has its own terminal, although kind of limited (sending files is only by copy&paste content). Putty, HyperTerminal, Hyper-V are better alternatives.
For instance, you can send a text file to your design from the HyperTerminal by "Send Text File..."  from the "Transfer" menu.

Lab 1: EDK Tutorial

  • Description (.pdf)
  • Allocated time: 1 lab (2 hours)

Lab 2: GCD-S1 Software, Uni-Processor Solution

  • Preparations: Read the axi_timer documentation. Have a look at the example files for the timer (polled timer especially), found via Vivado and SDK
  • Select two different GCD algorithms and implement them in C
  • Description (.pdf)
  • Additional files: getnum.c
  • Allocated time: 1 lab (2 hours)

Lab 3: GCD-SM Software, Multi-Processor Solution

  • Preparations: Decide on how to distribute the GCD on the processors and implement this in C (one program per processor)
  • Description (.pdf)
  • Allocated time: 1 lab (2 hours)

Lab 4: Hardware Accelerator for GCD

  • Description: (.pdf).
  • Allocated time: 2 labs (4 hours). If you have not done any VHDL Simulation previously, please read Xilinx User Guide on Vivado Simulation UG937 or watch this YouTube Video.
  • NOTE, bitshifts in VHDL:
    mySignal <= myOldSignal(1 to 31) & '0'; -- left shift, multiply by 2 (the operation & does bit concatenation)
    mySignal <= '0' & myOldSignal(0 to 30); -- right shift, divide by 2

Lab 5: GCD-S1H Hardware Accelerated Software, Uni-Processor Solution

  • Description (.pdf)
  • Additional files: the AXI IP core wrapper: myip_2.0.zip.
  • Allocated time: 1 lab (2 hours)

Laboratory Report

The deadline for handing in the report is June 23, 2020, 23:59.

NOTE: Do not expect ANY feedback on the report before this deadline!

NOTE: Reporting the lab results in Ladok may likely happen AFTER summer due to the late deadline.

You should write one report summarizing the experiences from all labs. Writing the lab report is necessary for completing the labs. In brief, the report should gather your experiences, thoughts and observations made during the lab assignments. It is supposed to be close to a technical/scientific report with a clear motivation of the problem, approach and solutions, advantages and drawbacks, as you perceive them from the lab assignments. Here are some important materials that can help you along:

  • A skeleton with structure and more detailed content description can be found in this .pdf file. Use it as a guideline for your report (This is for an older version of the tools!). Pay special attention to the Power and Energy section - you will need to do some work on your own.
  • Using LaTeX to edit and generate your report is strongly recommended. The sources for the skeleton given above can be found in this .zip file (.tex, .bib, figure). Information about LaTeX can be found in the Links page.
  • The report must contains a comparison of the different systems. To do this you must run the same test cases (sample data) with the same optimization levels for all systems (lab 2, 3, and 5)

You should hand in the final report by email, in .pdf format. Mail the report to edan15@cs.lth.se. The subject of the mail must be "report byuser1, user2" where the user1 and user2 are the SAM IDs you used when enrolling for the labs.

Page Manager: