L14: Final Project KickoffSchedule - ISchedule - IIChoosing A TopicGrading (36 points Total)Design RulesDesign Rules - 2 LabkitL14: 6.111 Spring 2008 1Introductory Digital Systems LaboratoryL14: Final Project KickoffL14: Final Project KickoffL14: 6.111 Spring 2008 2Introductory Digital Systems LaboratorySchedule Schedule -- II Form project teams – by April 2nd Project Abstract (Due April 7thin 39-5537 by 1PM) Start discussing project ideas with the 6.111 staff Each group should meet with Prof. Akinwande to discuss the scope of the project and breakdown of tasks Abstract should be about 1 page (clearly state the work partition) – a polished abstract will be published on the course website once your project has been finalized. Sample abstracts can be viewed at http://web.mit.edu/6.111/www/s2006/PROJECT/projects.htmlhttp://web.mit.edu/6.111/www/s2007/PROJECTS/projects.html Work in teams of two or three. A single person project requiresspecial approval by the 6.111 staff. Proposal Conference with TAs (April 9-11). Bring your detailed proposal with you (3-5 pages including figures). Block diagram conferences with TAs (April 14-18) Review the major components in the system and your overall design approach Each group in discussion with TA, creates a deliverables checklist (i.e., what we can expect to be demonstrated) – (Due April 28th in class). Specify the device components you need to acquire (small budget allocated for each project if component does not exist in the stock room). Get approval from the 6.111 staff and your TA will contact John Sweeney to obtain the parts.L14: 6.111 Spring 2008 3Introductory Digital Systems LaboratorySchedule Schedule -- IIII Project Design Presentation (in 32-144) on April 25 & 28 Each group will make an electronic presentation (power point or PDF) Everyone is required to attend all days (not just the days you are presenting) – this will count in your participation grade. Each student will write comments (anonymous) which will be provided to the presenting group as feedback. Final project check-off (with teaching staff) on May 13: 30 minutes Final project presentations and video taping on May 14 (Wednesday): ~3-4 minutes (videos to be posted on the course website with permission) Final project report (in electronic format, which will be published with permission on the course website) due May 15 by 5:00PM (no late project check-offs or reports accepted) Kits have to be returned by May 15that 5PML14: 6.111 Spring 2008 4Introductory Digital Systems LaboratoryChoosing A TopicChoosing A Topic You only have 5 weeks total (once your proposal abstract is turned in) to do this project. Be realistic in what you take on.It is important to complete your project.It is very difficult to receive an “A” in the class without completing the final project. The complexity should be equal or larger than lab4 for each student. Quite often you will need to include analog building blocks (video, wireless, motors, etc.). However, keep in mind that this is a digital class and your design should demonstrate digital design principles. Complexity and innovation factor. We will give credit to innovative applications, design approaches More complex is not necessarily betterL14: 6.111 Spring 2008 5Introductory Digital Systems LaboratoryGrading (36 points Total)Grading (36 points Total) Report and Presentation (6 points) Problem Definition and Relevance, Architecture, Design methodology (7 points) What is the problem and why is it important System architecture and partitioning Design choices and principles used Style of coding All of the above should be stated in the project presentation and report Functionality (17 points) Did you complete what your promised (i.e., graded by your customized checklist) Innovation (6 points)L14: 6.111 Spring 2008 6Introductory Digital Systems LaboratoryDesign RulesDesign Rules Use hierarchical design Partition your design into small subsystems that are easier to design and test Design each sub-system so they can be tested individually When appropriate, use Major/Minor FSMs Use the same clock edge for all edge-triggered flip-flops Beware of clock skew Avoid problems from ‘glitches’ Always assume that combinational logic glitches Never clock a register from the output of combinational logic Never drive a critical control signal such as write enable from the output of combinational logic Ensure a stable combinational output before it is sampled by CLK. Create glitch-free signals byz Registering outputs z Gating the clockL14: 6.111 Spring 2008 7Introductory Digital Systems LaboratoryDesign Rules Design Rules -- 22 Avoid tristate bus contention by design Synchronize all asynchronous signals Use two back to back registers Use memory properly Avoid address changes when WE is true Make sure your write pulse is glitch free Power supply can be noisy Use bypass capacitors to filter noise Chip-to-chip communication Beware of noise (inductance) Might need to synchronize signals Can also use “asynchronous” protocolsL14: 6.111 Spring 2008 8Introductory Digital Systems LaboratoryLabkitLabkit Based on a huge Xilinx FPGA Built-in audio/video interfaces, high-speed memory Supports moderately high-speed designs (50-100MHz)FPGA I/O (128 signals)Composite and S-Video in/outVGA outputPS/2 mouse, keyboardAlphanumeric DisplayAudio line in/outRS-2326M gate FPGA4MB ZBT SRAM16MB flash ROMHeadphones/
View Full Document
Unlocking...