AutoPie Studio

Piest Systems — Made in India

AutoPie Studio
Configure. Generate. Build. Flash.

The all-in-one AUTOSAR configurator tool that takes your ECU project from stack import to flashable firmware — without leaving the application. One tool. Every BSW module. Every platform.

18+BSW Modules
<4sProject Open Time
3Platforms
R22-11AUTOSAR Schema
AutoPie Studio — BCM_S32K144  |  SIP v1.2.0
BCM_S32K144
▾ Can
▾ CanConfigSet
  ► EcuTestNode
  ► CanController_1
▸ CanIf
▸ Com
▸ PduR
▸ Os
▸ EcuM
▸ BswM
▸ Dcm
▸ NvM (disabled)
<!– Can.arxml — EcucValues –>
<ECUC-MODULE-CONFIGURATION-VALUES>
  <SHORT-NAME>Can</SHORT-NAME>
  <CONTAINERS>
    <ECUC-CONTAINER-VALUE>
      <SHORT-NAME>CanConfigSet</SHORT-NAME>
      <SUB-CONTAINERS>
        <ECUC-CONTAINER-VALUE>
          <SHORT-NAME>EcuTestNode</SHORT-NAME>
          <!– BaudRate: 500.0 kbps –>
          <VALUE>500.0</VALUE>
⚙ EcuTestNode
BaudRate500.0 kbps
BusoffProcINTERRUPT
Activationtrue
PropSeg47
Seg116
Seg216
✔ All checks passed
AutoPie Studio is a production-grade AUTOSAR configurator tool built for automotive ECU software engineers. It provides a unified environment for BSW configuration, real-time validation, AUTOSAR code generation, integrated compilation, and firmware output — covering the complete development workflow from ARXML import to flashable .hex in a single cross-platform desktop application. Whether you’re configuring CAN baud rates, mapping PDU routing paths, setting up OS tasks, or generating configuration reports for ISO 26262 documentation, AutoPie Studio handles it all.
End-to-End Workflow

From Stack Import to Flashable Firmware — One Tool

No tool-hopping. No manual file juggling. AutoPie Studio covers the entire AUTOSAR development pipeline in six seamless steps.

01
Import
Register BSW SIP. Auto-validates all module definitions.
02
Configure
Set parameters via GUI tree + property editor + ARXML editor.
03
Validate
Real-time constraint checks with 150ms debounce.
04
Generate
Produce _Cfg.h and _PBCfg.c for all active modules.
05
Build
Parallel compile with bundled arm-none-eabi-gcc.
06
Flash
Output .hex / .srec / .elf ready for JTAG/SWD.
BSW Module Support

18+ AUTOSAR Classic Modules — Ready to Configure

AutoPie Studio ships with a comprehensive Software Integration Package covering every major AUTOSAR Classic BSW layer — with complete parameter definitions, validation rules, and code generation templates for each module.

📡CanCAN Driver
🔀CanIfCAN Interface
📦CanTpCAN Transport
📨ComCommunication
🔁PduRPDU Router
🔧DcmUDS Diagnostics
⚠️DemDiagnostic Events
🔍FiMFunction Inhibit
💾NvMNV Memory
🗂️MemIfMemory Abstraction
📄FeeFlash EEPROM
FlsFlash Driver
⏱️OsAUTOSAR OS
🚀EcuMECU Manager
📋BswMBSW Mode Manager
🐕WdgMWatchdog Manager
🔐CsmCrypto Service
🔑KeyMKey Manager
Configuration Engine

Three-Panel GUI — Designed for Speed

AutoPie Studio’s configuration engine gives you a familiar three-panel layout: ARXML tree navigation, parameter property editor, and an integrated ARXML source view. Every edit flows through a full undo/redo command bus with copy-on-write snapshots.

  • Tree + Properties + ARXML editor — complete visibility at every level.
  • Lazy hydration — opens 200+ ARXML files in under 4 seconds.
  • 200-deep undo/redo — COW patches track every single change.
  • Incremental save — only modified ARXML files rewritten on Ctrl+S.
  • Live validation — 12 built-in AUTOSAR constraint checks in real time.
  • Multi-instance containers — add, delete, rename controller instances.
⚡ Edit → Validate → Save
1. Select node in ARXML tree
→ Properties load instantly

2. Change BaudRate: 500 → 250
→ SetAttributeCmd → UndoStack

3. DirtyTracker flags Can.arxml
→ Validation runs in 150ms

4. Ctrl+S → incremental save
→ Only Can.arxml rewritten
Done in <200ms
Code Generation

Template-Driven AUTOSAR Code Generation

AutoPie Studio reads your BSW module definitions and configured parameter values together, then produces fully AUTOSAR-compliant C source files through a transparent template engine. Every generated file is auditable — no black-box code generation.

  • One .tmpl per output — transparent, version-controlled templates.
  • Parallel generation — all files written concurrently on N_CORES threads.
  • Complete output — _Cfg.h, _PBCfg.c, SchM_*.h, Rte_*.h/.c per module.
  • Auto-checkpoint — COW snapshot before every generation run.
  • Reports — HTML & PDF for QA and ISO 26262 traceability.
  • Plugin SDK — extend with custom generators via stable C ABI.
📄 Generated Files
gen/src/Can_Cfg.h      ← pre-compile config
gen/src/Can_PBCfg.c  ← post-build arrays
gen/src/CanIf_Cfg.h
gen/src/Com_Cfg.h
gen/src/Os_Cfg.h
gen/src/Os_Cfg.c      ← task/alarm config
gen/src/SchM_Can.h   ← exclusive areas
gen/src/Rte_Type.h   ← data types
gen/src/Rte_BcmSwc.h ← SWC RTE API

