Luís Teixeira

From single-core to multicore — but you don’t have to start from scratch. 🚗⚙️ In automotive embedded systems, the shift to multicore is inevitable. But with safety-critical legacy code and real-time constraints, migrating from single-core isn’t just plug-and-play. That’s where our AUTOSAR expertise comes in. We contributed to the introduction of multicore into AUTOSAR with release 4.0.1 in 2009 and simultaneously developed the ETAS RTA-CAR BSW stack: a robust, field-proven solution that fully supports any customer use case. Built by engineers, for engineers —RTA-CAR at a glance: 🔧 Compact & efficient - Optimized for resource-constrained, low-latency real-time environments. 🛡️ Safety & security - Complies with industry standards like ISO26262 and ISO/SAE21434, along with MISRA-C & CERT-C guidelines. 🛠️ Versatile compatibility - Suitable for all ECU types, from smart sensors to vehicle computers, and adaptable for single and multi-OEM projects. ⚡Wide device support - Compatible with various target devices and integrates seamlessly with third-party MCALs and security solutions. 🚀 Proven success - Deployed on over 4 billion ECUs globally. We’ve summed up more exclusive insights and real-world cases to help you navigate the transition in a white paper. Download it now: https://brnw.ch/21wSQG3 #YourAmbitionIsOurMission #AUTOSARClassic

53

Engineering, to the power of AI. ⚙️ In embedded systems, a single oversight in a requirement, a design choice or a line of code can cost millions or even lives. That’s where AI makes the difference. With Expleo, engineering teams move from quality-by-testing to quality-by-design: ⏱️ Reduce Hardware-in-the-Loop testing time and costs by up to 30% 🛠️ Minimise unscheduled maintenance by up to 50% with AI-driven predictive maintenance 🛡️ Add extra safety features with ultra-light EdgeAI virtual sensors Our experts help you design smarter from the start, so you can deliver safer systems, faster testing and fewer failures. 👉 Discover how to elevate product performance, to the power of AI: https://expleo.to/3JYLQ1E #ToThePowerOfAI

53

The Critical Role Of Safety Microcontrollers In ADAS And AD Applications. New Webinar: https://lnkd.in/d4bqBN-E Join us for an in-depth exploration of the critical role Safety Microcontrollers (MCUs) play in Advanced Driver Assistance Systems (ADAS) and Automated Driving (AD) applications. This webinar, presented by Infineon Technologies, aims to provide a comprehensive understanding of the functionalities and indispensability of Safety MCUs, particularly in contrast to the nascent Safety Islands within System on Chips (SoCs). Discover why OEMs continue to rely on external Safety MCUs, such as Infineon's AURIX™, despite the common availability of Safety Islands in modern automotive SoCs. Key takeaways: ✅ Essential Role of Safety MCUs: Safety MCUs are a cornerstone of a proper FUSA concept for ADAS/AD applications, such as domain controllers, smart cameras, LiDARs, and radars. ✅ Critical Functions of Safety MCUs: Safety MCUs supervise actuator commands, provide emergency response, monitor the health of all critical components, offer gateway functionality, and support an independent real-time software environment. ✅ Advantages of AURIX™ Safety MCUs: AURIX™ is the technically proven solution due to its best-in-class scalability, extensive AUTOSAR and safety software portfolio, and ability to handle fail-operational use cases. ✅ Limitations of Safety Islands: Safety Islands in SoCs lack the comprehensive feature set and hardware separation that dedicated Safety MCUs offer; hence, they cannot replace them.

165

2 comentários

