AUTOSAR and ECU software
Basic software, drivers and application integration for automotive microcontrollers.
- AUTOSAR Classic and Adaptive integration
- BSP, board bring-up and RTOS integration
- Bootloaders and over-the-air update paths
Industries · Automotive & Mobility
ECU software, safety and networks, engineered and verified in India.
AUTOSAR software, ISO 26262 evidence, cybersecurity for UNECE R155, and CAN, LIN and automotive Ethernet validation for the teams building software-defined vehicles. Engineering led from Bengaluru.
01 The challenge
ECU Software, Safety and Networks.
ECU software, ISO 26262 and UNECE R155 evidence, and CAN, LIN and Ethernet validation for ADAS, powertrain, body and connected vehicle platforms.
Software now decides much of what a vehicle does, and it runs across many Electronic Control Units, each with its own safety and security case. GSAS engineers ECU software and produces the verification evidence as the code is written. The safety case, type approval and certification stay with the vehicle manufacturer and its assessor.
The work follows the automotive V-model, from requirements through unit testing and integration. Klocwork and Perforce QAC check code against MISRA and AUTOSAR C++14 rules for ISO 26262 work. TESSY by Razorcat automates unit testing with MC/DC coverage, and Razorcat states it is qualified for ISO 26262. J-Link PRO provides on-target debug and trace, PicoScope decodes CAN, LIN and FlexRay traffic, and our automotive Ethernet capture and validation capability extends the same bench discipline to 100BASE-T1, SOME/IP and DoIP. On the electrical side, ISO 16750-2 supply voltage testing covers the starting profile, voltage drops, reset behaviour and load dump a control unit must survive on a 12 V or 24 V bus.
UNECE R155 and R156 and the EU Cyber Resilience Act add cybersecurity evidence to the safety work. Klocwork and Perforce QAC check code against MISRA, AUTOSAR C++14 and CERT rules in CI, and GSAS engineers secure boot and HSM integration on the ECU. Type approval and the cybersecurity management system stay with the vehicle manufacturer.
02 What we engineer
Six automotive services, mapped onto the vehicle.
Each card lights the part of the vehicle architecture that service touches, from the ECU software stack to the in-vehicle networks it talks over.
- 1. ECU software stack: AUTOSAR, RTOS, BSP
- 2. Safety case: ISO 26262 ASIL A to D
- 3. Gateway and HSM: Secure boot, R155
- 4. CAN and LIN buses: Body and powertrain
- 5. Ethernet backbone: 100/1000BASE-T1
- 6. Test bench: HIL, SIL and CI
-
-
ISO 26262 safety evidence
The verification evidence an assessor expects at each ASIL, produced as the code is written.
- MISRA C:2023 and AUTOSAR C++14 enforcement with deviation records
- Unit testing with statement, branch and MC/DC coverage
- Tool classification and qualification kits under ISO 26262-8
-
Cybersecurity for R155 and R156
Security designed into the ECU, with the evidence a cybersecurity management system needs.
- Secure boot chains and HSM integration
- ISO/SAE 21434 threat analysis and risk assessment support
- Static analysis for CWE and CERT findings in CI
-
CAN, CAN FD and LIN validation
What is actually on the bus, decoded, and the physical layer that carries it.
- CAN and CAN FD capture with J1939, ISO-TP, UDS and OBD-II decode
- Physical-layer checks against ISO 11898-2
- LIN 2.x and SAE J2602 schedule and response-time analysis
-
Automotive Ethernet
Physical layer to diagnostics on the in-vehicle Ethernet backbone.
- 100BASE-T1 and 1000BASE-T1 physical-layer validation
- SOME/IP, DoIP and UDS debugging
- TSN and 802.1AS time synchronisation checks
-
Test benches and regression
ECU tests that run the same way every time, on the bench and in CI.
- HIL and SIL test design
- Scripted bus stimulus and regression captures
- On-target tests and trace through a debug probe
03 How we work
Down the V-model, with evidence at every step.
The same discipline from requirement to ECU on the bench: each stage leaves something an assessor, a homologation engineer or the next team can check.
-
01
Specify
- Safety
- ASIL decomposition inputs, tool classification
- Security
- Threat analysis and risk assessment support
- Coding rules
- MISRA C:2023 and AUTOSAR C++14 baseline
Rules and tools agreed before the first commit
-
02
Build
- Software
- AUTOSAR integration, drivers, bootloader
- Analysis
- Static analysis gating every change in CI
- Unit test
- Requirements-based tests with MC/DC coverage
Findings reach the developer who made the change
-
03
Prove
- On target
- Tests and trace on the real core
- Networks
- CAN, LIN and Ethernet captured and decoded
- Electrical
- ISO 16750-2 supply profiles on a programmable DC bench
Evidence packaged for the safety and security case
- Half-acre build and test site, Bengaluru Rural, opened 2026
- Doddaballapur
- Specialists, engineering led from Bengaluru
- 40+
- In 9 Indian cities
- 11 offices
- Certified by TÜV Rheinland
- ISO 9001:2015
04 Capabilities
The GSAS capability pages behind Automotive & Mobility.
Each service above is a full practice at GSAS. These are the pages that describe it in depth.
- Embedded Software Engineering AUTOSAR Classic & Adaptive, firmware, RTOS integration, BSP development for automotive MCUs.
- Safety & Compliance Engineering ISO 26262 ASIL A-D verification evidence: MISRA enforcement, MC/DC unit testing and tool qualification documentation under ISO 26262-8.
- Testing & Verification Unit testing, MC/DC coverage, static analysis, HIL/SIL test bench design.
- Training & Enablement ISO 26262 for Software Engineers, MISRA C compliance and Keil MDK Essentials workshops for automotive teams.
- Automotive Ethernet 100BASE-T1 and 1000BASE-T1 capture and validation, SOME/IP and DoIP analysis, gPTP time sync.
05 Tools
The tools Automotive & Mobility teams use, and GSAS engineers use too.
GSAS is a value added distributor/reseller for these products. We have a dedicated FAE team ready to help you with custom built solutions matching your needs.
-
Perforce Klocwork Klocwork by Perforce is a scalable SAST tool for C, C++, C#, Rust, Java, JavaScript, Python, and Kotlin, built for DevSecOps with incremental analysis, MISRA, CERT, and CWE enforcement, and TUV SUD certified ISO 26262 and IEC 61508 tool qualification. Deployed and supported across India by GSAS. -
Perforce Perforce QAC MISRA compliance analysis tool for C and C++ with qualification kits for automotive and safety-critical certification. India pricing and local support from GSAS. -
Razorcat TESSY Automated dynamic unit, module, and integration testing for embedded C/C++ with MC/DC coverage. Qualified by Razorcat for safety-related software development per IEC 61508, IEC 62304, ISO 26262 and EN 50128. Buy in India from GSAS. -
SEGGER J-Link PRO Professional JTAG/SWD debug probe with USB and Ethernet connectivity, supporting Arm Cortex-M/A/R and RISC-V architectures. India pricing and local support from GSAS. -
Pico Technology PicoScope 4824A Pico Technology PicoScope 4824A, 8-channel, 12-bit USB 3.0 PC oscilloscope with 20 MHz bandwidth, 80 MS/s sampling and 256 MS deep capture memory, plus a built-in 80 MS/s 14-bit AWG and serial decoding for CAN, LIN, FlexRay, I2C, I2S, SPI and UART. Available in India from GSAS Micro Systems with probe selection, applications support and GST-compliant quotations.
06 Standards
Standards listed for Automotive & Mobility, and the tools placed against each.
A chip shows a published qualification scope where one exists, and the bare standard name where none does.
AUTOMOTIVE ISO 26262
REGULATION EU Cyber Resilience Act
CYBERSECURITY UNECE R155/R156
CODING STANDARDS MISRA C:2023
CODING STANDARDS AUTOSAR C++14
| Tool | Applicable Standards |
|---|---|
| Klocwork (Perforce) | ISO 26262 up to ASIL DMISRA C:2023UNECE R155/R156EU Cyber Resilience Act |
| Perforce QAC | ISO 26262 up to ASIL DMISRA C:2023AUTOSAR C++14 |
| Arm Compiler for Embedded FuSa | ISO 26262 ASIL D (qualified releases) |
| embOS-Safe (SEGGER) | ISO 26262 ASIL D |
| emCrypt (SEGGER) | UNECE R155/R156EU Cyber Resilience Act |
| TESSY (Razorcat) | ISO 26262 |
07 Working together
Three ways to start, depending on where your programme is.
A vehicle programme, an ECU on a supplier’s bench, or a new EV platform.
-
01
OEM programmes
Platforms and vehicle integration
Engineering capacity for software-defined vehicle platforms: AUTOSAR integration, network validation across CAN, LIN and Ethernet, and the security evidence UNECE R155 type approval asks for.
- AUTOSAR Classic and Adaptive
- Network validation
- R155 and R156 evidence
-
02
Tier-1 suppliers
ECUs to an OEM specification
ISO 26262 verification evidence produced alongside the code: MISRA enforcement, unit tests with MC/DC coverage, tool qualification, and test benches that rerun on every change.
- ASIL A to D evidence
- Tool qualification
- HIL and SIL benches
-
03
EV and new-mobility start-ups
First platform to production
Battery management, motor control and gateway software for a first platform, with the safety and security groundwork in place before the programme scales.
- BMS and motor control
- Safety and security groundwork
- Production flashing
08 Contact
Building an ECU or a vehicle platform?
Tell us the ECU, the ASIL and the networks it sits on. GSAS replies from Bengaluru with scope and a proposal: software, safety and security evidence, and bus validation.
Questions
Automotive & Mobility engineering with GSAS in India
What automotive engineering services does GSAS provide in India?
GSAS provides AUTOSAR and ECU software engineering, ISO 26262 verification evidence, cybersecurity engineering for ISO/SAE 21434 and UNECE R155, CAN, CAN FD and LIN validation, automotive Ethernet testing, and HIL and SIL test benches. Engineering is led from Bengaluru.
Can GSAS help us produce ISO 26262 evidence for an ASIL D ECU?
Yes. GSAS enforces MISRA C:2023 and AUTOSAR C++14 with deviation records, writes requirements-based unit tests with MC/DC coverage, and classifies how each tool is used, deploys the vendor qualification kits and helps prepare the tool documentation for your ISO 26262-8 activity. Hazard analysis and the safety case stay in your safety process. This work produces the evidence for them.
Does GSAS work on UNECE R155 and R156 cybersecurity?
GSAS engineers the ECU side: secure boot chains, HSM integration, ISO/SAE 21434 threat analysis support and static analysis for CWE and CERT findings. Type approval and the cybersecurity management system remain with the vehicle manufacturer.
Can GSAS validate CAN, LIN and automotive Ethernet networks?
Yes. GSAS captures and decodes CAN and CAN FD traffic, checks the physical layer against ISO 11898-2, analyses LIN schedules, and validates 100BASE-T1 and 1000BASE-T1 links with SOME/IP, DoIP and UDS debugging.
Does GSAS also supply the automotive tools?
Yes. GSAS is a value added distributor/reseller for the static analysis, unit test, debug and bus analysis tools on this page, and its engineers use the same tools on customer projects.
Blog
Latest Thinking: Automotive & Mobility
J-Link SEGGER Automotive & Mobility
J-Link Is Now Validated by ST for StellarStudio
STMicroelectronics has fully validated SEGGER J-Link for StellarStudio, the IDE for its Stellar automotive MCU family, and put the probe into continuous validation at Le Mans. What that changes for the toolchain review on a Stellar programme, from GSAS, an authorized engineering partner for SEGGER in India.
13 Sept 2026 · 2 min read
Automotive Ethernet Automotive & Mobility
100BASE-T1 Link Won't Come Up: A Vendor-Neutral Checklist
A 100BASE-T1 link that will not come up is almost never a mystery, but the answers on the web are written per silicon vendor and do not transfer. This is the ordered bring-up checklist that holds regardless of which PHY, switch or SoC you have: physical layer first, then the PHY over MDIO, then the master and slave pairing, then the causes of a link that comes up and drops. The standards and tooling claims trace to IEEE 802.3 task force records, the Linux ethtool and kernel documentation or published test material. Written by the GSAS Micro Systems engineering team in India.
29 Aug 2026 · 14 min read
Automotive Ethernet Automotive & Mobility
100BASE-T1 Media Converters: How to Choose One
Search for a 100BASE-T1 media converter and you get SKU pages that document their own DIP switches, plus a pile of copper-to-fibre converters that have nothing to do with single-pair automotive Ethernet. This is the selection guide neither publishes: what the box does at the PHY layer, when a converter is the wrong box, and the nine criteria that decide fitness, each written as a question to put to the supplier rather than a specification we invented. Standards claims trace to IEEE 802.3 task force records and the public OPEN Alliance specifications. Written by the GSAS Micro Systems engineering team in India.
29 Aug 2026 · 13 min read
Automotive Ethernet Automotive & Mobility
10BASE-T1S and PLCA: Multidrop Ethernet Explained
10BASE-T1S is the one member of the T1 single-pair Ethernet family that keeps a shared medium, and PLCA is the reconciliation sublayer that stops the nodes on it from colliding. This article covers what IEEE 802.3cg standardises, how the beacon and transmit opportunities schedule a cycle, the node count and segment length figures the OPEN Alliance interoperability test suite works to, and the failure modes that put a segment quietly back into contention while every link still looks up. Written by the GSAS Micro Systems engineering team in India for teams bringing up multidrop segments on the bench.
29 Aug 2026 · 12 min read
Automotive Ethernet Automotive & Mobility
ADAS Sensor Data Logging: Bandwidth Budgets That Add Up
Every page that tells you an ADAS test vehicle produces terabytes a day states the headline and skips the arithmetic, so you cannot redo it for your own sensor set. This article publishes the arithmetic instead: one formula, every table row derived on the page, a worked eight-hour drive that chains those rows into a sustained write rate, a media count and an offload window, and the five places bandwidth budgets go wrong. Written by the GSAS Micro Systems engineering team in India.
29 Aug 2026 · 15 min read
Automotive Ethernet Automotive & Mobility
Automotive Data Loggers: Capture Without Loss
Search for an automotive data logger and the results split into cheap OBD dongles at one end and enterprise ADAS recorders at the other, with nothing in between explaining the engineering that decides whether you lose frames. This is the loss budget end to end: mirror oversubscription upstream of the logger, encapsulation overhead on the capture path, sustained write rate against burst rate, rotation stalls, and storage arithmetic worked in full so you can redo it with your own numbers instead of trusting ours. Written by the GSAS Micro Systems engineering team in India.
29 Aug 2026 · 13 min read
Automotive Ethernet Automotive & Mobility
Automotive Ethernet Connectors: H-MTD, MATEnet, MQS
An ECU arrives on the bench with a connector nobody has a mate for, and the day is gone. Search the family names and you get connector product pages that describe their own part and stop there. This article puts the families side by side in one table using only what their public pages state, then makes the point those pages leave out: the IEEE link segment definition, not the connector, is what sets reach and loss limits, and shielding is a channel decision rather than a preference. Written by the GSAS Micro Systems engineering team in India.
29 Aug 2026 · 12 min read
Automotive Ethernet Automotive & Mobility
Automotive Ethernet Conformance: TC8 and Testing Above It
Summarising TC8 as a layer 1 to layer 4 suite is wrong in both directions. The public OPEN Alliance ECU test documents run from transmitter distortion up to a SOME/IP chapter with its own standardised test stub, and they contain exactly one time synchronisation test case. This is what those documents enumerate, chapter by chapter, what genuinely lives above their boundary, why a passing ECU can still fail against a partner node, and how much pre-compliance work a Tier-1 in India can honestly do in-house before a test house visit. Written by the GSAS Micro Systems engineering team in India.
29 Aug 2026 · 12 min read
Automotive Ethernet Automotive & Mobility
How to Choose an Automotive Ethernet Switch for the Lab
Search for an automotive Ethernet switch and you get silicon selection tables written for the engineer choosing a die for a zonal controller. The person searching from a validation lab wants a boxed switch that reproduces a vehicle network on a bench, and finds nothing addressed to them. This is that guide: how to separate the two products, how to count the ports you actually need, and an eight-row scoring matrix written as questions to put to a supplier rather than specifications we invented. Standards and documentation claims trace to IEEE 802.1 and 802.3, ASAM, AUTOSAR, the IETF and public Linux and Wireshark documentation. Written by the GSAS Micro Systems engineering team in India.
29 Aug 2026 · 13 min read
Automotive Ethernet Automotive & Mobility
The T1 Family Explained: 10BASE-T1S to Multi-Gig 802.3ch
The T1 family is the set of single-pair Ethernet physical layers used in vehicles, and every member is documented separately inside a different datasheet. This guide puts all of them in one table with rate, symbol rate, line code, specified reach and cabling traced to public IEEE task force documents, then answers the two questions that keep coming back: why 100BASE-T1 has no auto-negotiation, and why one end has to be master. Written by the GSAS Micro Systems engineering team in India.
29 Aug 2026 · 13 min read
Automotive Ethernet Automotive & Mobility
CAN vs Automotive Ethernet: When to Use Each
CAN and automotive Ethernet answer different questions, so the useful comparison is a decision table rather than a winner. This guide from GSAS Micro Systems sets CAN and CAN FD figures from CAN in Automation next to the IEEE 802.3bw objectives for 100BASE-T1, covers arbitration against switch queues, cost and harness consequences, failure modes on both sides, and what changes on an India bench team's setup when a project adds Ethernet next to the CAN it already runs.
29 Aug 2026 · 14 min read
Automotive Ethernet Automotive & Mobility
Buying Automotive Ethernet Test Gear in India
Search for a 100BASE-T1 tap or a T1 to RJ45 media converter from India and the results are fibre media converters and LAN cable testers, none of which are T1, and no forum thread that has been through the purchase. This is the missing page: the capability table for a first bench with a defer-or-borrow column, an honest account of what is stocked here versus imported to order, the parts that make up a landed cost as a structure rather than a number, and the compliance portals your teams will actually use. No prices, no duty rates and no lead-time bands, because all three change and none of them belong in an article. Written by the GSAS Micro Systems engineering team in India.
29 Aug 2026 · 13 min read