Third-Party Products & Services

K-SAR Suite – Configuration Editor & AUTOSAR Basic Software Modules

Configuration and Generation of AUTOSAR Basic Software and Runtime Environment (RTE)

Highlights

  • KPIT AUTOSAR Basic Software (BSW) platform
  • AUTOSAR BSW components for R2.x, R3.x, and R4.x
  • RTE configuration and generation
  • BSW configuration and code generation

Description

KPIT K-SAR suite comprises of K-SAR Editor (ECU Configuration Editor) & AUTOSAR Basic software stack. K-SAR Editor is a PC-based tool used for RTE configuration, RTE generation, and configuration and generation of AUTOSAR Basic Software code. The tool has been successfully evaluated by leading OEMs and tier 1 suppliers.

KPIT BSW components are pretested and tuned for the highest performance on a number of popular microcontroller variants and families. These standard compliant modules can be integrated with MCAL, OS, and complex drivers supplied by tier 1s, third-party vendors, and semiconductor suppliers. The components are implemented in embedded C with full compliance to MISRA rules and are developed by following stringent quality processes meeting Automotive SPICE Level 5 requirements. KPIT BSW components can be configured using any AUTOSAR compliant third-party configuration tools.

BSW configuration is performed using a graphical user interface (GUI) that takes ECU configuration parameter definition files as input and generates the run-time GUI for all BSW modules including MCAL. It also allows importing of the system configuration description and automatic mapping with ECU configuration from the system level. The editor supports imports of legacy file formats like DBC, FIBEX, ODX etc. Finally, it validates the configuration in the GUI and then generates the ECU configuration description files for BSW modules including MCAL.

BSW generation is performed using a command line interface. In this step, configuration source and header files are created for a specific BSW module. The BSW generation uses the ECU configuration description (XML) file as input to generate the C header file(s) and C source file(s) for BSW modules.

RTE configuration is performed using a GUI that takes ECU configuration parameter definition files as input and generates the run-time GUI for RTE, OS, COM, and other BSW modules. It also uses the AUTOSAR Software Component (SW-C) description file for importing the mapping from application data to ECU level and generates the ECU configuration description files for RTE, OS, COM, and other BSW modules.

RTE generation is performed using a command-line interface for creating the AUTOSAR Software Component API functions that link AUTOSAR Software Components to the OS. RTE manages communication between various AUTOSAR Software Components and also between AUTOSAR Software Components and Basic Software Modules. The required RTE source code will be generated using the ECU configuration description of BSW (RTE, COM, OS, and other BSW module), SW-C description, and AUTOSAR compliant application source code generated using Simulink and Embedded Coder from MathWorks.

kpit_logo

KPIT Technologies Ltd

Plot No 35/36, Rajiv Gandhi Infotech Park
Phase 1, MIDC, Hinjawadi
Pune, Maharashtra 411057
INDIA
Tel: +91-20-66525000
Fax: +91-20-66525001
autosar@kpit.com

Required Products

Platforms

  • Windows

Support

  • Consulting
  • E-mail
  • Fax
  • On-site assistance
  • System integration
  • Telephone
  • Training

Product Type

  • Embedded Software - Tools, IDE, RTOS

Tasks

  • Control Systems
  • Digital Signal Processing
  • Embedded Systems
  • MATLAB Programming
  • Real-Time Systems

Industries

  • Automotive