Professional Documents
Culture Documents
Course Outline Example topics covered in class include: Assembly, C programming Memory and pointers Editors/Assemblers Instruction set Program design Basic I/O Serial communication Interrupts and timers Networking (TCP/IP) Scheduling Resource sharing RTOS Homework (Total of 4 6 HWs) Homework submissions are due before class starts. No late submissions are accepted. If you are absent from class or you know that you will be absent from class, you should, as soon as possible, arrange with the instructor for any missed work. It is the student's responsibility to contact the instructor in such a case. Collaboration on homework is ok, copying is not ok; a separate solution is required for each student. Include your name on all homework assignments, reports, exams, etc. Turn in solutions that are written clearly and neatly; disorganized or esthetically-ugly solutions with scratched out text, figures, and formulas, etc. is penalized by deducting grade-points even if the final answer is correct. Labs (Total of 6 8 Labs) All labs must be completed or you will fail this course. One lab (missed for any reason) only can be madeup in the final week. Make-up labs will only be allowed in special situations. The extraordinary circumstances requiring a make-up lab must be verifiable. Lab assignment demos and reports are due in the next lab following the lab with the assignment. Project (Semester-long project) Students are required to complete a semester-long project devoted to the design of an embedded system implemented on the evaluation board. The projects topic is assigned by the instructor or proposed by students and approved by instructor. Each project requires three written reports (proposal, progress, and final) in PDF format. The final report must include a detailed description of the embedded system and its implementation, experimental results, and information on how to verify the solution. Students must demonstrate the project to the instructor during the last week. In addition, students must create a video presentation to describe and demonstrate their final project. Attendance Statement, Quizzes and Other Policies While university regulations do not require attendance in class, the student should know that there may be material covered in class which is not discussed in the text or which may be discussed in a different manner than presented in the text. The student is responsible for all the material discussed in class EE 500LLB Embedded Systems, Fall 2013
whether or not the student was in class. If the student misses a class period, it is the student's responsibility to obtain the notes from a classmate. Having said that, Quizzes are designed to encourage class attendance. A total of 4 6 in class surprise quizzes will be assigned in the class for a total of 5% of the final grade. If the student has questions about the way a particular homework or exam problem was graded, s/he should discuss this with the instructor during office hours. However, this must be done within one week the exam or homework was returned to the class. Questions during class are highly encouraged. Professionalism "Students are expected to use professional style in all communications, including email, with course faculty and teaching assistants. This includes the use of salutations and closings (including clear identification of the author) and proper grammar." "Students are expected to refrain from use of cell phones or other electronic devices unless they are clearly linked to class purposes (e.g., note-taking). Cell phones must remain off or muted." No food or drinks in the labs Special Needs Students with disabilities or other special needs, who need special accommodations in this course, are invited to share these concerns or requests with the instructor as soon as possible. Academic Honesty All work in this course must be completed in a manner consistent with University at Buffalo academic integrity policy. Violation of this policy will result in receipt of a failing grade. Please read: http://undergrad-catalog.buffalo.edu/policies/course/integrity.shtml If you are in doubt, please ask me. Do not assume. Expectations This course requires considerable amount of time and effort in order to successfully complete the project, HWs, Exams and other assignments. It is expected that the student is prepared for that. Skills Needed An embedded system application involves a diverse set of skills that extend across traditional disciplinary boundaries, including o computer hardware o software o interface electronics Make engineering tradeoffs that extend across these boundaries Course Relevance to your discipline As engineers, it is very likely that you will: o Design microprocessors and other digital circuits (e.g., ASICs, FPGAs, etc.) to be used in embedded applications o Develop software (e.g., design automation CAD tools, RTOS, apps, etc.) for the embedded market o Work in application fields that involve an embedded microprocessor o Design sensors/actuators (e.g., MEMS devices) that may be used in embedded systems It is certain that you encounter embedded systems in all aspects of your daily life! Acknowledgements: This Course syllabus is adopted from the Syllabus for EE 459/500 at UB, taught by Dr. Cristinel Ababei in Spring 2013. EE 500LLB Embedded Systems, Fall 2013
2. I got. . .
4. I am hoping. . .