For the validation of ADAS (Advanced Driver Assistance System) driving functions, developers need as much measurement data as possible from test drives – because this is the only way to ensure that the system has encountered many edge cases such as construction sites or rare traffic signs. But the measuring equipment for this is expensive, therefore making it cost-intensive to scale for large vehicle fleets. Validation is also generally associated with a large amount of work, as the example of traffic sign recognition shows: a developer in the passenger seat compares whether the ADAS system has correctly recognised a traffic sign during road tests. In the event of an error, they note the discrepancy manually. In addition, the corresponding measurement data from the vehicle is recorded on a hard drive. Porsche Engineering aims to reduce the manual work effort required for the validation of ADAS functions. To do so, it is employing smartphones equipped with software for traffic sign recognition from the Berlin-based start-up Peregrine.ai. Learn more: https://lnkd.in/e7Pzp8zZ Macan Turbo Electric (WLTP, preliminary values): Electrical consumption combined: 20.7 – 18.9 kWh/100 km; CO₂ emissions combined: 0 g/km; CO₂ class: A; Status 04/2025

431

16 comentários

Can virtual test automation contribute to road safety? The validation of functions for automated driving cannot do without virtual driving scenarios for testing. Test automation not only improves the efficiency of scenario creation but also increases test coverage. Engineers at Stellantis used the ASM simulation as a key role in validating assisted and automated driving functions in their challenging projects. Read more about how Stellantis and dSPACE are working together: https://ow.ly/7fOf50XA51a #dSPACE #autonomousdriving #simulationsoftware #validation #ASM

32

Many people believe Embedded Engineers only need software skills ❌ That belief limits growth in automotive projects. Here’s the reality 👇 An Automotive Embedded Engineer must understand both Hardware AND Software. Why? Because embedded software does not run in isolation. It interacts directly with real hardware. In real automotive projects, engineers deal with: • Sensors producing noisy signals • Power supply variations • Timing constraints • Communication buses (CAN, LIN, UART) • Actuators responding to software decisions A software bug may actually be: ❌ Hardware configuration issue ❌ Timing mismatch ❌ Incorrect pin setup ❌ Electrical noise 🚗 Automotive systems fail when hardware and software are misaligned. That’s why great embedded engineers: ✔ Read schematics and datasheets ✔ Understand pin multiplexing ✔ Know interrupts, timers, and clocks ✔ Debug hardware and software together 👉 If you had to choose, which is harder for you? Comment Hardware or Software 👇 #AutomotiveEmbedded #EmbeddedSystems #EmbeddedEngineer #ECU #Microcontroller #AutomotiveElectronics #EmbeddedLearning

20

12 comentários

Aptiv’𝘀 𝗜𝗻𝘃𝗲𝘀𝘁𝗼𝗿 𝗗𝗮𝘆 𝟮𝟬𝟮𝟱: 𝗦𝗵𝗼𝘄𝗰𝗮𝘀𝗶𝗻𝗴 𝗦𝘁𝗿𝗲𝗻𝗴𝘁𝗵 𝗮𝗻𝗱 𝗢𝗽𝗽𝗼𝗿𝘁𝘂𝗻𝗶𝘁𝘆 Today we shared with investors the strategy and financial profile for our two future companies: ✅ 𝗡𝗲𝘄 𝗔𝗽𝘁𝗶𝘃 – A $12B technology leader built around: • 𝗜𝗻𝘁𝗲𝗹𝗹𝗶𝗴𝗲𝗻𝘁 𝗦𝘆𝘀𝘁𝗲𝗺𝘀 (formerly Software and Advanced Safety & User Experience) • 𝗘𝗻𝗴𝗶𝗻𝗲𝗲𝗿𝗲𝗱 𝗖𝗼𝗺𝗽𝗼𝗻𝗲𝗻𝘁𝘀 About 25% of revenue already comes from markets beyond automotive—like aerospace, telecom, and industrial—delivering higher growth and margins. ✅ 𝗡𝗲𝘄 𝗘𝗗𝗦 𝗖𝗼𝗺𝗽𝗮𝗻𝘆 – The leader in electrical architecture with $8.6B in revenue, relationships with all top 10 global OEMs, and content on 21 of the top 25 vehicle platforms worldwide. We highlighted how automation, electrification, and digitalization are accelerating across industries, creating significant opportunities for both companies. Our technology powers 70M+ vehicles, top commercial aircraft, and major telecom networks worldwide. With world-class engineering, a resilient supply chain, and a global manufacturing footprint, we’re positioned to create value in any environment. We have the right strategy, the right capabilities, and the right team. #InvestorDay #Aptiv #IntelligentSystems #EngineeringExcellence #FutureReady

