Skip to main content
Functional Safety for Indian Automotive and EMS: Meeting ISO 26262 and IEC 61508, featured image

Functional Safety for Indian Automotive and EMS: Meeting ISO 26262 and IEC 61508

GSAS Editorial · · 3 min read

What Is Functional Safety?

Functional safety is the automatic protection layer that prevents physical injury or health damage caused by malfunctioning electronic systems. It is NOT general cybersecurity, it specifically addresses the question: “If this software fails, will someone get hurt?”

For any electronic control unit that influences vehicle dynamics, braking, steering, battery management, or rider assistance, functional safety certification is mandatory for export to EU and US markets. Indian OEMs and Tier-1 suppliers building for global customers face this requirement head-on.

The Standards Landscape

The functional safety ecosystem spans multiple industry-specific standards, all derived from IEC 61508:

StandardIndustrySafety LevelsKey Requirement
ISO 26262AutomotiveASIL A–DHazard analysis, FMEA, MC/DC coverage
IEC 61508IndustrialSIL 1–4Safety integrity lifecycle
IEC 62304Medical devicesClass A–CSoftware lifecycle processes
EN 50128 / EN 50716RailwaySIL 0–4Software for railway control
DO-178CAerospaceDAL A–EDesign assurance levels

Each standard defines which tools must be qualified, what coding standards must be enforced (MISRA C, AUTOSAR C++14), and what traceability evidence assessors require.

Why This Matters for India Now

India’s automotive and two-wheeler electronics ecosystem is at an inflection point:

  • Two-wheeler OEMs (Hero, Bajaj, TVS, Honda) are integrating ADAS features, forward collision warning, blind spot detection, and lane change assist, that fall under ISO 26262 ASIL B and above
  • Tier-1 suppliers (Minda and other major Indian and global Tier-1s) are increasingly required by European OEM customers to demonstrate ISO 26262 compliance, 52% of automotive teams now comply due to customer mandates (Perforce 2026 Report)
  • EV battery management systems for two-wheelers and commercial vehicles require functional safety assessment for cell balancing, thermal management, and charge control algorithms
  • Medical device exporters in Bangalore and Hyderabad must demonstrate IEC 62304 compliance for software in cardiac monitors, infusion pumps, and diagnostic equipment

The cost of non-compliance is not just a failed audit, it is exclusion from global markets.

The GSAS Functional Safety Toolchain

Building safety-certified software requires tools that are themselves qualified for use in safety-critical development. GSAS provides a complete, certified toolchain from four partner OEMs:

Static Analysis and Compliance: Perforce

Helix QAC is the reference implementation for MISRA C/C++ compliance checking, with TÜV SÜD-certified tool qualification kits for ISO 26262 ASIL D, IEC 61508 SIL 4, IEC 62304 Class C, and DO-178C DAL A. Klocwork extends coverage to multi-language SAST with AI-assisted remediation and TÜV SÜD certification for ASIL D.

Certified Compiler and Runtime: Arm

Arm Compiler for Embedded FuSa and Arm FuSa RTS provide a TUV SUD-qualified compiler and C runtime library for Arm Cortex-M and Cortex-R, the architectures powering the majority of automotive and industrial MCUs in India. Per Arm’s published AC6 FuSa product page, qualified releases are certified to ISO 26262 ASIL D (Automotive), IEC 61508 SIL 3 (Industrial), railway software at SIL 4, and IEC 62304 Class C (Medical). Arm names the specific railway standard revision on the certificate issued for each qualified release, so talk to GSAS for the railway certification scope that applies to the release you plan to certify against. DO-178C (aerospace) is not in Arm’s current qualification scope for AC6 FuSa.

Safety-Qualified RTOS: Segger

Segger embOS provides a deterministic RTOS with safety qualifications, sub-microsecond interrupt latency, and zero-interrupt-latency architecture. Combined with SystemView for runtime analysis and J-Link for debug, Segger completes the runtime layer of the safety stack.

Unit Testing and Verification: Razorcat

TESSY delivers automated unit and integration testing with MC/DC coverage analysis, the coverage metric required by ISO 26262 ASIL D. TÜV SÜD-qualified, with classification tree method for systematic test case generation.

From Tools to Certification

Having the right tools is necessary but not sufficient. GSAS provides the engineering services that bridge the gap between tool deployment and successful assessment:

  • MISRA and SAST workshops delivered across India’s automotive belt (Pune, Chennai, Bengaluru, NCR)
  • Tool qualification documentation: TÜV SÜD kit deployment and assessor-ready evidence packages
  • CI/CD pipeline integration: automated static analysis, unit testing, and coverage reporting in Jenkins, GitLab CI, and Azure DevOps
  • MISRA baseline establishment: initial scan, violation triage, suppression workflow, and deviation documentation

Whether your team is preparing for its first ISO 26262 assessment or scaling functional safety processes across multiple ECU programs, GSAS provides the local expertise and certified toolchain to get there.

Request a functional safety toolchain evaluation →

Interested in Perforce tools?

Talk to our application engineers for personalized tool recommendations.

Stay in the Loop

Get monthly compliance updates, product insights, and engineering best practices delivered to your inbox.

Related Articles

Classification tree and combination table used to design embedded unit test cases in Razorcat's Classification Tree Editor for TESSY, available in India from GSAS Micro Systems
Compliance & Safety Razorcat Automotive & Mobility

Test Case Design with the Classification Tree Method: Deriving Unit Tests You Can Defend in an Audit

Ad-hoc test cases can be perfectly good tests and still fail an audit, because nothing on file records why that particular set was sufficient. The Classification Tree Method derives test cases from the input space instead: identify the test-relevant aspects as classifications, partition each into equivalence classes, then combine leaf classes in a combination table. Razorcat implements CTM in the Classification Tree Editor, available integrated into TESSY or standalone. GSAS Micro Systems is the authorized Razorcat engineering partner for India, the UAE and Sri Lanka.

1 Aug 2026 · 10 min read
Fault injection and robustness testing for safety-related embedded C and C++ software, explained for Indian engineering teams by GSAS Micro Systems, the authorized Razorcat engineering partner
Compliance & Safety Razorcat Automotive & Mobility

Fault Injection and Robustness Testing for Embedded Software: What ISO 26262, IEC 61508 and DO-178C Actually Ask For

Every safety-related unit contains code that correct inputs never execute: range checks, error returns, timeouts, recovery paths. The functional safety standards require that code to be verified, and they are explicit about how. ISO 26262-6 lists fault injection test as a method for both software unit verification and software integration verification; IEC 61508-3 recommends defensive programming from SIL 2 upward and then concedes that defensive code is exactly what stops teams reaching 100 percent structural coverage. This guide separates robustness testing from fault injection, maps each to the obligation that asks for it, and shows how Razorcat implements automated fault injection in TESSY without leaving instrumentation in production code.

1 Aug 2026 · 11 min read
Buyer-side evaluation framework for embedded unit testing tools, covering compiler and debugger fit, on-target execution, coverage levels and qualification evidence, from GSAS Micro Systems in India
Compliance & Safety Razorcat Automotive & Mobility

How to Evaluate a Unit Testing Tool for Embedded Software: A Buyer's Framework for Indian Teams

Unit test tool evaluations rarely fail on features. They fail because the tool cannot drive the compiler and debugger the project is already committed to, or because the evidence it produces sits outside the scope of the certificate the assessor asks for. This is a buyer-side framework: six questions, what a credible answer looks like in vendor documentation, and a four-week pilot that measures the answers instead of accepting them.

1 Aug 2026 · 10 min read