Standardized boundaries
SWCs interact through RTE and BSW services, while ECU Abstraction and MCAL contain hardware-specific behavior.
AUTOSAR CLASSIC BSW
KopherSAR AUTOSAR Classic Basic Software
A configurable, generatable, and verifiable ECU software foundation connecting SWCs, RTE, communication, diagnostics, memory, and security services.
CAN / CAN FD / LIN / Ethernet UDS / DEM / DCM / FiM RTE / OS / NvM / Csm
PRODUCT ROLE
More than a library: the standardized software foundation of an ECU
KopherSAR separates application logic from MCU-specific hardware so OEM and ECU teams can manage communication, diagnostics, network management, persistent data, I/O, and security through consistent interfaces.
Configured per project
Select only the communication, diagnostics, NvM, security, and I/O modules required by the target ECU.
Production integration
Connect design inputs, configuration, generation, integration builds, and verification evidence in a repeatable workflow.
AUTOSAR CLASSIC LAYERS
Where does KopherSAR sit in the ECU architecture?
From top to bottom: application SWCs, RTE, BSW functional domains, ECU Abstraction and MCAL, then the target MCU and peripherals. Each layer has a clear responsibility.
SWC
Application Layer
Vehicle Control · Body Control · Charging · Diagnostics Application
KopherSAR
Runtime Environment (RTE)
Ports · Interfaces · Runnable Mapping · Cross-Partition IOC
Services & Mode
EcuM · BswM · Os · WdgM
Communication
COM · PduR · CanIf · LinIf · EthIf · SoAd
Diagnostics & Safety
DCM · DEM · FiM · Csm · KeyM · SecOC
Memory
NvM · MemIf · Fee · Ea · Fls · Eep
ECU Abstraction & MCAL
Dio · Adc · Pwm · Icu · Spi · Port · Mcu · Wdg · Can · Lin · Eth
Target Microcontroller & ECU Peripherals
The exact module scope depends on the target MCU, AUTOSAR release, ECU functions, and safety requirements.
MODULE MAP
BSW capabilities from communication to cybersecurity
Start with functional domains and expand module details only when needed, rather than reading a wall of abbreviations.
Vehicle communication
Signals, PDUs, transport protocols, and in-vehicle network interfaces.
Vehicle communication
Signals, PDUs, transport protocols, and in-vehicle network interfaces.
COMPduRCanIf / CanTpLinIf / LinTpEthIf / TcpIpSoAd / SOME-IP
Diagnostics and faults
UDS services, DTC handling, function inhibition, and service workflows.
Diagnostics and faults
UDS services, DTC handling, function inhibition, and service workflows.
DCMDEMFiMOBDSecurityAccessRoutine Control
Network and mode management
ECU wakeup, sleep, communication modes, and low-power networks.
Network and mode management
ECU wakeup, sleep, communication modes, and low-power networks.
NmCanNmLinNmUdpNmComMPartial Networking
Persistent data and memory
Parameters, learned values, DTC data, and Flash / EEPROM write strategies.
Persistent data and memory
Parameters, learned values, DTC data, and Flash / EEPROM write strategies.
NvMMemIfFeeEaFlsEep
Cybersecurity and crypto
Message authentication, key management, and hardware security interfaces.
Cybersecurity and crypto
Message authentication, key management, and hardware security interfaces.
CsmCryptoIfKeyMSecOCSeed / KeyHSM Integration
RTE, OS, and partitions
Clear boundaries across SWCs, tasks, OS Applications, and cross-core data flows.
RTE, OS, and partitions
Clear boundaries across SWCs, tasks, OS Applications, and cross-core data flows.
RTEOsIOCTrusted FunctionOS ApplicationMulti-Core
I/O and ECU abstraction
Consistent I/O interfaces that isolate ECU peripherals from application logic.
I/O and ECU abstraction
Consistent I/O interfaces that isolate ECU peripherals from application logic.
DioAdcPwmIcuSpiIoHwAb
System supervision
ECU startup, mode transitions, watchdogs, and error responses.
System supervision
ECU startup, mode transitions, watchdogs, and error responses.
EcuMBswMWdgMWdgIfSchMDet
CONFIGURATION TO ECU
From engineering inputs to a reproducible ECU build
KopherConfig handles configuration and validation; KopherSAR supplies the RTE and BSW runtime. Together they turn design data into ECU integration artifacts.
Engineering inputs
DBC / ARXMLSWC PortsOS TasksDTC / UDSNvM BlocksSecurity Policy
01
Import design data
Baseline network matrices, SWC interfaces, diagnostics, OS, NvM, and security requirements.
→ Design Baseline
02
Configure and validate
Select BSW modules in KopherConfig, set parameters, and check cross-module dependencies.
→ Validated Config
03
Generate and integrate
Generate ARXML, RTE, and BSW configuration code, then connect MCAL, bootloader, and application SWCs.
→ Generated C / ARXML
04
Build and verify
Complete the ECU build, static checks, bench or HIL validation, and retain traceable results.
→ ECU Build / Evidence
PLATFORM STRATEGY
Supported platforms and porting boundaries
Start quickly on integrated platforms. Other MCUs are assessed by MCAL, compiler, debugger, security mechanisms, and verification scope.
KCU GEN1
NXP MPC5744P
Power Architecture
For established KCU GEN1 projects with CAN / LIN, diagnostics, I/O, and production ECU integration.
KCU GEN2 / MICRO
Infineon TC387QP
TriCore · Multi-Core · HSM
For CAN FD, Ethernet, multicore partitioning, and hardware-security integration requirements.
PORTING ASSESSMENT
Other automotive MCUs
S32K3 · TC397 · TC4xx and others
Project-based assessment for MCAL connection, BSW porting, compiler build, and verification scope.
KOPHERBIT TOOLCHAIN
How does it connect to the KopherBit toolchain?
KopherSAR is the runtime core. Companion tools cover configuration, network data, SWC design, bootloader integration, and diagnostic validation.
What do you receive?
The exact package follows the license and integration scope, so teams receive reproducible engineering data rather than an isolated code drop.
01
BSW software package
Selected modules, target platform, and source or library licensing scope.
02
Configuration artifacts
ARXML, BSW configuration, RTE, and generated C outputs.
03
ECU integration project
Compiler, linker, MCAL, bootloader, and application integration settings.
04
Design and configuration documents
Module scope, parameter baselines, interfaces, and dependency notes.
05
Verification results
Build, static-analysis, bench, or HIL evidence according to project scope.
06
Porting and production support
Issue analysis, version baselines, change impact, and maintenance collaboration.
FAQ
Frequently asked questions
What is the difference between KopherSAR and KopherConfig?
KopherSAR is the AUTOSAR Classic RTE and BSW that runs on the ECU. KopherConfig is the engineering tool used to configure modules and generate code. Together they support BSW configuration and ECU integration.
Must every BSW module be included?
No. The module set is tailored to the ECU function, networks, diagnostics, memory, cybersecurity, and safety requirements, with matching configuration and verification scope.
Does KopherSAR support AUTOSAR Adaptive?
KopherSAR targets AUTOSAR Classic. Adaptive nodes may coexist and communicate with Classic ECUs over Ethernet / SOME-IP, but they are separate execution platforms.
Can it be ported to controllers outside the KCU family?
Yes, subject to project assessment. The target MCU, MCAL, compiler, debugger, memory, peripherals, security mechanisms, and verification ownership must be defined first.
Are SecOC, Partial Networking, and multicore partitions supported?
The architecture can use Csm / KeyM / SecOC, CanNm Partial Networking, and RTE IOC / OS Applications. Inclusion depends on vehicle requirements and platform capability.
Is source code available?
Source-code or library-based options can be defined by commercial license and module scope, together with configuration, integration, and maintenance interfaces.
Evaluating AUTOSAR BSW or an existing ECU migration?
Share the target MCU, interfaces, diagnostics, OS / partition needs, and production timing. We will help define the module and porting scope first.