Skip to main content

Capabilities · Embedded Software

Firmware from first silicon to the field update.

Board bring-up, RTOS and Linux integration, AUTOSAR Classic and Adaptive, edge AI, bootloaders and compiler migration on Arm Cortex-M, Cortex-A, Cortex-R and RISC-V, written in India by engineers who also design the boards it runs on.

  1. 01 What we build
  2. 02 How we work
  3. 04 How to start
01

Seven kinds of firmware work, one stack.

Organised by what a programme needs done. Each card lights the layer of the firmware stack it works on, from the silicon up to the application.

The embedded firmware stack, from silicon to application, with the tool chain beside it, numbered as on the capability cards Application · on-device inference TFLite Micro · CMSIS-NN 6 Middleware · AUTOSAR BSW and RTE Classic · Adaptive 5 RTOS · Embedded Linux RTX5 · embOS · FreeRTOS · Zephyr · Yocto 4 BSP · drivers · MCAL Clocks · memory · peripherals · device tree 3 Bootloader · OTA update MCUboot · U-Boot · dual-bank · rollback 2 M A R RV Silicon bring-up Cortex-M/A/R · RISC-V 1 compiler · linker · probe 7
The firmware stack · numbered as on the cards
  1. First silicon

    BSP and board bring-up

    From silicon evaluation to production-ready board support.

    • Clock tree, memory controller and peripheral initialisation
    • Driver integration for custom boards
    • Arm Cortex-M, Cortex-A, Cortex-R and RISC-V targets
  2. Real time

    RTOS integration

    Thread architecture and deterministic scheduling on RTX5, embOS, FreeRTOS, Zephyr and ThreadX.

    • Priority inversion analysis and stack sizing
    • Inter-task communication design
    • Scheduling validated on the target

    RTOS development →

  3. Cortex-A

    Embedded Linux BSP and drivers

    U-Boot, kernel and device tree for your board, built with Yocto or Buildroot.

    • U-Boot customisation and kernel configuration
    • Device tree authoring
    • Linux device drivers for custom peripherals
  4. Automotive ECUs

    AUTOSAR Classic and Adaptive

    BSW configuration and RTE generation for deeply embedded ECUs and high-performance compute nodes.

    • MCAL porting and complex device drivers
    • BSW configuration and RTE generation
    • Software component design
  5. On device

    Edge AI and ML deployment

    Trained models running on resource-constrained MCUs and MPUs.

    • TensorFlow Lite Micro and CMSIS-NN optimisation
    • Model quantisation
    • Inference pipelines for vision, audio and sensor fusion

    Edge AI and vision →

  6. In the field

    Bootloaders and OTA updates

    Field updates that can fail safely and roll back.

    • MCUboot and custom bootloaders
    • Dual-bank update with rollback protection
    • Over-the-air update infrastructure for connected devices

    Secure boot →

  7. IAR · GCC to armclang

    Compiler porting and tool-chain migration

    Moving firmware from IAR or GCC to the Arm Compiler and Keil MDK, with equivalence shown.

    • Keyword, pragma and intrinsic translation
    • IAR .icf and GCC .ld to Arm scatter-loading
    • C-library migration and a MISRA re-check

    Keil MDK →

Silicon we work with

Arm Cortex · RISC-V · multi-core

  • Cortex-M M0 · M3 · M4 · M7 · M33 · M55
  • Cortex-A A53 · A55 · A72 · A76
  • Cortex-R R5F · R52 · R52+
  • RISC-V RV32 · RV64
  • Multi-core AMP · SMP
  • ARM9 Legacy platforms
  • NXP
  • STMicroelectronics
  • Renesas
  • Infineon
  • TI
  • Microchip
  • Nordic
02

From a board that boots to firmware you can own.

Every engagement runs the same four stages on the tool chain GSAS supplies, so the evidence your reviewers ask for is produced along the way. Hover a stage to find it on the line.

