Tools and Benchmarks for Real-Time Systems

An updated version of the 2017 challenge can be found here: https://www.ecrts.org/forum/viewtopic.p ... 421789ceeb

Thanks again to Reinhard von Hanxleden for the great keynote. The slides are now available .

One interesting point from my side would be the following: For some kind of functionalities it might be of great use to "introspect" what is going on on scheduling level. For instance, in model predictive control or when using so-called anytime algorithms, one might want to decide dynamically if ano...

I would like to discuss the following topics at WATERS: - Would it make sense to include a physical notion of time in synchronous languages for real-time applications (e.g. to represent deadlines)? How could that be realized and what would be the semantics? - How can synchronous programs be executed...

Authors: Youcheng Sun, Étienne André and Giuseppe Lipari

Authors: Jorge Luis Martinez, Ignacio Sañudo, Paolo Burgio and Marko Bertogna

Authors: Kai-Björn Gemlau, Johannes Schlatow, Mischa Möstl and Rolf Ernst

Authors: Juan M Rivas, J. Javier Gutiérrez, Julio Medina and Michael González Harbour

Authors: Frédéric Boniol, Julien Forget and Claire Pagetti

Authors: Alessandro Biondi, Paolo Pazzaglia, Alessio Balsini and Marco Di Natale

Hi Julio, very good question ;-) In general not all order relations between runnables are of importance (even if they exchange data). What counts are "functional sensitive" cause-effect chains, e.g. chains that contribute to controlling physical processes with high dynamics. In a perfect world, all ...

The attached archive contains some screenshot explaining how to work with the model using the above mentioned tool chains.

We are happy to announce the industrial challenge of WATERS 2017 proposed by Arne Hamann, Simon Kramer, Michael Pressler, Dakshina Dasari, Falk Wurst, and Dirk Ziegenbein from Robert Bosch GmbH. Details about the intention of the challenge and a high level description can be found here: https://wate...

The complex dynamic behaviour of automotive software systems, in particular engine management, in combination with emerging multi-core execution platforms, significantly increased the problem space for timing analysis methods. As a result, the risk of divergence between academic research and industr...

Thanks Arne, I think I understand the problem enough to tackle it. When I analyzed the worst case end-to-end latencies of tasks and chains, too many tasks, 6 out of 21 tasks from my result, violate deadlines even without memory access delay. Chains that have runnables in unschedulable tasks are of ...

Hi, thanks arne for the previous answers. I have another questions on the memory access model: 1. What happens if preemptive task with higher priority is requested during a resource access of lower priority task? Is the preemptive task blocked until the resource access of lower priority task finish...

Thanks for the response, I got some new questions: - With regard to challenge 1: "ignoring memory accesses" means that the fetching of data in the reading/write phases takes "0" time? - With regard to challenge 2 when read/write time is not neglected: what happens if a task/runnable/core reads the ...

And sorry that I did not reply earlier to the forum post ...that one slipped through :/

Some more questions I received via Email: 1- Are the R/W accesses protected by some kind of semaphore or mutex? If so, what is the shared resource protocol (if any) used to arbitrate the access to shared resources (SRP, priority ceiling...)? R/W accesses are arbitrated by the memory in a FIFO manner...

Hi all, I got some new questions: -- Q: We are getting interested in the Waters challenge, but we cannot figure out the cooperative scheduling among the tasks that are tagged as such, nor what is the meaning of end-to-end latency in these cases (what is the definition, given that it is a cooperation...

Hi all, I got the following question via Email. 1- We understand that tasks are preemptible, but can the runnables be preempted? Generally we distinguish preemptive and cooperative tasks. Higher priority preemptive task can preempt lower priority tasks (of any type) at any point in time, also runnab...

Dear Paolo, the AMALTHEA model is not "executable" using the AMALTHEA tool chain. Basically, the AMALTHEA tool only helps you to access the model data. We use tools like SymTA/S and Timing Architects to get the numbers for the end-to-end latencies. And during the workshop we would like to compare th...

We corrected the challenge model. You can find the updated version here: http://ecrts.eit.uni-kl.de/forum/viewto ... 2&p=96#p96

We corrected some errors in the previous challenge model. We validated the attached updated version, and everything should work fine now.

Dear Juan, your interpretation is correct. We just checked the model, and found out that there was a mistake on our side. In principle, it is plausible that the system is overloaded if all worst-cases are considered simultaneously. However, in this case the numbers are far too high, such that alread...

Yes, as you mentioned, the file browser is the source and the empty project is the target of the drag and drop action ;-)

Hi Sophie,

the simplest way is the following:

1) Create an empty project File->New->Project then General -> Project
2) Drag and Drop the file GeneratedModel.amxml into the project and choose 'copy file'

I hope that helps,
Arne

Dear all, we are finally able to submit the promised Amalthea model for the challenge. Sorry for the delay. FMTV_Challenge_2016_Bosch_Engine_Control_Model.zip The model can be inspected and processed using the Amalthea tool chain that can be downloaded here (version 1.1.1): http://www.amalthea-proje...