Altreonic is now member of RTCA, Radio Technical Commission for Aeronautics
RTCA, Inc. is a private, not-for-profit corporation that develops consensus-based recommendations regarding communications, navigation, surveillance, and air traffic management (CNS/ATM) system issues. RTCA functions as a Federal Advisory Committee.
Membership of RTCA will help us supporting the avionics industry better.
A single approach for many-multi-parallel-distributed systems
After 3 successful sessions at IMEC in Leuven, we are planning to repeat the workshop elsewhere. We are looking for hosting partners across Europe. Find a place, agree on a date, register 20 registrants and we come to your place. Contact us at info. request (at=@) altreonic. com
This workshop aims at debunking the myth that writing concurrent programs for many-core, multi-core, parallel and distributed (embedded) systems is difficult. On the contrary, a single approach with a solid formal basis can handle them all, including reusing existing sequential code.
This survey is part of a R&D project. This project is looking into how to improve on the certification costs for the industry in the context of adhering to recognised or required standards.
This survey is the first in a series of two or more surveys. Your input is requested to establish a baseline to guide the project. Follow-up surveys will then go deeper and analyse the findings. Your help in responding is highly appreciated. You can subscribe for a summary report at the end of the survey.
Your contact details are only requested for follow-up and statistical purposes and will not be passed on to third parties. Many thanks for your cooperation.
After filling in the questionnaire don't forget to SUBMIT. Only one survey can be answered per respondent.
This booklet is the first of the Gödel Series, with the subtitle "Systems Engineering for Smarties". The aim of this series is to explain in a accessible way some important aspects of trustworthy systems engineering with each booklet covering a specific domain.
The first publication is entitled "Trustworthy Systems Engineering with GoedelWorks" and explains the high level framework Altreonic applies to the domain of systems engineering. It discusses a generic model that applies to any process and project development. It explains the 16 necessary but sufficient concepts. This model was applied to the import of the project flow of the ASIL (Automotive Safety Integrity Level) project of Flanders's Drive whereby a common process was developed based on the IEC-61508, IEC-62061, ISO-DIS-26262, ISO-13849, ISO-DIS-25119 and ISO-15998 safety standards covering the automotive on-highway, off-highway and machinery domain. Download for free from the download section.
OPENCOSS (Open Platform for EvolutioNary Certification of Safety-critical Systems) is a recently approved R&D project. The project 17 partners aim at a common certification framework that spans different vertical markets for the railway, avionics and automotive industry, and establish a common safety certification infrastructure. The strategy is to focus on a compositional and evolutionary certification approach with the capability to reuse safety arguments, safety evidence, and contextual information about system components, in a way that makes certification more cost-effective, precise, and scalable. OPENCOSS will define a common certification language by unifying the requirements and terminology of different industries and building a common approach to certification activities.
OPENCOSS aims at developing a tool infrastructure for managing certification information and performing safety assurance activities. Within this infrastructure, systematic and auditable processes will be developed to reduce uncertainty and (re)certification costs. To have long-lasting industrial impact, the project will pursue standardisation of the conceptual framework and the tool infrastructure resulting from the project.
More information will be made available at a later stage.
While published by a scientific publisher, this book is not a purely scientific one. But it shows how the state of the art in science can be applied to a real industrial development with great benefit. It documents (incompletely but sufficiently) the journey of the OpenComRTOS project. This project started out with the goal to see how we could apply formal methods to embedded software development. And because we had a background in a distributed Real-Time Operating System, we decided to use the design from scratch as a target. Not a trivial one as it covers concurrency, protocols, local as well distributed state machines as well as boundary conditions of efficiency, hard real-time capability, scalability and other non-functional requirements. An RTOS is however a suitable and grateful target as it is the key layer between hardware and application software.
Altreonic is now announcing a port of OpenComRTOS to the high performance C66xx DSP of Texas Instruments and integrating it in the OpenComRTOS Designer environment.
Full OpenComRTOS fits comfortably in L1 cache
A full kernel with all services only requires between 5.1 to 7.7 KBytes for program memory depending on the compile time options and services used. This was measured by compiling a minimal application for a C6670 target with program placement in L2 SRAM comparing the results using a mapfile analyser. Nevertheless, this is still a complete priority based preemptive scheduling RTOS with support for distributed priority inheritance. Besides task scheduling, services provided are: events, semaphores, resources, port hubs, fifos, packet and memory pools in blocking, non blocking, blocking with timeout and asynchronous semantics. OpenComRTOS transparently supports single as well as large multiprocessor systems.
OpenComRTOS is the most efficient and easy-to-use solution for high performance embedded parallel computing. Porting to the TI DSP has been swift and efficient.
Altreonic is now announcing a port of OpenComRTOS to the high performance PowerPC processors of Freescale and integrating it in the OpenComRTOS Designer environment.
A full kernel with all services only requires between 7.1 to 9.8 KBytes for program memory and less than 6 KBytes of data memory, depending on the compile time options and services used. This was measured by compiling a minimal application for an e600 target with Altivec support and comparing the results using a mapfile analyser. Nevertheless, this is still a complete priority based preemptive scheduling RTOS with support for distributed priority inheritance.