Four things PRTE brings
Specification updates, tool integration, target porting and project support all connect in one place.
01 / R25-11
Built against the latest specification
Implemented fresh against the AUTOSAR R25-11 specification. You get the latest communication, diagnostic, memory and security stacks without being tied to an older release, and specification updates land quickly.
02 / vECU Level 3
Implement and verify without a board
The whole BSW stack runs as a vECU process on a PC. Finish communication, diagnostics and state management before the hardware lands, and verify them with real scenarios.
03 / PAIO integration
One chain with the configuration tool
The PRTE generator consumes ARXML authored in PAIO directly. Change the configuration and it becomes generated code, with no conversion step between tools.
04 / Production know-how
Judgment earned in series projects
Decisions confirmed across PopcornSAR's AUTOSAR production programs are built into the structure and defaults of the stack — the choices you do not get from reading the standard alone.
Stop waiting for the board
The same BSW code runs on a PC and on the real target. Changing platform swaps only the bottom layer.
Start before the hardware
Development is no longer tied to board delivery. Communication, diagnostics and state management are finished up front, so bring-up becomes wiring.
Regression in CI
Run several ECUs as host processes and exercise CAN, Ethernet and diagnostic scenarios automatically — regression on every commit, with no bench hardware.
Port one layer
POSIX dependencies are confined to the bottom porting layer. Everything above it compiles for bare metal, so porting to a target comes down to replacing that one layer.
Every Classic Platform layer
System, communication, diagnostics, memory, security and MCAL in a single stack.
Configuration code and RTE code are generated from the project ARXML, and the BSW is delivered as a per-project library build — you get a stack that carries only the modules your project needs.
From configuration to execution, without a break
Four steps from configuration in PAIO to running on the target.
Author in PAIO
Configure SWCs, the system and ECUC in PAIO, then export as ARXML.
PRTE generator
The generator reads the project ARXML and emits RTE, SchM and module configuration code.
Project build
The BSW is built as a per-project library against the generated configuration.
Run on vECU or target
Verify the same artifacts on the vECU first, then move to the target board.
The generator lives inside PAIO
The PRTE code generator is embedded in the PAIO IDE, so configuration and generation finish in one tool. A configuration change lands in the generated code immediately, keeping the configuration in one place.
Supported hardware
From vECU to production MCUs, carried by the same stack.
x64
The full stack runs as a vECU Level 3 process on Linux hosts, WSL2 included.
NXP S32
Support for the S32 family widely used in production vehicle controllers.
Infineon TriCore
Support for the AURIX TriCore family used in high-performance and safety-critical domains.
Extensible
Porting is confined to the MCAL and the Os architecture layer, which makes bringing up a new MCU a bounded, well-defined job.
We work with you across the whole project, from design through to production handover.
AUTOSAR CP design & implementation
System and ECU design through BSW integration and verification — the full span of a Classic Platform project.
- System and ECU extract design, communication matrix integration
- BSW integration, startup and state management, integration testing
BSW engineering
Customer-specific BSW modules and CDDs, designed and implemented. Because we own the internals, nothing is off limits.
- Customer-specific BSW module development
- CDD design, implementation and stack wiring
MCAL engineering
MCAL development and porting for your target MCU, extended to meet customer-specific driver requirements.
- MCAL development and porting for new MCUs
- Customer-specific drivers, register-level work
Code generators
Code generators built around your configuration scheme and work-product conventions.
- ARXML-driven configuration and code generation
- Integration with in-house conventions and build systems
Automotive bootloader development
Three-stage PBL / SBL / application bootloaders, designed and implemented. The whole reprogramming path is verified on the vECU first, on top of the diagnostic stack.
- PBL / SBL / application staging
- UDS reprogramming sequences over CAN and DoIP
Security stack engineering
The crypto driver, Csm, KeyM and SecOC are project work every time - the HSM and the key handling differ from one programme to the next. We build a customer-specific implementation against your target HSM and the OEM's security requirements.
- Crypto driver development for your target HSM / SHE
- Customer-specific Csm / KeyM / SecOC development, secure boot
Start your project with
the team that owns the BSW
We will walk you through a technical consultation and a vECU demo matched to your project requirements.
Talk to an engineer