PHASE 1: PREPARATIONS
Inspection of initial design and calculations. Work load estimation of this phase: 20h.

1. Students must have made some idea of the solution to the topic and be familiar with the given main components. Study closely all features of MCU and select the features which suits the requirements. It is good idea to write these as theory part for final report in this phase.
   
   
2. Time table (days for each phase meeting) for project! The web pages give some workload estimates of each task set for each meeting. Based on these estimates and students own reasoning, the students must make their own timetable, and preliminarily book the rest of the meetings with their assistants. The meeting times are preliminary i.e. they can be revised later, but the purpose is to give the students the idea of how to spend time with this course. The students must notify certain things regarding the deadline:
   • The assistants may be on holiday at some points of the course, i.e. there may be restrictions for meeting times.
   • There are 25 other groups per assistant attending this course, i.e. this limits the available times for meetings, and the availability of programming and debugging points in TS139. Note that especially when the deadline is approaching TS139 tends to be very crowded.
   • The equipment may get broken occasionally due to too rough handling. The assistants repair things to their best ability, but they cannot be checking the equipment after every single group. Thus, we hope that you handle things very carefully, and repair what you break. Repair guide is available on the course web pages.
   • The ordering of components takes about a week.
   • The milling of the PCB takes about a week, depending on the milling queue.
   
   
   
3. The students must present block diagram of the hardware. You may also use SA/SD context diagram for that. Specify which peripheral of the MCU will be used for each functionality/external device.
   
   
4. Specify software functionalities. How control will be done in software level? How interfaces are used? What is included in execution cycle? Polling or interrupts? Use block diagram, SA/SD state chart or textual description. For drawing block diagrams, use for example SA/SD (like prosa), or Inkscape or other graphical tools (Word is not a good choice). You must have knowledge of what software features affect to hw design!