1.271

10 comentários

The COVESA Automotive AOSP App Framework Standardization Expert Group has completed the UnifiedPush project, and we encourage those using push notifications in their products to adopt this open-source solution! 📢 What is UnifiedPush? An open-source Push Notification service designed to meet automotive requirements, allowing OEMs, tier 1s, and suppliers to run and maintain it seamlessly. 🔹 Why it matters: Push notifications are crucial for connected cars, enabling real-time communication from external services to the vehicle—delivering important updates, alerts, or reminders that enhance user experience, safety, and maintenance. ✅ Until now, there was no agreed-upon, open-source push notification implementation in Automotive AOSP that met the requirements for connected vehicle applications. 💡 Get Involved & Learn More: 🔹 Join the weekly AOSP App Framework Expert Group meetings. 🔹 Attend the COVESA All Member Meeting in Berlin (May 14–15) for hands-on demos, how-tos, and workshops. 🔗 More details: https://lnkd.in/gje5mEAM #COVESA #UnifiedPush #PushNotifications #ConnectedVehicles #AutomotiveAOSP #OpenSource 🚘🔔

12

FORVIA HELLA has launched “Ignite by FORVIA HELLA,” a new software-focused entity dedicated to developing software-only products. Built for speed and agility, it brings together a growing team of software experts — expected to reach 40 by year-end — to accelerate innovation in both core and new business areas. The unit is working on software closely connected to FORVIA HELLA’s strengths in lighting, electronics, and lifecycle solutions. But it’s also going further. One standout: the Traffic Rules Engine, a compliance module for SAE Level 3+ automated driving. Co-developed with TÜV Rheinland, it checks if planned vehicle maneuvers comply with traffic laws in real time. With software now central to mobility, this is a focused step forward, rooted in our electronics leadership.

282

2 comentários

🧪 How do you validate software behavior when things go wrong? In safety-critical automotive systems, it's not enough to verify that everything works, engineers must prove the system behaves correctly even when it fails. That’s where Fault Injection Testing (FIT) steps in. By simulating faults like: 🔹 Bit flips 🔹 Sensor malfunctions 🔹 Communication dropouts 🔹 Timing delays FIT helps assess how well safety mechanisms respond under stress, a key requirement for ISO 26262 compliance and ASIL decomposition. More than just making systems work, fault-injection testing ensures that they fail safely. 🔗 Explore how FIT strengthens functional safety- https://lnkd.in/dSgDV63J #FunctionalSafety #ISO26262 #ASIL #FaultInjectionTesting #AutomotiveTesting #EmbeddedSoftware #SafetyCriticalSystems

32

2 comentários

