Download Latest Version Source code (990.0 kB)
Email in envelope

Get an email when there's a new version of Embedded Web Radio

Home
Name Modified Size InfoDownloads / Week
README 2012-03-21 3.9 kB
ewebradio-2.3.1.exe 2012-03-21 1.8 MB
ewebradio-2.2.1.exe 2010-11-18 1.0 MB
ewebradio-2.0.1.exe 2009-10-22 943.1 kB
ewbradio-src-20090917.zip 2009-09-17 990.0 kB
Totals: 5 Items   4.8 MB 1
This archive contains the firmware of an embedded Internet radio.

Hardware Requirements
---------------------

The following hardware has been tested:

- Elektor Internet Radio EIR1.0C
- Atmel AT91SAM9260-EK with Calypso board
- egnite Ethernut 2.1 with Medianut 2
- egnite Ethernut 3.0 with Medianut 2
- egnite Ethernut 3.1 with Medianut 2
- egnite Ethernut 5.0 with Medianut 2

The AT91SAM7X256-EK may work as well, but in a very limited way.


Software Requirements
---------------------

You will need a cross toolchain for your target board. When running
Windows on your host, check the following:

- http://www.yagarto.de/ for ARM targets
- http://winavr.sourceforge.net/ for AVR targets

You further need the Nut/OS distribution, at least version 4.10.
We tested the radio software with 4.10.3. Visit

- http://www.ethernut.de/en/download/


Building with the Windows Installer
-----------------------------------

Before running the installer, you need to download and install
Nut/OS on your PC. The Windows installer of the webradio will
then place the sources and binaries at the right places within
your Nut/OS installation directory.

When done with the installation, run the Nut/OS Configurator
and select the right configuration file for your target. The
following configuration files had been specifically created
for the radio application:

ethernut21b-medianut for all Ethernut 2.1 board revisions
ethernut30e-medianut for all Ethernut 3.0 board revisions
ethernut31d-medianut for all Ethernut 3.1 board revisions
ethernut50f-medianut for all Ethernut 5.0 board revisions

For the Elektor Internet Radio and the Atmel kits you can
use the configuration files that are included in the Nut/OS
distribution. After selecting the configuration file, you
must build the Nut/OS libraries. This requires, that the
related toolchain (YAGARTO, WinAVR etc.) is available.

In order to create an instance of the ewebradio source code
in your application build tree, select "Create sample tree"
in the Nut/OS Configurator. The term create is misleading.
In fact this can be also used to update existing application
trees.

More details are available in the Nut/OS Software Manual:

- http://www.ethernut.de/en/documents/


Building with the Source Package
--------------------------------

Install Nut/OS and the toolchain on your host PC. Configure the
system for your target board. The Atmel kits should work with the
configuration files included in the Nut/OS distribution. 

Special configuration files for Ethernut 2, 3 and 5 are available
in this package in directory conf. Copy them to the Nut/OS
nut/conf directory.

When configured, build the Nut/OS libraries and create a sample
directory using the Nut/OS Configurator. Copy the contents of
the src directory in a new directory of your application sample 
directory. For example, if your application directory is 
ethernut-4.10.3/nutapp, then move the sources to 
ethernut-4.10.3/nutapp/ewebradio.

Change to this new directory, make sure that the binary toolchain
is available on the command line (PATH) and type

  make clean all

This should build the binaries for your target board.

On Ethernut 2 there is not enough flash space available for
the web content. A special tool named ewebinit is provided
to transfer the HTML files into the on-board DataFlash. You
need to build and run this tool first.

More details are available in the Nut/OS Software Manual:

- http://www.ethernut.de/en/documents/


Using the Binaries
------------------

The Windows installer includes ready to use binaries, which
will be placed in a target specific subdirectory of
nut/bin/boards.


Optional Modifications
----------------------

Beside changing the source code a few general items can be
configured in the file UserConf.mk.
Source: README, updated 2012-03-21