wiki:Release/4.9

Version 65 (modified by Strauman, on Sep 25, 2008 at 2:01:50 AM) (diff)

4.9 Release Notes

The 4.9 branch was cut on 10 September 2008 and 4.9.0 was released on 24 September 2008. This is the first release from the 4.9 Release Series and although well tested, we have not received success reports on a number of BSPs. Please help by reporting success and updating the list at the bottom of this page.

<blockquote> <b>Latest:</b> http://www.rtems.org/ftp/pub/rtems/4.9.0/ </blockquote>

This page lists the changes and improvements that are planned and/or have been made to the RTEMS development source since the 4.8 release branch was made. As usual, there were submissions that were not expected and incorporated when submitted into the 4.9 release. In keeping with project history, the feature set of the 4.9 release series will be largely be driven by user submissions and requests.

<blockquote> The RTEMS project provides built tools sets that are available for download. For Linux the RPM package formater is support and avaliable from the APT/Yum Repository. For Windows MinGW Executable Installers are available. </blockquote>

If any changes or enhancements are missing in this list, feel free to add them. After all, that's why this is a Wiki.

Tool Improvements

  • Ralf Corsepius is continuing on his effort to improve the build infratructure and eventually support the CPU and BSP Kits in released version. This is both an RTEMS and a Tool Improvement as Ralf's goal is to be able to release CPU Kits in binary RPM form. In late May 2007, he made his first cpukits available for testing.
  • Thanks again to Ralf, it is possible to provide target specific versions of the development tools. This is important when GCC drops support for an old architecture or we are avoiding target specific bugs in a particular tool version. Nominally, most RTEMS targets will use the same tools and they have been upgraded to the following versions:
    • autoconf 2.62
    • automake 1.10.1
    • binutils 2.18
    • gcc 4.3.2 for C/C++ with newlib 1.16.0
    • gdb 6.8

The latest patch for each tools is in rtems/contrib/crossrpms/patches.

RTEMS Improvements

In this section, we discuss public API level changes as well as improvements to the implementation of those API routines.

Public API changes usually fall into one of the following categories:

  • Addition of new methods
  • Modifications to prototypes
  • Deletion of obsoleted methods

Implementation improvements usually fall into one of the following categories:

  • Algorithm improvements in execution time or memory usage
  • Critical section reduction

API Changes

  • Added readv() and writev(). Implemented by JoelSherrill
  • Added rtems_task_self(). Implemented by JoelSherrill
  • Added posix_memalign(). Implemented by JoelSherrill
  • Added Object Manager including documentation. Includes many new helper services related to object classes, Ids, and names and renamed some existing but unofficially available and undocumented services. Implemented by JoelSherrill. Changes include:
    • Added rtems_build_name() - build object name from characters
    • Added rtems_object_get_classic_name() - lookup name from id
    • Added rtems_object_get_name() - obtain object name as string
    • Added rtems_object_set_name() - set object name
    • rtems_object_id_api_minimum() - obtain minimum API value
    • rtems_object_id_api_maximum() - obtain maximum API value
    • rtems_object_id_api_minimum_class() - obtain minimum class value
    • rtems_object_id_api_maximum_class() - obtain maximum class value
    • rtems_object_get_api_name() - obtain API name
    • rtems_object_get_api_class_name() - obtain class name
    • rtems_object_get_class_information() - obtain class information
    • Renamed rtems_get_node() to rtems_object_id_get_node()
    • Renamed rtems_get_api() to rtems_object_id_get_api()
    • Renamed rtems_get_class() to rtems_object_id_get_class()
    • Renamed rtems_get_index() to rtems_object_id_get_index()
  • rtems_clock_get() is an overloaded routine which takes an enumerated value to indicate that format of the time related information that will be returned through the void * pointer. This particular method is certainly not an example of strong typing. Moreover, since its generality results in the inclusion of code which is almost certainly unused in any particular application. For example, it can return the current time of day in three formats. In this light, a set of new, smaller methods were refactored from rtems_clock_get() and the new version of rtems_clock_get() is implemented as subroutine calls to the new routines. These new routines should be simpler and easier to use. They are:
    • rtems_clock_get_tod() - Obtain TOD in Classic API structure
    • rtems_clock_get_tod_timeval() - Obtain TOD in struct timeval
    • rtems_clock_get_seconds_since_epoch() - Obtain TOD as seconds since 1988
    • rtems_clock_get_ticks_since_boot() - Obtain ticks since boot
    • rtems_clock_get_ticks_per_second() - Obtain ticks per second
  • The score chains code is now available via the documented chains API. Check the C User documentation for details. Implemented by ChrisJohns?.

