Stevica Đukić

Best Practices on the Integration of Functional Safety and Cybersecurity This webinar (https://lnkd.in/e3mdMnQJ) provides insight into the Security standard for vehicles ISO/SAE 21434 from an automotive safety standpoint. We talked about similarities to Functional Safety according to ISO 26262 and the dedicated enhancements of Cybersecurity which are also impacting the typical workflow of the safety managers and safety engineers. #CyberSecurity #Automotive #AutomotiveIndustry #ConnectedCars #VehicleCyberSecurity #AutomotiveSoftware

119

2 Comments

🚗🔌 Understanding CAN .dbc Files & Simulation in Automotive Testing If you are working in the automotive embedded domain, chances are you’ve come across a .dbc file while dealing with CAN communication. Let’s break it down: 🔹 What is a .dbc file? A .dbc (Database CAN) file is a CAN database file used to describe the structure of CAN messages and signals. It defines which messages (frames) exist, their IDs, which signals they contain, scaling, units, byte order, etc. In short: It acts as a dictionary between raw CAN data (hex values) and meaningful engineering values (like speed in km/h, RPM, fuel level). 🔹 Why is it needed? Without a .dbc, CAN traffic is just raw hexadecimal data. With a .dbc, engineers can decode and analyze signals in human-readable format. It enables testing, validation, logging, and simulation in tools like Vector CANoe, CANalyzer, vTestStudio. 🔹 How to create a new .dbc file? 1. Identify the CAN communication matrix (from OEM or supplier). 2. Open tools like Vector CANdb++ Editor, CANoe, or other database editors. 3. Define: Message IDs (standard/extended). Message cycle time, DLC (data length code). Signals (start bit, length, scaling, offset, unit). Node information (ECUs transmitting/receiving). 4. Save as .dbc file and use it for analysis or simulation. 🔹 What is Simulation? Simulation in automotive testing means mimicking real ECUs or systems in a test environment. Example: Using CANoe, you can simulate an ECU (say ABS) to test another ECU (say ECU under test – BCM). Benefits: Reduces dependency on hardware availability. Helps in early validation, debugging, and automation. 🔹 What is Physical Value Extraction? When an ECU sends data on the CAN bus, the information is packed into raw binary/hexadecimal format inside a CAN frame. But engineers don’t directly work with these raw values. Instead, we need to extract and convert them into real-world engineering values (like temperature, speed, or RPM). This process is called Physical Value Extraction. --- 🔹 The Formula for Conversion Each signal in a CAN frame has parameters defined in the .dbc file: Start Bit, Length, Byte Order → tells where the signal is located. Factor (Scaling) and Offset → defines how raw values are converted. Minimum, Maximum, Unit → defines valid range and measurement unit. The conversion is done using this formula: 👉 Physical Value = (Raw Value × Factor) + Offset --- 🔹 Example Suppose you have a signal Vehicle_Speed defined as: Start bit: 0 Length: 16 bits Factor: 0.1 Offset: 0 Unit: km/h If the ECU sends raw data 0x03E8 (= 1000 decimal): Physical Value = (1000 × 0.1) + 0 = 100 km/h 🚗💨 --- 🔹 Why It Matters? Makes data human-readable. Allows proper monitoring, logging, and validation in tools like CANoe or CANalyzer. Ensures signals are interpreted consistently across teams (OEMs, suppliers, testers). #EmbeddedSystems #CAN #Testing #Simulation #DBC #Vector #SystemTesting #automotive

58

🔐 UDS Service 0x27 vs. 0x29 – Old Guard vs. Modern Security in Automotive Diagnostics One of the most common questions I get in AUTOSAR & Diagnostics discussions is: 👉 “What’s the difference between Security Access (0x27) and Authentication (0x29)?” Both are about vehicle security, but their purpose and strength are worlds apart. Let’s break it down. ⸻ 🔑 Service 0x27 – Security Access (Seed & Key) This is the classic security method you’ll find in most vehicles today. • 🎯 Goal: Unlock an ECU for protected operations (e.g., flashing, WriteDataByIdentifier 0x2E, RoutineControl 0x31). • ⚙️ How it works: 1. Tester requests a seed. 2. ECU sends a random seed. 3. Tester applies a secret OEM algorithm → generates key. 4. ECU verifies → if correct, access granted. • 🔒 Crypto: Symmetric (shared secret algorithm). • ⚠️ Weakness: Once the algorithm leaks (firmware reverse-engineering), anyone can generate valid keys. Analogy: 🕺 A bouncer asking for a secret handshake before letting you in. ⸻ 🔒 Service 0x29 – Authentication (PKI-Based, Modern) Introduced in ISO 14229-1:2020, and now a key part of UNECE R155/R156 cybersecurity compliance. • 🎯 Goal: Verify the identity of the tester before granting access. • ⚙️ How it works: 1. Tester & ECU exchange supported methods (ACR – Authentication Configuration Record). 2. ECU sends a cryptographic challenge (nonce, APCE). 3. Tester signs the nonce with its private key and sends signature + certificate. 4. ECU verifies certificate chain, extracts public key, checks signature. • 🔐 Crypto: Asymmetric (RSA/ECDSA, PKI certificates). • ✅ Strength: Secure against replay/MITM. Breaking it requires cracking strong cryptography, not reverse-engineering. Analogy: 🛂 Showing your passport at border control, validated against trusted authorities. ⸻ 📊 Quick Comparison Feature 0x27 Security Access 0x29 Authentication Goal Unlock ECU security level Verify client’s identity Cryptography Symmetric (shared secret) Asymmetric (PKI: RSA/ECDSA) Data Exchanged Seed + Key Nonce, Signature, Certificates Security Strength Weak (algorithm leaks) Strong (private key protected) Common Use Flashing, legacy diagnostics Secure updates, R155/R156 compliance Analogy 🤝 Secret Handshake 🛂 Passport Verification ⸻ 🚘 Why This Matters • 0x27 → still dominant in legacy ECUs. • 0x29 → mandatory in new vehicle platforms to meet global cybersecurity regulations. • Future-proof ECUs will rely heavily on PKI-based authentication for software updates, diagnostics, and secure communication. 💡 Takeaway: • 0x27 = authorization to perform a function. • 0x29 = authentication of identity + trust establishment. Both will co-exist for a while, but 0x29 is the foundation of modern vehicle security.

123

5 Comments

🔧 AUTOSAR Development Process: Building the Software DNA of Modern Vehicles 🔧 In today’s automotive industry, vehicles are no longer just mechanical machines — they are software-driven systems on wheels. To manage this complexity across OEMs, Tier 1s, and suppliers, the industry relies on AUTOSAR (AUTomotive Open System ARchitecture): a global standard for automotive software architecture. Understanding the AUTOSAR development process is essential for engineers working on ECUs, middleware, automotive software, and embedded systems. 💡 What is AUTOSAR? AUTOSAR is a layered software architecture that enables: ✅ Reusable software components across ECUs and vehicle platforms ✅ Standardized interfaces for better integration ✅ Scalability from small microcontrollers to high-performance computers ✅ Compliance with functional safety (ISO 26262) and cybersecurity There are two main flavors: Classic Platform (for hard real-time, safety-critical ECUs) Adaptive Platform (for high-performance, dynamic applications like ADAS and autonomous driving) ⚙️ AUTOSAR Development Process (Simplified Steps) 1️⃣ System Requirements Define functional and non-functional requirements, safety goals, communication needs. 2️⃣ System Architecture Design Map functions across ECUs, define software components (SWCs), RTE (Runtime Environment), and communication stacks. 3️⃣ Software Component Development Develop or reuse application SWCs, interface definitions, and BSW (Basic Software) modules. 4️⃣ Configuration & Integration Configure BSW modules, RTE, and MCAL (Microcontroller Abstraction Layer); integrate third-party components. 5️⃣ Code Generation Use AUTOSAR tools (e.g., Vector DaVinci, Elektrobit Tresos) to generate production-ready code. 6️⃣ Testing & Validation Unit testing, integration testing, hardware-in-the-loop (HiL), software-in-the-loop (SiL), and functional safety verification. 7️⃣ Flashing & Deployment Deploy final binaries into ECUs, ready for vehicle integration. 🚗 Why AUTOSAR matters for engineers Enables modular, scalable automotive software development Supports multi-vendor collaboration Reduces development time & cost Ensures compliance with safety, security, and industry standards 👉 Download Now on Google Play 🔗 https://lnkd.in/gaw5GaFq 👉 Explore more on AUTOSAR Development: 🌍 https://lnkd.in/g9S5sN9z #Automotive #EmbeddedSystems #AUTOSAR #AUTOSARClassic #AUTOSARAdaptive #SoftwareArchitecture #ECUDevelopment #AutomotiveSoftware #RTE #MCAL #BSW #ADAS #AutonomousDriving #FunctionalSafety #ISO26262 #Cybersecurity #AutomotiveEngineering #FirmwareDevelopment #SoftwareDefinedVehicles #VehicleNetworking #Microcontrollers #AutomotiveIndustry #ConnectedVehicles #SmartVehicles #SoftwareIntegration #OpenSourceLearning #TechCommunity #Piembsystech #EngineeringCommunity #Innovation #MobilityTechnology #DeveloperCommunity #VehicleSoftware #AUTOSARDevelopment

45

12 Comments

🏀 Dribble your way past heavy lifting. When you understand the rules of physics, even a tough job can turn into a game. In manufacturing, it’s the same story. Before writing a single line of work instructions, the smartest move is to find the best way to do the job. Because once the method is right, speed, safety, and smiles follow naturally. 💬 What’s the cleverest trick you’ve seen for making a tough job easy? #LeanManufacturing #OperationalExcellence #StandardWork #Efficiency #Ergonomics #ContinuousImprovement ‐----------‐-------------------------------------- 👋 Hi, I'm Andrej! 📌 Follow me for a daily dose of Lean and Operational Excellence from real-life. 🔔 Turn on notifications, so you don’t miss a thing! 🗣 Don't forget to like, comment and share!

5,147

141 Comments

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 Comments

Here are the most pressing questions about using Qt under LGPL 3.0 on embedded devices. Can we use Qt LGPL on embedded devices? Yes. The Qt modules under LGPL are good enough for most manufacturers. Do we have to open-source the code of our proprietary software? No. You must only provide the Qt source code as used on the device. A written offer allows you to do this on request. Can our software link the Qt libraries statically? Yes. Do our customers have the right to install a modified Qt version on our devices? No for B2B products. Yes for consumer products. Can we move from Qt Commercial to Qt LGPL? Yes with the next release. Of course, you must honour the contract with The Qt Company and satisfy the obligations of LGPL-3.0. So, don't miss the notice period. You find detailed answers in my post "Using Qt 6 under LGPL-3.0": https://lnkd.in/eVk2aTxk

55

8 Comments

𝐖𝐞 𝐚𝐫𝐞 𝐡𝐢𝐫𝐢𝐧𝐠 𝟏𝟎𝟎+ 𝐀𝐮𝐭𝐨𝐦𝐨𝐭𝐢𝐯𝐞 𝐃𝐞𝐬𝐢𝐠𝐧 𝐄𝐧𝐠𝐢𝐧𝐞𝐞𝐫𝐬 𝐟𝐨𝐫 𝐨𝐮𝐫 𝐜𝐥𝐢𝐞𝐧𝐭𝐬 𝐚𝐜𝐫𝐨𝐬𝐬 𝐈𝐧𝐝𝐢𝐚 𝐭𝐡𝐫𝐨𝐮𝐠𝐡 𝐨𝐮𝐫 𝐆𝐏𝐃𝐗 𝐩𝐥𝐚𝐭𝐟𝐨𝐫𝐦. For those who don't understand #GPDX, here is a detailed explanation. 𝐆𝐏𝐃𝐗 (𝐆𝐥𝐨𝐛𝐚𝐥 𝐏𝐫𝐨𝐝𝐮𝐜𝐭 𝐃𝐞𝐯𝐞𝐥𝐨𝐩𝐦𝐞𝐧𝐭 𝐄𝐱𝐜𝐞𝐥𝐥𝐞𝐧𝐜𝐞) is an Automotive industry-recognized exam designed to benchmark the knowledge, skills, and problem-solving abilities of engineers in the automotive product development domain. It helps companies identify skilled candidates who are job-ready, while students and professionals gain a globally trusted score to showcase their expertise. 𝐆𝐏𝐃𝐗 𝐂𝐞𝐫𝐭𝐢𝐟𝐢𝐜𝐚𝐭𝐢𝐨𝐧 𝐒𝐲𝐥𝐥𝐚𝐛𝐮𝐬 𝐋𝐞𝐯𝐞𝐥 𝟎𝟏 – 𝐃𝐨𝐦𝐚𝐢𝐧 & 𝐂𝐨𝐫𝐞 𝐅𝐮𝐧𝐝𝐚𝐦𝐞𝐧𝐭𝐚𝐥𝐬 Format: 50 Questions – 30 Minutes Structure: Domain Questions (based on the candidate’s chosen domain: BIW / Plastic Trims / Powertrain / Electrical) Common Questions (for all domains): GD&T, DFMEA, CAD tools, Design Standards, Manufacturing Processes 𝐋𝐞𝐯𝐞𝐥 𝟎𝟐 – 𝐂𝐀𝐃 𝐀𝐩𝐩𝐥𝐢𝐜𝐚𝐭𝐢𝐨𝐧 𝐓𝐞𝐬𝐭 Platform: CATIA or NX (chosen by candidate) Topics: 2D to 3D Conversion Concept Design Remastering / Reverse Engineering Close Volume with Feature Creation 𝐋𝐞𝐯𝐞𝐥 𝟎𝟑 – 𝐂𝐚𝐬𝐞 𝐒𝐭𝐮𝐝𝐲 & 𝐓𝐞𝐜𝐡𝐧𝐢𝐜𝐚𝐥 𝐈𝐧𝐭𝐞𝐫𝐯𝐢𝐞𝐰 Format: Online Interview - Upon clearing Level 01 & Level 02 Focus: Domain-specific Case Study + Interview BIW – Assembly Structure, Reinforcements, Crash Safety Standards, Joining Techniques Plastic Trims – Class A to B Conversion, Attachment Strategy, Tooling Feasibility, Master Section Understanding, Material Selection Powertrain – Component Design, Tolerancing, NVH, Material Selection Electrical – Harness Routing, Packaging Rules, Clip/Bracket Design, EMI/EMC considerations 𝐖𝐡𝐲 𝐆𝐏𝐃𝐗? Standardized global benchmark for automotive engineers. Trusted by leading OEMs & Tier-1 companies. Eliminates repeated company-level screening. Enhances employability with direct placement opportunities. Transparent score-based shortlisting system. Comment "GPDX" below if you want to get take up the exam and get hired with our automotive clients. #automotive #disenosys #gpdx #design #biw #trims #openings #skilledengineers #placement

35

17 Comments

This post describes embedded software (SW) function specifications. For more information, please refer to this site. https://lnkd.in/dGgjeaBY The SW function specification document is a document that describes the design details of individual functions in SW development. This specification document clearly describes the purpose of the function, input/output parameters, prerequisites, processing details, return values, exception handling, etc., and serves as a guideline for implementers to code accurately. In addition, SW function specifications are used for information sharing and review within the team, test design in later stages, and understanding during maintenance, so they are not merely coding instructions, but important documents that support SW quality and productivity. Maintaining consistency between specifications and implementation is essential for reliable development, and it is necessary to appropriately update and manage specifications in each phase of design, implementation, and testing. Please note that this post is my personal opinion. I would be happy if it would be helpful to all of you. Best regards,Mitsuaki. #MCU #embedded #program #software #automotive #robot #IoT #consumer #industrial #medical #train

23

2 Comments