“Korea Serves as the Blueprint for Our Global Strategy”

— Houssem Ben Abder­rah­man, CRO of TASKING Ger­many GmbH

---

Ger­many-based glob­al embed­ded soft­ware develop­ment tools provider TASKING is posi­tion­ing Korea as a key hub in its glob­al strat­e­gy. Dur­ing his first visit to the coun­try, Houssem Ben Abder­rah­man, Chief Rev­enue Offi­cer (CRO) of TASKING, met with AEM at the company’s Pangyo office on Sep­tem­ber 22 to dis­cuss the company’s glob­al growth plans — includ­ing its expan­sion beyond auto­mo­tive into aero­space and defense, sup­port for the RISC‑V archi­tec­ture, and the inte­gra­tion of sta­t­ic analy­sis and ver­i­fi­ca­tion capa­bil­i­ties through the acqui­si­tion of LDRA. He noted that TASKING views the Kore­an mar­ket as an ideal blue­print for its world­wide strat­e­gy.

What are TASKING’s core business areas, key technologies, and solutions?

Ben Abder­rah­man    TASKING is a lead­ing provider of embed­ded soft­ware develop­ment tools, with a strong focus on safe­ty-crit­i­cal appli­ca­tions across the auto­mo­tive, indus­tri­al, aero­space, and defense sec­tors. Our busi­ness is struc­tured around 3 main areas: Com­pil­er tool­chains, Debug­ging Solu­tions and Code Analy­sis & Test­ing. We are an end-to-end solu­tion provider, offer­ing full life­cy­cle sup­port from require­ments to deploy­ment.

What are TASKING’s main strategies for maintaining a competitive edge in the embedded software development tools market?

Ben Abder­rah­man    We have a mul­ti­di­men­sion strat­e­gy tar­get­ing both tech­no­log­i­cal lead­er­ship and mar­ket posi­tion­ing. 
•   Diver­si­fi­ca­tion: His­tor­i­cal­ly, we are strong in AURIX based safe­ty appli­ca­tions. Now we are work­ing on expand­ing into non-AURIX archi­tec­tures such as Arm and RISC‑V, which are fore­cast­ed to drive future growth. This ini­tia­tive includes strength­en­ing our part­ner­ships with com­pa­nies like Rene­sas, NXP, TI, Syn­op­sys, and oth­ers.
•   Tool­chain Pro­vider: We are evolv­ing from a com­pil­er only ven­dor to a full-stack provider for safe­ty-crit­i­cal embed­ded soft­ware. We want to become a one-stop shop for ISO-26262, DO-178C and IEC-61508 com­pli­ance, cre­at­ing a high bar­ri­er to entry for com­peti­tors.
•   Seg­ment­ed mar­ket focus: TASKING is tar­get­ing OEMs, tier-1s and key sup­pli­ers across ver­ti­cals like auto­mo­tive, aero­space & defense, indus­tri­al, robot­ics, and med­ical. The strat­e­gy includes direct sales teams with deep region­al ties and part­ner-led chan­nels for scale. In addi­tion, we will be offer­ing tai­lored pack­ag­ing to sim­pli­fy adop­tion in the dif­fer­ent indus­tries.

What value does TASKING’s technology offer for automotive and embedded software development?

Ben Abder­rah­man    TASKING’s tool­chains are TÜV-cer­ti­fied and designed to meet strin­gent stan­dards like ISO 26262 (func­tion­al safe­ty) and ISO 21434 (cyber­se­cu­ri­ty), which are manda­to­ry for auto­mo­tive ECUs. Our debug­gers offer intu­itive inter­faces and faster trace per­for­mance, while sup­port­ing dif­fer­ent micro­con­trollers with one license. Jaguar Land Rover for instance report­ed reduced debug time and own­er­ship costs, with improved pro­duc­tiv­i­ty and safe­ty com­pli­ance.
In addi­tion to that, TASKING col­lab­o­rates with AUTOSAR ven­dors like Elek­tro­bit, ETAS, and Vec­tor to ensure opti­mal trace con­fig­u­ra­tion and instru­men­ta­tion sup­port for both Clas­sic and Adap­tive AUTOSAR appli­ca­tions.

In your view, what are the most important trends in the automotive software and embedded systems market?

