Index of /pub/rtems/releases/4.7/4.7.1

 NameLast modifiedSize

 Parent Directory  -
 PRs-closed-4.7.12007-04-13 23:15 2.2K
 README.txt2007-04-13 23:15 1.9K
 SUPPORT2007-04-13 23:15 750
 TOOL_VERSIONS2007-04-13 23:15 2.6K
 ada-examples-4.7.1.tar.bz22007-04-13 23:15 5.9K
 class-examples-4.7.1.tar.bz22007-04-13 23:15 18K
 contrib/2007-04-13 23:15 -
 examples-4.7.1.tar.bz22007-04-13 23:15 15K
 md5sum.txt2007-04-13 23:15 764
 network-demos-4.7.1.tar.bz22007-04-13 23:15 24K
 rtems-4.7.0-4.7.1.diff.bz22007-04-13 23:15 3.3M
 rtems-4.7.1.tar.bz22007-04-13 23:15 9.4M
 rtems-ChangeLog-4.7.0-4.7.1.diff.bz22007-04-13 23:15 4.7K
 rtems-addon-packages-4.7.1.tar.bz22007-04-13 23:15 4.7M
 rtemsdocs-4.7.1.tar.bz22007-04-13 23:15 8.6M


13 April 2007

This is the source distribution for RTEMS 4.7.1 source, 
add-ons, and documentation.  The primary development
platforms supported are GNU/Linux distribtions which use 
RPMs.

The 4.7.1 release is the second release in the 4.7 series.
It includes all bug fixes found in the 4.6 series along
with a number of enhancements and bug fixes since the 
4.7.0 release.  Some of the enhancements included
between the 4.6 and 4.7 release series are listed at:

http://www.rtems.org/rtems-4.7/index.html

Specific issues addressed between 4.7.0 and 4.7.1 are
listed in the file PRs-closed-4.7.1.

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

(1) Load the appropriate Yum repository configuration
    information.

    # Replace NNN with your 1-6 to reflect the Fedora version
    rpm -ivh ftp://ftp.rtems.org/pub/rtems/linux/4.7/fedora/NNN/i386/rtems-4.7-yum-conf-0.4-1.fcNNN.noarch.rpm

(2) Load cross development RPMs for your target architecture
    along with the RTEMS 4.7 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 avr h8300 i386 m68k mips powerpc sh sparc 
      yum -y install "*4.7*CPU*" "*4.7*auto*"

That's it.  You should be able to configure and build RTEMS
at the point.  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.  Configuring qemu so that it will boot an RTEMS
application for the i386/pc386 takes a bit longer but is
still quite straightfoward. Normally it takes longer to
download the tools via ftp than to build RTEMS.

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

--joel sherrill
joel.sherrill@OARcorp.com