Hardware Reference
In-Depth Information
tacted both of the original designers—the hardware schematic designer and the code au-
thor—and asked if it would be okay to make a derivative of their work and include that
derivative in my topic. The open source hardware definition does not require this step, but
the best practices recommend it.
I started with the schematic in
Figure 6.2
, which was created by Davy Uittenbogerd
(daaf84). The file can be opened with Fritzing: fritzing.org/projects/charlieplex-
snowfallshooting-star-20-leds.
(Source: Image CC-BY-SA Davy Uittenbogerd)
Figure 6.2
Schematic by Davy Uittenbogerd drawn in Fritzing.
A link to the code to run this circuit is included on the Fritzing page. The code was
written by Geoff Steele (strykeroz). This code can be found in this GitHub repository: git-
hub.com/strykeroz/ATTiny85-20-LED-snowflakes.
When I copied and altered the code, I added a statement at the top of the code (known
as the comment block) explaining where the original code was downloaded from and who
the original author was: Geoff Steele. This gives Geoff attribution. I added a brief state-
ment about which parts of Geoff's code I altered. I included comments throughout the
code when I changed something as well. Geoff included which pin numbers correlate with
which color of wire on the Fritzing schematic in the code. It is good practice to include
basic instructions for the hardware pinouts in the comment block.
Here are the altered chunks of code, including the attribution in the comment block. To
view the full code, refer to
www.bit.ly/blinkybuildings
.
----> /* downloaded from http://code.google.com/p/avr-hardware-
random-number-
generation/ Original code by Geoff Steele. Alicia Gibb altered the
code by
