IAY 0600 DIGITAL SYSTEMS DESIGN LABS Dmitri Mihhailov

IAY 0600 DIGITAL SYSTEMS DESIGN LABS Dmitri Mihhailov Tallinn University of Technology

Digital Systems Design Labs Staff n Lecturer: Alexander Sudnitson (associate professor) aleksander. sudnitson@ttu. ee ICT-503 (620 2255) n Lab Assistant: Dmitri Mihhailov dmitri. mihhailov@ttu. ee ICT-505 (no phone) n Technical Assistant: Artjem Rjabov artjom. rjabov@ttu. ee ICT-505 (no phone) 2

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

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

IAY 0600 Digital Systems Design Labs (3) n Lab Course webpage: http: //ati. ttu. ee/~alsu/ IAY 0600 l Digital Systems Design (WORKSHOPS) http: //ati. ttu. ee/~alsu/IAY 0600 l. html Lab Syllabus n The target lab course: LABS SET I (Xilinx FPGA-based) n The lab course consists of Tutorial (essentially not a lab) Set of compulsory labs (4 labs) Set of optional labs (4 labs) 9 labs: 5

Overview of the Lab Types n Tutorials: Introduce the working flow of design tools Optional n 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 n Optional labs: Form the advanced core of the course NOT REQUIRED to pass the course Increase the final grade 6

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

LABS Schedule n Tutorial labs: Week 1 : Tutorial (Vivado) n Compulsory labs: Week 2 : Lab 2 (Comparator) Week 4 : Lab 3 (Adder) Week 6 : Lab 4 (Parameterizable Adder) Week 8 : Lab 5 (Serial Adder) n 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

List of General Lab Requirements n General lab requirements (NOT final): The deadline is 16 th 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

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

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

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

List of General Report Requirements n 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