Ben Abder­rah­man    Among the var­i­ous trends, I con­sid­er the fol­low­ing to be the most sig­nif­i­cant cur­rent­ly.
•    Soft­ware-Defined Vehi­cles (SDVs) & Cen­tral­ized Archi­tec­tures. Zonal Con­trollers (ZCUs) and Cen­tral Con­trol Units (CCUs) are replac­ing dis­trib­uted ECUs, enabling bet­ter scal­a­bil­i­ty. This cen­tral­iza­tion demands new soft­ware par­a­digms that sup­port hard­ware vir­tu­al­iza­tion. 
•    Grow­ing adop­tion of RISC‑V and Arm as Instruc­tion Set Archi­tec­tures (ISAs). These archi­tec­tures require tool­chains to adapt and extend sup­port. 
•    Com­plex­i­ty vs. Pro­duc­tiv­i­ty Gap: Soft­ware com­plex­i­ty is grow­ing faster than develop­ment pro­duc­tiv­i­ty. This gap increas­es the need for advanced com­pil­ers, debug­gers and auto­mat­ed test­ing solu­tions.

What role does TASKING play in the era of SDVs (Software-Defined Vehicles), including autonomous and electric vehicles?

Ben Abder­rah­man    TASKING plays a foun­da­tion­al role in enabling SDVs by pro­vid­ing a cer­ti­fied tool­chain that sup­ports:
•   Multi-core per­for­mance opti­miza­tion
•   Hard­ware abstrac­tion
•   Safe­ty-crit­i­cal soft­ware develop­ment up to ASIL D
The TASKING tool­chain is designed to sup­port the lay­ered soft­ware archi­tec­ture of SDVs, which decou­ples hard­ware from soft­ware and enables mod­u­lar, ser­vice-ori­ent­ed develop­ment.

What is your perspective on the impact of AI and cybersecurity on automotive software development?

Ben Abder­rah­man    AI is reshap­ing auto­mo­tive soft­ware develop­ment across mul­ti­ple dimen­sions, such as improv­ing automa­tion, reduc­ing man­u­al effort and bring­ing embed­ded soft­ware test­ing to the next level. Nowa­days pen­e­tra­tion test­ing tools incor­po­rate AI to stim­u­late real-world hack­ing sce­nar­ios and opti­mize model robust­ness. Cyber­se­cu­ri­ty is no longer option­al, it’s foun­da­tion­al to auto­mo­tive soft­ware develop­ment. Atack trees and lay­ered secu­ri­ty mod­els are now stan­dard in develop­ment work­flows. 

How do you assess the impact of AI and machine learning on automotive software development and compiler optimization, and how is TASKING leveraging these technologies?

Ben Abder­rah­man    AI and ML are reshap­ing auto­mo­tive soft­ware develop­ment in sev­er­al key­ways. AI is used to improve code gen­er­a­tion effi­cien­cy and detect bugs and anom­alies ear­li­er in the develop­ment cycle. It’s also used to auto­mate regres­sion test­ing and com­pli­ance checks for stan­dards like ISO 26262. This is espe­cial­ly crit­i­cal in the develop­ment of autonomous and elec­tric vehi­cles, where deter­min­is­tic behav­ior and per­for­mance guar­an­tees are essen­tial.
TASKING is active­ly lever­ag­ing AI and ML across its prod­uct port­fo­lio and strate­gic roadmap. This includes:
•    Multi-core per­for­mance opti­miza­tion
•    Pre­dic­tive analy­sis for com­pil­er behav­ior
•    Auto­mat­ed qual­i­fi­ca­tion and ver­i­fi­ca­tion work­flows

What technological innovations differentiate TASKING’s latest compiler and toolchain from existing solutions?

Ben Abder­rah­man    TASKING intro­duced a new capa­bil­i­ty called Inspec­tor that auto­mat­i­cal­ly     detects whether cus­tomer code is impact­ed by known com­pil­er issues. 
This sim­pli­fies ISO 26262 com­pli­ance and reduces prod­uct lia­bil­i­ty risks.
The lat­est com­pil­er tool­chain also offers flex­i­ble mem­o­ry con­trol, which is cru­cial for per­for­mance and deter­min­ism in embed­ded sys­tems. It also includes qual­i­fied run­time and float­ing-point libraries, and a com­pre­hen­sive Safe­ty & Cyber­se­cu­ri­ty Man­u­al.

