School of Electronic
& Electrical Engineering
FACULTY OF ENGINEERING & PHYSICAL SCIENCES
ELEC5620M: Embedded Systems Design
Assignment 3: Mini-Project
Assignment Information
Technical Brief — Mini-Project — Interactive LCD based ARM Demonstrator
Dr David Cowell
Prof Steven Freear
Mr Thomas Carpenter
Mr Harry Clegg
Compiled with LuaTEX, last updated 20:36, on 24
th March, 2021
ELEC5620M: Embedded Systems Design Assignment 3: Mini-Project
Typographical conventions
The following typographical conventions are consistent throughout this module.
• Source code is shown in syntax highlighted monospaced font as:
a = !b;
• Buttons, menus and file-tree selections you should click are shown as:
File » Exit
• Graphic User Interface (GUI) selections and text input are shown in italics:
Select Go from the list
Type Hello in the box.
• Keyboard shortcuts are shown in square brackets as:
[ctrl + C]
• Names of physical things are shown as bold font:
Cyclone V
• Names of commands and processes are shown as bold monospaced font:
commit
• File and project names are shown in bold green monospaced font:
hello.v
new_project
• Paths are shown as bold green monospaced using the Windows path separator \ :
C:\Path\To\File
Note: Extra information and clarification that you might find useful can be found in note blocks.
Warning: Potential pitfalls and problems are highlighted in warning blocks.
Important: Important information is shown in important blocks.
1
ELEC5620M: Embedded Systems Design Assignment 3: Mini-Project
Part 1: Assignment Information
Part 1: Assignment Information
Important: This assignment is due at 2pm on Friday 21st May 2021. This mini-project is assessed
forming a total module weighting of 50%, split as 25% technical report and GitHub code and 25% video
presentation with hardware demonstration. You must submit your report via Turnitin, Code via GitHub
and Presentation via Minerva before the deadline. A 5% per day/partial day penalty will be subtracted
from your score for late submission. If you encounter technical difficulties during submission, you must
email your report before the deadline to d.m.j.cowell@leeds.ac.uk and then submit the report and code
without alteration through Minerva and GitHub at the next available opportunity.
1.1 Technical Report and Code Submission (25%)
1.1.1 Technical Report (Turnitin Submission)
The report has a strict page limit of 10 technical pages. A 10% penalty will be incurred for each additional
page over the limit. You should additionally include a cover page with the Report Title, your Name and SID.
The cover page does not count towards the page limit. You may additionally place supplementary diagrams
and images in an Appendix, which will not count towards the page limit. All of your source code MUST
also be included, as neatly formatted text in the Appendix (which will not count towards the page limit).
Screenshots or photos of code are not allowed and will not be marked!
1.1.2 Code Submission (GitHub Classrooms Repository)
All of your project files including source files (.c and .h) and your DS-5 Project Files (.project and
.cproject), must be incrementally uploaded to GitHub throughout your development and testing process.
Uploading code towards the end of the development cycle is not acceptable.
1.2 Video Presentation with Hardware Demonstration (25%)
You are expected to produce a 5-minute video of yourself presenting slides highlighting the key parts of the
project along with what you have learned during the project work. The video can contain either audio of
yourself narrating the presentation or a video of yourself overlaid on the presentation slides. The presen-
tation MUST also contain a working video demonstration of your mini-project and MUST clearly show the
number label on your DE1-SoC board. For general risk mitigation you are recommended to test whichever
technology you are planning to use for your video presentation early!
1.3 Plagiarism
The source of any IP cores, drivers or code structures from ANY external sources must be clearly identi-
fied in the references section of your report and in comments within your code. You will not be awarded any
marks for these parts of code, however you will not be penalised for using them so long as full reference to
the source of the code is given.
Any external IP core or code found that has not been properly referenced, or any code shared between
students, will be considered plagiarism and dealt with by the external University Plagiarism committee.
2
ELEC5620M: Embedded Systems Design Assignment 3: Mini-Project
Part 2: Technical Brief — Mini-Project — Interactive LCD based ARM Demonstrator
Part 2: Technical Brief — Mini-Project — Interactive LCD
based ARM Demonstrator
The aim of the mini-projects is to program the DE1-SoC development board and LT24 LCD module to
create an interactive demonstration of your ARM Microprocessor design skills you have learnt throughout
this module. You may choose to design a game, an educational device, a fractal generator, or other design
of your choosing.
You may make use of the peripherals used in the module e.g. Buttons, LEDs, 7-segment displays Timers,
Audio etc. Furthermore, you may make use of other peripheral devices not introduced in the lab sessions
however no module staff support is available. The project is ARM based, so the FPGA is off-limits.
Choose your demo wisely to ensure that you demonstrate ALL the skills you have learnt in this module.
You will create a report outlining the details of the system and its design, with evidence of as much testing,
both simulation and hardware, as is required to verify your design. The report and presentation will be
assessed according to the rubric on the Minerva » ELEC5620M » Assessment » Mini-Project page.
The project will be marked according to the following criteria.
• Minimum requirements:
– Use the LT24 LCD, or VGA output.
– Make use of Buttons/Switches for inputs.
– Software flow control using polling techniques.
– Evidence of hardware debugging.
– Well formatted, fully commented code, incrementally uploaded to GitHub.
– Technical report uploaded to Turnitin.
– Presentation uploaded to Minerva.
• To get better marks:
– Complex software control techniques.
– Text display.
– Generating Audio Output.
– Reuse of IP developed during this module.
– Use of your own custom IP blocks.
• To get even better marks:
– Developing fully parameterised and generalised custom IP blocks.
– Add features to existing hardware drivers provided during the module.
3













































































































学霸联盟