| Instructor(s) | Dr. Vadim Geurkov [Coordinator] Office: ENG430 Phone: (416) 979-5000 x 556088 Email: vgeurkov@torontomu.ca Office Hours: TBD | Calendar Description | This course introduces students to small microprocessor-based systems, with an emphasis on embedded system hardware and software design. Topics will include microprocessor architecture and structure, with an overview of 8- 16- and 32-bit systems, assembly language programming and the use of high-level languages. Basic input/output including parallel communications with and without handshaking and serial protocols. Hardware and software timing. Using interrupts and exceptions. Overview of single-chip microprocessors and controllers with an emphasis on the Freescale HCS12. The internal structure and design of peripheral devices. Memory system design and analysis. The use and structure of development tools such as (cross) assemblers or compilers, monitor programs, simulators, emulators, etc. | ||||||||
| Prerequisites | CEN 199 and COE 328 and ELE 404 and MTH 314 | ||||||||||
| Antirequisites | None | ||||||||||
| Corerequisites | None | ||||||||||
| Compulsory Text(s): |
| ||||||||||
| Reference Text(s): |
| ||||||||||
| Learning Objectives (Indicators) | At the end of this course, the successful student will be able to:
NOTE:Numbers in parentheses refer to the graduate attributes required by the Canadian Engineering Accreditation Board (CEAB). | ||||||||||
| Course Organization | 3.0 hours of lecture per week for 13 weeks | ||||||||||
| Teaching Assistants | TBA | ||||||||||
| Course Evaluation |
Note: In order for a student to pass a course, a minimum overall course mark of 50% must be obtained. In addition, for courses that have both "Theory and Laboratory" components, the student must pass the Laboratory and Theory portions separately by achieving a minimum of 50% in the combined Laboratory components and 50% in the combined Theory components. Please refer to the "Course Evaluation" section above for details on the Theory and Laboratory components (if applicable). | ||||||||||
| Examinations | Midterm exam in Week 7, one hour and fifty minutes, closed book (covers Weeks 1-5). Final exam, during the exam period, three hours, closed-book (covers Weeks 1-12). | ||||||||||
| Other Evaluation Information | Lab Project The lab assignments and the project (originally developed by Prof. Peter Hiscocks) involve a robot. The project is to program the eebot mobile robot with a navigation system that can find its way through a maze, reverse, and back its way out again. A possible variation on this is that the robot first learns the maze. Then it is started again at the beginning and should navigate the maze without errors. The project must be demonstrated during the demonstration week. The project report must be submitted on or before the end day of the semester. At the time of demonstration, students will also be required to submit the project source code electronically. Lab Management Labs will be graded 8 marks maximum for each lab, to a maximum of 40 marks which will be scaled to 20% of the final mark. And there will be lab quizzes at the end of labs 2, 3, 4 and 5, accounting for a maximum of 5% of the final mark. Credit for labs will be based on the quality of how well the project works (demonstration) and how well the student can answer questions about the lab. If answers to these questions are inadequate, the lab will be marked as 0, although the student will be given an opportunity to rectify his or her preparation. Partial marks may be assigned at the discretion of the instructor. The Lab Project accounts for 10% of the final mark. The project must be demonstrated during the Demonstration Week. The project report must be submitted on or before the end day of the semester. It must include: - A formal description of the work (at least 2 pages, no more than 5 pages) - An appendix containing a hard copy of all source code (.asm file) The proper report description should address the following: - Overall approach and description of performance - Main design decisions - Problems encountered and their solutions - Recommendations:how you would continue the project to make it even better and how you would try to fix any remaining bugs. At the time of demonstration, you will also be required to submit your source code electronically. (You will be told how to do this.) The Project Evaluation will be done according to the following: Evaluation of Lab Project (8%): - 3.5% Basic functionality - 3.5% Code quality - 1.0% Extra functionality Evaluation of Project Report (2%): - 1.0% Report English quality - 1.0% Report technical quality All the labs are done individually. The lab project is done in groups of 3 students. Each student must also keep a complete and continuous record of the year's lab activities. Equipment should not be moved during the lab; if you believe equipment to be defective, report it to the lab instructor who will take care of the problem. Labs are conducted using a Motorola HCS12-based microprocessor board and computer-aided design tools from Freescale, specifically "Special Edition: CodeWarrior for HCS12(X) Microcontrollers (Classic)". To obtain a passing grade in the course, a student must obtain at least 50% in both the lab and theory portions of the course. | ||||||||||
| Other Information | None |
Week | Hours | Chapters / | Topic, description |
|---|---|---|---|
1 | 3 | 1, 2 | Introduction to COE 538 - Scope and objectives, management |
2 | 3 | 2, 3, 4 | HCS12 Assembly Programming |
3 | 3 | 4, 7 | Advanced Assembly Programming |
4 | 3 | 6, 12 | Interrupts |
5 | 3 | 6, 8 | Interrupts, Clock Generation and Operation Modes |
6 | 3 | 8 | Timer Functions |
7 | 2 | 1-4, 6, 7, 12 | Midterm |
8 | 3 | 5 | C Language Programming |
9 | 3 | 9 | Serial Communication Interface |
10 | 3 | 10 | The SPI Function |
11 | 3 | 11 | Inter-Integrated Circuit (I2C) Interface |
12 | 3 | 14 | Internal Memory Configuration and External Expansion |
13 | 3 | 1-12,14 | Review and Catch Up |
Exam Period | 3 | 1-12,14 | Final Exam - Covers material up to the end of week 13 |
Week | L/T/A | Description |
|---|---|---|
2 | ENG411 | Lab 1: Using the CodeWarrior IDE and Introduction to Assembly Language Programming |
3-4 | ENG411 | Lab 2: Programming the I/O Devices |
5-6 | ENG411 | Lab 3: Battery and Bumper Displays |
7 | ENG411 | Lab 4: Motor Control & Using the Hardware Timer |
8-9 | ENG411 | Lab 5: Robot Roaming Program |
10-12 | ENG411 | Project: Robot Guidance Challenge |
Students are reminded that they are required to adhere to all relevant university policies found in their online course shell in D2L and/or on the Senate website
You can submit an Academic Consideration Request when an extenuating circumstance has occurred that has significantly impacted your ability to fulfill an academic requirement. You may always visit the Senate website and select the blue radio button on the top right hand side entitled: Academic Consideration Request (ACR) to submit this request.
For Extenuating Circumstances, Policy 167: Academic Consideration allows for a once per semester ACR request without supporting documentation if the absence is less than 3 days in duration and is not for a final exam/final assessment. Absences more than 3 days in duration and those that involve a final exam/final assessment, require documentation. Students must notify their instructor once a request for academic consideration is submitted. See Senate Policy 167: Academic Consideration.
Academic Accommodation Support (AAS) is the university's disability services office. AAS works directly with incoming and returning students looking for help with their academic accommodations. AAS works with any student who requires academic accommodation regardless of program or course load.
Academic Accommodations (for students with disabilities) and Academic Consideration (for students faced with extenuating circumstances that can include short-term health issues) are governed by two different university policies. Learn more about Academic Accommodations versus Academic Consideration and how to access each.
At Toronto Metropolitan University, we recognize that things can come up throughout the term that may interfere with a student’s ability to succeed in their coursework. These circumstances are outside of one’s control and can have a serious impact on physical and mental well-being. Seeking help can be a challenge, especially in those times of crisis.
If you are experiencing a mental health crisis, please call 911 and go to the nearest hospital emergency room. You can also access these outside resources at anytime:
If non-crisis support is needed, you can access these campus resources:
We encourage all Toronto Metropolitan University community members to access available resources to ensure support is reachable. You can find more resources available through the Toronto Metropolitan University Mental Health and Wellbeing website.