Bring up · Integrate · Verify · Ship
01 Bring up 02 Integrate 03 Verify 04 Ship
  1. 01

    Bring up

    Silicon
    evaluation, clocks, memory
    Board
    peripherals, drivers, BSP
    Probes
    J-Link, ULINKplus

    A board that boots and talks

  2. 02

    Integrate

    OS
    RTOS or embedded Linux
    Stacks
    middleware, AUTOSAR BSW and RTE

    One build, every layer in place

  3. 03

    Verify

    Unit test
    TESSY
    Static analysis
    Klocwork, Perforce QAC
    Timing
    SystemView
    Compiler
    SuperTest

    Evidence, not assertions

  4. 04

    Ship

    Update path
    bootloader, OTA, rollback
    Migration
    IAR or GCC to armclang
    Hand-over
    source, build and documentation

    Firmware your team can own

Related: RTOS development · Security engineering · Hardware and PCB · Functional safety

04

Three ways to start.

Hand GSAS the firmware, buy the tool chain your own team needs, or have your engineers trained on it. Many teams do all three.

  1. 01

    A firmware project

    Scoped to your board and deadline

    Tell us the silicon, the operating system and the milestone. GSAS engineers bring up the board, integrate the stack and hand back verified firmware your team can build and own.

  2. 02

    The tool chain

    Arm, SEGGER, Perforce, Razorcat, Solid Sands

    The compilers, probes, unit-test and static-analysis tools on this page are available from GSAS in India, with INR quotes, GST invoices and application engineers who use them on real projects.

  3. 03

    Your team, trained

    Workshops on your hardware

    Hands-on sessions for your engineers on the tool chain, RTOS and debug workflow, run on your own boards so the lessons carry straight into the product.

05

New silicon on the bench? Let’s bring it up.

Tell us the processor, the operating system and the milestone. GSAS replies from Bengaluru with scope and a proposal: bring-up, integration, verification and the tool chain to keep it going.

sales@gsasindia.com +91 80 6590 1783

Embedded software engineering with GSAS in India

What embedded software work does GSAS take on?

BSP and board bring-up, RTOS integration, embedded Linux BSPs and drivers, AUTOSAR Classic and Adaptive configuration, edge AI model deployment, bootloaders and OTA updates, and compiler migration from IAR or GCC to the Arm Compiler and Keil MDK.

Which processors and silicon vendors does GSAS work with?

The Arm Cortex-M, Cortex-A and Cortex-R families, RISC-V (RV32 and RV64), multi-core AMP and SMP designs and legacy ARM9 platforms, on silicon from NXP, STMicroelectronics, Renesas, Infineon, TI, Microchip and Nordic.

Can GSAS migrate our firmware from IAR or GCC to Keil MDK?

Yes. GSAS translates keywords, pragmas and intrinsics, converts IAR .icf and GCC .ld linker files to Arm scatter-loading, migrates the C library, integrates the new build into CI and shows functional equivalence with a MISRA re-check.

Which RTOS and operating systems does GSAS integrate?

RTX5, SEGGER embOS, FreeRTOS, Zephyr and ThreadX for real-time work, and embedded Linux built with Yocto or Buildroot for Cortex-A targets.

Can we buy the tool chain from GSAS as well?

Yes. GSAS is the authorized Arm development tools engineering partner for India, the UAE and Sri Lanka. It is also an authorized SEGGER engineering partner in India, and it supplies Perforce, Razorcat and Solid Sands tools, with INR quotes and GST invoices.

Where is the engineering done?

In India. Engineering is led from Bengaluru, and GSAS has 11 offices in nine Indian cities, including Hyderabad, Chennai, Pune, Mumbai and Delhi NCR. GSAS is ISO 9001:2015 certified by TÜV Rheinland.

Embedded Software Insights

