I’m Paul Fleischmann — Embedded Software Architect, Dipl.-Ing. (FH) Computer Engineering, based in Hirm, Burgenland, Austria.
For over 15 years I worked at Elektrobit Austria in Vienna on AUTOSAR Classic Platform — from writing the first MCAL driver to the role of Bundle Software Architect, responsible for the technical direction of several basic software modules.
What I do
What drives me: making low-level software work on real hardware — so that the customer holds a product in their hands that actually works.
A well-designed software module starts with architecture: clearly defined module boundaries, generic APIs, and a Hardware Abstraction Layer (HAL) that encapsulates everything chip-specific — registers, timing, and hardware quirks stay behind the HAL.
That is my standard: the user never notices the underlying hardware, and the next chip swap won’t be a surprise. What changes is the HAL. Everything else stays.
And when something doesn’t work: debugger on the target, oscilloscope on the board, schematic open — and find the root cause. Architecture and debugging are two sides of the same work for me.
What I work with
My core is the AUTOSAR Classic Platform stack — from MCAL drivers for CAN, LIN, SPI, and Ethernet to Complex Device Drivers for low-level protocol layers.
In automotive Ethernet I know the stack from hardware to application protocol: Switch Management, IEEE 1722, J1939, configured and integrated with EB tresos.
Going from hardware specification to implementation is part of the job for me: understanding the relevant registers and timing requirements — and deriving a clean driver architecture that doesn’t leak hardware details into the rest of the stack.
ASPICE and MISRA-C are not checkboxes for me — they are part of daily work.
Primary language is C. Plus Rust, Go, and Python where they are the better tool.
My projects
Professional
Professionally I have grown in two clearly distinct roles.
Started as an AUTOSAR integrator: porting and qualifying the EB AUTOSAR stack on several chip platforms, and integrating it in customer projects — ensuring AUTOSAR configuration and integration against customer requirements.
Then the move into AUTOSAR module development: low-level communication drivers and modules in the communication stack, close to the hardware drivers. Exactly the area where architecture and debugging intersect.
Personal
An embedded project on the BeagleBone Black — because embedded development stays interesting without a customer. Details in the BeagleBone project.
Plus a fully self-hosted development environment: Podman, Gitea, Drone CI, code-server — because working infrastructure should not be accidental.
Why this blog
Because 15 years of AUTOSAR development leaves opinions — about architecture, tooling, and the places where theory and practice diverge.
Knowledge that isn’t shared stays useless. What I have learned in 15 years — about architecture, tooling, the interplay of software and hardware — I write it down here so others can benefit from it.
Contact
I am currently open to new challenges in Embedded Software Engineering and AUTOSAR Classic Platform — preferably in the Austrian automotive environment.