Difference between revisions of "Main Page"
(→Current Lab Results) |
(→Contact Us) |
||
Line 87: | Line 87: | ||
! rowspan="2" | [[File:redphone.png|70px|left]] | ! rowspan="2" | [[File:redphone.png|70px|left]] | ||
| style="text-align:left;" | '''• [http://ati.ttu.ee/socdesign/index.php/User:Kjans Karl Janson]''' | | style="text-align:left;" | '''• [http://ati.ttu.ee/socdesign/index.php/User:Kjans Karl Janson]''' | ||
+ | | style="text-align:left;" | '''• [http://ati.ttu.ee/socdesign/index.php/User:madker Madis Kerner]''' | ||
|} | |} | ||
Revision as of 14:07, 29 January 2018
Introduction
Welcome to SoC design wiki. We started this series of labs/projects in 2014 and we are upgrading and fixing problems every year to make it better.
Learning Objectives
By completion of the SoC Design labs, you should be able to:
Tutorials:
|
|
Project:
|
Labs Requirements
For these labs we assume that you have passed the following courses:
- IAY0600: Digital Systems Design
- IAY0330: Embedded Systems
So that you are familiar with digital systems and Embedded Systems. You should be familiar with High Level Description Languages like VHDL or Verilog (our main focus is on VHDL but if you know Verilog, it is also ok!).
Lab Organization
Important dates
|
|
Lab grading policy
|
|
Current Lab Results
You can view you current lab results and statistics here |
---|
Contact Us
In case of any questions, please contact us:
• Karl Janson | • Madis Kerner |
Rules and Regulations
Please read the following page before you start the course:
Timing and Plans
Please note that the project ends at the end of semester and will not be extended.
General Rules
- Unplugging any cables from the lab computers is NOT ALLOWED! If you use your own computer, please use Wi-Fi.
- It is OK to discuss your code with co-students during the labs.
- Copying co-student's code is not OK! You need to write it yourself.
- You must understand the code you write! We will check everyone.
Writing Code
We would like to re-use your code later on so keep these things in mind:
- Use comments in your code. Even you, as the programmer, who wrote the code, will otherwise not understand your code after a while.
- Write a proper doc-string for the functions. It makes the life of you and others a lot easier.
- Use meaningful variable names. The purpose of a variable with the name "counterMaxValue" is much easier to understand that the same variable with the name "cMNum", for example.
In Case of Problems
Please use the following methods in the following order for solving your issues:
- Check the current lab's additional materials.
- Re-read the lab manual to make sure you did not miss anything.
- Google your problems
- Ask the lab assistants for help.
NOTE: In case you find a problem with the documentation, please tell the assistants. Then we can fix the problem and everyone will be happy :)
Lab Tasks
Lab Tutorials
Here you can find lab manuals for the tutorials:
- Lab 1: Kernel Driver [NOT UPDATED YET!]
- Lab 2: Building custom SoC on ZedBoard [NOT UPDATED YET!]
- Lab 3: Custom IP creation [NOT UPDATED YET!]
- Lab 4: Setup 1 board system for the lab [NOT UPDATED YET!]
Labs additional readings
Additional reading and more information about the labs can be found here:
General documents
Lab specific documents
Using Own Computer for the Labs
If you plan to use your own computer, please refer to the Using Own Computer page.
Tutorial Labs Archive
Audio Mixer Project
Project Description
Design project is defined in each round for System on Chip design(IAY0550) students with the aim of providing them with real world experience of working on a SoC project, teamwork and project management. This wiki will serve as a platform for students to pass-on their designs and documents to students in the next round of course. Full description of the project can be found on the Project Description page
- Project Description page.
Git
The project code should be stored in git. Every component of the project should be uploaded as a separate branch.
There exists a dedicated Github repository for the course, that can be accessed here: [1]
Team Organization
The following page is for clear and transparent team organization for design project: