There are various ways to download an executable image to a
There are various ways to download an executable image to a
target board, and these involve different ways of preparing the
target board, and these involve different ways of preparing the
executable image. In the eCos Hardware Abstraction Layer (HAL package)
executable image. In the eCos Hardware Abstraction Layer (HAL package)
there are configuration options to support the different download
there are configuration options to support the different download
methods. summarizes the
methods. summarizes the
ways in which an eCos image can be prepared for different types of
ways in which an eCos image can be prepared for different types of
download. This is not an exhaustive list, some targets define
download. This is not an exhaustive list, some targets define
additional start-up types of their own. Where a ROM Monitor is
additional start-up types of their own. Where a ROM Monitor is
mentioned, this will usually be RedBoot, although on some older, or
mentioned, this will usually be RedBoot, although on some older, or
low resource, targets you may need to use CygMon or the GDB stubs ROM,
low resource, targets you may need to use CygMon or the GDB stubs ROM,
see the target documentation for details.
see the target documentation for details.
Configuration for various download methods
Configuration for various download methods
Download method
Download method
HAL configuration
HAL configuration
Burn hardware ROM
Burn hardware ROM
ROM or ROMRAM start-up
ROM or ROMRAM start-up
Download to ROM emulator
Download to ROM emulator
ROM or ROMRAM start-up
ROM or ROMRAM start-up
Download to board with ROM Monitor
Download to board with ROM Monitor
RAM start-up
RAM start-up
Download to simulator without ROM Monitor
Download to simulator without ROM Monitor
ROM start-up
ROM start-up
Download to simulator with ROM Monitor
Download to simulator with ROM Monitor
RAM start-up
RAM start-up
Download to simulator ignoring devices
Download to simulator ignoring devices
SIM configuration
SIM configuration
Run synthetic target
Run synthetic target
RAM start-up
RAM start-up
You cannot run an application configured for RAM start-up
You cannot run an application configured for RAM start-up
on the simulator directly: it will fail during start-up. You can
on the simulator directly: it will fail during start-up. You can
only download it to the simulator if
only download it to the simulator if
you are already running RedBoot in the simulator,
you are already running RedBoot in the simulator,
as described in the toolchain documentation
as described in the toolchain documentation
or you load through the
or you load through the
SID
SID
GDB debugging component. This is not the same as the simulated
GDB debugging component. This is not the same as the simulated
stub, since it does not require a target program to be running to
stub, since it does not require a target program to be running to
get GDB to talk to it. It can be done before letting the simulator
get GDB to talk to it. It can be done before letting the simulator
run
run
or you use the ELF loader component to get a program into memory.
or you use the ELF loader component to get a program into memory.
Configuring eCos' HAL package for simulation should
Configuring eCos' HAL package for simulation should
rarely be needed for real development; binaries built with such
rarely be needed for real development; binaries built with such
a kernel will not run on target boards at all,
a kernel will not run on target boards at all,
and the MN10300 and
and the MN10300 and
TX39 simulators can run binaries built for stdeval1 and jmr3904
TX39 simulators can run binaries built for stdeval1 and jmr3904
target boards.
target boards.
The main use for a ``simulation'' configuration
The main use for a ``simulation'' configuration
is if you are trying to work around problems with the device drivers
is if you are trying to work around problems with the device drivers
or with the simulator. Also note that when using a TX39 system configured
or with the simulator. Also note that when using a TX39 system configured
for simulator start-up you should then invoke the simulator with
for simulator start-up you should then invoke the simulator with
the
the
option instead of
option instead of
If your chosen architecture does not have simulator support,
If your chosen architecture does not have simulator support,
then the combinations above that refer to the simulator do not apply.
then the combinations above that refer to the simulator do not apply.
Similarly, if your chosen platform does not have RedBoot
Similarly, if your chosen platform does not have RedBoot
ROM support, the combinations listed above that use
ROM support, the combinations listed above that use
RedBoot do not apply.
RedBoot do not apply.
The debugging environment for most developers will be either
The debugging environment for most developers will be either
a hardware board or the simulator, in which case they will be able
a hardware board or the simulator, in which case they will be able
to select a single HAL configuration.
to select a single HAL configuration.
<!-- <index></index> --></code></pre></td>
<td class="diff"><pre><code><TITLE><!-- <index></index> --></code></pre></td>
</tr>
<tr class="diffcode">
<td class="diff"><pre><code>Configuration Tool on Windows and Linux Quick Start
Configuration Tool on Windows and Linux Quick Start
Note that the use of the Configuration Tool
Note that the use of the Configuration Tool
is described in detail in
is described in detail in
LINKEND="THE-ECOS-CONFIGURATION-TOOL">.
LINKEND="THE-ECOS-CONFIGURATION-TOOL">.
The Configuration Tool (see )
The Configuration Tool (see )
has five main elements: the configuration window,
has five main elements: the configuration window,
the conflicts window,
the conflicts window,
the properties window, the short
the properties window, the short
description window,
description window,
and the output window.
and the output window.
Configuration Tool
Configuration Tool
Start by opening the templates window via Build->Templates.
Start by opening the templates window via Build->Templates.
Select the desired target (see ).
Select the desired target (see ).
Template selection
Template selection
Make sure that the configuration is correct for the target
Make sure that the configuration is correct for the target
in terms of endianness, CPU model, Startup type, etc. (see ).
in terms of endianness, CPU model, Startup type, etc. (see ).
LINKEND="FIGURE-SELECTING-THE-BUILD-LIBRARY-MENU-ITEM">). The
LINKEND="FIGURE-SELECTING-THE-BUILD-LIBRARY-MENU-ITEM">). The
application will configure the sources, prepare a build tree, and
application will configure the sources, prepare a build tree, and
build the libtarget.a library, which contains the
build the libtarget.a library, which contains the
eCos kernel and other packages.
eCos kernel and other packages.
Selecting the Build Library menu item
Selecting the Build Library menu item
The Save As dialog box will appear, asking
The Save As dialog box will appear, asking
you to specify a directory in which to place your save file. You
you to specify a directory in which to place your save file. You
can use the default, but it is a good idea to make a subdirectory,
can use the default, but it is a good idea to make a subdirectory,
called ecos-work for example.
called ecos-work for example.
Save file dialog
Save file dialog
The first time you build an eCos library for a specific
The first time you build an eCos library for a specific
architecture, the Configuration Tool may prompt
architecture, the Configuration Tool may prompt
you for the location of the appropriate build tools (including
you for the location of the appropriate build tools (including
make and
make and
TARGET-gcc) using a
TARGET-gcc) using a
Build Tools dialog box (as shown in
Build Tools dialog box (as shown in
LINKEND="FIGURE-BUILD-TOOLS-DIALOG">). You can select a location from
LINKEND="FIGURE-BUILD-TOOLS-DIALOG">). You can select a location from
the drop down list, browse to the directory using the
the drop down list, browse to the directory using the
Browse button, or type in the location of the
Browse button, or type in the location of the
build tools manually.
build tools manually.
Build tools dialog
Build tools dialog
The Configuration Tool may also prompt you
The Configuration Tool may also prompt you
for the location of the user tools (such as cat and
for the location of the user tools (such as cat and
ls) using a User Tools dialog
ls) using a User Tools dialog
box (as shown in ). As with
box (as shown in ). As with
the Build Tools dialog, you can select a location
the Build Tools dialog, you can select a location
from the drop down list, browse to the directory using the
from the drop down list, browse to the directory using the
Browse button, or type in the location of the
Browse button, or type in the location of the
user tools manually. Note that on Linux, this will often be
user tools manually. Note that on Linux, this will often be
unnecessary as the tools will already be on your PATH.
unnecessary as the tools will already be on your PATH.
User tools dialog
User tools dialog
When the tool locations have been entered, the Configuration
When the tool locations have been entered, the Configuration
Tool will configure the sources, prepare a build tree,
Tool will configure the sources, prepare a build tree,
and build the libtarget.a library, which contains
and build the libtarget.a library, which contains
the eCos kernel and other packages.
the eCos kernel and other packages.
The output from the configuration process and the building
The output from the configuration process and the building
of libtarget.a will be shown in the output
of libtarget.a will be shown in the output
window.
window.
Once the build process has finished you will have a kernel
Once the build process has finished you will have a kernel
with other packages in libtarget.a. You should
with other packages in libtarget.a. You should
now build the eCos tests for your particular configuration.
now build the eCos tests for your particular configuration.
You can do this by selecting Build -> Tests.
You can do this by selecting Build -> Tests.
Notice that you could have selected Tests instead
Notice that you could have selected Tests instead
of Library in the earlier step and it would
of Library in the earlier step and it would
have built both the library and the tests,
have built both the library and the tests,
but this would increase the build time substantially, and if you
but this would increase the build time substantially, and if you
do not need to build the tests it is unnecessary.
do not need to build the tests it is unnecessary.
Selecting the Build Tests menu item
Selecting the Build Tests menu item
will guide you through running one
will guide you through running one
of the test cases you just built on the selected target,
of the test cases you just built on the selected target,
using GDB.
using GDB.
<!-- <index></index> --></code></pre></td>
<td class="diff"><pre><code><TITLE><!-- <index></index> --></code></pre></td>
</tr>
<tr class="diffcode">
<td class="diff"><pre><code>Ecosconfig on Windows and Linux Quick Start
Ecosconfig on Windows and Linux Quick Start
As an alternative to using the graphical
As an alternative to using the graphical
Configuration Tool, it is still possible to
Configuration Tool, it is still possible to
configure and build a kernel by editing a configuration file manually
configure and build a kernel by editing a configuration file manually
and using the ecosconfig command.
and using the ecosconfig command.
Manual configuration and the ecosconfig command are
Manual configuration and the ecosconfig command are
described in detail in .
described in detail in .
To use the ecosconfig command you need to start a
To use the ecosconfig command you need to start a
shell. In Windows you need to start a
shell. In Windows you need to start a
CygWinbash shell, not a
CygWinbash shell, not a
DOS command line.
DOS command line.
-->
The following instructions assume that the
The following instructions assume that the
PATH and ECOS_REPOSITORY
PATH and ECOS_REPOSITORY
environment variables have been setup correctly as described in
environment variables have been setup correctly as described in
LINKEND="user-guide-installation-linux">. They also assume Linux
LINKEND="user-guide-installation-linux">. They also assume Linux
usage but equally well apply to Windows running Cygwin.
usage but equally well apply to Windows running Cygwin.
Before invoking ecosconfig you need to
Before invoking ecosconfig you need to
choose a directory in which to work. For the purposes of this tutorial,
choose a directory in which to work. For the purposes of this tutorial,
the default path will be BASE_DIR/ecos-work.
the default path will be BASE_DIR/ecos-work.
Create this directory and change to it by typing:
Create this directory and change to it by typing:
$ mkdir BASE_DIR/ecos-work
$ mkdir BASE_DIR/ecos-work
$ cd BASE_DIR/ecos-work
$ cd BASE_DIR/ecos-work
To see what options can be used with ecosconfig,
To see what options can be used with ecosconfig,
type:
type:
$ ecosconfig --help
$ ecosconfig --help
The available packages, targets and templates may be listed
The available packages, targets and templates may be listed
as follows:
as follows:
$ ecosconfig list
$ ecosconfig list
Here is sample output from ecosconfig showing
Here is sample output from ecosconfig showing
the usage message.
the usage message.
Getting <!-- <index></index> --> help from ecosconfig
Getting <!-- <index></index> --> help from ecosconfig
$ ecosconfig --help
$ ecosconfig --help
Usage: ecosconfig [ qualifier ... ] [ command ]
Usage: ecosconfig [ qualifier ... ] [ command ]
commands are:
commands are:
list : list repository contents
list : list repository contents
new TARGET [ TEMPLATE [ VERSION ] ] : create a configuration
new TARGET [ TEMPLATE [ VERSION ] ] : create a configuration
target TARGET : change the target hardware
target TARGET : change the target hardware
template TEMPLATE [ VERSION ] : change the template
template TEMPLATE [ VERSION ] : change the template
delays might be quite long. On a hardware board (where the clock
delays might be quite long. On a hardware board (where the clock
speed is 100 ticks/second) the delays should average to
speed is 100 ticks/second) the delays should average to
about 2.25 seconds. In simulation, the delay will depend on the
about 2.25 seconds. In simulation, the delay will depend on the
speed of the host processor and will almost always be much slower than
speed of the host processor and will almost always be much slower than
the actual board. You might want to reduce the delay parameter when running
the actual board. You might want to reduce the delay parameter when running
in simulation.
in simulation.
shows how this
shows how this
multitasking program executes. Note that apart from the thread
multitasking program executes. Note that apart from the thread
creation system calls, this program also creates and uses a
creation system calls, this program also creates and uses a
mutex for synchronization
mutex for synchronization
between the printf() calls in the two
between the printf() calls in the two
threads. This is because the C library standard I/O (by default) is
threads. This is because the C library standard I/O (by default) is
configured not to be thread-safe, which means that if more than one
configured not to be thread-safe, which means that if more than one
thread is using standard I/O they might corrupt each other. This is
thread is using standard I/O they might corrupt each other. This is
fixed by a mutual exclusion (or mutex) lockout
fixed by a mutual exclusion (or mutex) lockout
mechanism: the threads do not call printf() until
mechanism: the threads do not call printf() until
cyg_mutex_lock() has returned, which only happens
cyg_mutex_lock() has returned, which only happens
when the other thread calls
when the other thread calls
cyg_mutex_unlock().
cyg_mutex_unlock().
You could avoid using the mutex by configuring the C library to
You could avoid using the mutex by configuring the C library to
be thread-safe (by selecting the component
be thread-safe (by selecting the component
CYGSEM_LIBC_STDIO_THREAD_SAFE_STREAMS).
CYGSEM_LIBC_STDIO_THREAD_SAFE_STREAMS).
ID="FIGURE-TWOTHREADS-WITH-SIMPLE-PRINTS"> Two</code></pre></td>
<td class="diff"><pre><code>ID="FIGURE-TWOTHREADS-WITH-SIMPLE-PRINTS"><!-- <xref> --> <TITLE>Two</code></pre></td>
</tr>
<tr class="diffcode">
<td class="diff"><pre><code>threads with simple print statements after random delays
threads with simple print statements after random delays
More Features — <!-- <index></index> -->Clocks and Alarm</code></pre></td>
<td class="diff"><pre><code><TITLE>More Features — <!-- <index></index> -->Clocks and Alarm</code></pre></td>
</tr>
<tr class="diffcode">
<td class="diff"><pre><code>Handlers
Handlers
If a program wanted to execute a task at a given time, or
If a program wanted to execute a task at a given time, or
periodically, it could do it in an inefficient way by sitting in a
periodically, it could do it in an inefficient way by sitting in a
loop and checking the real-time clock to see if the proper amount of
loop and checking the real-time clock to see if the proper amount of
time has elapsed. But operating systems usually provide system calls
time has elapsed. But operating systems usually provide system calls
which allow the program to be informed at the desired time.
which allow the program to be informed at the desired time.
eCos provides a rich timekeeping formalism, involving
eCos provides a rich timekeeping formalism, involving
counters, clocks,
counters, clocks,
alarms, and timers. The
alarms, and timers. The
precise definition, relationship, and motivation of these features is
precise definition, relationship, and motivation of these features is
beyond the scope of this tutorial, but these examples illustrate how
beyond the scope of this tutorial, but these examples illustrate how
to set up basic periodic tasks.
to set up basic periodic tasks.
Alarms are events that happen at
Alarms are events that happen at
a given time, either once or periodically. A thread associates an
a given time, either once or periodically. A thread associates an
alarm handling function with the alarm, so that the function will
alarm handling function with the alarm, so that the function will
be invoked every time the alarm “goes off”.
be invoked every time the alarm “goes off”.
A Sample Program with Alarms
A Sample Program with Alarms
simple-alarm.c (in
simple-alarm.c (in
the examples directory) is a short program that creates a thread that
the examples directory) is a short program that creates a thread that
creates an alarm. The alarm is handled by the function
creates an alarm. The alarm is handled by the function
test_alarm_func(), which sets a global
test_alarm_func(), which sets a global
variable. When the main thread of execution sees that the variable has
variable. When the main thread of execution sees that the variable has
changed, it prints a message.
changed, it prints a message.
A sample <!-- <index></index> -->program that creates an alarm
A sample <!-- <index></index> -->program that creates an alarm
/* this is a very simple program meant to demonstrate
/* this is a very simple program meant to demonstrate
a basic use of time, alarms and alarm-handling functions in eCos */
a basic use of time, alarms and alarm-handling functions in eCos */
#include <cyg/kernel/kapi.h>
#include <cyg/kernel/kapi.h>
#include <stdio.h>
#include <stdio.h>
#define NTHREADS 1
#define NTHREADS 1
#define STACKSIZE 4096
#define STACKSIZE 4096
static cyg_handle_t thread[NTHREADS];
static cyg_handle_t thread[NTHREADS];
static cyg_thread thread_obj[NTHREADS];
static cyg_thread thread_obj[NTHREADS];
static char stack[NTHREADS][STACKSIZE];
static char stack[NTHREADS][STACKSIZE];
static void alarm_prog( cyg_addrword_t data );
static void alarm_prog( cyg_addrword_t data );
/* we install our own startup routine which sets up
/* we install our own startup routine which sets up
