Differences

This shows you the differences between two versions of the page.

--- en:examples:setup:linux [2010/04/01 13:07] – mikk.leini
+++ en:examples:setup:linux [2020/07/20 09:00] (current) – created - external edit 127.0.0.1
@@ Line 17: / Line 17: @@
   sudo apt-get install gcc-avr avrdude avr-libc
-or graphical installation software (such as Ubuntu software center or Synaptic packetmanager).
+or graphical installation software (such as Ubuntu software center or Synaptic packet manager).
-**2. Homelab library**
+**2. HomeLab library**
-The library simplifies the writing of program code, since lower-level functions are ready-made. Visit the Homelab website and download the file named //Homeland library vX.X.run//, where XX represents the version number. Run the following command to install the library:
+The library simplifies the writing of program code, since lower-level functions are ready-made. Visit the HomeLab website and download the file named //Homelab library vX.X.run//, where XX represents the version number. Run the following command to install the library:
   sudo sh homelab_library_vX.X.run
@@ Line 33: / Line 33: @@
   sudo dpkg -i kontrollerlab*.deb
-If you have problems with packet dependencies, run the command, which installs the missing packages:
+If you have problems with packet dependencies, run the command which installs the missing packages:
   apt-get install –f
@@ Line 51: / Line 51: @@
 ===== Creating a new project =====
-To write an AVR program, a project must be created which contains all the necessary files: source codes, header files, compiled program, etc. To clearly seperate projects, a folder for each project should be made (this option is given by the project wizard also).
+To write an AVR program, a project must be created which contains all the necessary files: source codes, header files, compiled program, etc. To clearly seperate projects, a folder for each project should be made (this option is also given by the project wizard).
 To create a project follow the steps:
@@ Line 59: / Line 59: @@
 {{  :kit:004_new_project_kontrollerlab.png?500  |}}
-**2.** The project must at least one C file where to write the program code. Files can be added from the //File -> New -> New// menu. In the opening window, select //C source// as a file type and specify the name of the file.
+**2.** The project must have at least one C file where to write the program code. Files can be added from the //File -> New -> New// menu. In the opening window, select //C source// as a file type and specify the name of the file.
 {{  :kit:005_new_file_kontrollerlab.png?500  |}}
-**3.** Next, the project must be configured for Homelab kit. From the //Project -> Configure Project// menu open the configurations window and select //Common// tab. CPU type should be ATmega128 and the clock should be 14745600,0 Hz. Also the names of the HEX and MAP files should be specified. Pressing a //Set as default// button makes these configurations as a default for new projects. This is reasonable when working only with Homelab AVR microcontroller. As the HEX and MAP files are also stored as a default it is recommended to use some general name for them, for example "out.hex".
+**3.** Next, the project must be configured for HomeLab kit. From the //Project -> Configure Project// menu open the configurations window and select //Common// tab. CPU type should be ATmega128 and the clock should be 14745600,0 Hz. Also the names of the HEX and MAP files should be specified. Pressing a //Set as default// button makes these configurations as a default for new projects. This is reasonable when working only with HomeLab AVR microcontroller. As the HEX and MAP files are also stored as a default it is recommended to use some general name for them, for example "out.hex".
-NB! As the Homelab library can not be added on the //Linker// configuration tab, the command "-lhomelab" must be added behind the name of the MAP file.
+NB! As the HomeLab library can not be added on the //Linker// configuration tab, the command "-lhomelab" must be added behind the name of the MAP file.
 {{  :kit:006_project_conf_common.png?500  |}}
-Apply settings on the //Compiler// tab as showed on the following screenshot. Before pressing //OK// set compiler configurations also as a default.
+Apply settings on the //Compiler// tab as shown on the following screenshot. Before pressing //OK// set compiler configurations also as a default.
 {{  :kit:007_project_conf_compiler.png?500  |}}
@@ Line 83: / Line 83: @@
 ===== Writing and testing a program =====
-After the configurations steps are done, it is time programm.
+After the configurations steps are done, it is time to programm.
 **1.** Connect the programmer with Controller module. Double-check if the programmer is correctly connected with a JTAG socket. The cable must head away from the board (look at the picture). Now connect the power supply and check if the green LED lights on the Controller board.

en/examples/setup/linux.1270127229.txt.gz · Last modified: 2020/07/20 09:00 (external edit)