Piyush D Jadhav

I used to think ASIL decomposition was the silver bullet for automotive safety. ↳ I assumed it always simplified development ↳ I believed it consistently reduced costs ↳ I thought it was a straightforward process But after 67 projects and countless sleepless nights, I've learned the hard truth: ASIL decomposition can be a double-edged sword. Here's what can go wrong: 1. Independence Illusion: You decompose ASIL D into B(D) + B(D), thinking you've created two independent systems. But a shared power supply becomes your Achilles' heel. 2. Complexity Creep: Suddenly, you're juggling multiple lower ASIL components. The integration nightmare begins. 3. False Economy: That initial cost saving? It evaporates as you realize the hardware metrics still need to meet the original ASIL D targets. 4. Legacy Landmines: Your brilliant decomposition strategy falls apart when faced with that untouchable legacy component. 5. Overconfidence: "We've decomposed, so we're safer!" - a dangerous mindset that can lead to overlooking critical failure modes. I once decomposed an ASIL D steering system, feeling clever about the B(D) + B(D) split. Two weeks before production, we discovered a common cause failure that rendered the entire decomposition useless. Cue panic, sleepless nights, and a very unhappy management team. But here's how I turned it around: 1. Holistic Approach: Now, I consider the entire system architecture before even thinking about decomposition. 2. Rigorous Independence Analysis: I've developed a comprehensive checklist to ensure true independence between decomposed elements. 3. Cost-Benefit Deep Dive: I run detailed simulations to understand the true long-term costs and benefits of decomposition. 4. Legacy-First Mindset: I start by mapping out all legacy components and constraints before planning decomposition strategies. 5. Cultivate Healthy Skepticism: I encourage my team to constantly question and validate our decomposition decisions. The result? Our last project came in under budget, ahead of schedule, and with a more robust safety architecture than ever before. ASIL decomposition isn't a magic wand - it's a powerful tool that demands respect and expertise. Used wisely, it can revolutionize your automotive safety approach. But always remember: with great decomposition comes great responsibility. Have you faced ASIL decomposition challenges? Share your experiences below! #AutomotiveSafety #FunctionalSafety #ASILDecomposition #LessonsLearned

100

12 Kommentare

🚗🔁 Which HiL Platform Do You Use in Automotive Testing – and Why? 🔍 In today’s fast-evolving automotive industry, Hardware-in-the-Loop (HiL) testing plays a vital role in validating ECUs, sensors, actuators, and software functionality before real-world deployment. But with a range of HiL platforms available, I’m curious 👇 Which platform do you use in your automotive projects – and what makes it your preferred choice? Here are a few widely-used platforms in the industry: ⚙️ dSPACE – known for powertrain, ADAS & complete ECU integration 🧩 Vector VT System – great for flexible signal manipulation and diagnostics 🛠️ NI (National Instruments) – modular, scalable, and ideal for custom setups 📏 ETAS – widely used with INCA integration, especially for calibration & measurement ⚡ Opal-RT – preferred for power electronics & real-time simulation 🔋 Typhoon HIL – perfect for electric drive and inverter systems 💻 Speedgoat + Simulink – tight MATLAB integration for rapid prototyping 🌐 Modelon, Siemens, AVL – for specialized or scalable plant modeling Each tool has its own niche – and the best fit often depends on your use case, whether it's ADAS, BMS, Powertrain, or complete vehicle systems. 🧠 Let’s exchange insights: ✅ Which HiL platform do you use? ✅ What domain do you apply it to? ✅ What advantages do you see? Let’s learn from each other and strengthen the automotive testing community 🔧🚘 👇 Share your experience in the comments! #HiLTesting #AutomotiveTesting #dSPACE #Vector #NI #ETAS #OpalRT #TyphoonHIL #Speedgoat #Simulink #ModelBasedDesign #RealTimeSimulation #AutomotiveTools #VehicleValidation #ADAS #Powertrain #BMS #ISO26262 #AutomotiveInnovation #MBD #AutomotiveEngineers #SoftwareDefinedVehicles #ECUTesting #SimulinkRealTime #HardwareInTheLoop #HiLPlatform

71

9 Kommentare

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.

166

2 Kommentare

The love story between C/C++ and Rust is getting serious…💙 💙 And that is a great mix for software safety especially in Autosar platforms. 𝗪𝗵𝗮𝘁 𝗵𝗮𝗽𝗽𝗲𝗻𝗲𝗱 𝗯𝗲𝘁𝘄𝗲𝗲𝗻 𝗯𝗼𝘁𝗵? In a recent collaboration Elektrobit, HighTec, and Infineon have teamed up to bring Rust into Autosar classic: ✦ Elektrobit Added Rust support to the EB Tresos AutoCore toolchain. ✦ Hightec Developed LLVM-based Rust and C/C++ compiler, which is ASIL-D certified. ✦ Infineon Technologies Acts as a hardware foundation based on the famous Aurix TC4x microcontrollers. The main objective is to enable developers to run Rust modules alongside with the legacy C/C++ code with minimal friction. 𝗕𝘂𝘁 𝘄𝗵𝘆 𝗱𝗼𝗲𝘀 𝗥𝘂𝘀𝘁 𝗶𝗺𝗽𝗿𝗼𝘃𝗲 𝘀𝗼𝗳𝘁𝘄𝗮𝗿𝗲 𝘀𝗮𝗳𝗲𝘁𝘆 𝗶𝗻 𝗔𝘂𝘁𝗼𝘀𝗮𝗿? → Strict memory rules at compile time. ↳ Each value has a single owner ↳ Memory is automatically freed when owner goes out of scope → Stronger static analysis. ↳ Enforces thread safety ↳ Prevents data races → Minimized use of unsafe code. ↳ Code is safe by default ↳ Unsafe code is marked and isolated → Improved cybersecurity. ↳ No stack smashing ↳ No integer overflows ↳ Variables are immutable by default ➖➖➖ 🔹𝗜𝗻 𝗦𝘂𝗺𝗺𝗮𝗿𝘆: C/C++ built the foundation for Autosar greatness, but Rust brought safety and a promise of fewer bugs. That sounds like a healthy relationship… 🖤 🖤 #SDV #Rust

64

4 Kommentare