Minimizing the Impact of System Latencies in Software-Defined Vehicles.
How the automotive industry is changing, and why software timing and latency are growing in importance.
Software has taken over from mechanics in today’s vehicles, defining everything from the performance of cockpit functions to its motive traction. At the same time, the automotive industry is transitioning to new E/E architectures, which reduce the number of electronic control units used.
As software is reused, it is often deployed across multiple processing platforms, altering its functionality within the context of these complex systems. This results in changes in timing and latency that lead to issues that were not previously present.
This means that software development teams need to be more aware of timing and latencies, while also adding tests that ensure any changes made don’t impact these carefully balanced systems.
Our white paper introduces these issues and provides a methodology and tools for resolving them, covering:
Our white paper introduces these issues and provides a methodology and tools for resolving them, covering:
-
Automotive is changing, and software timing is growing in importance
-
Managing the move to zonal architectures
-
Making event chain latencies controllable
-
Event chains for future-proofing the logical architecture
-
Leveraging logical event chains to make design decisions
-
Testing fulfillment of timing requirements in hardware using trace evaluation
-
Guaranteeing functionality and timing through all project phases
-
Summary