COMP32212 Implementing System-on-Chip Designs syllabus 2014-2015
The ultimate goal of any hardware design is a physical implementation. This course covers the translation of algorithms into a realisable hardware design. The practical part of the course develops higher level models into Verilog HDL and thence to an FPGA. In the lectures the process of mapping designs to ASICs is studied with emphasis on practicalities such as trading chip area, delays, power, etc. to meet a specification. Emphasis is also given to areas which are used extensively in the practical work, particularly simulation, debugging and verification.
The module aims to give an overview of the processes involved in taking a concept onto a product chip. It also illustrates some of the choices available to an implementer. Finally, the practicals are intended to give some experience of the flow, the frustration and the satisfaction of making a working device.
The practical part of the course involves migrating the design of a moderately complex FSM into Verilog, integrating it with other parts of a system-on-chip, verifying that it operates correctly and demonstrating it working. The intention is to use a graphics drawing example design so that the final result can easily be seen on its own display.
The lectures are planned approximately as follows:
The scale of the problem and what VLSI 'looks like', inside.
Some revision plus some features you may not have met before.
Test harness construction and making things 'realistic'.
What to look for and how to find it.
The sort of tools used to get source code into silicon and how to get the best from them.
Simulating big designs and getting sufficiently accurate results in days, not months.
Clocking, clock distribution and the perils of crossing between clock domains.
What every VLSI engineer needs to know about CMOS
Overcoming the crippling effects of reality on a nice, clean design.
Proving the device will work and then checking if it does when the silicon arrives.
Silicon fabrication is still evolving rapidly. A look at some things which are going to make life (even) harder.
2 hours/week (1 hour timetabled, 1 hour independent work)
Feedback methodsFeedback is given orally in scheduled laboratories; lectures are intended to be active and discussion is encouraged.
Annotated listings and diagrams will be returned to students.
Feedback as to whether a constructed (video) system operates correctly should be apparent from simulations during the work's progression and will definitely visible in the final realisation.
- Assessment written exam (2 hours)
- Lectures (12 hours)
- Practical classes & workshops (12 hours)
- Analytical skills
- Problem solving
|Programme outcome||Unit learning outcomes||Assessment|
|A2 B1 B2 B3 C1 C5 C6 C9 D4||Have implemented a substantial hardware unit.|
|A3 B1 B2 C1 C6 D5||Have integrated that unit into a larger hardware design.|
|C5 C6||Have developed greater understanding of HDLs.|
|B2 C4 D4||Be a more confident digital hardware designer.|
COMP32212 does not have a specified reading list.
Course unit materials
Links to course unit teaching materials can be found on the School of Computer Science website for current students.