Harald: 1 revision imported

2016-10-27T16:02:55Z

1 revision imported

Harald: /* Details */

2012-08-14T07:48:52Z

‎Details

New page

== Test Environments ==

{| class="smalldiv"
| style="background-color:#F6F9ED" |
| style="background-color:#F6F9ED" | Hardware Comments
| style="background-color:#F6F9ED" | '''Nut/OS 4.6.3'''
| style="background-color:#F6F9ED" | '''Nut/OS 4.6.4'''
| style="background-color:#F6F9ED" | '''Nut/OS 4.7.4'''
| style="background-color:#F6F9ED" | '''Nut/OS 4.8.0'''
| style="background-color:#F6F9ED" | '''Nut/OS 4.8.7'''
|-
| Ethernut 1.3 H
|
| OK
| OK [http://ethernut.de/arc/WIKI_BINARIES_ZIPPED/hello-world-enut13H-nutos-4.6.4.zip '''Binaries''']
| OK [http://ethernut.de/arc/WIKI_BINARIES_ZIPPED/hello-world-enut13H-nutos-4.7.4.zip '''Binaries''']
| OK [http://ethernut.de/arc/WIKI_BINARIES_ZIPPED/hello-world-enut13H-nutos-4.8.0.zip '''Binaries''']
| OK [[Media:Hello-world-enut13H-nutos-4.8.7.zip|'''Binaries''']] '''Compiler:''' AVR-GCC 4.3.2
|-
| Ethernut 2.1 B
|
| OK
| OK [http://ethernut.de/arc/WIKI_BINARIES_ZIPPED/hello-world-enut21B-nutos-4.6.4.zip '''Binaries''']
| OK [http://ethernut.de/arc/WIKI_BINARIES_ZIPPED/hello-world-enut21B-nutos-4.7.4.zip '''Binaries''']
| OK [http://ethernut.de/arc/WIKI_BINARIES_ZIPPED/hello-world-enut21B-nutos-4.8.0.zip '''Binaries''']
| OK [[Media:Hello-world-enut21B-nutos-4.8.7.zip|'''Binaries''']] '''Compiler:''' AVR-GCC 4.3.2
|-
| Ethernut 3.0 E
|
| OK
| OK [http://ethernut.de/arc/WIKI_BINARIES_ZIPPED/hello-world-enut30E-nutos-4.6.4.zip '''Binaries''']
| OK [http://ethernut.de/arc/WIKI_BINARIES_ZIPPED/hello-world-enut30E-nutos-4.7.4.zip '''Binaries''']
| OK [http://ethernut.de/arc/WIKI_BINARIES_ZIPPED/hello-world-enut30E-nutos-4.8.0.zip '''Binaries''']
| OK [[Media:Hello-world-enut30E-nutos-4.8.7.zip|'''Binaries''']] '''Compiler:''' ARM-GCC 4.3.3
|-
| EIR 1.0 C
| Set jumper JP1 to DEBUG mode.
| OK 
| OK [http://ethernut.de/arc/WIKI_BINARIES_ZIPPED/hello-world-EIR1C-nutos-4.6.4.zip '''Binaries''']
| OK [http://ethernut.de/arc/WIKI_BINARIES_ZIPPED/hello-world-EIR1C-nutos-4.7.4.zip '''Binaries''']
| OK [http://ethernut.de/arc/WIKI_BINARIES_ZIPPED/hello-world-EIR1C-nutos-4.8.0.zip '''Binaries''']
|
|-
| id="compilertd" colspan="5" |'''Compiler:''' ARM-GCC 4.2.2 ; AVR-GCC 4.3.0
|
|}

== Description ==

This very basic [[Nut/OS Examples|sample program]] puts out the phrase "Hello World" to the serial port.

== Source Code ==

<source lang="c">
#include <dev/board.h>
#include <stdio.h>

int main(void)
{
unsigned long baud = 115200;

NutRegisterDevice(&DEV_DEBUG, 0, 0);

freopen(DEV_DEBUG_NAME, "w", stdout);
_ioctl(_fileno(stdout), UART_SETSPEED, &baud);

printf("Hello World!");

for(;;);

return 0;
}
</source>

== Details ==

<source lang="c">#include <dev/board.h></source>
Includes a header file, which contains board specific definitions. This helps to make the program portable on all supported target platforms.

<source lang="c">#include <stdio.h></source>
Includes another header file. You need this if your code calls standard input and output functions.

<source lang="c">int main(void)</source>
Declares a C function named <code>main</code>. More advanced applications will have a large number of functions, but they always must declare a <code>main</code> function, which will be executed on startup.

<source lang="c">
NutRegisterDevice(&DEV_DEBUG, 0, 0);
freopen(DEV_DEBUG_NAME, "w", stdout);
</source>
Nut/OS doesn't provide a default device for standard output. If an application wants to write to the standard output via <code>printf</code> for example, it must assign a registered driver to the <code>stdout</code> stream. Furthermore, a device drivers must be registered before it can be used.

The first line registers a driver for debug output and the second line assigns this driver to the <code>stdout</code> stream.

<code>DEV_DEBUG</code> and <code>DEV_DEBUG_NAME</code> are defined in the header file <code>dev/board.h</code> and are available for all target boards. On the AVR this is the first USART, while DBGU is used on AT91 boards. On the Gameboy however, the LCD is used.

One specific feature of DEV_DEBUG is, that it is a polling device. That means, that its driver is quite simple, easy to implement and you can even use it for printing data in interrupt routines.

In most case it is write-only. You cannot use it for user input. Trying to do so will simply crash the system. If you need to read user input, then try

<source lang="c">
NutRegisterDevice(&DEV_CONSOLE, 0, 0);
freopen(DEV_CONSOLE_NAME, "w", stdout);
</source>

However, this is available on later Nut/OS releases only and may use a different hardware interface. Furthermore it is interrupt driven, you cannot use it within interrupt routines. However, if you enabled <tt>NUT_DEV_DEBUG_READ</tt> in the Configurator and if the device supports input, then DEV_CONSOLE will become equal to DEV_DEBUG for most target boards.

Whatever serial port device you may use to say "Hello", the remaining code works with all of them.

<source lang="c">
unsigned long baud = 115200;

_ioctl(_fileno(stdout), UART_SETSPEED, &baud);
</source>

A serial port like USART or DBGU needs to be configured, specifically its transfer rate, also known as baud rate. While most embedded systems can provide much higher rates, 115,200 bits per second is still the upper limit on most desktop computers.

The <code>_ioctl()</code> function is typically used in C programs to configure device specific settings. It expects a file handle, not a stream. Thus the function <code>_fileno()</code> is called to retrieve the file handle of the <code>stdout</code> stream.

Also note, that you can't directly pass configuration constanst to <code>_ioctl()</code>. Instead you must assign the value to a variable and use a pointer to this variable for the function argument.

<source lang="c">printf("Hello World!");</source>
Puts out the phrase "Hello World!" to standard output.

<source lang="c">
for(;;);
return 0;
</source>

Once started, Nut/OS applications will never return. If they do, the result is unknown, so we put an endless loop before the <code>return</code> statement to avoid this.

Although never reached, the <code>return 0</code> is sometimes necessary to get rid of a compiler warning. However, other compilers may spit out a warning about unreachable code.

== Output ==

[[Image:teraterm-serial-port-setup.png|thumb|right|TeraTerm serial port setup]]

On most target boards the output is sent to the first serial port and can be viewed by connecting a terminal emulator like TeraTerm on Windows or miniterm on Linux.

Hello World!

== See also ==
* More [[Nut/OS Examples]]

== External Links ==

[http://en.wikipedia.org/wiki/Hello_world Hello world program] A computer program that prints out "Hello world!".

[http://en.wikipedia.org/wiki/C_preprocessor C preprocessor] A separate program invoked by the compiler as the first part of translation.

[http://en.wikipedia.org/wiki/Standard_streams Standard streams] The three standard I/O connections are called standard input, standard output and standard error.

[http://www.ethernut.de/api/group__xg_device.html NutRegisterDevice] Register a specific device which will be used by a Nut/OS application.

[http://www.ethernut.de/en/documents/rs232primer.html Ethernut RS-232 Primer] explains how to connect serial communication ports.

[http://en.wikipedia.org/wiki/Ioctl ioctl] The most common use of ioctls is to control hardware devices.

[http://en.wikipedia.org/wiki/File_descriptor File descriptor] An abstract key for accessing a file or a device.

 

[[Category:Code Snippets]]

{{Languages}}

← Older revision	Revision as of 16:02, 27 October 2016
(No difference)

Hello World! - Revision history

Harald: 1 revision imported

Harald: /* Details */