What are the most important factors TASKING considers in the future development of its toolchain?

Ben Abder­rah­man    While sev­er­al fac­tors are worth not­ing, the fol­low­ing cur­rent­ly hold the great­est strate­gic impor­tance.
•    Safe­ty and Cer­ti­fi­ca­tion: Con­tin­ued focus on ISO 26262 ASIL D and IEC 61508 SIL3 com­pli­ance. 
•    Sup­port for Emerg­ing Archi­tec­tures: Expan­sion to newer Arm pro­files and sup­port of next-gen auto­mo­tive MCU’s
•    Secu­ri­ty-Dri­ven Evo­lu­tion: Enhanc­ing com­pil­er capa­bil­i­ties to detect vul­ner­a­bil­i­ties like buffer over­flows and use-after-free errors.
•    Cus­tomer-Cen­tric Inno­va­tion: Focus on mak­ing our tools intu­itive and easy to inte­grate, espe­cial­ly for devel­op­ers work­ing in safe­ty-crit­i­cal envi­ron­ment
•    Inte­gra­tion of ver­i­fi­ca­tion and analy­sis tools

Following the acquisition of LDRA, how will static analysis and software verification technologies be integrated with TASKING’s existing toolchain, and what added value can this integration bring to your customers?

Ben Abder­rah­man    Fol­low­ing TASK­ING’s acqui­si­tion of LDRA, the inte­gra­tion of sta­t­ic analy­sis and soft­ware ver­i­fi­ca­tion tech­nolo­gies is set to sig­nif­i­cant­ly enhance TASKING’s tool­chain, par­tic­u­lar­ly for safe­ty- and mis­sion-crit­i­cal embed­ded soft­ware develop­ment. In the future devel­op­ers will be able to invoke LDRA’s analy­sis and test­ing capa­bil­i­ties direct­ly with­in TASKING’s envi­ron­ment. The new inte­grat­ed tool­chain will pro­vide a more intu­itive work­flow with fewer con­fig­u­ra­tion chal­lenges and bet­ter tool inter­op­er­abil­i­ty.

How do you evaluate the importance of RISC‑V in the embedded systems and automotive industries?

Ben Abder­rah­man    RISC‑V is rapid­ly emerg­ing as a trans­for­ma­tive force in both the embed­ded sys­tems and auto­mo­tive indus­tries, offer­ing a com­pelling alter­na­tive to pro­pri­etary archi­tec­tures: RISC‑V’s open-stan­dard, license-free instruc­tion set archi­tec­ture (ISA) is par­tic­u­lar­ly well-suit­ed for embed­ded appli­ca­tions due to sev­er­al key advan­tages: Cus­tomiz­abil­i­ty, cost effi­cien­cy due to no licens­ing fees, and fast grow­ing ecosys­tem.

Compared to toolchains for Arm and other architectures, what differentiates TASKING’s support for RISC‑V in terms of features and technical strengths?

Ben Abder­rah­man    TASKING’s RISC‑V com­pil­er was devel­oped in close rela­tion­ship with major chip ven­dors, allow­ing devel­op­ers to eval­u­ate the impact of archi­tec­tur­al changes on per­for­mance, code size, power con­sump­tion, and sil­i­con area. This level of ISA con­fig­ura­bil­i­ty is not typ­i­cal­ly avail­able in other tool­chains, which are bound by pro­pri­etary con­straints. Built-in sta­t­ic analy­sis ensures com­pli­ance with MISRA and CERT cod­ing guide­lines, reduc­ing the need for addi­tion­al qual­i­fi­ca­tion efforts. TASKING sup­ports vir­tu­al pro­to­typ­ing via inte­gra­tion with major vir­tu­al­iza­tions solu­tions, enabling early soft­ware develop­ment before sil­i­con avail­abil­i­ty. TASKING also col­lab­o­rates with lead­ing IP and sil­i­con ven­dors like Syn­op­sys, Andes, Infi­neon, and oth­ers, ensur­ing early sup­port for auto­mo­tive-grade RISC‑V plat­forms. Our RISC‑V tool­chain is clear­ly posi­tioned to sup­port next-gen­er­a­tion embed­ded and auto­mo­tive sys­tems, espe­cial­ly where cus­tom sil­i­con, early develop­ment, and cer­ti­fi­ca­tion are crit­i­cal.

