Changeset cf65c408 in rtems


Ignore:
Timestamp:
Jun 27, 1998, 8:01:28 PM (22 years ago)
Author:
Joel Sherrill <joel.sherrill@…>
Branches:
4.10, 4.11, 4.8, 4.9, master
Children:
dc95ee8d
Parents:
5d18fb0
Message:

Bare BSP patch from Chris Johns <cjohns@…>. He also
sent an example bare bsp but we have not decided how to integrate it yet.

Files:
2 added
3 edited

Legend:

Unmodified
Added
Removed
  • README.configure

    r5d18fb0 rcf65c408  
    2525        --disable-ka9q
    2626        --enable-cxx
     27        --enable-bare-cpu-model=<MODEL>
     28        --enable-bare-cpu-cflags=<FLAGS>
    2729        --enable-gcc28               (also use enable-libcdir when disabled)
    2830        --enable-gmake-print-directory
     
    5860egcs source tree, testgcc snapshots, or gcc 2.8.0 or newer.
    5961
    60 By default, all bsps for a target are built. There are  two ways of
    61 changing this:
     62By default, all bsps for a target are built. The bare BSP is not built
     63unless directlty specified. There are  two ways of changing this:
    6264
    6365  + use the --enable-rtemsbsp otion which will set the specified
     
    8183        powerpc-rtems
    8284        sparc-rtems
     85        bare                    see notes
    8386       
    8487The cross-compiler is set to $(target)-gcc by default. This can be
     
    143146      cp libc_p.a INSTALL_POINT/lib/gcc-lib/i386-go32-rtems/2.7.2/libcgo32_p.a
    144147
     148bare:
     149
     150  1.  See the README in the bare bsp source directory. This should
     151      contain all info you need.
     152  2.  The bare bsp source contains a script to show how to build it.
     153  3.  The configure flags must be used to get the bare bsp to work.
     154      The --enable-bare-cpu-model and --enable-bare-cpu-cflags are the
     155      only pieces of information. The module is usually a gcc module
     156      such as m68302 or mcpu32. The flags are passed directly to gcc.
     157      Use "" if more than one option is specified.
    145158
    1461593. To use the installed RTEMS library
     
    178191powerpc         : papyrus
    179192sparc           : erc32
     193any             : bare
    180194
    1811955. Makefile structure
  • c/PROBLEMS

    r5d18fb0 rcf65c408  
    5656     --enable-gcc28 are given.
    5757   + force --enable-libcdir when --disable-gcc28 is given
     58   + Check for bare bsp getting CPU model set.
    5859
  • c/src/lib/libbsp/bare/README

    r5d18fb0 rcf65c408  
    1414
    1515#
     16# Overview
     17# ~~~~~~~~
    1618# This board support package is not a board support package at all, but
    1719# a means to build the RTEMS kernel without using a specific BSP.
     
    3840# I fit all the above.
    3941#
     42# Issues
     43# ~~~~~~
     44# I do not consider the bare BSP as a starting point for RTEMS. The
     45# BSP code integrated into the RTEMS build tree has the advantage of
     46# building all the test and sample code. The sample and test code is
     47# important for validatation of your tools, and getting your BSP
     48# working correctly.
     49#
     50# Once you gain experience with RTEM and your application matures the
     51# need to break the BSP code out from the kernel becomes important. It
     52# is at this point in time that the bare BSP becomes useful.
     53#
     54# Once free you are able to upgrade without the worry of makefile or
     55# build tree changes which can break your BSP.
     56#
     57# How To Configure
     58# ~~~~~~~~~~~~~~~~
     59# RTEMS requires you to select a BSP inorder to build the kernel.
     60# If you take a close look at a BSP which is closest to your
     61# needs you will find somewhere the CPU model and CPU compile
     62# flags are specified. This is the only piece of information
     63# required by the kernel inorder for it to build.
     64#
     65# This highlights the clean design of the kernel and its
     66# independence from the particulars of target hardware.
     67#
     68# The CPU model is the RTEMS model and usually tries to match with
     69# the GCC model. There are variations on some processors. If you are
     70# unsure please ask on the RTEMS list. Someone will know (I hope).
     71#
     72# The CPU flags allow you to select specific operating modes for
     73# GCC. For example the PowerPC has specific flags to control various
     74# cache resouces. Another example is the 68000 family of embedded
     75# processor do not have FPU hardware and require software emulation.
     76#
     77# An example configuration command line is:
     78#
     79#  ../rtems-4.0/configure  --target=m68k-rtems \
     80#                          --prefix=/ods/egcs/test \
     81#                          --enable-cxx \
     82#                          --enable-gmake-print-directory \
     83#                          --disable-tests \
     84#                          --disable-posix \
     85#                          --enable-ka9q \
     86#                          --enable-bare-cpu-cflags=-mcpu32 \
     87#                          --enable-bare-cpu-model=mcpu32 \
     88#                          --enable-rtemsbsp=bare
     89#
     90# Building RTEMS
     91# ~~~~~~~~~~~~~~
     92# You are required to do nothing special here. Just follow the documented
     93# steps. The samples are built but no linking occurs. The link command
     94# is stubbed out to produce a Unix shell script.
     95#
     96# After installation you will find a directory called 'bare'. The nature
     97# of the RTEMS build system means the bare BSP will only install into the
     98# the bare directory under the specifed configuration prefix.
     99#
     100# I therefore suggest you move the directory to another name. This allows
     101# you to make and install another bare BSP for a different variant of
     102# CPU without over writing the last installed variant.
     103#
     104# I have provided a script file I use to configure and build RTEMS
     105# from the arcihve. Take a copy and use it if you find it useful.
     106#
     107# Creating an Application.
     108# ~~~~~~~~~~~~~~~~~~~~~~~~
     109# This is something which is usually specific to your local environment.
     110# The bare BSP does not lock you into any specific makefile or build
     111# system. A couple of suggestions are:
     112#
     113#   o Get the sample bare BSP application, or
     114#   o Watch RTEMS build a BSP which is closest to yours and copy
     115#     the command lines used.
     116#
    40117
    41 BSP NAME:           bare
    42 BOARD:              not applicable
    43 BUS:                not applicable
    44 CPU FAMILY:         all
    45 COPROCESSORS:       not applicable
    46 MODE:               not applicable
    47 
    48 DEBUG MONITOR:      not applicable
    49 
    50 PERIPHERALS
    51 ===========
    52 not applicable
    53 
    54 DRIVER INFORMATION
    55 ==================
    56 not applicable
    57 
    58 STDIO
    59 =====
    60 not applicable
    61 
    62 NOTES
    63 =====
    64 
    65 Board description
    66 -----------------
    67 not applicable
    68 
    69 Host System
    70 -----------
    71 Linux (RedHat 4.0/5.0)
    72 egcs-1.0.2
    73 binutils-2.8.1, with rtems patches
    74 newlib-1.8.0, with rtems patches
    75 
    76 Verification
    77 -------------------------------
    78 Single processor tests:  not applicable
    79 Multi-processort tests:  not applicable
    80 Timing tests:
    81         not applicable
    82 
    83 Porting
    84 -------
    85         not applicable
Note: See TracChangeset for help on using the changeset viewer.