Difference between revisions of "F18: 2048"

From Embedded Systems Learning Academy
Jump to: navigation, search
(Schedule)
(Schedule)
Line 130: Line 130:
 
| 11/20
 
| 11/20
 
|  
 
|  
* Integration of all the Software modules
+
* Integrate all the Individual Software modules
* Assembling components and Hardware Testing
+
* Assemble all the components on PCB and test hardware design - connections, voltage, current.
* Testing and debugging complete system
+
* Test entire system after PCB assembly
 
|
 
|
 
*  
 
*  
Line 142: Line 142:
 
| 11/27
 
| 11/27
 
|  
 
|  
* Final testing and debugging
+
* Review complete work in detail; Refactor Code, Make Improvisations
* Work on project demo, presentation and Wiki report
+
* Make project demo video and presentation.
 
|
 
|
 
*  
 
*  
Line 152: Line 152:
 
| 12/03
 
| 12/03
 
|  
 
|  
* Ultimate deadline; Review complete project work in detail
+
* Finalize Wiki Report
 
|
 
|
 
*  
 
*  

Revision as of 21:33, 21 November 2018

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.

2048

Two Zero Four Eight (2048) is a game having a grid of numbered tiles (i.e., power of 2) to combine them to create a tile with the number 2048. It is usually played on a 4x4 grid with tiles that slide smoothly when a player moves them towards right, left, up or down. Every time a new tile will randomly appear in an empty spot on the display with a value of either 2 or 4. If two tiles of the same number collide then they will merge into one tile with value of sum of those two tiles. Game continues until no merge is possible.

Objectives & Introduction

Team Members & Responsibilities

Schedule

Week# Start Date Task Status Completion Date
1 09/18
  • Submission of Project Proposals
  • Completed
  • 09/25
2 10/09
  • High-level project design
  • Decide on the components and order them.
  • Completed
  • Completed
  • 10/16
  • 10/16
3 10/16
  • Dividing Individual responsibilities and tasks
  • Hardware Schematic design
  • Completed
  • Completed
  • 10/20
  • 10/23
4 10/23
  • PCB Layout design
  • Joystick drivers
  • In Progress
  • Completed
  • 11/08
5 10/30
  • LED Matrix Display drivers
  • Basic Game strategy implementation on Linux console
  • Completed
  • Completed
  • 11/16
  • 11/17
6 11/06
  • Display random numbers on LED Matrix using drivers
  • Review of PCB design by team and ISA team/Professor
  • Completed
  • 11/16
7 11/13
  • Control LED Matrix using Joystick
  • Implementation of game logic on SJOne board
  • Finalize PCB design
8 11/20
  • Integrate all the Individual Software modules
  • Assemble all the components on PCB and test hardware design - connections, voltage, current.
  • Test entire system after PCB assembly
9 11/27
  • Review complete work in detail; Refactor Code, Make Improvisations
  • Make project demo video and presentation.
10 12/03
  • Finalize Wiki Report

Parts List & Cost

Component Cost Quantity Seller
SJOne Board $80 1 Preetpal Kang
Adafruit RGB (64x64) LED Matrix Display $99.78 1 Adafruit
Adafruit Analog 2-axis thumb Joystick $10.18 1 Amazon

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.

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:

<Bug/issue name>

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.