Ahmed ElMessiry

#Morningtopic #Automotive #Classic #AUTOSAR #Security Functional description of AUTOSAR KeyM: -------------------------------------------------------- The #Key Management module is divided into two parts: 1. The #Cryptokey sub-module is mainly used to interact with a key provisioning entity (key master) that initiates the generation or provides key material directly. These keys are assigned to crypto keys of the CSM and stored in dedicated NVM blocks or can be stored as keys of the respective crypto driver e.g. HSM. 2. The #Certificate sub-module allows to configure certificates of a chain, providing interfaces to store and verify them. The public key contained in a certificate can further be assigned to CSM keys so that they can be used by crypto jobs of signature verification. Also the secure storage of certificates can be located in key storage locations of the CSM, e.g. to allow to store the root certificate within the HSM. Important API required when you deal with Certificates management: KeyM_SetCertificate() KeyM_VerifyCertificate() KeyM_CertGetStatus() #knowledgeexchange #learnsomethingnew #BeAnExpert => Reference to AUTOSAR Spec. of KeyM module

201

1 Kommentar

Advancing #AutomotiveSafety with Aptiv’s Gen 6 ADAS Platform The evolution of Advanced Driver Assistance Systems (ADAS) is pushing automotive innovation into new territory. Aptiv’s Gen 6 ADAS platform is a cutting-edge solution, merging sensor technology with AI/ML capabilities to offer scalable and efficient driver assistance across a wide range of vehicle types. This platform addresses a critical need for increased safety, performance, and energy efficiency while supporting modular integration for OEMs. One of the key highlights of this platform is its sensor-to-cloud technology stack, empowering automakers to develop and deploy software-defined vehicles. The system’s integration of AI-powered sensor fusion enables vehicles to interpret their environment in real-time, ensuring safe and adaptive navigation under various weather and lighting conditions. With software-defined functionality backed by Wind River’s containerized software solutions, Aptiv’s platform also supports over-the-air updates (OTA), allowing continuous enhancements over the vehicle’s life cycle. This modularity offers OEMs flexibility to tailor the system to specific needs, whether aiming for L2+ hands-off driving or L3 autonomous capabilities. Through smart resource optimization, the Gen 6 platform delivers up to 60% energy savings compared to market alternatives, making it both a sustainable and future-proof solution in the era of electric vehicles. Aptiv’s approach marks a significant milestone in automotive safety and automation, paving the way for the widespread adoption of hands-free driving and AI-driven safety systems. #Automotive #Innovation #Engineering #ADAS #AI #AutonomousVehicles #Technology #EdgeComputing #SmartMobility

10

𝗱𝗦𝗣𝗔𝗖𝗘 𝗔𝗨𝗧𝗢𝗦𝗔𝗥 𝗖𝗼𝗺𝗽𝗮𝗿𝗲 – 𝗖𝗼𝗺𝗽𝗮𝗿𝗶𝗻𝗴 𝗮𝗻𝗱 𝗠𝗲𝗿𝗴𝗶𝗻𝗴 𝗔𝗨𝗧𝗢𝗦𝗔𝗥 𝗙𝗶𝗹𝗲𝘀 𝗠𝗮𝗱𝗲 𝗘𝗮𝘀𝘆 AUTOSAR (ARXML) files are the backbone of embedded software development in the automotive industry. These files contain all information, interfaces, data types, and configurations from architecture design to basic software integration. For collaboration in AUTOSAR workflows, ARXML files are usually managed in a version control system, such as Git. Handling of AUTOSAR files can be a challenge: ➡️ Comparing and merging AUTOSAR files can be complicated and time consuming. ➡️ Text-based comparisons are often tedious and error-prone. 👉 Take advantage of 𝗱𝗦𝗣𝗔𝗖𝗘 𝗔𝗨𝗧𝗢𝗦𝗔𝗥 𝗖𝗼𝗺𝗽𝗮𝗿𝗲 to 𝗲𝗮𝘀𝗶𝗹𝘆 𝗰𝗼𝗺𝗽𝗮𝗿𝗲 𝗮𝗻𝗱 𝗺𝗲𝗿𝗴𝗲 AUTOSAR files: ✅ Check out the product information on dSPACE AUTOSAR Compare : https://ow.ly/yvea50TFnbm ✅ Download and try out dSPACE AUTOSAR Compare: https://ow.ly/pc6v50TFnbl #dSPACE #git #arxml #AUTOSAR #Diff #Merge #Versioncontrol #SVN

