The project involved ensuring the cybersecurity
compliance of the Stellantis STLA Brain Platform. This included the analysis of
item definition, performing the Threat Analysis and Risk Assessment (TARA) at
the item level, Identify the threats and cybersecurity controls as well as the
cybersecurity requirements. System and software teams were guided to realize
the cybersecurity controls and validate the cybersecurity requirements.
Standard/Protocol
ISO 21434
Contribution
This project involved the creation of a process
landscape for the development of cybersecurity critical systems and software
development based on ASPICE. This includes the definition of the process,
tailoring rules, guidelines, and best practices along with the creation of
templates. All the ASPICE processes in the scope of VDA and the processes under
ASPICE for cybersecurity are covered.
Standard/Protocol
Contribution
Standard/Protocol:
ISO 21434
Contribution:
Asset identification for the defined Item boundary for
more than 40 ECUs. Identification of possible attacks on the assets and
violation of security property. Analysis of possible impact and identification
of risk associated with the asset. Derive security requirements and test cases
based on requirements.
Standard/Protocol:
ISO 21434
Contribution:
The product ?Gear Select Lever? consists of mechanics,
including the select lever itself, electronics, including hall sensors and a
microcontroller, and software. The software is AUTOSAR 4.3.0 compliant. The
product realizes a human-machine interface to the powertrain. The interface
between the Gear Select Lever and the powertrain includes digital communication
via the CAN bus. The product has been assigned safety goals up to ASIL B.
The software also supported Software updates using cryptographic algorithms like SHA, AES, and RSA and required compliance with UNECE WP29. The software also supported the Over the Air (OTA) update.
Standard/Protocol:
AUTOSAR 4.0, ISO26262 (ASIL B), UNECE WP29
FuSa Contribution:
The project BMW CCU is based on the development of the charger control
unit for next-generation BMW electric vehicles. The project involves a
distributed development environment with teams working in different regions.
The project activities include the complete responsibility for planning the qualification activities, reviewing the safety artifacts, and supporting and guiding the safety team and developers in safety-relevant development activities.
Standard/Protocol:
AUTOSAR 4.0, ISO26262
FuSa Contribution:
Escrypt GmbH is the developer of the CycurCSM tool, a
code generator that generates a standard AUTOSAR 4 BSW component CSM (Crypto
Service Manager), responsible for acting as the interface to the Hardware
Security Module functioning as the security peripheral. The component enables
the communication between the Application Software Component to the Hardware
Security Module through AUTOSAR APIs and other predefined APIs.
The project involved creating safety artifacts such as Safety Plan, FMEA, Software Verification Plan, Software Verification Specification, Tool Qualification report, and constant communication with Tüv Nord for a safety audit, assessment, etc.
Standard/Protocol:
AUTOSAR 4.0, ISO26262 (ASIL B)
Contribution:
This project is about the keyless go features for
Daimler trucks. It contains many prime
components such as Start-Stop systems, Klemen Control Module, etc.
The scope of work is to perform the requirement analysis, design, and development of the Start-Stop system. It includes coding the CDD driver and the development of the Application part in the Matlab/Simulink/TargetLink toolchain. The implementation includes reading the Start-Stop button status from the hardware using ADC/Microcontroller registers and deciding the keypress with plausible voltage values. It also includes the implementation of the safety mechanism and Diagnostic service in both CDD and the Model. Also performed Integration and testing of software along with the Autosar BSW stack.
Standard / Protocol: AUTOSAR 4.0.1, ISO26262, XCP 2.03.1, E2E, CAN, ASPICE
Actuator:
Daimler Start-Stop switch
Contribution:
The sophisticated technology in Open-Path gas detection - the Dräger Polytron Pulsar 3 is focused on the detection of a range of gaseous hydrocarbons. This includes alkanes from methane to hexane, propylene, ethylene, methanol, and ethanol. Equipped with either a terminal box or a certified cable entry point, the detector incorporates flexible installation. The continuous communication between Receiver and Transmitter across a signal line allows the system to adapt to difficult environmental conditions and ensure the highest availability.
Scope of work was to perform the safety critical Integration and Unit testing using HITEX Tessy aiming at MCDC coverage for the safety component. Also performing regression testing on various internal safety-critical modules and analyzing results on Jenkins build server. Also involved in the detection of bugs during the testing, regular discussions with developers, and making MANTIS entry of bugs as per the software testing process.
Actuator:
Dräger Polytron Pulsar 3
Contribution:
BMW M decided to migrate the existing project into the AUTOSAR environment including the safety composition. It also includes the change of ECU from Bosch to Melecs. The eLSD is used in the vehicle traction control system to maintain the proper torque between both wheels. Due to the under/over steering or slippery road conditions when any of the tires start spinning faster than others, eLSD will reduce the torque supplied to it to reduce the speed.
The project included new feature addition and modification of code as per AUTOSAR standards, and the creation of a wrapper layer for the communication between the application and basic software level. Integration involved application software along with the basic software, complex device drivers, COM, and BMW BAC module. Integration testing was part of the project where the entire software is tested with the help of CAN communication.
Actuator:
Electronic Limited Slip Differential
Standard/Protocol:
AUTOSAR 4.0.1, ISO26262, XCP 2.03.1, E2E, CAN, FlexRay
Contribution:
BMW Power Electronic Group (EA-412 Hybrid/Electric cars) had decided to transform the existing Power Electronic compositions into AUTOSAR compliant & ISO26262 compliance, with the usage of AUTO CODE generation using BACE (BMW Auto Code Environment) tool. BACE tool works along with MATLAB/Simulink and auto-generates the code using custom BMW libraries.
This project involves building and integrating generated auto code for BMW Electric/Hybrid vehicle compositions such as Hybrid manager, dog clutch, etc. Autosar-compliant code generation is performed by the model received from the developer. Errors are fixed in the model and build is performed. Performing debugging and fixing the toolchain errors. Also performed static code analysis on the deliverable code.
Standard/Protocol:
AUTOSAR 4.0.1
Contribution:
This is a development cum maintenance project for
different body control
features of a car like a Sunroof, Wiper washer, Convertible roof, and Power window. This
project includes maintenance of the existing features and enhancement and bug
fixes for the body control
Modules. Issues were analyzed and fixed in the models, and also new
features/change request was implemented in the model, and AUTOSAR-compliant
code was generated for functional testing. For the issue reported or change
requested, SIL testing has been carried out with AUTOSAR-compliant code.
BMW decided to migrate the model from the ASCET environment to MATLAB toolchain with code generation using TargetLink. Most of the features were re-modeled with MATLAB toolchain and AUTOSAR-compliant code is generated using DSpace TargetLink.
Standard/Protocol:
AUTOSAR 3.x
Contribution:
The Knock sensor will sense the knock occurring inside
the engine as an analog signal and converts it into electrical form. This
process includes Detection, Processing & Envelope Detection of the signal.
Signal processing is carried out with the help of digital IIR filters and
envelope detectors using Simulink
blocks. The knock is detected at the particular interval of the Crank angle.
This signal is passed to the ECU to prevent further knocks by retarding fuel
injection.
Autosar-compliant code is generated using the Dspace TargetLink, which also included the creation of the data dictionary. Real-time simulation is performed on the designed model using dSPACE Control Desk, where output is monitored on the control desk panels.
Standard/Protocol:
AUTOSAR 3.x, ISO26262
Contribution
Role: Model-Based Designer
Customer: BMW AG
Standard/Protocol:
AUTOSAR 4.0.1, ISO26262
Contribution:
6 Months: Power Window Safety Mechanism
Role: Functional Test Engineer
Customer: BMW AG
PWSM is the safety mechanism used for the power windows in the latest BMW cars. When some of the functionalities get corrupted in power window, PWSM will take control and allows the necessary minimum functionality. This component was of ASIL level B, which was designed in C++ language. The scope was to write test cases which satisfy ASIL level B. The ISO26262-compliant tool TcEd was used for the test case design along with the manual C++ test cases. Also, the Google test framework was designed for the unit testing. Software: Autosar Builder, ASIM, TcEd, Google Test
Standard/Protocol:
ISO26262
Contribution:
Educational Qualification
VTU Belgaum, India
BACHELOR of Engineering (Electronics & Communication)
Certification
The project involved ensuring the cybersecurity
compliance of the Stellantis STLA Brain Platform. This included the analysis of
item definition, performing the Threat Analysis and Risk Assessment (TARA) at
the item level, Identify the threats and cybersecurity controls as well as the
cybersecurity requirements. System and software teams were guided to realize
the cybersecurity controls and validate the cybersecurity requirements.
Standard/Protocol
ISO 21434
Contribution
This project involved the creation of a process
landscape for the development of cybersecurity critical systems and software
development based on ASPICE. This includes the definition of the process,
tailoring rules, guidelines, and best practices along with the creation of
templates. All the ASPICE processes in the scope of VDA and the processes under
ASPICE for cybersecurity are covered.
Standard/Protocol
Contribution
Standard/Protocol:
ISO 21434
Contribution:
Asset identification for the defined Item boundary for
more than 40 ECUs. Identification of possible attacks on the assets and
violation of security property. Analysis of possible impact and identification
of risk associated with the asset. Derive security requirements and test cases
based on requirements.
Standard/Protocol:
ISO 21434
Contribution:
The product ?Gear Select Lever? consists of mechanics,
including the select lever itself, electronics, including hall sensors and a
microcontroller, and software. The software is AUTOSAR 4.3.0 compliant. The
product realizes a human-machine interface to the powertrain. The interface
between the Gear Select Lever and the powertrain includes digital communication
via the CAN bus. The product has been assigned safety goals up to ASIL B.
The software also supported Software updates using cryptographic algorithms like SHA, AES, and RSA and required compliance with UNECE WP29. The software also supported the Over the Air (OTA) update.
Standard/Protocol:
AUTOSAR 4.0, ISO26262 (ASIL B), UNECE WP29
FuSa Contribution:
The project BMW CCU is based on the development of the charger control
unit for next-generation BMW electric vehicles. The project involves a
distributed development environment with teams working in different regions.
The project activities include the complete responsibility for planning the qualification activities, reviewing the safety artifacts, and supporting and guiding the safety team and developers in safety-relevant development activities.
Standard/Protocol:
AUTOSAR 4.0, ISO26262
FuSa Contribution:
Escrypt GmbH is the developer of the CycurCSM tool, a
code generator that generates a standard AUTOSAR 4 BSW component CSM (Crypto
Service Manager), responsible for acting as the interface to the Hardware
Security Module functioning as the security peripheral. The component enables
the communication between the Application Software Component to the Hardware
Security Module through AUTOSAR APIs and other predefined APIs.
The project involved creating safety artifacts such as Safety Plan, FMEA, Software Verification Plan, Software Verification Specification, Tool Qualification report, and constant communication with Tüv Nord for a safety audit, assessment, etc.
Standard/Protocol:
AUTOSAR 4.0, ISO26262 (ASIL B)
Contribution:
This project is about the keyless go features for
Daimler trucks. It contains many prime
components such as Start-Stop systems, Klemen Control Module, etc.
The scope of work is to perform the requirement analysis, design, and development of the Start-Stop system. It includes coding the CDD driver and the development of the Application part in the Matlab/Simulink/TargetLink toolchain. The implementation includes reading the Start-Stop button status from the hardware using ADC/Microcontroller registers and deciding the keypress with plausible voltage values. It also includes the implementation of the safety mechanism and Diagnostic service in both CDD and the Model. Also performed Integration and testing of software along with the Autosar BSW stack.
Standard / Protocol: AUTOSAR 4.0.1, ISO26262, XCP 2.03.1, E2E, CAN, ASPICE
Actuator:
Daimler Start-Stop switch
Contribution:
The sophisticated technology in Open-Path gas detection - the Dräger Polytron Pulsar 3 is focused on the detection of a range of gaseous hydrocarbons. This includes alkanes from methane to hexane, propylene, ethylene, methanol, and ethanol. Equipped with either a terminal box or a certified cable entry point, the detector incorporates flexible installation. The continuous communication between Receiver and Transmitter across a signal line allows the system to adapt to difficult environmental conditions and ensure the highest availability.
Scope of work was to perform the safety critical Integration and Unit testing using HITEX Tessy aiming at MCDC coverage for the safety component. Also performing regression testing on various internal safety-critical modules and analyzing results on Jenkins build server. Also involved in the detection of bugs during the testing, regular discussions with developers, and making MANTIS entry of bugs as per the software testing process.
Actuator:
Dräger Polytron Pulsar 3
Contribution:
BMW M decided to migrate the existing project into the AUTOSAR environment including the safety composition. It also includes the change of ECU from Bosch to Melecs. The eLSD is used in the vehicle traction control system to maintain the proper torque between both wheels. Due to the under/over steering or slippery road conditions when any of the tires start spinning faster than others, eLSD will reduce the torque supplied to it to reduce the speed.
The project included new feature addition and modification of code as per AUTOSAR standards, and the creation of a wrapper layer for the communication between the application and basic software level. Integration involved application software along with the basic software, complex device drivers, COM, and BMW BAC module. Integration testing was part of the project where the entire software is tested with the help of CAN communication.
Actuator:
Electronic Limited Slip Differential
Standard/Protocol:
AUTOSAR 4.0.1, ISO26262, XCP 2.03.1, E2E, CAN, FlexRay
Contribution:
BMW Power Electronic Group (EA-412 Hybrid/Electric cars) had decided to transform the existing Power Electronic compositions into AUTOSAR compliant & ISO26262 compliance, with the usage of AUTO CODE generation using BACE (BMW Auto Code Environment) tool. BACE tool works along with MATLAB/Simulink and auto-generates the code using custom BMW libraries.
This project involves building and integrating generated auto code for BMW Electric/Hybrid vehicle compositions such as Hybrid manager, dog clutch, etc. Autosar-compliant code generation is performed by the model received from the developer. Errors are fixed in the model and build is performed. Performing debugging and fixing the toolchain errors. Also performed static code analysis on the deliverable code.
Standard/Protocol:
AUTOSAR 4.0.1
Contribution:
This is a development cum maintenance project for
different body control
features of a car like a Sunroof, Wiper washer, Convertible roof, and Power window. This
project includes maintenance of the existing features and enhancement and bug
fixes for the body control
Modules. Issues were analyzed and fixed in the models, and also new
features/change request was implemented in the model, and AUTOSAR-compliant
code was generated for functional testing. For the issue reported or change
requested, SIL testing has been carried out with AUTOSAR-compliant code.
BMW decided to migrate the model from the ASCET environment to MATLAB toolchain with code generation using TargetLink. Most of the features were re-modeled with MATLAB toolchain and AUTOSAR-compliant code is generated using DSpace TargetLink.
Standard/Protocol:
AUTOSAR 3.x
Contribution:
The Knock sensor will sense the knock occurring inside
the engine as an analog signal and converts it into electrical form. This
process includes Detection, Processing & Envelope Detection of the signal.
Signal processing is carried out with the help of digital IIR filters and
envelope detectors using Simulink
blocks. The knock is detected at the particular interval of the Crank angle.
This signal is passed to the ECU to prevent further knocks by retarding fuel
injection.
Autosar-compliant code is generated using the Dspace TargetLink, which also included the creation of the data dictionary. Real-time simulation is performed on the designed model using dSPACE Control Desk, where output is monitored on the control desk panels.
Standard/Protocol:
AUTOSAR 3.x, ISO26262
Contribution
Role: Model-Based Designer
Customer: BMW AG
Standard/Protocol:
AUTOSAR 4.0.1, ISO26262
Contribution:
6 Months: Power Window Safety Mechanism
Role: Functional Test Engineer
Customer: BMW AG
PWSM is the safety mechanism used for the power windows in the latest BMW cars. When some of the functionalities get corrupted in power window, PWSM will take control and allows the necessary minimum functionality. This component was of ASIL level B, which was designed in C++ language. The scope was to write test cases which satisfy ASIL level B. The ISO26262-compliant tool TcEd was used for the test case design along with the manual C++ test cases. Also, the Google test framework was designed for the unit testing. Software: Autosar Builder, ASIM, TcEd, Google Test
Standard/Protocol:
ISO26262
Contribution:
Educational Qualification
VTU Belgaum, India
BACHELOR of Engineering (Electronics & Communication)
Certification