As automotive manufacturers move towards software-defined vehicles and zonal architectures, developing secure and reliable software is becoming increasingly complex. TASKING has introduced a unified development toolchain for NXP’s S32K5 microcontroller family, bringing compilation, debugging and verification into a single environment to simplify development and certification. Semicon Leaders Asia speaks with Christoph Herzog, Co-CEO & CTO, TASKING about its collaboration with NXP, automotive software challenges, safety requirements and the future of embedded software development.
Q. TASKING has introduced a unified software development toolchain for NXP’s S32K5 microcontroller family. What makes this launch important for the company, and how will it benefit automotive manufacturers and suppliers?
This launch shows what TASKING stands for: one unified toolchain for embedded teams building safety- and security-critical software. For the S32K5 family, TASKING offers compilation, debugging and full verification – including testing, coverage and requirements traceability – from a single vendor, developed in close collaboration with NXP. That matters because automotive teams today often put together tools from several vendors, and each extra tool adds integration work, qualification effort and schedule risk.
With one certified environment from the first compile to final validation, OEMs and Tier-1s work with one toolchain and one support team across compile, debug and verification. In practice, they win back time, reduce cost and spend their engineering effort on the application rather than on managing tools. For us, it also builds on almost 50 years of experience in automotive embedded software and on our long partnership with NXP.
Q. TASKING has worked closely with NXP to develop this solution. How has this partnership helped address customer needs, and what advantages does it bring to automotive software developers?
We built the toolchain alongside the silicon, not after it. Working closely with NXP let us tune it for the S32K5’s main features: the Arm Cortex-M7 cores, the hypervisor-enabled Cortex-R52 cores, DSP acceleration and the hardware isolation mechanisms. Developers get compiler-aware flashing, debugging and tracing that understands the device from day one. Through NXP’s AUTOSAR Real-Time Drivers (RTD), they also get MCAL certification out of the box.
The result is a toolchain matched to the hardware it runs on. That means fewer surprises during integration, a faster path to production-ready code and more confidence in safety and security compliance. It also builds on our existing debug and test support for NXP devices, so customers who already work with both companies get a continuous, familiar experience.
Q. As the automotive industry moves toward software-defined vehicles and zonal architectures, what are the biggest challenges engineers face in software development, and how does TASKING’s new toolchain help overcome them?
Software-defined vehicles concentrate more functions on fewer, more powerful controllers. Engineers now have to run mixed-criticality workloads side by side, keep them safely separated, and meet ISO 26262 and ISO/SAE 21434 requirements – all on fixed program timelines. On top of that, tool fragmentation makes every one of these challenges harder.
Our toolchain addresses this in three ways. It supports secure partitioning of mixed-criticality workloads on the S32K5’s virtualization and isolation features. It brings compilation, debugging and verification into one workflow, so teams don’t have to integrate and qualify tools from several vendors. And it enables “shift-left” testing, combining compiler technology, real-time debugging and automated testing so that issues, requirements traceability and compliance gaps are found earlier, when they cost far less to fix.
Q. The new toolchain combines compilation, debugging and verification in a single environment. How will this help customers reduce development time, costs and certification challenges?
Every tool boundary costs something: data has to be moved, results reconciled and each tool qualified separately. When compilation, debugging and verification share one environment, those costs shrink. Developers spend less time managing tools and more time writing software – our customers report 15–30% faster debugging with our debug solutions.
On certification, the toolchain is certified for compliance with ISO 26262 ASIL D TCL3 and ISO/SAE 21434. Teams can produce traceable evidence within one workflow instead of assembling it across vendors. On cost, customers deal with one supplier, one support organization and one set of qualification documents. The overall effect is lower certification risk, more predictable schedules, and a lower total cost of development.
Q. TASKING has also focused on making it easier for customers to move from NXP’s S32K3 to S32K5 platforms. Why is software reuse important for automotive companies, and how does this capability help protect their existing investments?
Automotive software represents years of engineering work and validation, so customers can’t afford to start over with each new MCU generation. Teams with existing S32K3 code can move to the S32K5 without changing their development environment. They keep the same compiler technology, workflows and expertise.
This lowers migration risk, keeps validated code and processes intact, and lets engineers be productive on the new platform from day one. It continues the compiler support we introduced for the S32K3 family. More broadly, it reflects a core TASKING principle: making life easier for developers, so that adopting new architectures or moving between projects doesn’t come with the added burden of changing tools or tool partners.
Q. The toolchain supports applications such as zone controllers, body control, chassis systems and vehicle electrification. Which of these areas is seeing the strongest customer demand, and what are TASKING’s next priorities for expanding its automotive software business?
We see the strongest interest in zone and domain controllers, which sit at the center of the shift to zonal architectures and combine many functions on one device. Body control, chassis and safety systems, and electrification are following closely, because they share the same need for certified, high-performance software.
Looking ahead, we’ll keep expanding the unified toolchain across the architectures automotive teams rely on – Arm, TriCore, RH850 and RISC-V – so customers can choose the silicon that best fits their application, without being constrained by their development tools. We’re also investing in AI-assisted development across the workflow and deepening our silicon partnerships, including NXP. For us, what matters most is the same: to be trusted by embedded teams who develop tomorrow’s cars.