Course coordinator
Dr Matthew D'Souza
Course overview
- Study period
- Semester 2, 2024 (22/07/2024 - 18/11/2024)
- Study level
- Undergraduate
- Location
- St Lucia
- Attendance mode
- In Person
- Units
- 2
- Administrative campus
- St Lucia
- Coordinating unit
- Elec Engineering & Comp Science School
Microcontroller system hardware and software. C programming for embedded microcontroller and peripheral devices. Principles and practice of using Embedded RTOS (Real Time Operating System) and peripheral devices such as sensors and actuators to build a small embedded system. Peripheral interfacing methods and standards. Analog-digital conversion methods and interfacing. Basics of digital communication signals, modulation schemes and error correction methods. Data compression, formats for audio, image and video coding.
CSSE3010 introduces students to concepts, methods, and techniques in developing embedded real-time systems. The required prerequisite knowledge should be gained in CSSE2010 and CSSE2310 courses. This course aims to provide students with the theoretical basis and practical skills in using microcontrollers with Real Time Operating Systems (RTOS). A 32-bit platform is used throughout the course, with all development using the C language and a real-time operating system. Since most modern embedded systems communicate with other computer-based systems, the basics of data communication are covered and extensively applied in the project.
CSSE3010 covers:
- 32-bit processor architecture and peripherals
- RTOS principles.
- Theory and practice of interfacing to analog world and other digital systems.
- Principles of building larger systems with microcontrollers
- Communication buses used in embedded systems
- Principles of data coding and communication
Course requirements
Assumed background
1. Knowledge of microcontroller architecture and principles of operation:ﾠprogram execution, subroutines, stack operation, basics of timing generation and capture, software - hardware interfacing basics: polling andﾠinterrupts, basics of microcontroller C programmingﾠ-- material covered in CSSE2010.
2. Knowledge and advanced skills in C programmingﾠ-- material covered in CSSE2310. ﾠ
3. Good understanding of operating systems principles and basics of networking, covered in CSSE2310, is useful to have but not necessary.ﾠAdditional sources of related material will be provided during lectures.
4. An understanding of electrical circuits as covered in ELEC2004 or ELEC2400 is usefulﾠto have but is not necessary. Additional sources of related material will be provided during lectures.
It is recommended to complete CSSE2010 and CSSE2310, before CSSE3010.ﾠIt is recommended to NOT take CSSE2010 or CSSE2310, at the same time as CSSE3010.
Prerequisites
You'll need to complete the following courses before enrolling in this one:
CSSE2010 and CSSE2310
Incompatible
You can't enrol in this course if you've already completed the following:
CSSE4001 or CSSE7003 or CSSE7301
Course contact
Course staff
Lecturer
Dr Matthew D'Souza
Guest lecturer
Associate Professor Konstanty Bialkowski
Timetable
The timetable for this course is available on the UQ Public Timetable.
Aims and outcomes
The course aims at providing a theoretical background and practical skills in design and implementation of embedded systems with microcontrollers.
Learning outcomes
After successfully completing this course you should be able to:
LO1.
Implement real-world solutions using the design principles of embedded systems and system interfacing
LO2.
Use the principles of data encoding to implement robust communication channels
LO3.
Analyse an embedded system's performance and infer potential problems
LO4.
Maximise the performance and efficiency of an embedded system design implementation
LO5.
Build and test software library sub-modules and hardware sub-modules for embedded systems
LO6.
Employ a real-time operating system with bare metal C programming libraries to develop functional embedded systems.
LO7.
List the technology and design methods used in real-world engineering.
LO8.
Illustrate and outline the details of your embedded systems designs.
Assessment
Assessment summary
| Category | Assessment task | Weight | Due date |
|---|---|---|---|
| Computer Code, Notebook/ Logbook, Practical/ Demonstration, Quiz |
Stages Assessment
|
30% |
5/08/2024 3:00 pm 19/08/2024 3:00 pm 2/09/2024 3:00 pm 16/09/2024 3:00 pm
All stated dates and times are AEST |
| Computer Code, Notebook/ Logbook, Practical/ Demonstration, Project |
Project Milestone
|
5% |
30/09/2024 3:00 pm
All stated dates and times are AEST |
| Computer Code, Practical/ Demonstration, Project |
Project
|
30% |
21/10/2024 1:00 pm
All stated dates and times are AEST |
| Examination |
Final Exam
|
35% |
End of Semester Exam Period 2/11/2024 - 16/11/2024 |
A hurdle is an assessment requirement that must be satisfied in order to receive a specific grade for the course. Check the assessment details for more information about hurdle requirements.
Assessment details
Stages Assessment
- Hurdle
- In-person
- Mode
- Product/ Artefact/ Multimedia, Written
- Category
- Computer Code, Notebook/ Logbook, Practical/ Demonstration, Quiz
- Weight
- 30%
- Due date
5/08/2024 3:00 pm
19/08/2024 3:00 pm
2/09/2024 3:00 pm
16/09/2024 3:00 pm
All stated dates and times are AEST
Task description
All stage specifications are available on Black Board. Four stages are optional (non-compulsory) to attempt and will be assessed at 7.5% per stage. The marks of all four stages are summed together to calculate the final stage mark. The assessed stages and schedule will be listed on Blackboard.
Stage. Code and Quiz Due Date
Blackboard submissions and quizzes must be completed by the due date and time. The code developed for the stage must be submitted to the student's repository by the due date and time.
Demonstration (in-person) - your lab session
Each stage must be demonstrated (in person) during your assigned lab session using the submitted stage code by the due date and time. Failure to demonstrate your stage will result in no marks being recorded for the demonstration, blackboard submission, or code.
Hurdle requirements
You must obtain at least 50% of the combined Stages, Milestones, and Project marks. e.g. Stages + Milestone + Project > =50%Submission guidelines
Stage quiz and diagrams must be submitted on BlackBoard. Stage code must be submitted to the code repository by the due date, using git push. Code submissions made with only git commit, will not be accepted.
Deferral or extension
You may be able to apply for an extension.
The maximum extension allowed is 7 days. Extensions are given in multiples of 24 hours.
If you have an approved extension, you must post a private note on the ED Discussion Board, using the EXTENSION tag, when your code has been uploaded to your repository. A staff member will respond to your note to state when your demo will be assessed.
Marked submissions with feedback and/or detailed solutions with feedback will be released to students within 7-14 days, where the earlier time frame applies if no extensions.
Late submission
A penalty of 10% of the maximum possible mark will be deducted per 24 hours from time submission is due for up to 7 days. After 7 days, you will receive a mark of 0.
You must post a private note on the ED Discussion Board, using the LATE tag, when your code has been uploaded to your repository. A staff member will respond to your note to state when your demo will be assessed.
Project Milestone
- Hurdle
- In-person
- Mode
- Product/ Artefact/ Multimedia, Written
- Category
- Computer Code, Notebook/ Logbook, Practical/ Demonstration, Project
- Weight
- 5%
- Due date
30/09/2024 3:00 pm
All stated dates and times are AEST
Task description
Project Milestone - as specified in the Project sheet, available on Blackboard.
Diagrams must be submitted to BlackBoard by the due date and time.
Demonstration (in-person) - your lab session
You must attend your session in the due week to do your demo. Failure to demonstrate your milestone will result in no marks being recorded.
Hurdle requirements
You must obtain at least 50% of the combined Stages, Milestones, and Project marks. e.g. Stages + Milestone + Project > =50%Submission guidelines
All project milestone code must be submitted to the code repository by the due date. The diagrams must be submitted to BlackBoard by the due date. Code must be submitted to the code repository by the due date, using git push. Code submissions made with only git commit, will not be accepted.
Deferral or extension
You may be able to apply for an extension.
The maximum extension allowed is 7 days. Extensions are given in multiples of 24 hours.
If you have an approved extension, you must post a private note on the ED Discussion Board, using the EXTENSION tag, when your code has been uploaded to your repository. A staff member will respond to your note to state when your demo will be assessed.
Marked submissions with feedback and/or detailed solutions with feedback will be released to students within 7-14 days, where the earlier time frame applies if no extensions.
Late submission
A penalty of 10% of the maximum possible mark will be deducted per 24 hours from time submission is due for up to 7 days. After 7 days, you will receive a mark of 0.
You must post a private note on the ED Discussion Board, using the LATE tag, when your code has been uploaded to your repository. A staff member will respond to your note to state when your demo will be assessed.
Project
- Hurdle
- In-person
- Mode
- Product/ Artefact/ Multimedia, Written
- Category
- Computer Code, Practical/ Demonstration, Project
- Weight
- 30%
- Due date
21/10/2024 1:00 pm
All stated dates and times are AEST
Task description
The project is specified in the Project sheet available on Blackboard. The project code repository and blackboard upload must be submitted by due date and time.
Demonstration (in-person) - your lab session
You must attend your session in the due week to do your demo. Failure to demonstrate your project will result in no marks being recorded.
Hurdle requirements
You must obtain at least 50% of the combined Stages, Milestones, and Project marks. e.g. Stages + Milestone + Project > =50%Submission guidelines
All stage code must be submitted to the code repository by the due date. All diagrams and other assessment must be submitted to BlackBoard. Code must be submitted to the code repository by the due date, using git push. Code submissions made with only git commit, will not be accepted.
Deferral or extension
You may be able to apply for an extension.
The maximum extension allowed is 7 days. Extensions are given in multiples of 24 hours.
If you have an approved extension, you must post a private note on the ED Discussion Board, using the EXTENSION tag, when your code has been uploaded to your repository. A staff member will respond to your note to state when your demo will be assessed.
Marked submissions with feedback and/or detailed solutions with feedback will be released to students within 7-14 days, where the earlier time frame applies if no extensions.
Late submission
A penalty of 10% of the maximum possible mark will be deducted per 24 hours from time submission is due for up to 7 days. After 7 days, you will receive a mark of 0.
You must post a private note on the ED Discussion Board, using the LATE tag, when your code has been uploaded to your repository. A staff member will respond to your note to state when your demo will be assessed.
Final Exam
- Hurdle
- Identity Verified
- In-person
- Mode
- Written
- Category
- Examination
- Weight
- 35%
- Due date
End of Semester Exam Period
2/11/2024 - 16/11/2024
Task description
The final exam assesses only the theoretical aspects of the course.
Hurdle requirements
To pass this course, you must obtain at least 40% of the final exam marks.Exam details
| Planning time | 10 minutes |
|---|---|
| Duration | 120 minutes |
| Calculator options | (In person) Casio FX82 series only or UQ approved and labelled calculator |
| Open/closed book | Closed Book examination - no written materials permitted |
| Exam platform | Paper based |
| Invigilation | Invigilated in person |
Submission guidelines
Deferral or extension
You may be able to defer this exam.
Course grading
Full criteria for each grade is available in the Assessment Procedure.
| Grade | Cut off Percent | Description |
|---|---|---|
| 1 (Low Fail) | 0 - 19 |
Absence of evidence of achievement of course learning outcomes. |
| 2 (Fail) | 20 - 44 |
Minimal evidence of achievement of course learning outcomes. |
| 3 (Marginal Fail) | 45 - 49 |
Demonstrated evidence of developing achievement of course learning outcomes |
| 4 (Pass) | 50 - 64 |
Demonstrated evidence of functional achievement of course learning outcomes. |
| 5 (Credit) | 65 - 74 |
Demonstrated evidence of proficient achievement of course learning outcomes. |
| 6 (Distinction) | 75 - 84 |
Demonstrated evidence of advanced achievement of course learning outcomes. |
| 7 (High Distinction) | 85 - 100 |
Demonstrated evidence of exceptional achievement of course learning outcomes. |
Additional course grading information
Your overall percentage will be the sum out of 100 of your assessment marks which is then rounded to the nearest whole percent and then possibly capped as described below. Assessment items will be weighted as described above.
If you achieve less than 40% on the final exam then your overall percentage will be capped at 49% and your final grade is capped at 3.
If you achieve less than 50% on your combined Stages, Milestone and Project mark then your overall percentage will be capped at 49% and your final grade is capped at 3.
In other words, to pass the course, you must achieve:
- at least 50% of the total course marks, and
- at least 40% of the final exam marks, and
- at least 50% on the combined Stages, Milestone and Project mark.
Supplementary assessment
Supplementary assessment is available for this course.
Additional assessment information
Use of AI Tools
All assessment tasks evaluate students' abilities, skills and knowledge without the aid of generative Artificial Intelligence (AI) or Machine Translation (MT). Students are advised that the use of AI technologies to develop responses is strictly prohibited and may constitute student misconduct under the Student Code of Conduct.
Learning resources
You'll need the following resources to successfully complete the course. We've indicated below if you need a personal copy of the reading materials or your own item.
Library resources
Find the required and recommended resources for this course on the UQ Library website.
Additional learning resources information
Lecture recordings will be made available on Blackboard.ﾠ
All additional technical information required in this course will be supplied as copies of engineering papers, documentation, or source code.
A complete development kit and software environment is available for loan. The development kit must be signed out, in-person during a lab session, during the first week. If you are unable to attend a lab session, in the first week, contact the coordinator to make an alternate arrangement. The development kits can only be collected from the lab. The development kit must be returned at the end of the semester or if theﾠstudent unenrolls in the course.
Alternatively, the components for the development kit can be purchased directly from third parties (not supported by the university). Aﾠlist of components and suggested suppliers will be made available. It will be then theﾠstudent's responsibility to ensure that they have access the correct components.
Learning activities
The learning activities for this course are outlined below. Learn more about the learning outcomes that apply to this course.
Filter activity type by
Please select
| Learning period | Activity type | Topic |
|---|---|---|
Multiple weeks |
Lecture |
Lectures Lectures cover topics in embedded system design. The lectures are synchronised, as much as possible, with topics covered in projects. |
Practical |
Project Stage Sessions Weekly laboratory development and consultation sessions with tasks specified according to the project stages. Software modules developed in these sessions are to be reused and integrated in the project. |
Policies and procedures
University policies and procedures apply to all aspects of student life. As a UQ student, you must comply with University-wide and program-specific requirements, including the:
- Student Code of Conduct Policy
- Student Integrity and Misconduct Policy and Procedure
- Assessment Procedure
- Examinations Procedure
- Reasonable Adjustments - Students Policy and Procedure
Learn more about UQ policies on my.UQ and the Policy and Procedure Library.
School guidelines
Your school has additional guidelines you'll need to follow for this course: