Start development and initial integration work with virtual hardware

Before a real tar­get hard­ware is avail­able, it makes sense to start develop­ment and ini­tial inte­gra­tion work with vir­tu­al hard­ware. The increas­ing com­plex­i­ty of embed­ded soft­ware in gen­er­al, time-to-mar­ket, and the early setup of test automa­tion jus­ti­fy the use of such vir­tu­al hard­ware also called Vir­tu­al Tar­get or Vir­tu­al Pro­to­type. 

The TASKING winIDEA IDE for Syn­op­sys VDK (Vir­tu­al Develop­ment Kit) and Syn­op­sys Sil­ver use the same front-end and func­tion­al­i­ty used for on-tar­get soft­ware develop­ment and debug­ging. As soon as tar­get hard­ware is avail­able, sim­ply switch to it with a mouse click and con­tin­ue work­ing on real hard­ware. Sim­i­lar­ly, any automa­tion scripts that use the TASKING debug and test automa­tion SDK can be used on a vir­tu­al or a real ECU with­out any changes. 

Syn­op­sys VDKs enable soft­ware develop­ment in much ear­li­er design cycle phas­es and are suit­ed for soft­ware develop­ment of: 

  • Device dri­vers 
  • Oper­at­ing sys­tem (OS) bring-up 
  • Mid­dle­ware 

The main use cases for the TASK­ING-Syn­op­sys VDK setup: 

  • Boot­loader and dri­ver develop­ment 
  • Micro­con­troller Abstrac­tion Layer (MCAL) develop­ment & inte­gra­tion  
  • Ini­tial inte­gra­tion of an AUTOSAR Stack: Basic Soft­ware (BSW) includ­ing the MCAL, Run-Time-Envi­ron­ment (RTE) & Appli­ca­tion Layer 
  • Regres­sion-Test­ing, Test­ing of Hard- and Soft­ware-Inte­gra­tion 
  • Test Automa­tion & Con­tin­u­ous Inte­gra­tion (CI) 

Cur­rent­ly sup­port­ed devices: 

  • ARM Base Ref­er­ence 
  • S32K388 
  • SR6P7G7 
  • TC39x 
  • TC4x
  • TC38x
  • TC36x

Syn­op­sys Sil­ver enables early Soft­ware-in-the-Loop develop­ment, pro­to­typ­ing, and test­ing. Main use cases focus on: 

  • Appli­ca­tion Soft­ware develop­ment 
  • Appli­ca­tion Soft­ware inte­gra­tion 
  • Basic Soft­ware develop­ment (par­tial­ly) 
Scroll to Top