Verification of key timing use cases for ECU software development
Systematic ECU development, the company says, 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 Symtavision solutions 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 solutions 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 – perform Schedule Optimisation and CPU Load Forecast
– Explore Architecture – execute Software and Scheduling Architecture Design
– Create Reference Model – by Capturing ECU Timing Requirements
– And as a hot architectural ECU topic: Migration to Multicore ECUs.
“With the complexity increase in recent years, more and more ECU projects suffer from timing issues. 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,” asserts Dr. Kai Richter, CTO of Symtavision. “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 solutions 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.”
Symtavision; www.symtavision.com
If you enjoyed this article, you will like the following ones: don't miss them by subscribing to :