🚗 DTCs in Automotive Diagnostics — What, Why, and How If you work with automotive embedded software, you’ve definitely met DTCs (Diagnostic Trouble Codes). But in real projects, DTCs are much more than error numbers — they are a contract between software, hardware, testers, workshops, and even legislation. Let’s break it down clearly 👇 🔍 What is a DTC? A DTC (Diagnostic Trouble Code) represents a detected fault related to: - Sensors or actuators - Communication (CAN, LIN, Ethernet) - Internal ECU software or hardware - Safety, emissions, or drivability functions Each DTC has: - A unique identifier - A status byte (bit-coded life cycle) - Optional extended data (snapshots, counters, timestamps) Standards typically come from AUTOSAR and ISO 14229 (UDS). 🎯 Why DTCs Are Critical in Real Projects In production vehicles, DTCs are used to: ✔ Enable on-board diagnostics (OBD) ✔ Support workshop troubleshooting ✔ Fulfill legal and emission requirements ✔ Trigger limp-home or degradation modes ✔ Provide data for field analysis & recalls 👉 A wrongly implemented DTC can cause: - False warning lamps - Missed safety issues - Rejected vehicle homologation - Costly customer complaints ⚙️ How DTCs Are Used in Practice (Real ECU Flow) 1) Monitoring Software continuously checks conditions (timeouts, range checks, CRCs, plausibility). 2) Detection If a fault condition is fulfilled → diagnostic event fails. 3) Debouncing / Qualification Counters, time filters, or operation cycles avoid false positives. 4) DTC Storage DTC is stored with a status byte update and optional snapshot data. 5) Reporting Tester reads it via UDS services (e.g. 0x19 ReadDTCInformation). 6) Healing / Aging If the fault disappears for defined cycles → DTC may heal or age. 🧠 The Heart of a DTC: Status Byte The status byte tells the story of the fault, not just that it exists. Bit 0 TestFailed : Fault is currently present Bit 1 TestFailedThisOperationCycle: Fault occurred in the current driving cycle Bit 2 PendingDTC: Fault detected but not yet confirmed Bit 3 ConfirmedDTC: Fault confirmed after qualification Bit 4 TestNotCompletedSinceLastClear: Test hasn’t run since last clear Bit 5 TestFailedSinceLastClear: Fault happened at least once since clear Bit 6 TestNotCompletedThisOperationCycle: Test didn’t run in current cycle Bit 7 WarningIndicatorRequested: MIL / warning lamp requested 📌 Key takeaway: A DTC is not binary (present / not present). Its status byte represents its life cycle. 🏁 Final Thought A good diagnostic implementation doesn’t just detect faults — it tells a reliable story about them. If your DTCs are clean, consistent, and well-qualified: - Testing becomes easier - Workshops trust the ECU - Customers trust the brand 💬 How do you usually implement DTC qualification? Counters or time-based? Let’s exchange experiences 👇

234

6 comentários

Accelerate Automotive Expertise with edForce 🚗 Unlock industry-vetted learning paths, hands-on labs, and certifications across EV, ADAS, AUTOSAR, Embedded & AI. Empower your teams to lead the future of mobility. Why edForce Stands Out: • 25+ automotive training courses & 6 enterprise learning paths for OEMs & Tier‑1s • Real-world labs powered by RTOS, GPOS, AUTOSAR tools, EMU, MATLAB, ROS • Delivered by SMEs with deep automotive industry experience Ready to upskill your teams? ✨ Explore learning paths → https://lnkd.in/gNbNdEUb 🔧 Discover course catalog → https://lnkd.in/gg3j_uB6 #AutomotiveTraining #WorkforceUpskillingAccelerated #edForce #EnterpriseLearning #ADAS #EV #EmbeddedSystems

120

11 comentários

