Difference between revisions of "S16: Sound Buddy"

From Embedded Systems Learning Academy
Jump to: navigation, search
(Design & Implementation)
(Design & Implementation)
Line 160: Line 160:
 
The design section can go over your hardware and software design.  Organize this section using sub-sections that go over your design and implementation.
 
The design section can go over your hardware and software design.  Organize this section using sub-sections that go over your design and implementation.
  
[[File:https://docs.google.com/drawings/d/1UsDQaFljZgJpJpgS817N__fUlJOMXhRr0UuXnSKvjg4/pub?w=960&h=720]]
+
[[File:Sound Buddy Top Level.jpg]]
  
 
=== Hardware Design ===
 
=== Hardware Design ===

Revision as of 00:59, 7 April 2016

Grading Criteria

  • How well is Software & Hardware Design described?
  • How well can this report be used to reproduce this project?
  • Code Quality
  • Overall Report Quality:
    • Software Block Diagrams
    • Hardware Block Diagrams
      Schematic Quality
    • Quality of technical challenges and solutions adopted.

Project Title

Sound Buddy

Abstract

This section should be a couple lines to describe what your project does.

Objectives & Introduction

Show list of your objectives. This section includes the high level details of your project. You can write about the various sensors or peripherals you used to get your project completed.

Team Members & Responsibilities

  • Brigitte De Leon
    • Nordic Wireless
  • Catherine Gamboa
    • PCB Design/Delivery
  • Hudo Assenco
    • Integration Master
  • Yang Thao
    • MP3 Decoder

Schedule

Show a simple table or figures that show your scheduled as planned before you started working on the project. Then in another table column, write down the actual schedule so that readers can see the planned vs. actual goals. The point of the schedule is for readers to assess how to pace themselves if they are doing a similar project.

Week# Date Task Actual
1 03.14
  • Finalize Schedule
  • Determine PCB board circuit
  • Order Parts
  • Update Wiki
  • Completed
  • 2 03.21
  • Design PCB schematic on Eagle
  • Review Nordic Wireless component on SJOne Board
  • Update Wiki
  • Completed
  • 3 03.28
  • Order PCB
  • Develop Nordic communication protocol
  • Write code to allow Nordic wireless communication between two boards
  • Update Wiki
  • In Progress
  • 4 04.04
  • Build MP3 decoder prototype circuit and verify its functionality
  • Update Wiki
  • Incomplete
  • 5 04.11
  • Load small MP3 into SD card and send out to MP3 decoder to hear audio
  • Update Wiki
  • Incomplete
  • 6 04.18
  • Integrate the system (SD from Master -> Nordic Wireless -> Flash -> MP3 decoder circuit -> Speakers)
  • Update Wiki
  • Incomplete
  • 7 04.25
  • Solder parts onto PCB
  • Integrate into test system
  • Update Wiki
  • Incomplete
  • 8 05.02
  • Integration test
  • Update Wiki
  • Incomplete
  • 9 05.09
  • System test
  • Update Wiki
  • Incomplete
  • 10 05.16
  • Run final tests
  • Prepare for DEMO --> 05.20
  • Incomplete
  • Parts List & Cost

    Item# Part Desciption Qty Cost
    1 STA013 MP3 Decoder Chip 2 $11.67
    2 CS4334 DAC 2 $2.97
    3 Audio Jack 3.5mm 1 $1.50
    4 Crystal 14.7456MHz 5 $0.95
    5 Printed Circuit Boards 2 $-.--
    6 SparkFun SOIC to Dip Adapter 8-pin 1 $2.95
    7 SparkFun SOIC to Dip Adapter 28-pin 1 $7.90
    8 Breakaway headers 2 $1.50
    9 Screw Terminals 3.5mm Pitch(2-Pin) 3 $0.95
    10 SJOne Board 3 $80.00
    Total Cost $-.--

    Design & Implementation

    The design section can go over your hardware and software design. Organize this section using sub-sections that go over your design and implementation.

    File:Sound Buddy Top Level.jpg

    Hardware Design

    Discuss your hardware design here. Show detailed schematics, and the interface here.

    Hardware Interface

    In this section, you can describe how your hardware communicates, such as which BUSes used. You can discuss your driver implementation here, such that the Software Design section is isolated to talk about high level workings rather than inner working of your project.

    Software Design

    Show your software design. For example, if you are designing an MP3 Player, show the tasks that you are using, and what they are doing at a high level. Do not show the details of the code. For example, do not show exact code, but you may show psuedocode and fragments of code. Keep in mind that you are showing DESIGN of your software, not the inner workings of it.

    Implementation

    This section includes implementation, but again, not the details, just the high level. For example, you can list the steps it takes to communicate over a sensor, or the steps needed to write a page of memory onto SPI Flash. You can include sub-sections for each of your component implementation.

    Testing & Technical Challenges

    Describe the challenges of your project. What advise would you give yourself or someone else if your project can be started from scratch again? Make a smooth transition to testing section and described what it took to test your project.

    Include sub-sections that list out a problem and solution, such as:

    My Issue #1

    Discuss the issue and resolution.

    Conclusion

    Conclude your project here. You can recap your testing and problems. You should address the "so what" part here to indicate what you ultimately learnt from this project. How has this project increased your knowledge?

    Project Video

    Upload a video of your project and post the link here.

    Project Source Code

    References

    Acknowledgement

    Any acknowledgement that you may wish to provide can be included here.

    References Used

    List any references used in project.

    Appendix

    You can list the references you used.