1. IAY0600 DIGITAL SYSTEMS DESIGN
IAY0600 DIGITAL SYSTEMS DESIGN LABS
Dmitri Mihhailov
Tallinn University of Technology 1

2. Digital Systems Design Labs Staff
Lecturer:
Alexander Sudnitson (associate professor)
ICT-503 ( )
Lab Assistant:
Dmitri Mihhailov
ICT-505 (no phone)
Technical Assistant:
Artjem Rjabov
ICT-505 (no phone) 2 2

3. IAY0600 Digital Systems Design Labs (1)
Lab Room:
ICT-501 (~ 30 working places)
Lab PCs require the same password that is used to access other computers in TTU network
Lab Time:
GROUP A
Wednesdays 16: :30 (primary time)
ICT-501
GROUP B
Wednesdays 17: :15 (reserve time) 3 3

4. IAY0600 Digital Systems Design Labs (2)
Xilinx Design Software:
Vivado Design Suite (7-Series and newer)
System Edition (in the lab)
WebPACK Edition (free)
FPGA boards:
Digilent Nexys-4 DDR (Xilinx Artix-7 FPGA)
used for all labs (1-9)
Power Switch 4 4

5. IAY0600 Digital Systems Design Labs (3)
Lab Course webpage:
IAY0600l Digital Systems Design (WORKSHOPS)
Lab Syllabus
The target lab course:
LABS SET I (Xilinx FPGA-based)
The lab course consists of 9 labs:
Tutorial (essentially not a lab)
Set of compulsory labs (4 labs)
Set of optional labs (4 labs) 5 5

6. Overview of the Lab Types
Tutorials:
Introduce the working flow of design tools
Optional
Compulsory labs:
Form the basic core of the course
MUST be completed within deadline
Yield MINIMUM positive final grade
Allow possibility to attend the exam
Optional labs:
Form the advanced core of the course
NOT REQUIRED to pass the course
Increase the final grade 6 6

7. LABS SET I (Xilinx FPGA-based)
Tutorial labs:
Tutorial (Vivado)
Compulsory labs (+40 points):
Lab 2 (Comparator)
Lab 3 (Adder)
Lab 4 (Parameterizable Adder)
Lab 5 (Serial Adder)
Optional labs (+30 points in total):
Lab 6 (Finite State Machine) pts.
Lab 7 (Greatest Common Divisor) pts.
Lab 8 (Linear Feedback Shift Register) +5 pts.
Lab 9 (Creeping Line) pts. 7 7

8. LABS Schedule Tutorial labs: Compulsory labs: Optional labs:
Week 1 : Tutorial (Vivado)
Compulsory labs:
Week 2 : Lab 2 (Comparator)
Week 4 : Lab 3 (Adder)
Week 6 : Lab 4 (Parameterizable Adder)
Week 8 : Lab 5 (Serial Adder)
Optional labs:
Week 10 : Lab 6 (FSM)
Week 11 : Lab 7 (Greatest Common Divisor)
Week 13 : Lab 8 (LFSR)
Week 14 : Lab 9 (Creeping Line) 8 8

9. List of General Lab Requirements
General lab requirements (NOT final):
The deadline is 16th week (all labs)
One extra DEFENSE ONLY session may be added during the first week of examination session
Labs are done either INDIVIDUALLY, or in teams of TWO students
Labs are passed in the same order as they are listed on the webpage
Lab manuals DO NOT feature all the necessary information for solving the task
Some lab manuals feature TASK description and EXAMPLE solution of a similar task 9 9

10. Step 1 (Visual Demonstration):
How to Pass a Lab
Step 1 (Visual Demonstration):
Working prototype is examined for functional correctness during lab session
Step 2 (Report, INDIVIDUAL):
Submit the following to (cc:
Lab report (PDF)
Project archive (see Tutorial for details)
Wait for acknowledgment of acceptance
Step 3 (Defense, INDIVIDUAL):
Book a slot for defense during lab session
Be ready to answer ANY questions 10 10

11. Reports are written in FREE form
How to Write a Report (1)
Reports are written in FREE form
The goals of lab report:
Document the workflow
Describe the results and their significance
Demonstrate writer’s comprehension
List of topics to cover in the report:
Introduction
Background
Workflow
Results and discussion
Conclusion (including feedback)
References and appendices 11 11

12. In is highly advised to start working on the reports BEFORE the lab
How to Write a Report (2)
In is highly advised to start working on the reports BEFORE the lab
Prepare before the lab:
Introduction
Background and References
Workflow (part that can be done outside the lab)
Prepare during the lab:
Workflow (remaining part)
Prepare after the lab:
Results and discussion
Conclusion 12 12

13. List of General Report Requirements
General report requirements (NOT final):
Lab report MUST feature things that are specifically required to be included in the task
All objects in the text MUST be numbered, labeled and referenced
All concepts, statements, results MUST be explicitly described in verbal form within text
Complete source codes MUST NOT be part of the report (even in appendices)
Functional simulation MUST always be performed and described 13 13