<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://www.ethernut.de/nutwiki/index.php?action=history&amp;feed=atom&amp;title=Ethernut_1.3_H</id>
	<title>Ethernut 1.3 H - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://www.ethernut.de/nutwiki/index.php?action=history&amp;feed=atom&amp;title=Ethernut_1.3_H"/>
	<link rel="alternate" type="text/html" href="https://www.ethernut.de/nutwiki/index.php?title=Ethernut_1.3_H&amp;action=history"/>
	<updated>2026-11-22T13:27:12Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.43.11</generator>
	<entry>
		<id>https://www.ethernut.de/nutwiki/index.php?title=Ethernut_1.3_H&amp;diff=86&amp;oldid=prev</id>
		<title>Harald: 1 revision imported</title>
		<link rel="alternate" type="text/html" href="https://www.ethernut.de/nutwiki/index.php?title=Ethernut_1.3_H&amp;diff=86&amp;oldid=prev"/>
		<updated>2016-10-27T16:02:54Z</updated>

		<summary type="html">&lt;p&gt;1 revision imported&lt;/p&gt;
&lt;table style=&quot;background-color: #fff; color: #202122;&quot; data-mw=&quot;interface&quot;&gt;
				&lt;tr class=&quot;diff-title&quot; lang=&quot;en&quot;&gt;
				&lt;td colspan=&quot;1&quot; style=&quot;background-color: #fff; color: #202122; text-align: center;&quot;&gt;← Older revision&lt;/td&gt;
				&lt;td colspan=&quot;1&quot; style=&quot;background-color: #fff; color: #202122; text-align: center;&quot;&gt;Revision as of 16:02, 27 October 2016&lt;/td&gt;
				&lt;/tr&gt;&lt;tr&gt;&lt;td colspan=&quot;2&quot; class=&quot;diff-notice&quot; lang=&quot;en&quot;&gt;&lt;div class=&quot;mw-diff-empty&quot;&gt;(No difference)&lt;/div&gt;
&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;</summary>
		<author><name>Harald</name></author>
	</entry>
	<entry>
		<id>https://www.ethernut.de/nutwiki/index.php?title=Ethernut_1.3_H&amp;diff=85&amp;oldid=prev</id>
		<title>Harald: Corrected slashes on WIndows path</title>
		<link rel="alternate" type="text/html" href="https://www.ethernut.de/nutwiki/index.php?title=Ethernut_1.3_H&amp;diff=85&amp;oldid=prev"/>
		<updated>2010-10-01T12:48:45Z</updated>

		<summary type="html">&lt;p&gt;Corrected slashes on WIndows path&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;[[Image:enut13.png|upright|thumb|400px|Ethernut 1.3 H]]&lt;br /&gt;
