VLAB Vir­tu­al Develop­ment Machines (VDMs) pro­vide fast level 4 vir­tu­al ECUs for auto­mo­tive and embed­ded soft­ware develop­ment and test. With soft­ware-defined vehi­cles (SDV), con­tin­u­ous soft­ware updates and develop­ment through­out the life­cy­cle is crit­i­cal.

Vir­tu­al­iza­tion pro­vides devel­op­ers with the nec­es­sary fast and scal­able infra­struc­ture for soft­ware inte­gra­tion and test.

VDMs can be used before hard­ware is avail­able for soft­ware and sys­tem shift-left, as well as for ongo­ing soft­ware develop­ment for in-pro­duc­tion and out-of-pro­duc­tion hard­ware.

VDMs run the same soft­ware as the real hard­ware, includ­ing Autosar clas­sic and adap­tive stacks, Linux, QNX, RTOS, and Hyper­vi­sor-based con­fig­u­ra­tions.

They sim­u­late com­plete boards (ECUs, HPC nodes, cus­tom boards, etc.) and sup­port sim­u­lat­ing net­works and inte­gra­tion with com­plete sys­tem dig­i­tal twin solu­tions. Soft­ware can be test­ed, val­i­dat­ed, and debugged on VDMs before deploy­ing the same bina­ries on the phys­i­cal hard­ware.

VLAB VDMs are designed for speed, using a mod­ern sim­u­la­tion ker­nel com­bined with advanced instruc­tion-set sim­u­la­tion tech­niques and par­al­lel exe­cu­tion to max­i­mize per­for­mance. They pro­vide winIDEA with unmatched vis­i­bil­i­ty into the tar­get sys­tem, includ­ing proces­sors, mem­o­ries, and periph­er­al devices.

Python script­ing enables auto­mat­ed debug­ging and test­ing across both winIDEA and VLAB tool­chains.

winIDEA sup­ports VLAB VDMs and offers the same front-end and func­tion­al­i­ty used for on-tar­get soft­ware develop­ment, debug­ging, and test­ing — regard­less of whether the tar­get is vir­tu­al or phys­i­cal. Devel­op­ers can switch between vir­tu­al and phys­i­cal ECUs with a sin­gle click and con­tin­ue work­ing in the famil­iar winIDEA envi­ron­ment.

Like­wise, the winIDEA SDK pro­vides iden­ti­cal inter­faces, allow­ing the same Con­tin­u­ous Inte­gra­tion (CI) automa­tion scripts to run with­out mod­i­fi­ca­tion on both real and vir­tu­al ECUs.

• Low-level soft­ware develop­ment develop­ment, includ­ing dri­vers and oper­at­ing sys­tems
• AUTOSAR CP inte­gra­tion
• Mid­dle­ware develop­ment
• Appli­ca­tion develop­ment
• Test automa­tion and con­tin­u­ous inte­gra­tion and deploy­ment
• Com­plex soft­ware debug
• Pre-sil­i­con soft­ware develop­ment and test­ing