1. EMBEDDED SYSTEM DESIGN CONTEST 2009 THINKLABS NAME OF TEAM MEMBERS Reference template http://thinklabs.in ThinkLABS 2009

2. Embedded System Design Contest Keywords related to :  Hardware:  eg: LCD 16*2  IR sensor  Software  eg: python  uIP  Protocols  eg: I2C  CAN http://thinklabs.in ThinkLABS 2009

3. Embedded System Design Contest Introduction  This section should include a short summary of what the project is all about and some major distinctive aspects of the project (if any) http://thinklabs.in ThinkLABS 2009

4. Embedded System Design Contest Purpose  In this section, elaborate on the purpose of selecting this project. We would specifically like to hear on how this project is innovative and what sort of an existing gap is it filling e.g. eCOS is a POSIX compliant RTOS. There exist no POSIX compliant RTOSes for the AVR family. So, through this project we are trying to develop an eCOS port for ATMega128 of the AVR family. http://thinklabs.in ThinkLABS 2009

5. Embedded System Design Contest Features  List down the features of the application that you have developed.  It should NOT list features of uNiBoard but of the application that you have developed. e.g. If you have built a camera for surveillance the features would be: 1. CIF resolution 2. 5fps 3. 2GB Flash (can store up to 10000 images) and so on… http://thinklabs.in ThinkLABS 2009

6. Embedded System Design Contest High level design  This should be a block diagrammatic representation of your system (for hardware) and a flowchart/algorithmic representation (for software)  Functional modules for hardware and software should be listed here and the status of these modules at the time of submission of this report should be quantified  In case you had planned something in the high level design that you were not able to practically achieve list it down along with the problems faced http://thinklabs.in ThinkLABS 2009

7. Embedded System Design Contest Applications  List down some immediate application areas of the project that you have developed  Along with applications, also list down the kind of applications in which your project can be used as a reference design http://thinklabs.in ThinkLABS 2009

8. Embedded System Design Contest Photo-Gallery (if required)  This should primarily give us an indication of the user interface (if any)/usability of the product  You can also include phase wise photographs of some hardware module that you have developed to showcase the making of the project  In case you have written a software library for some peripheral, you might ignore this section or you might include snapshots of the software (Desktop software / Hyper-terminal) if it is showing some meaningful output like log of sensor data etc. http://thinklabs.in ThinkLABS 2009

9. Embedded System Design Contest Videos  Attach some videos showing the working of your project.  Videos of software can be in the form of screen capture. http://thinklabs.in ThinkLABS 2009

10. Embedded System Design Contest Source code  Explain the hierarchy of the source code  List down any third party code that you have used (RTOS, some open source stack)  List down the coding standards (MISRA etc.) that you have followed (if any) http://thinklabs.in ThinkLABS 2009

11. Embedded System Design Contest Apart from this presentation template your submission should have the following attachments:  Source code (Zipped form)  Videos (Zipped form) http://thinklabs.in ThinkLABS 2009

12. Embedded System Design Contest References:  http://code.google.com/p/uniboard http://code.google.com/p/uniboard  http://thinklabs.in/resources http://thinklabs.in/resources Discussion forums:  http://groups.google.com/group/openuniboard?pli=1 http://groups.google.com/group/openuniboard?pli=1  http://thinklabs.in/forums http://thinklabs.in/forums For any further queries send a mail to: roboshop@thinklabs.in roboshop@thinklabs.in http://thinklabs.in ThinkLABS 2009