42

The automotive industry is currently in a transition phase to the so-called "Software Defined Vehicle". This transition also requires new concepts for the architecture of the software. One answer is the #AUTOSAR Adaptive Standard which provides a modular service oriented software architecture. ➡️ On 31st March 2017, AUTOSAR #Adaptive Platform is introduced and is designed to handle the high-performance computing platforms, such as service oriented architectures (SaaS), providing flexibility and dynamic reconfiguration capabilities compared to AUTOSAR #Classic.   📝 In this article, Yatish C. describes the future of automotive technology with the AUTOSAR Adaptive Platform. https://lnkd.in/eu56UDat

21

🚗🔧 𝐖𝐡𝐲 𝐀𝐔𝐓𝐎𝐒𝐀𝐑 𝐢𝐬 𝐂𝐫𝐮𝐜𝐢𝐚𝐥 𝐢𝐧 𝐀𝐮𝐭𝐨𝐦𝐨𝐭𝐢𝐯𝐞 𝐒𝐨𝐟𝐭𝐰𝐚𝐫𝐞 𝐃𝐞𝐯𝐞𝐥𝐨𝐩𝐦𝐞𝐧𝐭 🔧🚗 In the dynamic landscape of automotive technology, ensuring a seamless and standardized software development process is paramount. This is where AUTOSAR (AUTomotive Open System ARchitecture) comes into play, revolutionizing the way we approach automotive software. As someone with extensive experience in the automotive sector, I can attest to the critical role AUTOSAR plays in driving innovation and efficiency. Why AUTOSAR Matters: 𝟏. 𝐒𝐭𝐚𝐧𝐝𝐚𝐫𝐝𝐢𝐳𝐚𝐭𝐢𝐨𝐧 𝐚𝐧𝐝 𝐈𝐧𝐭𝐞𝐫𝐨𝐩𝐞𝐫𝐚𝐛𝐢𝐥𝐢𝐭𝐲: AUTOSAR provides a standardized software architecture that allows different manufacturers and suppliers to collaborate seamlessly. This standardization reduces complexity and ensures interoperability across various systems and components. 𝟐. 𝐒𝐜𝐚𝐥𝐚𝐛𝐢𝐥𝐢𝐭𝐲 𝐚𝐧𝐝 𝐅𝐥𝐞𝐱𝐢𝐛𝐢𝐥𝐢𝐭𝐲: AUTOSAR’s layered architecture supports scalability, making it easier to adapt to different vehicle platforms and functionalities. This flexibility is crucial in developing advanced features like autonomous driving and electric powertrains. 𝟑. 𝐄𝐧𝐡𝐚𝐧𝐜𝐞𝐝 𝐒𝐚𝐟𝐞𝐭𝐲 𝐚𝐧𝐝 𝐑𝐞𝐥𝐢𝐚𝐛𝐢𝐥𝐢𝐭𝐲: By adhering to stringent safety standards such as ISO 26262, AUTOSAR ensures that safety-critical applications are robust and reliable. This is particularly important for functionalities in highly automated driving and functional safety. 𝟒. 𝐂𝐨𝐬𝐭 𝐄𝐟𝐟𝐢𝐜𝐢𝐞𝐧𝐜𝐲: Reusing software components across different projects and platforms reduces development costs and time-to-market. AUTOSAR enables efficient reuse, leading to significant cost savings and faster deployment. 𝟓. 𝐅𝐮𝐭𝐮𝐫𝐞-𝐏𝐫𝐨𝐨𝐟𝐢𝐧𝐠: With the automotive industry rapidly evolving, AUTOSAR’s adaptability to new technologies and trends is invaluable. It supports the integration of cutting-edge technologies, ensuring that your systems are future-proof and ready for upcoming innovations. 𝐇𝐨𝐰 𝐖𝐞 𝐂𝐚𝐧 𝐇𝐞𝐥𝐩: With over 7 years of global software development experience in the automotive sector, we specialize in applying the product development’s V-model and ASPICE standards. Our expertise includes highly automated driving, functional safety, and agile methodologies, ensuring innovative and safe solutions in advanced automotive technologies. Let's collaborate to leverage the power of AUTOSAR in your projects, ensuring a smooth, efficient, and innovative development process. Reach out to discuss how we can drive your projects to success! #Automotive #SoftwareDevelopment #AUTOSAR #Innovation #FunctionalSafety #AgileMethodologies #AutomotiveTechnology #VModel #ASPICE