API Implementation Improvements

  • The region directives were restructured in order to produce simpler assembly code and allow for complete test coverage. Changes included:
    • move the OBJECTS_LOCAL case to the top of the switch statement,
    • use a single exit with one call to _RTEMS_Unlock_allocator,
    • eliminate the fall-through return of RTEMS_INTERNAL_ERROR.
  • Code Space Reduced - Much work has gone on and continues to go on in this area. Some of the improvements are:
    • Configure time control over inlining of some RTEMS internal routines.
    • OBJECT_REMOTE is now defined only in multiprocessor configuration. Having this constant led to the generation of code which could not be reached in single processor configurations.
    • More files with multiple methods were split including the Malloc Family, POSIX timers, and many of the POSIX stubs for routines RTEMS does not support.
    • When a set of initialization tasks or threads is not configured for a particular API, those task/thread creation routines are no longer required in the minimum executable. For examnple, in 4.8 and older, the code to create POSIX initialization threads was always present when POSIX was enabled and thus pthread_create() was included in the executable.
  • Each object class no longer allocates a name table. The name information is always stored directly with the object. This was an improvement in memory usage.

Configuration Changes

  • Addition of configure constants in confdefs.h:
    • CONFIGURE_MALLOC_DIRTY - enable dirtying of memory returned by malloc().
    • CONFIGURE_MALLOC_STATISTICS - enable more detailed statistics gathering.
    • CONFIGURE_ZERO_WORKSPACE_AUTOMATICALLY - By default, RTEMS does not zero the RTEMS Work Space or C Program Heap. The BSP can change the default to zeroing this memory. Further even if the BSP does not require this zeroing, the application can use this constant to specify that it requires it.
    • CONFIGURE_MALLOC_BSP_SUPPORTS_SBRK - defined by BSP which wants to be able to extend the C Program Heap at run-time.
    • CONFIGURE_TASK_STACK_ALLOCATOR and CONFIGURE_TASK_STACK_DEALLOCATOR - allow the application to define their own task stack allocation routines.
    • CONFIGURE_BSP_PREQUISITE_DRIVERS and CONFIGURE_APPLICATION_PREQUISITE_DRIVERS which allows the BSP and application to add drivers to the beginning of the static driver table.
    • CONFIGURE_APPLICATION_EXTRA_DRIVERS which allows the application to add drivers to the end of the static driver table.
  • Addition of network stack configuration parameters to control default buffer sizes for sockets. This addresses the issue that was described in http://www.rtems.org/ml/rtems-users/2004/february/msg00200.html in which the default socket buffer tend to be large in comparison to the amount of memory users configure for mbufs. This leads to a starvation and TCP/IP "freeze". This scenario can be created with just a handful of sockets and fairly light traffic and is worsened by use of UDP sockets which default to larger buffering than TCP sockets. See the Network Supplement for more details on each of the following parameters:
    • sb_efficiency - buffering factor or multiplier
    • udp_tx_buf_size - default size of transmit buffers for UDP sockets
    • udp_rx_buf_size - default size of receive buffers for UDP sockets
    • tcp_tx_buf_size - default size of transmit buffers for TCP sockets
    • tcp_rx_buf_size - default size of receive buffers for TCP sockets
  • Addition of error checks for the following common application configuration mistakes:
    • Configuring POSIX objects or a POSIX initialization thread without POSIX being configured
    • Configuring ITRON objects or a POSIX initialization task without ITRON being configured
    • Add CONFIGURE_APPLICATION_DOES_NOT_NEED_CLOCK_DRIVER configuration parameter so the application has to explicitly configure the Clock driver in or out if the Timer driver is not configured.
    • Configuring a multiprocessor application when RTEMS was configured for multiprocessing.

