Tips for HDMI2USB / Hardware related Google Summer of Code Proposals

[Tim Ansell]

Hello everyone,

As HDMI2USB / hardware related projects for TimVideos are a little different to the normal projects I wanted to write up this set of extra tips for people applying for these proposals. These projects are on the top of the list of ideas we would love to accept but it is important to note that proposal strength and community participate are stronger factors in if we select a proposal or not.

Firstly, before submitting your application you must read our Summer of Code page at http://code.timvideos.us/Summer-Of-Code.html, the page contains all the information you need to create an awesome proposal. Proposals which don't follow the tips provided on that page have a very low chance of being accepted (at any organisation)!

Secondly, share your application as soon as possible. We are happy to look at half finished applications and provide direction on where they need improvement. We will evaluate on your final proposal, not on your initial attempt. Getting feedback early means that you will have more time to fix any issues. You also shouldn't be shy about sharing your application with other students, they are another great source of feedback and it is practically impossible for someone to steal your proposal.

These hardware proposals need a unique set of skills with peculiar tools (Xilinx ISE, VHDL/Verilog, FPGA programming). You must demonstrate in your proposal that you have used these tools and are happy to worth with them. Some ways to demonstrate this include;

• Proving that you have having compiled the existing firmware.
• Proving that you were able to modify in some way and then compile firmware would be even better!
• Submitting a pull request with even a minor change would be the ultimate example.

All the hardware proposals are going to need access to an FPGA board during some part of the project. While substantial can be done without a device, eventually all code will need to be tested on actual hardware. Our preferred board is the Digilent Atlys board. In your proposal you must explain what hardware you will be using and why the hardware is suitable for the project. If you are not using the Digilent Atlys board you need explain how you expect to deal with differences between your board and the Atlys board.

A number of the ideas require development of physical PCB boards. As the program is the Summer of Code, it is important that your project include substantial integration work of the board (such as firmware development). You will also need to demonstrate an understand the PCB creation, production and processing times. It is unlikely you'll get the PCB right on the first go (not even professionals get it perfectly right the first time), so must include information in your timeline on how you plan to handle setbacks. Your proposal should include information on;

• The tools you are going to use for creation (CadSoft Eagle? KiCad? Other?)
  
• The tools you are going to use for debugging and testing of the board. (Oscilloscope? Logic Analyzer? Other?)
• The major components you plan to use in the board, including links to datasheets and where you plan to purchase them from.
• The fabrication houses you plan to use, including costing and turn around times.
• Number of times you plan to do PCBs runs and the number of PCBs produced. 

Summary

• Hardware projects are exciting but proposal strength and community participate are stronger factors in if we select a proposal or not.
• You must follow the tips given at http://code.timvideos.us/Summer-Of-Code.html
• Share your application ASAP and ask for feedback sooner rather then later.
• You must demonstrate in your proposal that you have used the required tools successfully.
  
• You must explain what hardware you will be using and why the hardware is suitable for the project.
  
• If you need to create a PCB, you must demonstrate knowledge and planning for the process including contingency plans for when things go wrong.

Hope that helps everyone!

Tim 'mithro' Ansell