&lt;br /&gt;
== Test Environments ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;smalldiv&amp;quot;&lt;br /&gt;
| style=&amp;quot;background-color:#F6F9ED&amp;quot; | Board&lt;br /&gt;
| style=&amp;quot;background-color:#F6F9ED&amp;quot; | Nut/OS&lt;br /&gt;
| style=&amp;quot;background-color:#F6F9ED&amp;quot; | WinAVR&lt;br /&gt;
| style=&amp;quot;background-color:#F6F9ED&amp;quot; | Tera Term&lt;br /&gt;
|-&lt;br /&gt;
| 1.3 H&lt;br /&gt;
| 2.6.4&lt;br /&gt;
| 20080610&lt;br /&gt;
| 4.61&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Description ==&lt;br /&gt;
&lt;br /&gt;
On this page you will learn how to setup an Ethernet 1.3 development and testing environment.&lt;br /&gt;
&lt;br /&gt;
You will learn the &amp;#039;&amp;#039;&amp;#039;easiest way&amp;#039;&amp;#039;&amp;#039; on how to use the examples from nutwiki and your own applications.&lt;br /&gt;
This Guide is not supposed to be a complete manual but as a Quick Start Guide, teaching one of the many methods to get an application running on your Ethernut board.&lt;br /&gt;
&lt;br /&gt;
Immediatly after working through this document, you have the competence to test the examples featured by nutwiki.&lt;br /&gt;
&lt;br /&gt;
Additionally all major topics are also covered in screencasts (Win only).&lt;br /&gt;
&lt;br /&gt;
# [[Image:flashvideo.png|16px]] [http://ethernut.de/arc/screencasts/ENUT13CONFIGURATOR.htm Screencast Part 1] The Nut/OS Configurator&lt;br /&gt;
# [[Image:flashvideo.png|16px]] [http://ethernut.de/arc/screencasts/ENUT13PREP.htm Screencast Part 2] Preparations&lt;br /&gt;
# [[Image:flashvideo.png|16px]] [http://ethernut.de/arc/screencasts/ENUT13BURN.htm Screencast Part 3] Compiling and Burning&lt;br /&gt;
# [[Image:flashvideo.png|16px]] [http://ethernut.de/arc/screencasts/TERATERM.htm Screencast Part 4] Serial Communications / TeraTerm&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== [[Image:winpath.png|24px]] Required Tools for Windows ==&lt;br /&gt;
=== Nut/OS ===&lt;br /&gt;
Of course you need the latest version of Nut/OS.&lt;br /&gt;
&lt;br /&gt;
Visit this page to download the latest version for Win32:&amp;lt;br&amp;gt;&lt;br /&gt;
Download: [http://ethernut.de/en/download/index.html http://ethernut.de/en/download/index.html]&lt;br /&gt;
&lt;br /&gt;
Nut/OS for Windows features an installer which will do most of the work for you.&lt;br /&gt;
&lt;br /&gt;
It is recommended to install the ethernut folder directly on the root directory: &lt;br /&gt;
 [[Image:winpath.png|24px]] C:/ethernut-4.6.4/ &lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Note:&amp;#039;&amp;#039;&amp;#039; All paths in this guide refer to that location and will be referred to as &amp;quot;ethernut folder/directory&amp;quot; or &amp;quot;/ethernut-4.6.4&amp;quot;&lt;br /&gt;
&lt;br /&gt;
=== Tera Term ===&lt;br /&gt;
[http://ttssh2.sourceforge.jp/ Tera Term] is a so called terminal emulator. We use it to communicate via COM with the board.&lt;br /&gt;
&lt;br /&gt;
Download: [http://sourceforge.jp/projects/ttssh2/releases/ http://sourceforge.jp/projects/ttssh2/releases/]&lt;br /&gt;
&lt;br /&gt;
=== WinAVR ===&lt;br /&gt;
[http://winavr.sourceforge.net/index.html WinAVR] (pronounced &amp;quot;whenever&amp;quot;) is a suite of executable, open source software development tools for the Atmel AVR series of RISC microprocessors hosted on the Windows platform.&lt;br /&gt;
&lt;br /&gt;
It includes the GNU GCC compiler for C and C++. &lt;br /&gt;
&lt;br /&gt;
Download: [http://sourceforge.net/project/showfiles.php?group_id=68108 http://sourceforge.net/project/showfiles.php?group_id=68108]&lt;br /&gt;
&lt;br /&gt;
It is recommended to install the WinAVR folder directly on the root directory:&lt;br /&gt;
 [[Image:winpath.png|24px]] C:/winavr/&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Note:&amp;#039;&amp;#039;&amp;#039; All paths in this guide refer to that location!&lt;br /&gt;
&lt;br /&gt;
=== Text Editor ===&lt;br /&gt;
You can use any text editor you want.&lt;br /&gt;
Some recommended ones include:&lt;br /&gt;
* [http://www.eclipse.org/ Eclipse] Open Source&lt;br /&gt;
* [http://www.e-texteditor.com/ The e Text Editor] Commercial, Trial&lt;br /&gt;
&lt;br /&gt;
== [[Image:linuxpath.png|24px]] Required Tools for Linux==&lt;br /&gt;
&lt;br /&gt;
=== Essential Tools ===&lt;br /&gt;
The following GNU tools are required to configure and build a minimal Nut/OS development environment: &lt;br /&gt;
* C compiler 4.1 or later&lt;br /&gt;
* Binutils 2.18 or later&lt;br /&gt;
* Autoconf 2.61&lt;br /&gt;
* Automake 1.10&lt;br /&gt;
&lt;br /&gt;
=== AVR cross toolchain ===&lt;br /&gt;
Furthermore, you need a so called cross toolchain, which allows us to create binaries on a Linux host, which will later run on our target board. When developing for 8-bit AVR, we need &lt;br /&gt;
* GNU Compiler Collection for AVR&lt;br /&gt;
* GNU Binary Utilities for AVR&lt;br /&gt;
* AVRDUDE programmer software&lt;br /&gt;
&lt;br /&gt;
=== WxWidgets ===&lt;br /&gt;
[http://www.wxwidgets.org/ wxWidgets] is a cross-platform C++ GUI framework, required for Nut/OS configurator GUI.&lt;br /&gt;
&lt;br /&gt;
=== Lua ===&lt;br /&gt;
[http://www.lua.org/ Lua] is an embeddable scripting language, which is used here to specify the configuration rules. This is also required for Nut/OS configurator to run.&lt;br /&gt;
&lt;br /&gt;
=== Nut/OS ===&lt;br /&gt;
Of course you need the latest version of Nut/OS.&lt;br /&gt;
&lt;br /&gt;
Visit this page to download the latest source code package for Linux (Debian):&amp;lt;br&amp;gt;&lt;br /&gt;
Download: [http://ethernut.de/en/download/index.html http://ethernut.de/en/download/index.html]&lt;br /&gt;
&lt;br /&gt;
It is recommended to create a new folder named &amp;quot;ethernut&amp;quot; in your home directory and copy the source code package in to this directory before unpacking it. The complete sequence of shell command for installing Nut/OS is:&lt;br /&gt;
[[Image:linuxpath.png|24px|right]] &lt;br /&gt;
 mkdir ~/ethernut&lt;br /&gt;
 cp ethernut-4.6.4.tar.bz2 ~/ethernut&lt;br /&gt;
 cd ~/ethernut&lt;br /&gt;
 tar -xjf ethernut-4.6.4.tar.bz2&lt;br /&gt;
 ln -s ethernut-4.6.4 nut&lt;br /&gt;
 cd nut/&lt;br /&gt;
 ./configure&lt;br /&gt;
 make&lt;br /&gt;
 sudo make install&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Note:&amp;#039;&amp;#039;&amp;#039; All paths in this guide refer to that location and will be referred to as &amp;quot;ethernut folder/directory&amp;quot; or &amp;quot;/ethernut&amp;quot;&lt;br /&gt;
&lt;br /&gt;
http://www.ethernut.de/en/documents/debian.html provides more informations about installing Nut/OS on Linux.&lt;br /&gt;
&lt;br /&gt;
=== Minicom ===&lt;br /&gt;
[http://alioth.debian.org/projects/minicom/ Minicom] is a so called terminal emulator. We use it to communicate via COM with the board.&lt;br /&gt;
&lt;br /&gt;
== The Nut/OS Configurator ==&lt;br /&gt;
&lt;br /&gt;
[[Image:flashvideo.png|64px]][http://ethernut.de/arc/screencasts/ENUT13CONFIGURATOR.htm Screencast Part 1]&lt;br /&gt;
&lt;br /&gt;
In order to build an optimized Nut/OS for you needs you have to configure it.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;In some examples from nutwiki you are asked to setup something in the Nut/OS configurator. This is the time and place to do so.&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
In general the workflow is as following:&lt;br /&gt;
&lt;br /&gt;
1. Start the Nut/OS Configurator:&lt;br /&gt;
[[Image:winpath.png|24px|right]] &lt;br /&gt;
 Start &amp;amp;gt; Programs &amp;amp;gt; Ethernut 4.6.4 &amp;amp;gt; Configurator&lt;br /&gt;
&lt;br /&gt;
[[Image:linuxpath.png|24px|right]]&lt;br /&gt;
 cd ~/ethernut&lt;br /&gt;
 nutconf&lt;br /&gt;
2. Select and open the configuration file for your board:&lt;br /&gt;
 ethernut103.conf for old Ethernuts with ATmega103&lt;br /&gt;
 ethernut13f.conf for Ethernut 1.3 Rev-F and earlier&lt;br /&gt;
 ethernut13g.conf for Ethernut 1.3 Rev-G and later&lt;br /&gt;
&lt;br /&gt;
3. Click on Menubar: &amp;#039;&amp;#039;&amp;#039;Edit &amp;gt; Settings&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
* Goto Tab: &amp;#039;&amp;#039;&amp;#039;Build&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
** Choose Platform: &amp;#039;&amp;#039;&amp;#039;avr-gcc&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
** Choose Build Directory: &amp;#039;&amp;#039;&amp;#039;nutbld_enut13&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
* Goto Tab: &amp;#039;&amp;#039;&amp;#039;Tools&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
** [[Image:winpath.png|24px]] Enter Tool Paths: &amp;#039;&amp;#039;&amp;#039;c:\ethernut-4.6.4\nut\tools\win32;c:\winavr\utils\bin;c:\winavr\bin;&amp;#039;&amp;#039;&amp;#039; (Win only, left bank on Linux)&amp;lt;br&amp;gt;&lt;br /&gt;
* Goto Tab: &amp;#039;&amp;#039;&amp;#039;Samples&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
** Choose Application Directory: &amp;#039;&amp;#039;&amp;#039;nutapp_enut13&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
** Choose Programmer: &amp;#039;&amp;#039;&amp;#039;avr-dude&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
* Click &amp;#039;&amp;#039;&amp;#039;OK&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
4. Click on Menubar: &amp;#039;&amp;#039;&amp;#039;Build &amp;gt; Build Nut/OS&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
* Say &amp;#039;&amp;#039;&amp;#039;OK&amp;#039;&amp;#039;&amp;#039; 2 times.&lt;br /&gt;
5. Click on Menubar: &amp;#039;&amp;#039;&amp;#039;Build &amp;gt; Create Sample Directory&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
* Say &amp;#039;&amp;#039;&amp;#039;OK&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Note:&amp;#039;&amp;#039;&amp;#039; You should create a new sample directory every time you build a new system, even if you do not want to use the samples. There are two files named&lt;br /&gt;
* Makerules&lt;br /&gt;
* Makedefs&lt;br /&gt;
in that directory, that are necessary for every application to compile.&lt;br /&gt;
&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Nut/OS Configurator built a customized version for your needs and put it in:&lt;br /&gt;
 \ethernut-4.6.4\nutbld_enut13\&lt;br /&gt;
&lt;br /&gt;
Additionally it created an associated Sample Application Directory with source codes ready to compile:&lt;br /&gt;
 \ethernut-4.6.4\nutapp_enut13\&lt;br /&gt;
&lt;br /&gt;
== Preparations ==&lt;br /&gt;
&lt;br /&gt;
[[Image:flashvideo.png|64px]][http://ethernut.de/arc/screencasts/ENUT13PREP.htm Screencast Part 2]&lt;br /&gt;
&lt;br /&gt;
=== Application Directory ===&lt;br /&gt;
First of all we need a home for our application. &lt;br /&gt;
&lt;br /&gt;
Create a new directory &amp;quot;&amp;#039;&amp;#039;&amp;#039;testcode&amp;#039;&amp;#039;&amp;#039;&amp;quot; in&lt;br /&gt;
 \ethernut-4.6.4\nutapp_enut13\&lt;br /&gt;
&lt;br /&gt;
You can, of course, use any names you want.&lt;br /&gt;
&lt;br /&gt;
=== Editing ===&lt;br /&gt;
1. Write your application code, or for testing purposes, paste in an example code from nutwiki in a plain text file.&lt;br /&gt;
&lt;br /&gt;
2. Save it as &amp;lt;code&amp;gt;testcode.c&amp;lt;/code&amp;gt; in:&lt;br /&gt;
 \ethernut-4.6.4\nutapp_enut13\testcode\&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Note:&amp;#039;&amp;#039;&amp;#039; Make sure, that in your Windows folder options, the setting &amp;#039;Hide file extensions for unknown file types&amp;#039; is deactivated! If not, you will create .txt files instead of .c or Makefiles, when saving in the Editor!&lt;br /&gt;
&lt;br /&gt;
=== Makefile ===&lt;br /&gt;
For our applications to compile, we need a makefile.&lt;br /&gt;
&lt;br /&gt;
This is used and interpreted by a tool called GNU Make, which we will use later.&lt;br /&gt;
&lt;br /&gt;
Makefiles may differ from application to application, but the following is a general purpose one, which will work for basic applications.&amp;lt;br&amp;gt;&lt;br /&gt;
Later, when you are familiar with Nut/OS and makefiles you can create your own ones.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Note&amp;#039;&amp;#039;&amp;#039;, that in this example makefile, the project name,&lt;br /&gt;
&amp;lt;source lang=&amp;quot;text&amp;quot;&amp;gt;&lt;br /&gt;
PROJ = testcode&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
has to be identical to the name of your application&amp;#039;s &amp;lt;code&amp;gt;.c&amp;lt;/code&amp;gt; file!&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=&amp;quot;text&amp;quot;&amp;gt;&lt;br /&gt;
PROJ = testcode&lt;br /&gt;
&lt;br /&gt;
include ../Makedefs&lt;br /&gt;
&lt;br /&gt;
SRCS =  $(PROJ).c&lt;br /&gt;
OBJS =  $(SRCS:.c=.o)&lt;br /&gt;
LIBS =  $(LIBDIR)/nutinit.o -lnutpro -lnutos -lnutnet -lnutfs -lnutcrt -lnutdev -lnutarch&lt;br /&gt;
TARG =  $(PROJ).hex&lt;br /&gt;
&lt;br /&gt;
all: $(OBJS) $(TARG) $(ITARG) $(DTARG)&lt;br /&gt;
&lt;br /&gt;
include ../Makerules&lt;br /&gt;
&lt;br /&gt;
clean:&lt;br /&gt;
	-rm -f $(OBJS)&lt;br /&gt;
	-rm -f $(TARG) $(ITARG) $(DTARG)&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Note&amp;#039;&amp;#039;&amp;#039;, when copy and pasting the above Makefile: the spaces before &amp;#039;&amp;#039;&amp;#039;-rm...&amp;#039;&amp;#039;&amp;#039; have to be &amp;#039;&amp;#039;&amp;#039;tabs&amp;#039;&amp;#039;&amp;#039; instead of normal spaces!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Create a plain text file and paste in the code above. &lt;br /&gt;
&lt;br /&gt;
Call it &amp;lt;code&amp;gt;Makefile&amp;lt;/code&amp;gt; (Without any file extension) and save it to:&lt;br /&gt;
 \ethernut-4.6.4\nutapp_enut13\testcode\&lt;br /&gt;
&lt;br /&gt;
=== Configuration Files ===&lt;br /&gt;
The files&lt;br /&gt;
* Makedefs&lt;br /&gt;
* Makerules&lt;br /&gt;
from&lt;br /&gt;
 \ethernut-4.6.4\nutapp_enut13\&lt;br /&gt;
are essential.&lt;br /&gt;
By building a new Nut/OS and a new sample directory (nutapp_enut13) these files get updated. &lt;br /&gt;
Your application directory (testcode) will remain untouched.&lt;br /&gt;
&lt;br /&gt;
(If you used different paths, note, that the configuration files have to be located in the top directory of the apllication directory.)&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Note:&amp;#039;&amp;#039;&amp;#039; You have to build a new sample directory and move &amp;#039;Makedefs&amp;#039; and &amp;#039;Makerules&amp;#039; to your application&amp;#039;s parent directory (if your app directory is not already a subfolder of &amp;quot;nutapp_enut13&amp;quot; as recommended) every time you build a new Nut/OS!&lt;br /&gt;
&lt;br /&gt;
=== Path environment (Win only) ===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Every command line session has its own PATH variable. &lt;br /&gt;
&lt;br /&gt;
Applications like GNU Make look up paths in that variable.&lt;br /&gt;
&lt;br /&gt;
We need to add to the path variable our tools:&lt;br /&gt;
 [[Image:winpath.png|24px]] C:/ethernut-4.6.4/nut/tools/win32;c:/winavr/utils/bin;c:/winavr/bin;&lt;br /&gt;
&lt;br /&gt;
To do so, we could enter in the command line prompt:&lt;br /&gt;
 SET PATH=c:/ethernut-4.6.4/nut/tools/win32;c:/winavr/utils/bin;c:/winavr/bin;%PATH%&lt;br /&gt;
&lt;br /&gt;
(The &amp;lt;code&amp;gt;%PATH%&amp;lt;/code&amp;gt; at the end appends the original content of the PATH variable to the newly set.&amp;lt;br&amp;gt;&lt;br /&gt;
By leaving that out the PATH gets overwritten.)&lt;br /&gt;
&lt;br /&gt;
Because every time you close the command line prompt your PATH variable gets lost,&amp;lt;br&amp;gt;&lt;br /&gt;
there is a better way to handle it.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
1. Create a plain text file and enter:&lt;br /&gt;
 SET PATH=c:/ethernut-4.6.4/nut/tools/win32;c:/winavr/utils/bin;c:/winavr/bin;%PATH%&lt;br /&gt;
&lt;br /&gt;
2. Name it &amp;lt;code&amp;gt;AVR.bat&amp;lt;/code&amp;gt; and save it to:&lt;br /&gt;
 [[Image:winpath.png|24px]] C:\ethernut-4.6.4\nutapp_enut13\testcode\&lt;br /&gt;
&lt;br /&gt;
This is called a Batch file.&amp;lt;br&amp;gt;&lt;br /&gt;
Everytime you type in &amp;lt;code&amp;gt;AVR&amp;lt;/code&amp;gt; in the &amp;lt;code&amp;gt;testcode&amp;lt;/code&amp;gt; directory now, the PATH variable gets set.&amp;lt;br&amp;gt;&lt;br /&gt;
You have to execute &amp;lt;code&amp;gt;AVR&amp;lt;/code&amp;gt; every time after you open a new command line window.&amp;lt;br&amp;gt;&lt;br /&gt;
If you do not, GNU Make will not find the tools.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Connecting ===&lt;br /&gt;
&lt;br /&gt;
To connect your Ethernut 1.3&lt;br /&gt;
&lt;br /&gt;
*Connect the SP DUO to Ethernut&amp;#039;s JTAG connector&lt;br /&gt;
*Connect the SP DUO to an available COM port of your computer using the serial cable.&lt;br /&gt;
*Connect the power supply to the barrel connector on the Ethernut board. The&lt;br /&gt;
Ethernut board is equipped with its own rectifier bridge and voltage regulator.&lt;br /&gt;
Therefore the polarity of the barrel connector isn&amp;#039;t important.&lt;br /&gt;
*Apply power to the Ethernut board by connecting the power supply to an&lt;br /&gt;
electrical outlet. When the board is powered up, the red power LED should go&lt;br /&gt;
on.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For further details have a look at the [http://ethernut.de/pdf/enhwm13e.pdf Hardware Manual]&lt;br /&gt;
&lt;br /&gt;
== Compiling and Burning ==&lt;br /&gt;
&lt;br /&gt;
[[Image:flashvideo.png|64px]][http://ethernut.de/arc/screencasts/ENUT13BURN.htm Screencast Part 3]&lt;br /&gt;
&lt;br /&gt;
Now its time to compile.&lt;br /&gt;
&lt;br /&gt;
1. Open a command line window.[[Image:winpath.png|24px]] / Shell window [[Image:linuxpath.png|24px]]&lt;br /&gt;
&lt;br /&gt;
2. Change to&lt;br /&gt;
 [[Image:winpath.png|24px]] C:\ethernut-4.6.4\nutapp_enut13\testcode\&lt;br /&gt;
&lt;br /&gt;
 [[Image:linuxpath.png|24px]] ~/ethernut-4.6.4/nutapp_enut13/testcode/&lt;br /&gt;
&lt;br /&gt;
3. Enter: Windows only!&lt;br /&gt;
&amp;lt;div class=&amp;quot;konsole&amp;quot;&amp;gt;[[Image:winpath.png|24px]] SET PATH=c:\ethernut-4.6.4\nut\tools\win32;c:\winavr\utils\bin;c:\winavr/bin;%PATH%&amp;lt;/div&amp;gt;&lt;br /&gt;
or&lt;br /&gt;
&amp;lt;div class=&amp;quot;konsole&amp;quot;&amp;gt;[[Image:winpath.png|24px]] AVR&amp;lt;/div&amp;gt;&lt;br /&gt;
if you are using a batch file.&lt;br /&gt;
&lt;br /&gt;
4. Enter:&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;div class=&amp;quot;konsole&amp;quot;&amp;gt;make clean&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;This tells &amp;quot;Make&amp;quot; to clean up the directory with respect to the rules made in the Makefile&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
You should get something like:&lt;br /&gt;
&amp;lt;div class=&amp;quot;konsole&amp;quot;&amp;gt;&lt;br /&gt;
rm -f testcode.o&lt;br /&gt;
&lt;br /&gt;
rm -f testcode.hex testcode.bin testcode.elf&amp;lt;br&amp;gt;&lt;br /&gt;
rm -f testcode.eep&amp;lt;br&amp;gt;&lt;br /&gt;
rm -f testcode.obj&amp;lt;br&amp;gt;&lt;br /&gt;
rm -f testcode.map&amp;lt;br&amp;gt;&lt;br /&gt;
rm -f testcode.lst&amp;lt;br&amp;gt;&lt;br /&gt;
rm -f testcode.bak&amp;lt;br&amp;gt;&lt;br /&gt;
rm -f testcode.i&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
If not, you maybe left out step 3.&lt;br /&gt;
&lt;br /&gt;
=== &amp;#039;Make Burn&amp;#039; ===&lt;br /&gt;
1. Connect your Ethernut 1.3. (for further details take a look at the [http://ethernut.de/pdf/enhwm13e.pdf Hardware Manual])&lt;br /&gt;
* Power Supply&lt;br /&gt;
* COM to SP DUO to JTAG&lt;br /&gt;
&lt;br /&gt;
2. Enter:&lt;br /&gt;
&amp;lt;div class=&amp;quot;konsole&amp;quot;&amp;gt; make burn&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This &amp;#039;&amp;#039;&amp;#039;compiles&amp;#039;&amp;#039;&amp;#039; the necessary files for you &amp;#039;&amp;#039;&amp;#039;and&amp;#039;&amp;#039;&amp;#039; a tool called avr-dude &amp;#039;&amp;#039;&amp;#039;burns&amp;#039;&amp;#039;&amp;#039; the binaries onto your Ethernut board&amp;#039;s flash storage.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;To configure avr-dude, please edit the following file:&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
 \ethernut-4.6.4\nut\app\Makeburn.avr-dude&lt;br /&gt;
&lt;br /&gt;
[[Image:winpath.png|24px]]&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;BURNPORT=com1&amp;#039;&amp;#039;&amp;#039;(2,3..etc.)&lt;br /&gt;
[[Image:linuxpath.png|24px]]&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;BURNPORT=/dev/ttyS0&amp;#039;&amp;#039;&amp;#039;(1,2,3..etc.)&lt;br /&gt;
&lt;br /&gt;
== Serial Communications / Tera Term ==&lt;br /&gt;
&lt;br /&gt;
[[Image:flashvideo.png|64px]][http://ethernut.de/arc/screencasts/TERATERM.htm Screencast Part 4]&lt;br /&gt;
&lt;br /&gt;
Done. All you have to do now, is to connect the serial cable to the Ethernut&amp;#039;s COM Port and start &amp;#039;&amp;#039;&amp;#039;TeraTerm&amp;#039;&amp;#039;&amp;#039; or any other serial communications tool.&lt;br /&gt;
&lt;br /&gt;
Configure TeraTerm with the follwing settings:&lt;br /&gt;
*Menubar &amp;gt; Setup &amp;gt; Serial port...&lt;br /&gt;
**Baud rate: &amp;#039;&amp;#039;&amp;#039;115200&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
**Data: &amp;#039;&amp;#039;&amp;#039;8Bit&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
**Parity: &amp;#039;&amp;#039;&amp;#039;None&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
**Stop: &amp;#039;&amp;#039;&amp;#039;1bit&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
**Flow control: &amp;#039;&amp;#039;&amp;#039;none&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
**Transmit delay: &amp;#039;&amp;#039;&amp;#039;0&amp;#039;&amp;#039;&amp;#039;;&amp;#039;&amp;#039;&amp;#039;0&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Now reset your Ethernut board and you will (hopefully) see the output.&lt;br /&gt;
&lt;br /&gt;
== Important things to remember ==&lt;br /&gt;
In order to not get frustrated remember:&lt;br /&gt;
&lt;br /&gt;
* Make sure, that the setting &amp;#039;Hide file extensions for unknown file types&amp;#039; is deactivated in you Windows folder options. Otherwise, &amp;#039;Editor&amp;#039; won&amp;#039;t create proper .c or Makefiles.&lt;br /&gt;
* In the Makefile, make sure, that the project name is identical to your &amp;lt;code&amp;gt;.c&amp;lt;/code&amp;gt; file&amp;#039;s name!&lt;br /&gt;
* Update the PATH variable every time you open a new command line prompt! Write a batch file for that.&lt;br /&gt;
* You have to build a new sample directory and move &amp;#039;Makedefs&amp;#039; and &amp;#039;Makerules&amp;#039; from there to your application&amp;#039;s parent directory every time you build a new Nut/OS with the Configurator! &lt;br /&gt;
* To configure avr-dude and toggle the COM port for example, please edit the following file: &amp;lt;code&amp;gt;c:\ethernut-4.7.4\nut\app\Makeburn.avr-dude&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== See also ==&lt;br /&gt;
* [[Nut/OS Examples]]&lt;br /&gt;
* [[Hello World!]] Example&lt;br /&gt;
&lt;br /&gt;
== External Links ==&lt;br /&gt;
&lt;br /&gt;
[http://ethernut.de/pdf/enhwm13e.pdf] Ethernut 1.3 Rev-G Hardware Manual (November 2005)&lt;br /&gt;
&lt;br /&gt;
[http://ethernut.de/pdf/enswm24e.pdf] Ethernut Software Manual (November 2005)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:Code Snippets]]&lt;br /&gt;
&lt;br /&gt;
{{Languages}}&lt;/div&gt;</summary>
		<author><name>Harald</name></author>
	</entry>
</feed>