Difference between revisions of "F21: MARIO"
From Embedded Systems Learning Academy
Proj user13 (talk | contribs) (→Project Title) |
Proj user13 (talk | contribs) (→Schedule) |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 40: | Line 40: | ||
! scope="row"| 1 | ! scope="row"| 1 | ||
| | | | ||
| − | * 10/ | + | * 10/15/2021 |
| − | |||
| | | | ||
| − | * 10/ | + | * 10/25/2021 |
| − | |||
| | | | ||
* Read previous projects, gather information and discuss among the group members. | * Read previous projects, gather information and discuss among the group members. | ||
| Line 51: | Line 49: | ||
* Finalize parts list | * Finalize parts list | ||
* Setup splitwise account for cost sharing | * Setup splitwise account for cost sharing | ||
| − | |||
* Create GitLab repository for project | * Create GitLab repository for project | ||
* Decide on day/time for weekly meetings | * Decide on day/time for weekly meetings | ||
| | | | ||
* <span style="color:green">Completed</span> | * <span style="color:green">Completed</span> | ||
| − | * <span style="color: | + | * <span style="color:green">Completed</span> |
| + | * <span style="color:green">Completed</span> | ||
| + | * <span style="color:green">Completed</span> | ||
| + | * <span style="color:green">Completed</span> | ||
| + | * <span style="color:green">Completed</span> | ||
| + | * <span style="color:green">Completed</span> | ||
| + | |||
| + | |||
|- | |- | ||
! scope="row"| 2 | ! scope="row"| 2 | ||
| | | | ||
| − | *10/ | + | *10/25/2021 |
| | | | ||
| − | * | + | *11/03/2021 |
| | | | ||
*Choose game based on Preet's Project Proposal feedback | *Choose game based on Preet's Project Proposal feedback | ||
| Line 71: | Line 75: | ||
*Brainstorm gameplay, rules, and level design on paper | *Brainstorm gameplay, rules, and level design on paper | ||
| | | | ||
| − | * <span style="color: | + | * <span style="color:green">Completed</span> |
| + | * <span style="color:green">Completed</span> | ||
| + | * <span style="color:green">Completed</span> | ||
| + | * <span style="color:green">Completed</span> | ||
| + | * <span style="color:green">Completed</span> | ||
| + | * <span style="color:green">Completed</span> | ||
|- | |- | ||
! scope="row"| 3 | ! scope="row"| 3 | ||
| | | | ||
| − | * | + | *11/04/2021 |
| | | | ||
| − | *11/ | + | *11/09/2021 |
| | | | ||
*Read and familiarize with LED Matrix Datasheet | *Read and familiarize with LED Matrix Datasheet | ||
| Line 104: | Line 113: | ||
! scope="row"| 5 | ! scope="row"| 5 | ||
| | | | ||
| − | *11/09/ | + | *11/09/2021 |
| − | *11/09/ | + | *11/09/2021 |
| − | *11/09/ | + | *11/09/2021 |
| − | *11/09/ | + | *11/09/2021 |
| | | | ||
| − | *11/10/ | + | *11/10/2021 |
| − | *11/15/ | + | *11/15/2021 |
| − | *11/15/ | + | *11/15/2021 |
| − | *11/15/ | + | *11/15/2021 |
| | | | ||
* Finalize wiki schedule | * Finalize wiki schedule | ||
| − | |||
* circuit board and component assembly | * circuit board and component assembly | ||
* Circuit board testing | * Circuit board testing | ||
| Line 125: | Line 133: | ||
*Bluetooth modules can send controls data back and forth between game pad board and master board | *Bluetooth modules can send controls data back and forth between game pad board and master board | ||
*Controls data can be accessed using "get" and "set" API | *Controls data can be accessed using "get" and "set" API | ||
| − | *Plan PCB design on paper | + | *Plan PCB design on paper. |
*Game pad controller can read joystick and accelerometer values and detect switch presses | *Game pad controller can read joystick and accelerometer values and detect switch presses | ||
*Decide how to handle each collision detection case (character/enemy, bullet/enemy, etc.) | *Decide how to handle each collision detection case (character/enemy, bullet/enemy, etc.) | ||
| − | |||
| − | |||
| − | |||
| − | |||
*Finish enclosure design in AutoCAD software and start printing | *Finish enclosure design in AutoCAD software and start printing | ||
| − | |||
*Finalize PCB design on paper and design in PCB software | *Finalize PCB design on paper and design in PCB software | ||
| − | |||
*LED matrix displays character orientation correctly depending on current movement direction | *LED matrix displays character orientation correctly depending on current movement direction | ||
*Controller input (joystick or accelerometer) option is implemented on game pad controller | *Controller input (joystick or accelerometer) option is implemented on game pad controller | ||
| − | |||
*Bullet moves on LED matrix when button is pressed | *Bullet moves on LED matrix when button is pressed | ||
*Finalize PCB design in software and order PCB | *Finalize PCB design in software and order PCB | ||
| Line 150: | Line 151: | ||
! scope="row"| 6 | ! scope="row"| 6 | ||
| | | | ||
| − | *11/16/ | + | *11/16/2021 |
| | | | ||
| − | *11/22/ | + | *11/22/2021 |
| | | | ||
*LED matrix menu screens and game over/victory screens are implemented on matrix | *LED matrix menu screens and game over/victory screens are implemented on matrix | ||
| Line 162: | Line 163: | ||
*Finalize MP3 track selection for each screen and during gameplay | *Finalize MP3 track selection for each screen and during gameplay | ||
*Collision detection logic is fully functional and displays correctly on LED matrix | *Collision detection logic is fully functional and displays correctly on LED matrix | ||
| − | |||
| − | |||
* Testing and debugging the game logic | * Testing and debugging the game logic | ||
| | | | ||
| Line 172: | Line 171: | ||
! scope="row"| 7 | ! scope="row"| 7 | ||
| | | | ||
| − | * 11/23/ | + | * 11/23/2021 |
| | | | ||
| − | * 11/29/ | + | * 11/29/2021 |
| | | | ||
* Integrate game logic code with LED matrix | * Integrate game logic code with LED matrix | ||
* Integrate game sounds with game logic | * Integrate game sounds with game logic | ||
| − | *Finish rough draft of project report | + | * Finish rough draft of project report |
| − | *Write gameplay logic code on master controller. Gameplay logic should update the score and status bar items correctly | + | * Write gameplay logic code on master controller. Gameplay logic should update the score and status bar items correctly |
| − | *LED matrix graphics design for all levels is complete | + | * LED matrix graphics design for all levels is complete |
| − | *MP3 decoder plays correct song/track during gameplay and for each menu/game over screen | + | * MP3 decoder plays correct song/track during gameplay and for each menu/game over screen |
| − | *Gameplay state machine switches to next state based on user button presses and gameplay progression | + | * Gameplay state machine switches to next state based on user button presses and gameplay progression |
| | | | ||
* <span style="color:red">Not started</span> | * <span style="color:red">Not started</span> | ||
| Line 190: | Line 189: | ||
! scope="row"| 8 | ! scope="row"| 8 | ||
| | | | ||
| − | * 11/30/ | + | * 11/30/2021 |
| | | | ||
| − | * 12/06/ | + | * 12/06/2021 |
| | | | ||
| Line 205: | Line 204: | ||
! scope="row"| 9 | ! scope="row"| 9 | ||
| | | | ||
| − | * 12/07/ | + | * 12/07/2021 |
| | | | ||
| − | * 12/13/ | + | * 12/13/2021 |
| | | | ||
* Address bugs during testing of integrated system | * Address bugs during testing of integrated system | ||
| Line 218: | Line 217: | ||
! scope="row"| 10 | ! scope="row"| 10 | ||
| | | | ||
| − | *12/16/ | + | *12/16/2021 |
| − | *12/14/ | + | *12/14/2021 |
| − | *12/14/ | + | *12/14/2021 |
| − | *12/14/ | + | *12/14/2021 |
| | | | ||
*12/16/2020 | *12/16/2020 | ||
Latest revision as of 03:23, 3 November 2021
Contents
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
Hotshot Mario
Abstract
Super Mario is one of the best-selling games of all time, with more than 50 million copies sold worldwide. Our goal will be to produce a similar version of it where the player controls Mario. Mario has to race through the Mushroom Kingdom and save Princess.
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
- Vivek Tapkir
- Shreevats Gadhikar
- Daya Modekar
Schedule
| Week# | Start Date | End Date | Task | Status |
|---|---|---|---|---|
| 1 |
|
|
|
|
| 2 |
|
|
|
|
| 3 |
|
|
|
|
| 4 |
|
|
|
|
| 5 |
|
|
|
|
| 6 |
|
|
|
|
| 7 |
|
|
|
|
| 8 |
|
|
|
|
| 9 |
|
|
|
|
| 10 |
|
|
|
|
Parts List & Cost
Give a simple list of the cost of your project broken down by components. Do not write long stories here.
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.
