Difference between revisions of "S14: CAN Firmware Uploader"
(→Parts List & Cost)
(→Parts List & Cost)
|Line 108:||Line 108:|
Revision as of 07:32, 6 March 2014
- 1 Grading Criteria
- 2 Project Title
- 3 Abstract
- 4 Objectives & Introduction
- 5 Schedule
- 6 Parts List & Cost
- 7 Design & Implementation
- 8 Testing & Technical Challenges
- 9 Conclusion
- 10 References
- 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.
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
- Pradyumna Upadhya
- CAN Bus Driver Software Design
- In Application Programming
- Yash Parulekar
- Hardware Design
- SPI Flash Driver Software Design
|Sl. No||Start Date||End Date||Task||Actual|
|1||2/25||2/28||Order CAN Transceiver||Completed|
|3||3/8||3/14||Build H/w and read on establishing CAN communication|
|4||3/15||3/21||Design CAN protocol and Establish SIMPLE CAN communication|
|5||3/22||3/28||Read/Develop about SPI Flash driver to read and write .bin files|
|6||3/29||4/11||Transmit .bin file by integrating SPI driver and CAN|
|7||4/12||4/18||Read about IAP|
|9||4/26||5/5||Testing and remove bugs, further enhancements|
Parts List & Cost
SJ One Board
Twisted Pair Cable
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.
Discuss your hardware design here. Show detailed schematics, and the interface here.
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.
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.
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.
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?
Upload a video of your project and post the link here.
Project Source Code
Send me your zipped source code and I will upload this to SourceForge and link it for you.
Any acknowledgement that you may wish to provide can be included here.
List any references used in project.
You can list the references you used.