Key timing use cases for ECU software development

Symtavision has identified key timing use cases for a systematic, timing-enriched ECU development process, which can save development time and unit cost as well as increasing the realisation probability and maturity level of ECU development projects.
Systematic ECU development starts with specifying the function architecture and defining the requirements of the desired functions. From this, reasonable software architectures and schedules are developed, followed by the actual software development with integration and test at every release. The entire process is typically supported by appropriate assessments and executed through deliveries according to a negotiated timeline between the OEM and the supplier or ECU development team.
The use cases and corresponding systems represent distinct steps to enrich this established process towards true timing-aware ECU development. Each such extension adds value to the existing process and can be deployed independently from other steps. Altogether, these Symtavision systems help in creating a true timing-enriched ECU software development process across all phases of the automotive ECU design, development and integration lifecycle. They cover from late to early phases:
- Compare and verify by ECU timing assessment;
- Optimise code through CPU load and execution time optimisation;
- Optimise architecture by performing schedule optimisation and CPU load forecast;
- Explore architecture by executing software and scheduling architecture design;
- Create reference model by capturing ECU timing requirements; and
- Migrate to multicore ECUs.
“With the complexity increase in recent years, more and more ECU projects suffer from timing issues,” said Kai Richter, CTO of Symtavision. “Therefore, the complete ECU development cycle should be supported by a continuous timing assessment process that must be easy to deploy and deliver clear benefit for our customers. From our experience in many mass-production projects, we have identified a few primary timing analysis use cases that virtually every ECU development project has to address sooner or later. We have developed effective solutions for each of them, optimally supported by the modelling, analysis and optimisation capabilities of our Symta/S and TraceAnalyzer tools. These also consider the changing collaboration models between OEMs and suppliers. At the heart of the process is an agreed timing reference model of the system, which both the OEM and the suppliers can refer to.”
A more detailed description of the automotive ECU use cases for Symta/S and TraceAnalyzer follows:
- Compare and Verify: As the complexity of ECU software continues to increase, so will timing problems, such as CPU overload or missed task deadlines, and the resultant functional failures. To determine and verify key timing properties, such as CPU load, task execution times, response times and so on, Symtavision offers timing analysis based on ECU traces. Using this trace data, a model can be constructed to perform a worst-case analysis that increases corner-case coverage to uncover possible timing errors.
- Optimise code: CPU overload is a common source of ECU malfunction. The TraceAnalyzer tool identifies load hot-spots to pinpoint the areas for optimisation. For these, Symtavision provides static code analysis tools that point directly to the lines of code where optimisation will be most effective in helping reduce CPU load.
- Optimise Schedule: Schedule optimisation is a key ingredient in increasing CPU efficiency and reducing timing issues such as CPU overload or missed deadlines. Symtavision supports this through a model-based scheduling simulation and analysis, which pre-verifies new scheduling to find the optimum scheduling.
- Explore architecture: The software architecture in terms of the structure and partitioning of software components, cycle times, execution order, communications and so on determines the efficiency, robustness, and extensibility of an ECU. Model-based timing analysis enables designers to evaluate and optimise their software architecture efficiently.
- Create Model: The overall development process starts with specifying the function architecture and defining the requirements on the desired functions. These are then mapped to the software architecture and enriched by timing information such as runtime estimates of functions and software components, end-to-end functional deadlines, and cycle time and throughput requirements. Modelling capabilities with suitable views for OEMs and ECU suppliers, including mapping one view to the other, are supported by reasonable exchange formats.
- Migration to multicore: The efficient and correct use of multicore ECUs is a major challenge for many new ECU designs. Symtavision’s tools and experience can help in the successful migration to multicore, especially by optimising the partitioning of software, data mapping, managing communications overhead and scheduling design.
The process extensions, use cases and Symtavision Symta/S and TraceAnalyzer will form part of the interactive workshop discussions at Symtavision’s ninth annual customer conference to be held in Braunschweig from 30 September to 1 October 2015.
