ECE 370 - Computer Organization and Assembly Programming

Announcements

• No lab during Week 0Pinned

  9/23/2026 · ECE 370 · Lab · Schedule Update

  ECE 370 labs do not meet during Week 0. Regular lab sections begin in Week 1.

Course Information

Lab Time & Location

TA Information

For due-date adjustments covered by the course Exception Credit policy, please contact your assigned TA. TAs administer Exception Credit requests in accordance with the published course policy.

Exception Credit

This course provides each student with two deadline override opportunities through the Exception Credit system. Each unused Exception Credit will automatically contribute 2.5% to the student's final course grade at the end of the term. Exception Credits belong to the student and may be used at the student's discretion. Students are NOT required to provide a reason, explanation, or documentation to the TA in order to use an Exception Credit. To use one, the student only needs to notify the TA that an Exception Credit should be applied to the assignment. The TA does not evaluate or approve the student's reason for using an Exception Credit. The TA's role is administrative only: once notified, the TA will record the use of one Exception Credit and override the corresponding due date.

This policy applies to both Homework and Lab assignment (Check off & lab report), exams are not eligible.

Exception Credits are the standard and primary mechanism for handling individual circumstances that interfere with assignment deadlines. If a student has an available Exception Credit, requests for an individual deadline extension will be handled through the Exception Credit system rather than through a separate discretionary extension. Students may not request an additional extension in order to preserve an unused Exception Credit. Requests for deadline extensions based on ordinary personal circumstances, whether made before or after the deadline, will be handled exclusively through the Exception Credit system.

Exception Credits are intended to allow students to manage ordinary unexpected circumstances without disclosing or justifying personal details to the instructional team. Students are therefore responsible for deciding when to use their available Exception Credits.

Once both Exception Credits have been used, no additional extensions will be granted for ordinary personal circumstances, regardless of whether they affect the same or different assignments.

Additional extensions beyond the Exception Credit system will be considered only for a documented emergency or when required by an applicable university accommodation or policy. Appropriate documentation or official verification is required for an emergency-based request to be considered. Documentation establishes eligibility for consideration but does not guarantee that an extension will be granted. The instructor will determine whether an extension or alternative arrangement is warranted and, if so, its appropriate scope.

Lab FAQ

Lab Timeline

Lab Policies (Please Read)

• The lab is graded based on the correctness of your source code submitted to Canvas as a .asm file.
• When any of you turning in source code or checking the demo is absent, you will receive zero points.
• You must indicate your partner's name and your name if you worked in a group. Otherwise, you will lose points.
• Late work will not be accepted.

Grading Weights

Labs 1-6 are 12.5% each, and lab 7 is 25%. Total lab grade will be 50% to your final grade.

Academic Integrity

It is never allowed to represent another person's work as your own. Additionally, this course does not allow you to recycle your previous work even though you have previously taken this course. As an Oregon State University student, you are obligated to conduct yourself by the Student Conduct Code (PDF link). The Student Conduct Code makes it clear that cheating and plagiarism qualify as academic dishonesty and are strictly forbidden. This applies to all submitted lab work, including lab report content, actual assembly code, and study questions. For some examples of acceptable and unacceptable academic conduct in the context of ECE 370, please read the following document: DOs and DO NOTs. If you have any questions about these examples or the Academic Integrity policy in general, please don't hesitate to ask your lab TA.

Plagiarism Penalty: You will be reported to the department for the first instance and receive zero points for the lab.

General Resources

Reference Documents

• ATmega32U4 Datasheet
• AVR Instruction Set Manual
• AVR Assembler
• ECE370 Board Schematic 1
• ECE370 Board Schematic 2
• Atmega32u4 starter guide
• Atmega128_starter_guide
• AVR Simulator Installation Guides
• AVR Guide for Windows (You’re required to use Windows due to a compatibility issue with a debugger tool)

Files

• Pre-compiler Directives (m32U4def.inc; download m32U4def.inc)
• LCD Driver (LCDDriver.asm; download LCDDriver.asm). You will need to include this file in a project directory alongside your project (.asm) file for labs that require the use of LCD.