RTEMS Shell Improvements

The RTEMS Shell has many improvements.

  • Can run scripts from a file.
  • Can configure set of commands available in application.
  • Commands not tied to shell implementation so you can use them in your own "maintenance shell".
  • Many new commands:
    • malloc [info|stats]
    • cpuuse - [-r] print or reset per thread cpu usage
    • stackuse - print per thread stack usage
    • perioduse - [-r] print or reset per period usage
    • wkspace - Report on RTEMS Executive Workspace
    • ifconfig
    • route
    • ls, rm, cp, mv, ln from NetBSD
    • mount

General

  • telnetd overhaul submitted by Till Straumann.
  • Malloc Family refactoring and improvements. Previously, these routines were in only a couple of files. Now they are in multiple files. In addition, the malloc() features that were previously now conditionally compiled can be enabled at run-time. This includes statistics and setting all malloc'ed memory to 0xc5c5c5c5 to ease debugging.
  • DHCP client changes from Arnout Vandecappelle? and Maarten Van Es to allow a DHCP request to be request when the interface detects valid media.
  • M68K CPU Coldfire clean up. The Coldfire is now built based on the instruction set of the Coldfire. The BSP's configuration files now use the -mcpu=* option to select the Coldfire. Support for small memory Coldfire's has been added.
  • Coldfire FPU support has been added. Testing feedback to ChrisJohns? would be welcome.
  • Updated bdbuf file system cache by ChrisJohns?. The new code does not disable pre-emption in the cache code or in the standard drivers in RTEMS such as the ATA driver. The updated code added configuration parameters to confdefs.h to change the number of read ahead buffers and the number of write buffers. The swap out task has a configurable sample period and modified buffers to be written have a configurable hold time before being committed to disk. The code has been tested on a mvf5235 with the RAM, FLASH and NV disks and on the PC with the ATA, RAM and NV disks.
    • <b>Warning</b> There are API changes in libblock. The code has had the interfaces moved to under rtems_*. Driver will need to be updated. Another warning is buffers by default are <b>not continuous</b> by default unless the driver adds a new ioctl call. See the ATA driver in libchip for an example. The buffers each have a block number and that should be used if not requiring continuous buffers.

BSPs and Device Drivers

  • All methods and public variables in the Benchmark Timer Driver used only by the tmtests were renamed to be "benchmark_timer_xxx". The former naming scheme was very inconsistent. In addition, a common method was moved to a shared location.
  • Coldfire Mcf52235 small memory BSP from Matthew Riek
  • Coldfire Mcf5329 - New BSP from Matthew Riek
  • Coldfire genmcf548x - New BSP for MCF548x from Peter Rasmussen of Embedded Brains.
  • powerpc/gen83xx - New BSP for MPC83xx from Thomas Doerfler of Embedded Brains.
  • powerpc/haleakela - New BSP from Michael Hamel
  • powerpc/gen55xx - New BSP for MPC55xx from Sebastian Huber of Embedded Brains.
  • powerpc/tqm8xx - New BSP to support boards based on TQ Component TQM8xx modules
  • powerpc/mvme3100 - New BSP (and 8540 CPU support) from Till Straumann (SLAC)
  • Significant updates to existing BSPs
    • i386/pc386 - Clock driver now supports nanoseconds per tick
    • powerpc/gen5200 - Now supports Freescale IceCube? board variant
    • powerpc/psim - shared memory now works, scripts rewritten, RTC and Flash devices mapped into address space
  • Removal of obsoleted BSPs
    • powerpc/gen405 - remaining powerpc "old" exception BSPs removed
    • powerpc/helas403 - remaining powerpc "old" exception BSPs removed

Test Suites

  • In addition to adding new tests to the psxtests and sptests for new functionality, existing tests were enhanced and new tests added to improve coverage.
  • The Ada tests were updated so that they would compile and run without errors. Tests that were no longer valid using the current binding were removed.
  • The Ada example programs received a considerable amount of cleanup and saw the addition of a few new tests.
    • cpuuse to demonstrate long names for POSIX threads via Ada by JoelSherrill
    • test_exception to demonstrate Ada exceptions by Laurent Guerby?
    • dumpwebpage from web to demonstrate GNAT sockets
    • delay_until from web to demonstrate stability of RTEMS timing
    • pingpong is from web to demonstrate GNAT sockets
    • stack_check to demonstrate GNAT Ada task stack checking is functional by JoelSherrill
    • task_priority to show how Ada priorities map onto SuperCore? priorities by JoelSherrill