🚀 𝗦𝗽𝗲𝗮𝗸𝗲𝗿 𝗔𝗻𝗻𝗼𝘂𝗻𝗰𝗲𝗺𝗲𝗻𝘁 – 𝟭𝟲𝘁𝗵 𝗔𝗨𝗧𝗢𝗦𝗔𝗥 𝗢𝗽𝗲𝗻 𝗖𝗼𝗻𝗳𝗲𝗿𝗲𝗻𝗰𝗲 (𝗔𝗢𝗖) 🚀 We are excited to reveal more of our outstanding speakers at the 16th AOC! Ahmed Saad from Expleo Group Ahmed brings 8 years of experience across AUTOSAR Classic and Adaptive platforms. Representing BMW at the AUTOSAR WG-SEC working group, he is also the document owner of RS/SWS Cryptography standards. 🎙️ Session Title: "𝘼𝙘𝙘𝙚𝙨𝙨 𝘾𝙤𝙣𝙩𝙧𝙤𝙡 𝙞𝙣 𝘼𝙐𝙏𝙊𝙎𝘼𝙍: 𝙎𝙚𝙘𝙪𝙧𝙞𝙩𝙮 𝘼𝙨𝙥𝙚𝙘𝙩𝙨 𝙛𝙤𝙧 𝙎𝘿𝙑" 🌟 Key Takeaways: 🔹 Learn about Access Control mechanisms like IAM, SOME/IP-ACL, and Firewalls. 🔹 Understand AUTOSAR security aspects crucial for Software-Defined Vehicles (SDVs). 🔹 Discover how access control improves the resilience of automotive systems. Dr. Alexander Mattausch from Elektrobit Alexander Mattausch is an expert in embedded operating systems, software integration, and functional safety. After earning his PhD in theoretical physics he led the development of an ASIL-D certified AUTOSAR OS. He later focused on the OS infrastructure of automotive HPC systems. 🎤 Talk: "𝙀𝙣𝙖𝙗𝙡𝙞𝙣𝙜 𝙎𝙖𝙛𝙚𝙩𝙮 𝙞𝙣 𝙩𝙝𝙚 𝙎𝘿𝙑 𝙬𝙞𝙩𝙝 𝙊𝙥𝙚𝙣-𝙎𝙤𝙪𝙧𝙘𝙚 𝙎𝙤𝙛𝙩𝙬𝙖𝙧𝙚" ✨ What you’ll explore: 🔹 Why SDVs need modern, scalable E/E and software architectures. 🔹 How Linux and AUTOSAR platforms create a safe foundation for SDV development. 🔹 Innovative concepts for building safety applications on top of open-source technologies. 𝐇𝐚𝐫𝐢𝐬𝐡 𝐆𝐨𝐮𝐭𝐡𝐚𝐦 from AVIN Systems Harish, a Technical Architect at AVIN Systems, specializes in the integration of Classic and Adaptive AUTOSAR on High-Performance Computers for SDVs. With over a decade of experience delivering integrating platform and tooling solutions for global OEMs and Tier-1s in the automotive industry. 🎤 Presentation: "𝙏𝙝𝙚 𝘾𝙤𝙣𝙫𝙚𝙧𝙜𝙚𝙣𝙘𝙚 𝙤𝙛 𝘼𝙪𝙩𝙤𝙢𝙤𝙩𝙞𝙫𝙚 𝙖𝙣𝙙 𝘾𝙡𝙤𝙪𝙙 𝘾𝙤𝙢𝙥𝙪𝙩𝙞𝙣𝙜" 🧠 Session Highlights: 🔹 The transformative role of cloud computing in automotive development. 🔹How AUTOSAR's Automotive API is shaping seamless vehicle-to-cloud communication. 🔹 Exploring q’s collaboration with standards like the Vehicle Signal Specification (VSS). ✨ Don’t miss these powerful insights shaping the future of SDVs at the 16th AUTOSAR Open Conference! 📅 𝗦𝗲𝗰𝘂𝗿𝗲 𝘆𝗼𝘂𝗿 𝘁𝗶𝗰𝗸𝗲𝘁 𝗳𝗼𝗿 𝘁𝗵𝗲 𝗔𝗢𝗖: https://lnkd.in/dZv5yPGq 𝑻𝒊𝒎𝒆 𝒊𝒔 𝒓𝒖𝒏𝒏𝒊𝒏𝒈 𝒐𝒖𝒕! #AUTOSAR #AOC2025 #16thAOC #SoftwareDefinedVehicles #AutomotiveSecurity #CloudComputing #OpenSourceSoftware #FunctionalSafety #SDV

161

2 comentários