2

AUTOSAR has brought many improvements to the automotive industry and has tremendous potential for many systems. However, the most innovative engineers in any industry never blindly accept a requirement without understanding alternative options. Especially if those requirements can bring major cost and performance burdens. This article by my colleague, Adam Saenz, does a great job mapping out some of the things you should be thinking about before incorporating AUTOSAR into your product design as a one-size-fits-all approach. https://lnkd.in/gvWmR5xg

8

Is the evergreen layered software architecture dead? When the AUTOSAR standard was introduced in 2003 - it was a significant milestone in tackling increased software complexity in automotive. #AUTOSAR quickly became the norm - and remains even now widely used across the industry. But what do we do now as we head towards autonomous driving and software defined vehicles? Is #AUTOSAR still suitable? The answer is somewhere in the middle. #Layered architecture remains a fundamental aspect of automotive software #design, however many systems in automotive now, like autonomous driving software, personalisation, V2V/V2X scenarios are data or event driven. That means that the architecture premise needs to change. Hybrid models, either layered + data-driven, or layered + even driven must be considered, perfected and standardised. As we can see - the latest trends in #automotive require a change in approach all around! What’s your view on the evolution of #software #architecture? Dr. Moritz Neukirchner Connected Vehicle Systems Alliance (COVESA) Eclipse Software Defined Vehicle

16

Has AUTOSAR been a success? Definitely! But does it still have a future? AUTOSAR Classic has been around sind the mid 2000s and AUTOSAR Adaptive since the mid 2010s. It’s provided an open industry standard for the automotive E/E architecture and will continue to play an important role in the years ahead. However, with the move to Software Defined Vehicles (SDVs), we’re going to see a lot of changes. The hope here is that we’ll see less focus on specification and more on developing common APIs and implementation so that we have a common software base that is used industry wide. This will help us focus on developing differentiating features and simplify the development and maintenance of common functionality used across the industry. #autosar #inchron #sdv

10

8 Kommentare

🛑 Just Released - Software-Defined Vehicle: E/E Architecture Guide🛑 As more new vehicles integrate a growing number of hardware and software technologies, E/E architectures are set to play an important role across the vehicle lifecycle. The significance of E/E architectures in SDVs, as well as today’s vehicles, makes it crucial for OEMs to carefully plan and map out a holistic approach to them. Doing so will allow automakers to create cost-effective vehicles that are safer, more secure, and provide enhanced system usability. Our new SDV: E/E Architecture Guide includes everything automotive planners and engineers need to understand around the state of the art of E/E architectures, and the journey to enable a software defined vehicle. It provides insight into the decisions that enable year-on-year delivery with optimal utility and costs while highlighting relevant trends and profiling key technologies. An accompanying Excel version offers the latest data to encourage strong decision-making, with thousands of data points presented with every release. View the sample below, taken from the full 120+ page report, featuring OEMs including Rivian, Tesla, NIO & XPENG! Then be sure to follow the link to learn more about our industry leading SDV: E/E Architecture Guide and speak with one of our experts today! https://lnkd.in/gTwAvgyX #sdv #softwaredefinedvehicle #oems