What support can TASKING provide to existing customers who are transitioning to RISC‑V?

Ben Abder­rah­man    The TASKING tools are built on the Viper com­pil­er frame­work, which allows rapid retar­get­ing and opti­miza­tion for dif­fer­ent microar­chi­tec­tures, min­i­miz­ing migra­tion com­plex­i­ty. Fur­ther­more, TASKING pro­vides man­u­als and migra­tion guides tai­lored for safe and secure tool usage.
The doc­u­men­ta­tion includes best prac­tices for adapt­ing exist­ing code­bas­es to RISC‑V, opti­miz­ing for per­for­mance, and ensur­ing com­pli­ance. 

How do recent strategic moves such as the LDRA acquisition and expanded RISC‑V support align with TASKING’s long-term vision?

Ben Abder­rah­man    Those recent strate­gic moves are tight­ly aligned with our long-term vision to become a cer­ti­fi­ca­tion-ready tool­chain provider for safe­ty-crit­i­cal appli­ca­tions across auto­mo­tive, aero­space, and other embed­ded sec­tors. 
The LDRA acqui­si­tion helps to offer an end-to-end develop­ment and ver­i­fi­ca­tion plat­form, cov­er­ing the entire life­cy­cle from cod­ing to com­pli­ance. It also expands our reach into aero­space and defense, where LDRA is strong.
TASKING’s invest­ment in RISC‑V sup­port reflects our com­mit­ment to ven­dor inde­pen­dence and archi­tec­tur­al flex­i­bil­i­ty. It will help posi­tion­ing TASKING as a leader in next-gen embed­ded develop­ment, while sup­port­ing the shift toward cus­tom sil­i­con and soft­ware-defined archi­tec­tures. It will also enable cross-indus­try adop­tion, from auto­mo­tive to indus­tri­al and med­ical sys­tems. 

What are the key technology areas or markets that TASKING aims to focus on moving forward, and what preparations are being made to support this?

Ben Abder­rah­man    TASKING con­tin­ues to invest in com­pil­ers, debug­gers, sta­t­ic and dynam­ic test­ing, and safe­ty libraries tai­lored for safe­ty-crit­i­cal appli­ca­tions. These tools are deeply inte­grat­ed into cus­tomer work­flows and sup­port long prod­uct life­cy­cles. In addi­tion to that we are explor­ing AI-enhanced soft­ware develop­ment and test­ing, includ­ing vir­tu­al­ized envi­ron­ments that sup­port hard­ware abstrac­tion and sim­u­la­tion. 

What is the next crucial step for TASKING to grow in the global market, and how do you view the role of the Korean market in this strategy?

Ben Abder­rah­man    To grow in the glob­al mar­ket, TASKING’s next cru­cial step involves deep­en­ing its pres­ence in high-growth regions and align­ing its offer­ings with emerg­ing tech­nol­o­gy trends, par­tic­u­lar­ly in auto­mo­tive, indus­tri­al automa­tion, robot­ics and aero­space & defense. TASKING must tai­lor its approach to each region, choos­ing between joint ven­tures, sub­sidiaries, or licens­ing mod­els depend­ing on reg­u­la­to­ry com­plex­i­ty and mar­ket matu­ri­ty. Build­ing strong local alliances with OEMs, Tier 1 sup­pli­ers, and semi­con­duc­tor com­pa­nies is essen­tial for gain­ing mar­ket access and cred­i­bil­i­ty. Korea is a glob­al leader in semi­con­duc­tors, auto­mo­tive elec­tron­ics, and smart infra­struc­ture, align­ing per­fect­ly with TASKING’s embed­ded soft­ware focus. Kore­an firms are increas­ing­ly adopt­ing AI, EV plat­forms, and autonomous sys­tems, cre­at­ing demand for high-per­for­mance, safe­ty-com­pli­ant soft­ware tools. We see the Kore­an mar­ket as the ideal blue­print for our glob­al strat­e­gy.

Inter­view orig­i­nal­ly pub­lished by AEM (Auto­mo­tive Elec­tron­ics Mag­a­zine)

Read the orig­i­nal arti­cle here.

Author: BJ Yoon_bjyun@autoelectronics.co.kr