Kinematic Equations in ADAS Advanced Driver Assistance Systems (ADAS) rely on kinematic equations to predict motion, avoid collisions, and keep drivers safe. These equations help calculate: ✔ How fast a car is moving (velocity) ✔ How quickly it can stop (deceleration) ✔ How far it travels before reacting (stopping distance) v=v₀+at: Final velocity. d=v₀t+½at²: Displacement. v²=v₀²+2ad: Velocity-displacement relationship. d=1/2(v₀+v)t: Displacement with average velocity. Where: v = final velocity v₀ = initial velocity a = acceleration t = time d = displacement Automatic Emergency Braking (AEB): Scenario: Your car is traveling at 20 m/s (v₀). A pedestrian suddenly appears 25 meters ahead (d). The AEB system needs to determine the deceleration (a) required to stop in time. Calculation: We know the final velocity (v) must be 0 m/s to stop. Using v²=v₀²+2ad, we can rearrange to solve for a: a=(v2−​vo^2)/(2d) a=(0^2−20^2)/(2∗25) −400/50 =-8m/s² This means the AEB system needs to apply a deceleration of 8 m/s² to avoid a collision. Adaptive Cruise Control (ACC): Scenario: Your car is traveling at 30 m/s (v₀). The car ahead slows down, causing your radar to detect a relative acceleration of -2 m/s² (a). The system wants to calculate the distance (d) your car will travel in the next 3 seconds (t). Calculation: Using the equation d=Vo​t+1/2​at^2 d=(30∗3)+(0.5∗−2∗3^2) d=90+(−9) d=81 meters. The system calculates your car will travel 81 meters in that time frame. This information is used to adjust your car's speed to maintain a safe following distance. Time-to-Collision (TTC): Scenario: Your car is traveling at 15 m/s, and a car ahead is traveling at 10 m/s. The distance between them is 25 meters. Assuming the car ahead maintains its velocity. How much time until a collision? Calculation: Relative velocity = 15-10 = 5 m/s. TTC = distance / relative velocity. TTC = 25 / 5 = 5 seconds. Therefore, the time to collision is 5 seconds. If the car ahead were decelerating, then the "a" variable would be used to calculate a more accurate TTC. Key ADAS Points Sensors (radar, lidar, cameras) provide the initial data (position, velocity). ADAS algorithms use kinematic equations to: Predict future object positions. Calculate safe following distances. Determine necessary braking or steering actions. The accuracy of these calculations is critical for the reliable operation of ADAS. Disclaimer: This post is intended for educational purposes from a software development perspective. It does not cover complex non-linear vehicle dynamics.

561

12 comentários

Imagine passing every unit test but failing the final exam. Even when every ADAS component performs flawlessly, the system can still fail — that’s the paradox of modern automotive development. This presentation dives into real-world examples and industry insights to show how shifting from part-level success to system-level assurance through early MBSE adoption and a systems-first mindset can dramatically reduce delays, improve quality, and align teams around a shared vision. Loved bouncing ideas around with Rohit swarnakar The subsequent Slides provides an in depth explanation 👇 #EngineeringExcellence #InnovationInMotion #ISO26262 #ASPICE #FunctionalSafety #AutomotiveStandards #SystemsThinking #MBSE #AutomotiveEngineering #ADAS #SoftwareDefinedVehicles

21

2 comentários

Two Initiatives, One Goal: Stronger Processes and Stronger Skills At KIRCHHOFF Automotive Portugal, we recently completed two training initiatives that support this direction. The Digital Design Tools Training enabled the Hardware team to align workflows, unify tool structures and strengthen shared best practices. This creates transparency, reduces redundant work and increases efficiency in our industrialization processes. In parallel our Production colleagues completed a Welding Process Technology Training - combining theoretical insights with practical application to deepen technical expertise. Both initiatives reflect a clear leadership principle: Building strong capabilities within our teams creates long‑term stability and performance. #KIRCHHOFFAutomotive #MakingMobilitySafe #DigitalTransformation

14