1. ARRANGEMENTS FOR ‘PRODUCT’ TIME Mark Neil - Microprocessor Course 1 Microprocessor Laboratory

2. Example Product: Signal Generator Mark Neil - Microprocessor Course 2 A Signal Generator should be programmable. A user can use the the LCD display and the keyboard to change the:  Frequency scale  Amplitude scale  Offset on/off etc.  Waveform shape (Square, Sinusoidal, Triangle..) Analog control given by potentiometer Analog signal output by using a Digital to Analog Converter (DAC)

3. Other ideas for a ‘product’ Mark Neil - Microprocessor Course 3 Alarm Clock Home Security System Digital Thermometer Calculator Cycle Computer Distance ranging device Programming Language (parser/Interpreter) Guitar tuner Elevator Control I2C Master/Slave interfaces Tetris Game Digital Safe(swipe/PIN) Voice Recorder X-Y Plotter Data Logger Signal Generator Plant water control Password generator Guitar effects

4. Project Mark Neil - Microprocessor Course 4 Produce plan by beginning of next week and submit as ‘progress report’. It will be assessed and used to agree your project with your demonstrator. 1 report per design team - 2 sides A4 max  What are you going to do?  How will it work? (Top down modular design)  What equipment will you need?  How will you divide the effort within your team? Be creative  We are looking for innovative ideas

5. Hardware Mark Neil - Microprocessor Course 5 You will be using the Atmega-128 boards and breadboards for your design Plus any of the hardware we have been using in the lab so far Lots of other hardware is available  Ask the demonstrators  Ask Lee Parker  Try to avoid rummaging through cupboards yourself!

6. Demonstrators Mark Neil - Microprocessor Course 6 Demonstrators will now reduce their time in the laboratory to a 15 minute visit during each session. Demonstrators remain available on call at any time during their allocated periods.

7. Reports Mark Neil - Microprocessor Course 7 2 unit experiments automatic sign-off on Friday 26 th February Report deadline is 11 days later on Monday 7 th March Submit using standard 3rd year lab process and forms Standard penalties apply for late submissions Report submitted in electronic form Your programmes should be left on the machines and they will be looked at by the assessors. Attach (commented!) programme code as appendix Use laboratory guidelines for report writing Length guidelines – <4000 words

8. The ‘Product’ Report Structure Mark Neil - Microprocessor Course 8 Abstract Introduction High Level Design Software and Hardware Design Results and Performance Updates, Modifications and Improvements Conclusions Product Specifications Appendices

9. Top Down Modular Programming Mark Neil - Microprocessor Course 9 C C Calculator Initialise Get command CalculateOutput Reset Load values Prompt message Input Interpret command Select/run routine Format output Display Output character Input character Output character Output character …. complexitycomplexity time C C

10. Assessment process Mark Neil - Microprocessor Course 10 Report will be first marked by assigned demonstrator within 1 week. Demonstrator will arrange interview with you for sometime in week of 14 th March or the following week Individual interview (15 minutes) should include working demonstration and question and answer session. Feedback on report will be given. Second marking by me

11. Assessors Mark Neil - Microprocessor Course 11

12. Project advisor contact details Mark Neil - Microprocessor Course 12 SurnameForenameGroupPhoneBuildingRoomEmailMon 10-12Mon 2-5Thu 2-4Fri 9-12 FoxPeterSPAT47764Huxley6M59peter.fox10@imperial.ac.uk MunroIanPHOT45531Blackett631i.munro@imperial.ac.uk PesaresiMarkHEP47798Blackett513mark.pesaresi01@imperial.ac.uk RaymondMarkHEP47799Blackett511m.raymond@imperial.ac.uk RoseAndrewHEP47798Blackett513andrew.rose01@imperial.ac.uk LepertGuillaumePHOT47221Blackett642guillaume.lepert07@imperial.ac.uk in lab

13. ARRANGEMENTS FOR ‘REPORT’ TIME Mark Neil - Microprocessor Course 13 Microprocessor Laboratory

14. Reports Mark Neil - Microprocessor Course 14 2 unit experiments automatic sign-off on Friday 26 th February Report deadline is 11 days later on Monday 7 th March Submit using standard 3rd year lab process and forms Standard penalties apply for late submissions Report submitted in electronic form Your programmes should be left on the machines and they will be looked at by the assessors. Attach (commented!) programme code as appendix Use laboratory guidelines for report writing Length guidelines – <4000 words 3 rd lab cycle begins Thursday 3 rd March

15. The ‘Product’ Report Structure Mark Neil - Microprocessor Course 15 Abstract Introduction High Level Design Software and Hardware Design Results and Performance Updates, Modifications and Improvements Conclusions Product Specifications Appendices

16. Top Down Modular Programming Mark Neil - Microprocessor Course 16 C C Calculator Initialise Get command CalculateOutput Reset Load values Prompt message Input Interpret command Select/run routine Format output Display Output character Input character Output character Output character …. complexitycomplexity time C C

17. Assessment process Mark Neil - Microprocessor Course 17 Report will be first marked by assigned demonstrator within 1 week. Demonstrator will arrange interview with you for sometime in week of 14 th December or the following week Individual interview (15 minutes) should include working demonstration and question and answer session. Feedback on report will be given. Second marking by me

18. Assessors Mark Neil - Microprocessor Course 18 Arrange your interview times NOW!

19. Marking scheme! Mark Neil - Microprocessor Course 19 Marks Available 5Abstract Concisely summarises the main report aims and findings Includes main performance achievements or quantitative results 10Introduction Successfully puts experiment in its scientific/theoretical and/or technical context Good acount of the underlying physics (including key equations) Effectively presents objectives/purpose/hypothesis of experiment 10High Level Design * Clearly gives an overview of the hardware and the role of key components Clearly gives an overview of the software functionality 20Software and Hardware Design * Describes the software giving a detailed description of the functionality Code is well structured, clear - description clear, flowcharts where needed Describes the detailed hardware functionality clear and sufficiently detailed diagrams of any circuits built are included

20. Marking scheme! Mark Neil - Microprocessor Course 20 Results and Performance * How challenging were the project goals and how well were those goals achieved? Correct analysis of any errors, were any problems encountered understood? Tables and figures, content/accuracy/presentation/captions 5Updates Modifications and Improvements Clear and thoughtful discussion of how to solve any identified problems 5Product Specification Thoughtful quantitative list of project features 5Conclusion Successfully summarises goals and achievements of the project 5Appendices Assembler code included and well commented 15Overall Structure and Presentation Accurate vocabulary / grammar / punctuation / spelling Consistent layout and presentation throughout the report Evidence of a clear and concise writing-style Comprehensive and relevant set of references (accurately cited) 100 Final Score * This score is partly informed by student perfomance in the laboratory