gen/out/firmware.hex ← FLASH THIS
Build Pipeline

Compile & Link — Inside the Tool

AutoPie Studio bundles the ARM GCC toolchain and invokes compiler/linker processes natively. No shell scripts, no external build systems, no context switching.

  • Bundled toolchain — ships with the installer. Zero setup.
  • Parallel compile — all CPU cores used automatically.
  • Build profiles — Debug, Release, HiL — switch with one click.
  • Incremental builds — only changed sources recompile.
  • Multi-format output — .elf, .hex, .srec, .map files.
  • Live output — streaming compiler log with clickable error navigation.
🔨 Build Output
[1/21] Compiling Can.c
[2/21] Compiling Can_PBCfg.c
[3/21] Compiling CanIf.c

[19/21] Compiling Bcm_AppSwc.c
[20/21] Compiling Rte_BcmSwc.c
[LINK] → BCM_S32K144.elf
[OBJCOPY] → BCM_S32K144.hex

✔ BUILD SUCCEEDED — 18.3s
AI Assistant

Built-in AI — 4 Providers, 16 Tools

AutoPie Studio includes an AI assistant that understands your live AUTOSAR model. Connect to cloud providers or run fully offline. Every write action requires your explicit approval.

  • 4 LLM providers — OpenAI, Claude, DeepSeek, Ollama (offline).
  • 16 MCP tools — read, configure, validate, generate, build.
  • Approval workflow — diff preview before every AI mutation.
  • Context-aware — prompts built from your live project state.
  • CLI integrationautopie-cli ai fix for automated repair.
💬 AI Chat
You: Set CAN baud rate to 250 kbps

AI: I’ll update that.
Tool: configure_bsw_module
  path: …/CanControllerBaudRate
  value: 250.0

⚠ Approval Required
BaudRate: 500.0250.0  [Accept] [Reject]
Why AutoPie Studio

Built Different — By Engineers, for Engineers

🖥️

Cross-Platform

Runs natively on Windows, Linux, and macOS. Same features, same performance on every platform. No lock-in.

⌨️

Full CLI for CI/CD

Every GUI action has a CLI equivalent. Validate, generate, and build from Jenkins, GitHub Actions, or any pipeline.

📥

Multi-Format Import

Import ARXML, DBC, LDF, ODX, PDX, FIBEX, and XDM files. Migrate from any existing toolchain seamlessly.

🔀

ARXML Diff & Merge

Built-in 3-way merge engine with conflict detection. Compare project snapshots and safely merge team changes.

🔌

Plugin Architecture

Extend code generation, validation, and import with custom plugins. Stable C ABI ensures compatibility across versions.

📊

ISO 26262 Reports

Generate HTML and PDF configuration reports for quality assurance, functional safety audits, and traceability documentation.

Performance

Engineered for Real-World Speed

Built on a lazy-hydration, copy-on-write architecture. Every performance target is enforced in CI — if a benchmark regresses, the build fails.

<4s
Project Open
200+ ARXML files with lazy hydration
<50ms
UI Response
Heavy ops on worker threads only
<200ms
Incremental Save
Only dirty ARXML files rewritten
<200ms
Live Validation
Debounced constraint checks
<30s
Code Generation
Parallel writes on all CPU cores
<60s
Full Build
Parallel compile + link
FAQ

Frequently Asked Questions

What is AutoPie Studio?

AutoPie Studio is a production-grade AUTOSAR configurator tool developed by Piest Systems. It provides a single unified desktop environment for BSW module configuration, AUTOSAR code generation, integrated compilation, and flashable firmware output — covering the complete ECU development workflow.

Which BSW modules are supported?

AutoPie Studio supports 18+ AUTOSAR Classic BSW modules out of the box: Can, CanIf, CanTp, Com, PduR, Dcm, Dem, FiM, NvM, MemIf, Fee, Fls, Os, EcuM, BswM, WdgM, Csm, and KeyM. Each module includes complete parameter definitions, code generation templates, and validation constraints. Additional modules can be added through the plugin architecture.

What platforms does it run on?

AutoPie Studio runs natively on Windows 10/11, Ubuntu 22.04+, and macOS 13+. All features — configuration, code generation, build pipeline, AI assistant, and CLI — are fully available on all three platforms with identical performance.

How does code generation work?

AutoPie Studio reads two inputs — BSWMD definition files (which define parameter shapes, types, and ranges) and EcucValues files (which contain your configured parameter values). It combines them through a transparent template engine to produce AUTOSAR-compliant C source files: _Cfg.h headers, _PBCfg.c post-build config arrays, SchM exclusive area stubs, and Rte glue code.

Can I use it in CI/CD pipelines?

Yes. The autopie-cli command-line tool mirrors every GUI capability. You can validate configurations, generate code, build firmware, and run AI-assisted fixes — all headlessly from any CI/CD pipeline.

Which MCU targets are supported?

The primary supported target is NXP S32K144 (ARM Cortex-M4) with the arm-none-eabi-gcc toolchain. The architecture supports multiple MCU families through derivative overrides, with additional targets on the roadmap.

Does it include an AI assistant?

Yes. AutoPie Studio includes a built-in AI assistant connected to 4 LLM providers (OpenAI, Claude, DeepSeek, and Ollama for offline use). The AI interacts with your live AUTOSAR model through 16 MCP tools and every write action requires explicit user approval with a diff preview.

Can I import projects from other tools?

Yes. AutoPie Studio includes built-in importers for standard AUTOSAR .arxml, XDM, DBC (CANdb++), LDF (LIN), ODX/PDX (diagnostics), and FIBEX network description files — making migration from any existing toolchain seamless.

Scroll to Top