Changeset cf65c408 in rtems for c/src/lib/libbsp/bare
- Timestamp:
- 06/27/98 20:01:28 (26 years ago)
- Branches:
- 4.10, 4.11, 4.8, 4.9, 5, master
- Children:
- dc95ee8d
- Parents:
- 5d18fb0
- Location:
- c/src/lib/libbsp/bare
- Files:
-
- 2 added
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
c/src/lib/libbsp/bare/README
r5d18fb0 rcf65c408 14 14 15 15 # 16 # Overview 17 # ~~~~~~~~ 16 18 # This board support package is not a board support package at all, but 17 19 # a means to build the RTEMS kernel without using a specific BSP. … … 38 40 # I fit all the above. 39 41 # 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 # 40 117 41 BSP NAME: bare42 BOARD: not applicable43 BUS: not applicable44 CPU FAMILY: all45 COPROCESSORS: not applicable46 MODE: not applicable47 48 DEBUG MONITOR: not applicable49 50 PERIPHERALS51 ===========52 not applicable53 54 DRIVER INFORMATION55 ==================56 not applicable57 58 STDIO59 =====60 not applicable61 62 NOTES63 =====64 65 Board description66 -----------------67 not applicable68 69 Host System70 -----------71 Linux (RedHat 4.0/5.0)72 egcs-1.0.273 binutils-2.8.1, with rtems patches74 newlib-1.8.0, with rtems patches75 76 Verification77 -------------------------------78 Single processor tests: not applicable79 Multi-processort tests: not applicable80 Timing tests:81 not applicable82 83 Porting84 -------85 not applicable
Note: See TracChangeset
for help on using the changeset viewer.