Difference between revisions of "S14: CAN Firmware Uploader"
Proj user3 (talk | contribs) (→Schedule) |
Proj user3 (talk | contribs) (→Schedule) |
||
| Line 59: | Line 59: | ||
| 3/21 | | 3/21 | ||
| Design CAN protocol and Establish SIMPLE CAN communication | | Design CAN protocol and Establish SIMPLE CAN communication | ||
| − | | | + | | Completed on 4/17. We faced few problems in CAN driver and hardware. |
|- | |- | ||
! scope="row"| 5 | ! scope="row"| 5 | ||
| Line 65: | Line 65: | ||
| 3/28 | | 3/28 | ||
| Read/Develop about SPI Flash driver to read and write .bin files | | Read/Develop about SPI Flash driver to read and write .bin files | ||
| − | | | + | | Completed on 4/21. Integrating bin reading logic with CAN driver. |
|- | |- | ||
! scope="row"| 6 | ! scope="row"| 6 | ||
| Line 71: | Line 71: | ||
| 4/11 | | 4/11 | ||
| Transmit .bin file by integrating SPI driver and CAN | | Transmit .bin file by integrating SPI driver and CAN | ||
| − | | | + | | Ongoing. Tried sending sample bin to the receiver board. File save logic at receiver is being implemented now. As of now facing few sync problems in CAN ISR. |
|- | |- | ||
! scope="row"| 7 | ! scope="row"| 7 | ||
| Line 77: | Line 77: | ||
| 4/18 | | 4/18 | ||
| Read about IAP | | Read about IAP | ||
| − | | | + | | Completed on 4/22 |
|- | |- | ||
! scope="row"| 8 | ! scope="row"| 8 | ||
| Line 83: | Line 83: | ||
| 4/25 | | 4/25 | ||
| Implement IAP | | Implement IAP | ||
| − | | | + | | Completed on 4/22. It has to be integrated with CAN transfer state diagram logic. |
|- | |- | ||
! scope="row"| 9 | ! scope="row"| 9 | ||
| Line 89: | Line 89: | ||
| 5/5 | | 5/5 | ||
| Testing and remove bugs, further enhancements | | Testing and remove bugs, further enhancements | ||
| − | | | + | | Ongoing. |
|- | |- | ||
! scope="row"| 10 | ! scope="row"| 10 | ||
Revision as of 01:24, 25 April 2014
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
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
- Pradyumna Upadhya
- CAN Bus Driver Software Design
- In Application Programming
- Yash Parulekar
- Hardware Design
- SPI Flash Driver Software Design
Schedule
| Sl. No | Start Date | End Date | Task | Actual |
|---|---|---|---|---|
| 1 | 2/25 | 2/28 | Order CAN Transceiver | Completed |
| 2 | 3/1 | 3/7 | Procure Components | Completed |
| 3 | 3/8 | 3/14 | Build H/w and read on establishing CAN communication | Completed.Hardware built. Plan to test it with CAN driver by 3/22 |
| 4 | 3/15 | 3/21 | Design CAN protocol and Establish SIMPLE CAN communication | Completed on 4/17. We faced few problems in CAN driver and hardware. |
| 5 | 3/22 | 3/28 | Read/Develop about SPI Flash driver to read and write .bin files | Completed on 4/21. Integrating bin reading logic with CAN driver. |
| 6 | 3/29 | 4/11 | Transmit .bin file by integrating SPI driver and CAN | Ongoing. Tried sending sample bin to the receiver board. File save logic at receiver is being implemented now. As of now facing few sync problems in CAN ISR. |
| 7 | 4/12 | 4/18 | Read about IAP | Completed on 4/22 |
| 8 | 4/19 | 4/25 | Implement IAP | Completed on 4/22. It has to be integrated with CAN transfer state diagram logic. |
| 9 | 4/26 | 5/5 | Testing and remove bugs, further enhancements | Ongoing. |
| 10 | 5/8 | 5/8 | Demo |
Parts List & Cost
| Parts | Cost* |
|---|---|
|
SJ One Board[1] |
$80.00 x2 |
|
MCP2551 |
$1.02 x2 |
|
Twisted Pair Cable |
Junk |
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.
MOM
MOM1 Date: 3/14 1) Read about CAN code by 3/15 2) Get resistors and assemble CAN setup by 3/15 3) Test and modify existing CAN driver by 3/21
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
Send me your zipped source code and I will upload this to SourceForge and link it for you.
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.