RTEMS API Changes

This section covers the API changes between the 4.8 and 4.9 release series which are expected to have an impact on application source code. This section does NOT cover additions to the API.

  • As part of adding the new set of Object Services, some existing undocumented routines that previously existed were renamed as follows:
    • Renamed rtems_get_node() to rtems_object_id_get_node()
    • Renamed rtems_get_api() to rtems_object_id_get_api()
    • Renamed rtems_get_class() to rtems_object_id_get_class()
    • Renamed rtems_get_index() to rtems_object_id_get_index()

Changes Per Point Release

Release 4.9.1 Changes

NOTE: 4.9.1 has not been released yet. This section describes changes which will be in the 4.9.1 release.

Significant changes between 4.9.0 and 4.9.1 include the following:

  • Issues With Problems Report Numbers
    • TBD
  • Issues Without Problems Report Numbers
    • TBD

Release 4.9.0 Changes

This release is the first in the 4.8 series and was cut on 24 September 2008.

BSPs Reported to Work

One of the challenges of RTEMS is that it includes so many Board Support Packages and no single person has access to the breadth of hardware RTEMS supports. We rely on users like you to report that you have or have not successfully run RTEMS 4.9 on a particular board. Please add to this list so we know what works, what doesn't and what BSPs may no longer be in use.

NOTE: A tarball of 4.9 CVS along with some ticker.exe files are located in http://www.rtems.org/ftp/pub/rtems/people/joel/4.9-testing/2008-09-11/. If you spot a BSP that does not have a ticker.exe, please report it on the mailing list. If ticker.exe runs as built, report it here. If it doesn't run correctly, report that and try to fix it -- we need things fixed before 4.9.0.

  • arm/csb337 - JoelSherrill reports ticker runs on SkyEye
  • arm/gba - JoelSherrill reports ticker runs on BoyCott? Advance/SDL simulator
  • arm/gba - AlanCudmore? reports ticker runs on real hardware
  • arm/nds - JoelSherrill reports ticker runs on Desmume simulator
  • arm/nds - Someone reports ticker runs on real Nintendo DS hardware, Please. :)
  • arm/edb7312 - JoelSherrill reports ticker runs on SkyEye
  • arm/rtl22xx - JoelSherrill reports ticker runs on SkyEye
  • arm/smdk2410 - JoelSherrill reports ticker runs on SkyEye
  • m68k/mcf5235 - AlanCudmore? reports ticker runs and CEXP works.
  • m68k/uC5282 - EricNorum? reports EPICS runs
  • powerpc/mvme2100 - EricNorum? reports EPICS runs
  • powerpc/mvme3100 - EricNorum? reports EPICS runs
  • mips/jmr3904 - JoelSherrill report ticker runs on simulator
  • powerpc/gen83xx - ThomasDoerfler? report ticker runs on hsc_cm01, mpc8349eamds and mpc8313erdb
  • powerpc/hsc_cm01 - ThomasDoerfler? report ticker runs
  • powerpc/icecube - JoelSherrill report ticker runs on Freescale MPC5200 Eval baord and Embedded Planets EP5200
  • powerpc/mpc8313erdb - JoelSherrill report ticker runs on Freescale MPC8313E RDB
  • powerpc/mpc8349eamds - ThomasDoerfler? report ticker runs Freescale MPC8349E MDS
  • powerpc/psim - JoelSherrill report ticker runs on psim
  • powerpc/virtex - BobGrimes? reports: My application runs (uses serial, Ethernet, clock, SPI, other stuff)
  • i386/pc386 - EricNorum? reports EPICS runs
  • sparc/erc32 - JoelSherrill report ticker runs on tsim
  • sparc/leon2 - JoelSherrill report ticker runs on tsim
  • sparc/leon3 - JoelSherrill report ticker runs on tsim
  • sparc/sis - JoelSherrill report ticker runs on sis