Applying Time-Triggered Architectures in Mainstream Embedded Systems
Workshop Overview In a time-triggered embedded system, we have one (and only one) interrupt enabled. This interrupt is usually linked to a timer, which will generate “ticks”: these ticks will, in turn, drive an appropriate (often very simple) operating system.
Time-triggered architectures are widely used in safety-related systems (for example in aerospace or medical sectors) because they are known to provide highly predictable behaviour, which in turn reduces testing, maintenance and (where relevant) certification costs.
During this workshop it will be argued that TT architectures can be (and should be) used more widely. Numerous examples of the use of TT architectures will be presented, and you will have a chance to try out various TT system designs for yourself (and compare them with “event triggered” alternatives).
Workshop Objectives
To demonstrate how time-triggered systems can be created easily and quickly
To compare time-triggered (TT) and event triggered (ET) solutions
To illustrate how use of timing analysis and TT systems can reduce testing effort and – therefore – reduce time-to-market
Delegates will learn
How to create embedded systems with a time-triggered architecture.
How to adapt existing designs (based on event-triggered architectures) into a TT format
How to reduce testing times using TT architectures
How to work with leading TT development tools
Who Should Attend
Software engineers wishing to shorten the development time for their next application.
Hardware engineers that need to work with software engineers in the creation of reliable embedded systems.
Project managers who wish to understand design and tool options for modern embedded systems.
Pre-Requisites
Some experience with embedded systems
Some knowledge of the C programming language
Duration:
3 hrs (with coffee break)
Seminar and Hand-on session
This workshop will begin with a short seminar (around 30 minutes) which will introduce key TT concepts.
We will then move in to a “hands on” session, where you will have a chance to try out some TT architectures and development tools for yourself.
What this workshop won’t do
Developing embedded systems is not easy, and there are no “silver bullets”.
During this workshop, we won’t try to argue that a TT approach is a perfect match for all embedded systems (it isn’t). However, the workshop will conclude by suggesting that – as you start your next project – you should ask yourself: “Should we use a TT architecture this time?”
By the end of this workshop, we think you may be surprised how often the answer is: “Yes”.
(This workshop is £95+VAT per delegate - payable in advance of the event.)
Dr Michael J. Pont is CEO of TTE Systems Ltd and Professor of Embedded Systems Engineering at the University of Leicester. Since the mid 1990s, Michael has worked with an internationally-recognised research team to develop tools and techniques which support the rapid development of reliable embedded systems through the use of time-triggered architectures. This research work has resulted in a number of patent applications and the creation of the RapidiTTy® tool family, which is now being further developed and sold by TTE Systems Ltd. Michael is author or co-author of more than 100 technical papers, and is the author of three books (including “Patterns for Time-Triggered Embedded Systems” and “Embedded C”).
Dr Devaraj Ayavoo received the B.Eng. and PhD degrees from University of Leicester, UK, in 2000 and 2006 respectively. Having worked previously at Altera Corporations, Malaysia, Devaraj joined TTE Systems Ltd in 2006: he is now Technical Manager with the company and is responsible for the development of the RapidiTTy® family of software development tools.
Time-Triggered Embedded System are known to provide highly predictable behaviour, which in turn reduces testing, maintenance and (where relevant) certification costs.
In a time-triggered embedded system, we have one (and only one) interrupt enabled. This interrupt is usually linked to a timer, which will generate “ticks”: these ticks will, in turn, drive an appropriate (often very simple) operating system.
