Commit 7d83c6c7 authored by Thanassis Tsiodras's avatar Thanassis Tsiodras

RTEMS is at 4.12 now

parent b5bc5de5
...@@ -11,7 +11,7 @@ source code demonstrates how to: ...@@ -11,7 +11,7 @@ source code demonstrates how to:
Building RTEMS via the RSB Building RTEMS via the RSB
-------------------------- --------------------------
The contrib folder includes a script that you can use to compile RTEMS4.11 The contrib folder includes a script that you can use to compile RTEMS4.12
with the Leon2 and Leon3 BSPs from the OAR repository. Note that with the Leon2 and Leon3 BSPs from the OAR repository. Note that
[as discussed in the RTEMS mailing list](https://lists.rtems.org/pipermail/users/2016-February/029782.html), [as discussed in the RTEMS mailing list](https://lists.rtems.org/pipermail/users/2016-February/029782.html),
you will need to compile your BSP for native or emulated FPU, based you will need to compile your BSP for native or emulated FPU, based
...@@ -90,7 +90,7 @@ To use emulation (default, if `FPU` option is not provided), pass `FPU=0`: ...@@ -90,7 +90,7 @@ To use emulation (default, if `FPU` option is not provided), pass `FPU=0`:
The `FPU` and `CFG` options are completely independent ; you can e.g. The `FPU` and `CFG` options are completely independent ; you can e.g.
compile a debug version that uses native FPU, and a release one that uses compile a debug version that uses native FPU, and a release one that uses
emulation. Just keep in mind that currently, 4.11 emulation. Just keep in mind that currently, 4.12
[does not allow you to use the same BSP](https://lists.rtems.org/pipermail/users/2016-February/029782.html), [does not allow you to use the same BSP](https://lists.rtems.org/pipermail/users/2016-February/029782.html),
for both native and emulated FPU usage ; you'll have to build separate for both native and emulated FPU usage ; you'll have to build separate
BSPs by tweaking the `leon2.cfg`/`leon3.cfg` files when you build RTEMS. BSPs by tweaking the `leon2.cfg`/`leon3.cfg` files when you build RTEMS.
...@@ -118,23 +118,23 @@ If you want to see the complete commands used, pass `V=1`: ...@@ -118,23 +118,23 @@ If you want to see the complete commands used, pass `V=1`:
$ touch src/task1.c $ touch src/task1.c
$ make CFG=debug FPU=0 V=1 $ make CFG=debug FPU=0 V=1
/opt/rtems-4.11-2016.04.01.NONFPU/bin/sparc-rtems4.11-gcc -c \ /opt/rtems-4.12-2016.06.13.NONFPU/bin/sparc-rtems4.12-gcc -c \
-B/opt/rtems-4.11-2016.04.01.NONFPU/sparc-rtems4.11/leon3/lib \ -B/opt/rtems-4.12-2016.06.13.NONFPU/sparc-rtems4.12/leon3/lib \
-specs bsp_specs -qrtems -mcpu=cypress -DBSP_leon3 -ffunction-sections \ -specs bsp_specs -qrtems -mcpu=cypress -DBSP_leon3 -ffunction-sections \
-fdata-sections -Wall -Wmissing-prototypes \ -fdata-sections -Wall -Wmissing-prototypes \
-Wimplicit-function-declaration -Wstrict-prototypes -Wnested-externs \ -Wimplicit-function-declaration -Wstrict-prototypes -Wnested-externs \
-g -Wall -D_DEBUG -I src -msoft-float \ -g -Wall -D_DEBUG -I src -msoft-float \
-o objs.debug.NONFPU.leon3/task1.o src/task1.c -o objs.debug.NONFPU.leon3/task1.o src/task1.c
/opt/rtems-4.11-2016.04.01.NONFPU/bin/sparc-rtems4.11-gcc -g \ /opt/rtems-4.12-2016.06.13.NONFPU/bin/sparc-rtems4.12-gcc -g \
-o bin.debug.NONFPU.leon3/fputest objs.debug.NONFPU.leon3/init.o \ -o bin.debug.NONFPU.leon3/fputest objs.debug.NONFPU.leon3/init.o \
objs.debug.NONFPU.leon3/task1.o objs.debug.NONFPU.leon3/task2.o \ objs.debug.NONFPU.leon3/task1.o objs.debug.NONFPU.leon3/task2.o \
objs.debug.NONFPU.leon3/common.o -msoft-float \ objs.debug.NONFPU.leon3/common.o -msoft-float \
-B/opt/rtems-4.11-2016.04.01.NONFPU/sparc-rtems4.11/leon3/lib \ -B/opt/rtems-4.12-2016.06.13.NONFPU/sparc-rtems4.12/leon3/lib \
-specs bsp_specs -qrtems -mcpu=cypress -DBSP_leon3 \ -specs bsp_specs -qrtems -mcpu=cypress -DBSP_leon3 \
-ffunction-sections -fdata-sections -Wall -Wmissing-prototypes \ -ffunction-sections -fdata-sections -Wall -Wmissing-prototypes \
-Wimplicit-function-declaration -Wstrict-prototypes \ -Wimplicit-function-declaration -Wstrict-prototypes \
-Wnested-externs -Wl,--gc-sections -Wnested-externs -Wl,--gc-sections
Built with RTEMS at /opt/rtems-4.11-2016.04.01.NONFPU/sparc-rtems4.11/leon3/lib for leon3. Built with RTEMS at /opt/rtems-4.12-2016.06.13.NONFPU/sparc-rtems4.12/leon3/lib for leon3.
# Support # Support
......
#!/bin/bash #!/bin/bash
# #
# This script builds the RTEMS4.11/Sparc cross-compiler # This script builds the RTEMS/SPARC cross-compiler
# and Leon2/3 BSPs. # and leon2/leon3/ngmp BSPs.
# #
# To have a reproducible setup, we suggest you execute # To have a reproducible setup, it would be prudent if you
# this script under a Debian jessie chroot, bootstrapped # executed this script under a Debian jessie chroot,
# via the following: # bootstrapped via the following:
# #
# mkdir /opt/jessie-chroot # mkdir /opt/jessie-chroot
# debootstrap jessie /opt/jessie-chroot # debootstrap jessie /opt/jessie-chroot
...@@ -59,7 +59,8 @@ BUILD_LOG=/root/rtems.build.logs/${DATE}.log ...@@ -59,7 +59,8 @@ BUILD_LOG=/root/rtems.build.logs/${DATE}.log
# If your network is like the one in ESA/ESTEC and this is forbidden, # If your network is like the one in ESA/ESTEC and this is forbidden,
# you'll have to fetch these tarballs and hardlink to them each time # you'll have to fetch these tarballs and hardlink to them each time
# (so no FTP action is triggered by the RTEMS RSB builder). # (so no FTP action is triggered by the RTEMS RSB builder).
# This is how I do it - adapt according to your needs: #
# This is one way to do it - adapt it according to your needs:
# #
# cd rtems # cd rtems
# [ ! -d sources ] && { # [ ! -d sources ] && {
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment