Inside scoop: Top critical mistakes in developing automotive software functions on microcontroller

• Gain deep insights into critical software development issues specific to automotive microcontrollers.
• Understand how to set-up the software development process correctly to avoid critical errors from the start, demonstrated through real-world examples and practical solutions.
• Learn how to unlock your project's potential by avoiding critical mistakes from the start.
• Strengthen your expertise in cybersecurity, integration testing, power optimization, and customer-driven development.

Join us for an in-depth webinar on the top critical mistakes in developing automotive software functions on microcontrollers. This session leverages 30 years of experience collaborating with OEMs and Tier 1 suppliers, compiling a comprehensive list of common mistakes and their consequences through practical examples. Our goal is to empower developers and engineers in the automotive industry to avoid these pitfalls and elevate their software development processes.

In automotive systems, microcontrollers play a pivotal role as ECUs (Electronic Control Units), managing essential functions ranging from engine performance to safety features. Despite the expertise of developers, errors in software development can significantly impact product performance and reliability.

The Panel discussion with our ETAS Experts focuses on the key challenges and mistakes that Original Equipment Manufacturers (OEMs) and Tier suppliers in the automotive industry often encounter when developing software functions on microcontrollers.

The session will be structured around six critical areas, that OEMs and Tiers need to be aware of when setting up their development processes:

• Ignoring hardware constraints: Failing to consider the limitations of the microcontroller, such as memory size, processing power, and available peripherals, can lead to inefficient or non-functional code.
• Inadequate timing control: Many microcontroller applications have real-time constraints. Ignoring these can lead to missed deadlines and system failures. Developers must ensure that their code meets the timing requirements of the application.
• Overlooking cybersecurity: Failing to implement robust security measures, leaving systems vulnerable to cyber threats.
• Insufficient testing: Insufficient testing, especially under different conditions and over long periods, can result in unreliable software.
• Failure to ensure software safety: Not adhering to safety standards like ISO 26262.
• Missing of proper documentation: Poor or nonexistent documentation makes it difficult for others (or even the original developer) to understand and maintain the code. Good documentation is essential for long-term project success.
• Lack of effective automation: Insufficient and ineffective automation of recurring integration, testing, and deployment activities creates a high demand for resources.

• Automotive software engineers
• Embedded systems experts
• Technical leads and project managers in automotive
• Tech enthusiast in the automotive domain

• Nigel Tracey, Vice President of RTA Solutions, ETAS
• Dr. Frederic Stumpf, Head of Cybersecurity Solutions, ETAS
• Zoran Cutura, Technical Acquisition Manager, ETAS
• Gavin Wooler, Campaign Manager, ETAS