45

KINNOVIA white paper on Generative AI and Automotive Software: Embracing AUTOSAR and Model-Based Design Application of Generative AI in Automotive Software A. Generative AI for AUTOSAR AUTOSAR is a standardized automotive software architecture designed to streamline the development process by creating a more organized method for system integration. Here’s how generative AI can be integrated into this framework: 1. Configuration and Integration • Generative AI can automate the configuration of AUTOSAR environments by predicting optimal settings and parameters based on the specific requirements of a vehicle’s software system. This can reduce human error and speed up the initial setup processes. 2. Component Generation • AI can generate basic software components and modules required in AUTOSAR. By training on a vast dataset of well-designed modules, a generative AI system can produce high-quality, error-free code, thus reducing the manual coding burden on developers. 3. Simulation and Testing • Generative models can be used to create various scenarios for simulation and testing. These AI-generated scenarios can cover a wider range of edge cases than traditional methods, improving the robustness of the software. 4. Documentation Automation • AI can generate and update documentation automatically as changes are made to the software architecture. This ensures that documentation is always up-to-date and reduces the workload for technical writers. B. Generative AI for Model-Based Design (MBD) Model-Based Design is a graphical approach to software development used extensively in the automotive industry, particularly for designing control systems and logic. Generative AI’s role in MBD includes: 1. Model Generation • AI can assist in creating more accurate and efficient models by analyzing existing data and generating predictive models that optimize performance. These AI-enhanced models can lead to better product design and quicker prototyping. 2. Code Generation • Once a model is defined, generative AI can be employed to automatically generate production-quality code that can be deployed directly into automotive systems. This reduces the transition time from design to production and ensures that the generated code is optimized for performance and safety. 3. Simulation Data Generation • Generative AI can create comprehensive datasets that mimic real-world operating conditions, which are essential for testing models developed in MBD. This includes generating sensor data, environmental conditions, and other variables that affect automotive software. 4. Optimization of System Design • AI can analyse the performance of different design choices and suggest optimisations, potentially exploring combinations and configurations that might not be immediately obvious to human designers. Learn more on: https://lnkd.in/dUtf2rt5 #KINNOVIA #Success #Value #Engineering

21

How generative AI will take over roles as code & model generation in the automotive software industry.

3

#Morningtopic #Automotive #Classic #AUTOSAR #security AUTOSAR Key Manager different states of a Certificate: ---------------------------------------------------------------------------------------- For each Certificate in KeyM has a status which represents the current state which can be requested by KeyM_CertGetStatus(). The following description of each status may help you while #debugging in #KeyM: 1. KEYM_CERTIFICATE_NOT_AVAILABLE: This certificate status is entered after initialization of KeyM. 2. KEYM_CERTIFICATE_NOT_PARSED: When the Certificate parsing is in progress, the certificate status shall change to this transient status until the parsing process is completed. 3. KEYM_E_CERTIFICATE_INVALID_FORMAT: If the certificate parse operation detects violations to basic encoding rules or violations to the format. 4. KEYM_CERTIFICATE_PARSED_NOT_VALIDATED: If the parsing operation has been completed without failure. 5. KEYM_E_CERTIFICATE_INVALID_ CHAIN_OF_TRUST: When the subject field of the currently validated certificate is verified with the issuer field of the next upper certificate and the process was failed. 6. KEYM_E_CERTIFICATE_SIGNATURE_FAIL: If the signature verification fails. 7. KEYM_E_CERTIFICATE_VALIDITY_PERIOD_FAIL: If the certificate format type contains a time period, If the comparison of the current time doesn't match the valid period of the certificate. 8. KEYM_E_CERTIFICATE_INVALID_CONTENT: If one of the configured rules for the certificated content are violated. 9. KEYM_CERTIFICATE_VALID: If all verification steps have been performed and no error was detected during the verification. #knowledgeexchange #learnsomethingnew #BeAnExpert => Reference to AUTOSAR Spec. of Key Manager

96

1 Kommentar

