525.615.81 - Embedded Microprocessor Systems

Expanded Course Description

This section may be cross-listed with other sections in the same course. Sections are cross-listed to enrich student learning and enhance collaboration opportunities.

Course Structure

Course Topics

• ARM Architectures
• Memory in Embedded Systems
• Inputs/Outputs in Embedded Systems
• The Software Design Process and Real-Time Systems
• Design and Debugging
• RTOS
• Open Source vs Proprietary Software
• Case Studies in Embedded Systems
• Best Practices in Designing Embedded Systems
• Performance and Optimization
• Device Interfacing
• Security
• Standards

Course Goals

Course Learning Outcomes (CLOs)

• Compare and contrast embedded and desktop systems.
• Develop code in assembly and C for embedded microprocessor units.
• Explain basic embedded system architectural elements, such as general input-outputs, timers, and interrupts.
• Utilize technical information about the hardware/software architecture being used/designed.
• Conduct architectural trades for embedded systems.
• Apply your own testing strategies for embedded systems for troubleshooting and design improvement.
• Design an embedded system based on a set of requirements, producing specification, implementation, and testing plans.
• Utilize a distributed version control system for tracking changes and coordinate work among collaborators.
• Discriminate between various types of embedded systems and critique their strengths and weaknesses.

Textbooks

There are three textbooks for this course:

• E. White, Making Embedded Systems, O'Reilly Media, 2012.
• J. Catsoulis, Designing Embedded Hardware, O'Reilly Media, 2005.
• D. Norris, Programming with STM32:  Getting Started with the Nucleo Board and C/C++, McGraw-Hill Education, 2018.

Other Materials & Online Resources

Equipment will be shipped to students by the 3rd week of the class. The equipment will be shipped in a box that will have a return box and label for packing and returning at the end of the semester. The Elegoo parts kit is for each student to keep after the class; return the STM32 development boards, the Analog Discovery 3 device, and the USB cables that come with them.

Required Software

Student Coursework Requirements

It is expected that each module will take approximately 7–12 hours per week to complete. Here is an approximate breakdown:  Researching the topic (approximately 3-4 hours per week), viewing the video slide presentations (approximately 1-2 hours per week), completing lab assignments (approximately 2-5+ hours per week), and collaboration assignments (approximately 1 hour per week).  Not all modules will have collaboration assignments.

This course will consist of the following basic student requirements:

Assignments (40% of the overall grade)
Collaboration (15% of the overall grade)
Quizzes (15% of the overall grade)
Final Project (30% of the overall grade)

• Assignments: Students should approach each module in the order it's presented in Canvas. This includes reading, watching short lecture videos, and completing assignments.The assignments are hosted through GitHub Classrooms. Students are encouraged to work together, but not copy, on labs. For some students, the hands-on part will go easily and quickly. For others, it will be a lot of work and trial/error as you debug your circuits and code. Do not wait until the last minute to start the assignments. This will help you turn in your assignments on time.
  
• Collaboration: Students will be required to collaborate with one another on 3 to 4 person teams. Each team will be responsible for posting collaborative materials and answering questions via Canvas. Each directed assignment will have the points its worth posted in the written directions. Collaboration must be done interactively and collaboratively, as the name suggests.
• Quizzes: There will be two quizzes for this course, one midway (Module 8 for FA/SP and Module 6 for SU) and one towards the end (Module 14 for FA/SP and Module 12 for SU). The quizzes will be primarily multiple choice, true/false, and essay (but not limited to those).
• Final Project: Students will design, implement, test, and deliver an embedded system against a set of requirements. This project will require the student to formalize their design, identify risks in the design/implementation/testing process, propose mitigations against those risks. This will be conducted in the last four weeks of the course.

Late Policy: Students should make every effort to turn Assignments, Discussions/Collaborations, and Quizzes on time. Late submissions for Assignments and Discussions/Collaborations will result in a 5% penalty each day the submission is late, up to one week. After that week, the submission will no longer be considered. For example, if an assignment is worth 100 points, then each day the submission is late, 5 points will be deduced from the final grade, up to 35 points (7 days x 5 points = 35 points/week). After one week, the Assignment or Discussion/Collaboration will become a zero. For example, if the assignment is due on Tuesday at 23:59 Eastern, then the absolute latest you can turn in the assignment would be on Monday at 23:59 Eastern. Students may coordinate with the instructor for a waiver of the late penalty and submission timeline; this must be done before the due date. Acceptable excuses include, but are not limited to, travel for work, family issues/emergencies, planned vacations. If you work with the instructor well in advance, there should be no issues. The Quizzes will be unavailable after each module, so there is no opportunity for a late submission. So, make every effort to finish the quiz during that module week.

