Embedded Software for Production Vehicle Systems.

It covers the software written for the ECU itself: MCAL and low-level drivers, board bring-up, Complex Device Drivers for peripherals AUTOSAR does not standardise, bootloaders and flash drivers, diagnostics, and application software. Agnile develops it in MISRA C on automotive microcontrollers such as Infineon AURIX, Renesas RH850, and NXP S32K and S32G, under ASPICE-aligned processes with traceable test evidence.

Embedded software engineering is the code we write ourselves: MCAL-level and Complex Device Drivers, bootloaders, diagnostics, and application software. AUTOSAR development is configuration and integration of the standard platform: BSW and RTE configuration, communication, diagnostic and Crypto Stack modules, and Adaptive services. Many ECU programmes need both, and Agnile can deliver them together as one work package.

Yes. We develop UDS-based bootloaders and flash drivers that implement the programming sequence — request download, transfer data, request transfer exit — guarded by security access or authentication, and integrate signature verification with the HSM so only authentic software is flashed and booted. Behaviour on interrupted programming is designed in, and the result is tested on target hardware.

Infineon AURIX, Renesas RH850, NXP S32K and S32G, and TI TDA4 are our common targets for production ECU software, across single-core and multicore architectures. We work in your compiler, debugger, and static-analysis toolchain, so the code and build configuration stay maintainable by your own team after handover.

Cost is driven by scope: the number of drivers and CDDs, whether the microcontroller and board are new to the programme, bootloader and security requirements, the ASIL and the verification depth it implies, the share of application software, and the number of planned release iterations. We quote each work package after a scoping call, or offer team extension for open-ended programmes.

Typically six to ten weeks per microcontroller family for MCAL and Complex Device Driver work, four to six weeks for a focused diagnostic stack, and eight to twelve weeks for ECU bring-up from first boards to a tested first release. New silicon, missing specifications, or ASIL D verification extend these; team-extension engagements run for the life of the programme.

Yes. Board bring-up and complex device driver development is one of our core strengths. We develop low-level drivers for microcontrollers (Infineon AURIX, Renesas RH850, NXP S32K/S32G, TI TDA4), power management ICs, external memory interfaces, and custom ASICs. Our board bring-up process includes clock configuration, pin mux setup, peripheral initialization, debug interface validation, power sequencing verification, and initial communication stack validation. We deliver production-ready MCAL-level drivers integrated with the AUTOSAR BSW stack.

Yes. We provide Model-Based Development (MBD) services using MATLAB/Simulink for control algorithm design, simulation, and automatic code generation. Our MBD workflow includes plant model development, controller design, MIL/SIL/PIL testing, production code generation using Embedded Coder, and integration of generated code with hand-written BSW and driver layers. We follow MAAB guidelines for model architecture and have experience generating ASIL-compliant code from qualified code generators.

Yes. We develop and configure complete diagnostic stacks compliant with ISO 14229 (UDS) and ISO 15031 (OBD). This includes diagnostic communication manager (DCM) configuration, diagnostic event manager (DEM) setup, fault memory management (NvM integration), diagnostic service implementation (session management, security access, routine control, data transfer), and OBD-II PIDs for emission-related diagnostics. We also develop diagnostic descriptions (ODX/CDD files) for integration with vehicle-side diagnostic tools.