SEGGER SystemView recording of a FreeRTOS application on an STM32H743, captured through pyOCD in Arm's CMSIS example, supported in India by GSAS
CMSIS Arm SEGGER

CMSIS and SEGGER: J-Link, RTT and SystemView in Keil Studio

SEGGER tools now plug into the CMSIS workflow in Keil Studio for VS Code: the Arm CMSIS Debugger connects to J-Link, SEGGER RTT and SystemView are available as CMSIS software packs, and pyOCD reads RTT on multi-core targets, including to files for hardware-in-the-loop tests. GSAS is demonstrating the workflow at embedded world India 2026, Stand D4, BIEC Bengaluru, 17 to 19 November.

17 Nov 2026 · 6 min read
SEGGER J-Link PRO debug probe, official SEGGER product photo, illustrating a debug and trace tool selection guide for Indian automotive Tier-1 teams by GSAS Micro Systems
Comparisons & Buying Automotive & Mobility SEGGER

Choosing Debug and Trace Tools for Indian Automotive Tier-1s

A probe that is right for a Cortex-M body controller is the wrong tool for a multicore TriCore powertrain ECU. This guide walks Indian automotive Tier-1 teams through choosing a debug and trace setup by architecture: Cortex-M, Cortex-R and Cortex-A, TriCore, RH850 and RISC-V, and by the question each programme actually needs trace to answer.

13 Nov 2026 · 11 min read
SEGGER J-Trace PRO Cortex-A/R/M trace probe, official SEGGER product photo, illustrating multicore debug on AURIX, RH850 and Cortex-R52 for Indian automotive teams by GSAS Micro Systems
Technical Guides Automotive & Mobility Arm

Multicore Debug on AURIX, RH850 and Cortex-R52 in India

Halting one core of a multicore safety microcontroller while the others keep running changes the system you are trying to debug. This guide explains lockstep, cross-triggering and synchronous halt on Infineon AURIX, Renesas RH850 and Arm Cortex-R52, from public silicon-vendor documentation, for automotive teams in India.

13 Nov 2026 · 11 min read
Arm DSTREAM-ST streaming trace debug probe, official Arm product image, illustrating non-intrusive debug of safety-critical ECUs on production silicon by GSAS Micro Systems India
Compliance & Safety Automotive & Mobility Arm

Non-Intrusive Debug of Safety ECUs on Production Silicon

A safety ECU cannot be paused to see what it is doing, and production silicon often ships with debug locked and no trace connector. This guide ranks the debug techniques available on production parts by how much they disturb the target, explains debug authentication and emulation devices, and shows Indian ECU teams how to plan observability before the hardware freezes.

13 Nov 2026 · 10 min read
Arm DSTREAM-PT parallel trace probe with its target probe and ribbon cable, official Arm product image, illustrating an off-chip trace explainer by GSAS Micro Systems India
Technical Guides Automotive & Mobility Arm

Off-Chip Trace Explained: ETM, Serial Trace, Trace Buffers

Instruction trace is only useful if it can leave the chip. This explainer compares the three routes embedded teams in India actually have: a parallel trace port fed by the ETM, a high-speed serial trace port, and on-chip trace buffers, with a decision table for picking one before the board design freezes.

13 Nov 2026 · 10 min read
Arm Keil ULINKpro and ULINKpro D debug and trace adapters, official Arm product image, illustrating trace-based code coverage evidence for ISO 26262 and DO-178C by GSAS Micro Systems India
Compliance & Safety Automotive & Mobility Aerospace & Defense

Trace-Based Code Coverage as ISO 26262 and DO-178C Evidence

Hardware trace can measure structural coverage on the target without adding instrumentation to the build. This guide explains what trace-based coverage measures, how object code coverage relates to the source-level metrics ISO 26262 and DO-178C discuss, where it fits next to instrumented unit test coverage, and what a reviewer will ask about it. Written for Indian automotive and aerospace verification teams.

13 Nov 2026 · 11 min read