Grading Policy

A grade of A indicates achievement of consistent excellence and distinction throughout the course—that is, conspicuous excellence in all aspects of assignments and discussion in every week.

A grade of B indicates work that meets all course requirements on a level appropriate for graduate academic work. These criteria apply to both undergraduates and graduate students taking the course.

EP uses a +/- grading system (see “Grading System”, Graduate Programs catalog, p. 10). You should contact your Program Chair for guidance on the breakdown used by your program.

Overall Percentage Points for Course:

Final grades will be determined by the following weighting:

Academic Policies

Deadlines for Adding, Dropping and Withdrawing from Courses

Students may add a course up to one week after the start of the term for that particular course. Students may drop courses according to the drop deadlines outlined in the EP academic calendar (https://ep.jhu.edu/student-services/academic-calendar/). Between the 6th week of the class and prior to the final withdrawal deadline, a student may withdraw from a course with a W on their academic record. A record of the course will remain on the academic record with a W appearing in the grade column to indicate that the student registered and withdrew from the course.

Academic Misconduct Policy

All students are required to read, know, and comply with the Johns Hopkins University Krieger School of Arts and Sciences (KSAS) / Whiting School of Engineering (WSE) Procedures for Handling Allegations of Misconduct by Full-Time and Part-Time Graduate Students.

This policy prohibits academic misconduct, including but not limited to the following: cheating or facilitating cheating; plagiarism; reuse of assignments; unauthorized collaboration; alteration of graded assignments; and unfair competition. Course materials (old assignments, texts, or examinations, etc.) should not be shared unless authorized by the course instructor. Any questions related to this policy should be directed to EP’s academic integrity officer at ep-academic-integrity@jhu.edu.

Students with Disabilities - Accommodations and Accessibility

Johns Hopkins University values diversity and inclusion. We are committed to providing welcoming, equitable, and accessible educational experiences for all students. Students with disabilities (including those with psychological conditions, medical conditions and temporary disabilities) can request accommodations for this course by providing an Accommodation Letter issued by Student Disability Services (SDS). Please request accommodations for this course as early as possible to provide time for effective communication and arrangements.

For further information or to start the process of requesting accommodations, please contact Student Disability Services at Engineering for Professionals, ep-disability-svcs@jhu.edu.

Student Conduct Code

The fundamental purpose of the JHU regulation of student conduct is to promote and to protect the health, safety, welfare, property, and rights of all members of the University community as well as to promote the orderly operation of the University and to safeguard its property and facilities. As members of the University community, students accept certain responsibilities which support the educational mission and create an environment in which all students are afforded the same opportunity to succeed academically. 

For a full description of the code please visit the following website: https://studentaffairs.jhu.edu/policies-guidelines/student-code/

Classroom Climate

JHU is committed to creating a classroom environment that values the diversity of experiences and perspectives that all students bring. Everyone has the right to be treated with dignity and respect. Fostering an inclusive climate is important. Research and experience show that students who interact with peers who are different from themselves learn new things and experience tangible educational outcomes. At no time in this learning process should someone be singled out or treated unequally on the basis of any seen or unseen part of their identity. 
 
If you have concerns in this course about harassment, discrimination, or any unequal treatment, or if you seek accommodations or resources, please reach out to the course instructor directly. Reporting will never impact your course grade. You may also share concerns with your program chair, the Assistant Dean for Diversity and Inclusion, or the Office of Institutional Equity. In handling reports, people will protect your privacy as much as possible, but faculty and staff are required to officially report information for some cases (e.g. sexual harassment).

Course Auditing

When a student enrolls in an EP course with “audit” status, the student must reach an understanding with the instructor as to what is required to earn the “audit.” If the student does not meet those expectations, the instructor must notify the EP Registration Team [EP-Registration@exchange.johnshopkins.edu] in order for the student to be retroactively dropped or withdrawn from the course (depending on when the "audit" was requested and in accordance with EP registration deadlines). All lecture content will remain accessible to auditing students, but access to all other course material is left to the discretion of the instructor.