Skip to main content

Posts

Showing posts from October, 2016

[RTEMS] Overrun Handling for Mixed-Criticality support in RTEMS

I will be on Workshop of Mixed-Criticality systems in Porto, Portugal on 29th of Nov.. https://gsathish.github.io/wmc2016/program/ There is a presentation about how overrun handling can be done in RTEMS for further supporting mixed-criticality systems with RTEMS. The corresponding paper can be found here: http://ls12-www.cs.tu-dortmund.de/daes/media/documents/publi cations/downloads/2016-wmc.pdf

[RTEMS] Qemu SMP testing and building configuration

Suddenly, I move my interest to multi-core systems scheduling. (The setting for latest version RTEMS is here ) This article only contents the configuration you can use to build up the RTEMS with BSP realview_pbx_a9_qemu_smp , which delivered the kernel with SMP support and the official SMP example in RTEMS ver 4.11. (Suppose you have rtems cross compiler in your host with ver 4.11) To have a full test-suites for the smptest or sptest/mptest, the option of --enable-tests should be "yes". The BSP for SMP should be realview_pbx_a9_qemu_smp bsp rather than real-view_pbx_a9_qemu. I suppose you can follow the tutorial or instructions in Quick Start of RTEMS's documents and build up the toolchain of arm-rtems4.11. After you extract the source code and create a build folder: In the source code folder, you type: ./bootstrap In the build folder, you configure the installation: ../rtems/configure --target=arm-rtems4.11 --enable-rtemsbsp=realview_pbx_a9_qemu_smp --ena...

[RTEMS/RSB] rtems-source-builder: The installation of cross toolchains for gdb 7.9 to 7.11

This is about the error in RSB for RTEMS 4.12 on Ubuntu 14.04 LTS. Most likely, we can directly follow the tutorial here: https://devel.rtems.org/wiki/Developer/Tools/RSB Or deeply refer to the document https://docs.rtems.org/rsb/#_why_build_from_source Please note that the version of this document is still for 4.11. You have to change it accordingly to 4.12. If there is any one who has this error message before (for gdb): checking whether to use python... yes checking for python... /usr/local/bin/python checking for python2.7... no configure: error: python is missing or unusable However, you think you definitely have python2.7 in your system, either you used sudo apt-get install or built the source code by yourself. By referring to http://askubuntu.com/questions/513626/cannot-compile-gdb7-8-with-python-support , we can see that the automatic configuration will check if the environment of your host can compile that simple C program. Therefore, I focus on the problem that ...