Index of /pub/rtems/releases/4.10/4.10.1

21 July 2011

This is the source distribution for RTEMS 4.10.1 source, add-ons,
and documentation.  The primary development platforms supported are
GNU/Linux distribtions which use RPMs.  MS-Windows is supported as a
secondary platform.

The 4.10.1 release is the second release in the 4.10 series.  This
release is a bug fix release which also includes BSP updates and
corrections.   It includes fixes for 29 issues with PRs of varying
severity.  The list of PRs is at:

http://www.rtems.org/wiki/index.php/4.9_Release_Notes#Release_4.9.4_Changes

Some of the enhancements included between the 4.9 and 4.10 release series
are listed at:

http://www.rtems.org/wiki/index.php/4.10_Release_Notes

Installing Tools
================
For Fedora users, loading the prebuilt tools should be very easy and
something like this:

(1) Load the appropriate Yum repository configuration
    information.  This example is for Fedora GNU/Linux.
    RPMs are also provided for RedHat Enterprise Linux
    and SUSE.

    # Replace NNN with your 7-15 to reflect your Fedora version
    # Replace ARCH with your i386 or x86_64 to reflect your host architecture
    # Replace VVV with the current version of the RPMs
    rpm -ivh ftp://ftp.rtems.org/pub/rtems/linux/4.10/fedora/NNN/ARCH/rtems-4.10-yum-conf-VVV.fcNNN.noarch.rpm ftp://ftp.rtems.org/pub/rtems/linux/4.10/fedora/NNN/ARCH/rtems-4.10-release-VVV.fcNNN.noarch.rpm

    The above loads the Yum Repository configuration for RTEMS 4.10
    Tools for your development host.

(2) Load the cross development RPMs for your RTEMS target architecture
    along with the RTEMS 4.10 specific version of GNU autoconf
    and automake.

      # Replace CPU with the name of the CPU architecture you
      # want to use RTEMS on.  Choice are: 
      #   arm bfin h8300 i386 m68k mips powerpc sh sparc 
      yum -y install "*4.10*CPU-*" "*4.10*auto*"

That's it.  You should be able to configure and build RTEMS at this
point.  

Building the SPARC/SIS BSP
==========================
If targeting a simulator BSP included with GDB (sparc/sis,
powerpc/psim, or mips/jm43904), you should be able to generate and run
target executables in a matter of minutes.  Normally it takes longer
to download the tools via ftp than to build RTEMS.

In this example, we will build RTEMS for the sparc/sis BSP. Since
it has a simulator which requires no command line arguments to
run executable, there is less opportunity for something to go wrong.
The following steps should get you to a running example after you
have loaded the SPARC RTEMS tools.

tar xjf rtems-4.10.0.tar.bz2
export PATH=/opt/rtems-4.10/bin:$PATH
mkdir b-sis
cd b-sis
../rtems-4.10.0/configure --target=sparc-rtems4.10 --enable-rtemsbsp=sis \
  --enable-tests=samples
make
sparc-rtems4.10-run sparc-rtems4.10/c/sis/testsuites/samples/ticker/ticker.exe

At this point you should see the output of the ticker sample executable.

Conclusion
==========

Configuring qemu so that it will boot an RTEMS application for the
i386/pc386 takes a bit longer but is still quite straightfoward. 
Many ARM and Blackfin BSPs can be executed on the Skyeye simulator.
The rtems-testing CVS module provides scripts which aid in the use
of simulators.

Comments, feedback welcomed.  See the instructions at http://www.rtems.org
on joining the users mailing list.

--joel sherrill
joel.sherrill@OARcorp.com