Professional Documents
Culture Documents
Appendix: Installing Java (Windows) and Writing Your First Program
Appendix: Installing Java (Windows) and Writing Your First Program
C:\Program Files\Java\jdk1.6.0_24\bin
13 | P a g e
Enter the following code. Java is case
sensitive, so be careful to capitalize EXACTLY
the same as what is below.
javac HelloWorld.java
java HelloWorld
14 | P a g e
Now that you have installed Java, make a
directory for your first Java program and
open Gedit.
15 | P a g e
Installing Java (Mac) and Writing your First Program
Java is installed by default on Mac OS, make a
directory for your first Java program and
open your editing program.
javac HelloWorld.java
java HelloWorld
16 | P a g e
FTDI/Serial Installation
Installing the FTDI drivers and a Terminal Program in Windows
1. Most versions of windows already have the
FTDI driver as part of the operating system.
http://www.ftdichip.com/Drivers/VCP.htm
http://www.compuphase.com/software_termite.ht
m
17 | P a g e
Installing the FTDI drivers and a Terminal Program in Linux
1. Most versions of Linux already have the
FTDI driver as part of the operating
system.
http://www.ftdichip.com/Drivers/VCP.htm
18 | P a g e
4. Once everything is installed, connect your
Wunderboard as described in step 1. Give
your computer time to setup drivers and
then open the Cutecom program by
typing cutecom into a terminal.
http://www.ftdichip.com/Drivers/VCP.htm
19 | P a g e
3. Once installed, Open a terminal and type:
ls /dev/tty.*
http://www.cheat-sheets.org/saved-
copy/screen.cheat.sheet.txt
Doxygen
There are many different philosophies on how much documentation is enough and how it should be done. Many
companies have a standard method that all of their employees must follow. In this manual, one method will be shown
and expected. While other ways might seem sufficient, you must adhere to the philosophy in this manual. The
commenting style used is Doxygen.
When documenting code, essentially every line of code that is not a simple assignment should have an inline comment.
These ‘tags’ tell Doxygen that there is information inside of them to be processed. In addition to in line comments, well
documented code includes comments for: variables, functions, includes, defines, and flow control.
• Variables
When documenting a variable use a Doxygen comment following the variable definition. The style for a
following comment is: /**< comment text */ Unless all variables are of an identical type and are used in
essentially the same way, they should be declared on separate lines with a comment for each.
• Functions
Functions have the most complicated definition. Functions should only be defined once. The definition should
precede the function. Every function should have a brief description, all parameters defined, and the return
20 | P a g e
value defined. For example, Documentation for the function ‘main’ might look like:
• Includes
When documenting an include use a Doxygen comment following the include statement. The style for a
following comment is: /**< why is this file included? */
• Logic Control
All statements that control flow of code must be commented. This includes; if(), while(), switch(), and for()
statements. These comments should explain why the logic test exists, not just re-iterate what is already written.
Ensure that every option has a following comment of the format: /**< comment */
21 | P a g e