Some Practical Challenges in implementing safety Mechanisms

9

This is a really great talk. If you're limited in time, whizz to 8:00 minutes and see examples of CPU overheads in three completely different ECUs. The AUTOSAR RTE really can gobble up a lot of the CPU cake 🍰 Interrupt suspend/copy/resume being done 340,000 times per second is just crazy. And $170m in extra silicon costs for a faster CPU just to run all these interrupt suspend/resume locks is beyond crazy.

73

5 Kommentare

🤔 How is UDS vehicle diagnostics implemented in AUTOSAR base software module? In modern vehicles, diagnostics is required to be performed on all ECUs to ensure that there are no issues with electronically controlled components of the vehicle. Any issue encountered by an automotive ECU is stored as Diagnostics Trouble Code (DTC) in the Electrically Erasable Programmable Read-Only Memory (EEPROM). These codes can be retrieved later using an automotive diagnostic tool. To understand how the diagnostics is implemented in #AUTOSAR architecture, let us quickly revisit the architecture. In the #BaseSoftwareLayer, there are hundreds of software modules including those categorized under the Microcontroller Abstraction Layer (MCAL), ECU Abstraction Layers and Service layer. Our blog focuses on the service layer of the AUTOSAR Base Software Module and decodes how #UDS #VehicleDiagnostics is implemented there - https://lnkd.in/g6RVEka6

19

🚗 🚘 🔋 AUTOSAR Adaptive Platform: Powering the Future of Automotive Systems As the automotive industry drives towards higher levels of autonomy, connectivity, and real-time communication, the AUTOSAR Adaptive Platform is leading the charge with flexible software architecture and robust security. 🔑 Key Features: Service-Oriented Architecture (SOA): Dynamic and modular design for scalable software. High-Performance Computing (HPC): Ideal for advanced driver assistance systems (ADAS) and autonomous driving. Dynamic Memory Management: Efficiently handles complex tasks like image recognition and real-time communication. 🏛️ Architecture: 📌 POSIX-Compliant OS: The platform runs on a POSIX-compliant OS, ensuring compatibility with many real-time operating systems (RTOS) and delivering strict real-time performance for tasks like ADAS and sensor processing. 📌 Middleware & Communication Framework: Some/IP: Enables scalable service-oriented communication within the vehicle, essential for real-time applications. Real-Time Ethernet: High-bandwidth data exchange is supported through Ethernet for critical tasks like ADAS, infotainment, and sensor fusion. 📌 Application Layer: Hosts cloud-based services and vehicle-specific applications like autonomous driving, predictive maintenance, and V2X communication. Cloud Integration: Supports seamless interaction with cloud services for remote processing and updates. Over-the-Air (OTA) Updates: Secure OTA updates ensure vehicles remain up-to-date with the latest software and features. 🔒 Security Features: 📌 Hardware Security Module (HSM): Integrates HSM to securely manage cryptographic keys, ensuring secure boot processes, data encryption, and safe transmission of sensitive data. 📌 Secure Boot: Prevents malicious software from running on the vehicle by only allowing authenticated code during boot. 📌 Data Encryption: Protects data shared between services and vehicles, ensuring confidentiality and integrity. 📌 Identity & Access Management (IAM): Ensures role-based access control (RBAC), so only authorized applications or services can interact with critical vehicle components like the braking system or engine control. 📌 Public Key Infrastructure (PKI): Secures communication between software components using encryption, ensuring only trusted components can access the system. 🚀 Use Cases: Autonomous Driving Vehicle-to-Everything (V2X) Communication Predictive Maintenance The AUTOSAR Adaptive Platform is reshaping the automotive landscape by providing the performance, flexibility, and security required for future mobility in electric vehicles #AUTOSAR #AutomotiveInnovation #AutonomousVehicles #ConnectedCars #Security #FutureTech #CloudIntegration #V2X #HPC #SoftwareDefinedVehicles #PredictiveMaintenance Image below is Classic Autosar. Refer to comment session for Adaptive Autosar diagram

70

6 Kommentare