Labs will be based on web pages, GCC documentation, and PIC MCU documentation.
We will expect you to become completely familiar with detailed MCU information from microchip.
The purpose of this course is to enable students to carry out sophisticated designs of the modern digital systems which now appear in products such as automobiles, appliances and industrial tools. The basis of such systems is the microcontroller, a microcomputer optimized for single-chip system design by possessing many peripheral devices geared to real-time applications. The microcontrollers we will use are the MIcrochip PIC32 series RISC microcontrollers. There is a large design project which is due the last week of classes.
This course is a design course. This
means that we will expect you to show considerable creativity, flexibility,
In particular you will need to:
In other words, we are trying to make it a little like the real world.
There will be lab assignments and a final project, plus some consideration of class participation.
The final design project is due the last week of classes.
The course grade will be calculated as follows:
You are expected to attend your assigned lab period every week and to finish the lab assignment in the alloted time. You must finish the assignment before the end of the alloted 3 hours, or you will lose up to 50% of your lab grade. You can, of course, start early on an assignment. All negotiations concerning lab absences due to plant trips or sickness are to be conducted with your lab instructor. For plant trips you must notify your instructor in advance.
Lab work will be in groups of 2 or 3. All members are expected to become proficient with all aspects of the lab. Where each has prepared design work or code assigned as homework, the group design will involve negotiation. The members of a group may be graded differentially if it becomes obvious that one person is doing the bulk of the work.
Each student in this course is expected to abide by the Cornell
University Code of Academic Integrity. Any work submitted by a student
in this course for academic credit will be the student's own work. For
this course, collaboration is allowed between partners in a group.
Students agree that by taking this course all required papers
may be subject to submission for textual similarity review to
Turnitin.com for the detection of plagiarism. All submitted papers
will be included as source documents in the Turnitin.com reference
database solely for the purpose of detecting plagiarism of such
papers. Use of Turnitin.com service is subject to the Usage Policy
posted on the Turnitin.com site.
Examples of allowed/not allowed collaboration:
++ Allowed: All homework and code must be shared within a group.
-- Not Allowed: Sharing of any material between groups.
++ Allowed: Talking in lab about code with another group.
-- Not Allowed: Emailing code to another group or using another group's keyboard to type code.
++ Allowed: Showing another group your circuit.
-- Not Allowed: Wiring for another group, or lending them your circuit.
++ Allowed: Talking about the contents of a lab report to another group.
-- Not Allowed: Copying anything (even one sentence) from any web or print document, unless the source is stated and the quote is short.
++ Allowed: Using code from previous final projects or web sources with attribution.
-- Not Allowed: Using code from previous final projects or web sources without attribution.
Each laboratory assignment requires a written report. You will submit a single report for your group. The report must be handed in at your assigned lab section, one week after the lab is finished. The report should be submitted as a collection of pages stapled or bound together.
The report should be a concise documentation of the project assigned. The presentation should be arranged so that any reader with technical competence in the subject can easily understand what was done and how it was done. The following report organization is suggested:
Past TAs have expanded on this outline with an example report and another and another.
But NOTE that this year's reports do not include homework. Homework is handed in separately.
Guidlines for student assessment (from ABET guidlines). Final projects will be evaluated by the guidelines given in abilty to design, ability to commmunicate, problem solving, and professional and ethical responsibility.
Access to computers
You and your partner will have use of a PC, microcontroller evaluation board, and peripheral breadboard in Phillips 238 during your assigned lab period. Students from other lab periods may use setups not needed by students attending their assigned lab.
N.B. Machines and file systems sometimes die. You should always back up all your work. There is no excuse for lost work, even if it is because of a compiler or other system error.
If you are experiencing undue personal or academic stress at any time during the semester or need to talk with someone about a personal problem or situation, I encourage you to seek support as soon as possible. I am available to talk with you about stresses related to your work in my class. Additionally, I can assist you in reaching out to any one of a wide range of campus resources, including:
DISABILITY-RELATED CONCERNS: Students with either an ongoing or short-term disability are encouraged to contact Student Disability Services (SDS) for a confidential discussion of their need for academic accommodations.SDS is located in 420 CCC building; phone number is 254-4545.