From Infineon ModusToolbox to TASKING winIDEA: debug virtual or physical targets

Modus­Tool­box Project Cre­ator gen­er­ates device-spe­cif­ic project files for Visu­al Stu­dio Code or Eclipse for Modus­Tool­box. Both envi­ron­ments can use TASKING winIDEA through an exten­sion or plu­g­in, giv­ing embed­ded soft­ware teams a con­sis­tent path from project cre­ation to develop­ment and debug­ging.

The challenge

Embed­ded teams need a smooth path from project gen­er­a­tion to soft­ware develop­ment, debug­ging, ver­i­fi­ca­tion, and deploy­ment.

Modus­Tool­box Project Cre­ator makes it easy to gen­er­ate a project for the select­ed Infi­neon device and develop­ment envi­ron­ment. The next step is con­nect­ing that project to a debug­ging envi­ron­ment.

In our case devel­op­ers may work in Visu­al Stu­dio Code, Eclipse for Modus­Tool­box, or direct­ly in winIDEA. They have the free­dom to choose either vir­tu­al or phys­i­cal tar­gets or switch between them.

How TASKING can help

Today, Modus­Tool­box Project Cre­ator has built-in sup­port to work with TASKING winIDEA:

#1 Visu­al Stu­dio Code + winIDEA exten­sion

Cre­ate a project with Modus­Tool­box Project Cre­ator, install the winIDEA exten­sion in VS code and open the pre­vi­ous­ly gen­er­at­ed project.

The winIDEA exten­sion makes winIDEA func­tion­al­i­ty avail­able inside of VS code to down­load and exe­cute code on your tar­get.

#2 Eclipse for Modus­Tool­box + winIDEA plu­g­in

The same idea applies for the winIDEA Eclipse plu­g­in. It allows you to use winIDEA fea­tures as part of the Eclipse envi­ron­ment.

Direct winIDEA workflow

The two built-in IDE work­flows are not the only option avail­able.

When cre­at­ing a project in Modus­Tool­box project cre­ator, you can select Tar­get IDE = None. This cre­ates an IDE-inde­pen­dent project, that can be opened direct­ly in winIDEA. This approach is ideal for teams that pre­fer a ded­i­cat­ed winIDEA-based develop­ment and debug­ging work­flow with­out rely­ing on Visu­al Stu­dio Code or Eclipse.

Sim­pli­fy­ing the work­flow fur­ther

Although Modus­Tool­box projects can already be used with winIDEA, there is still room to improve the user expe­ri­ence.

The main chal­lenge across all work­flows is the ini­tial con­fig­u­ra­tion of a winIDEA work­space. At the moment you need to con­nect the gen­er­at­ed project with a winIDEA work­space before you can down­load embed­ded soft­ware to your tar­get and start debug­ging it.

TASKING is work­ing on a solu­tion that makes it eas­i­er to use Modus­Tool­box gen­er­at­ed projects inside of winIDEA. The goal is to cre­ate a smoother tran­si­tion from project cre­ation to debug­ging.

Why this makes life easier

  • One project gen­er­a­tion flow: Projects are gen­er­at­ed for the select­ed tar­get device and pre­ferred develop­ment envi­ron­ment.
  • One work­flow, mul­ti­ple tar­gets: Use the same project with vir­tu­al or phys­i­cal tar­gets or both.
  • Use your pre­ferred develop­ment envi­ron­ment: Work in Visu­al Stu­dio Code, Eclipse for Modus­Tool­box, or direct­ly in winIDEA.
  • Down­load and debug on tar­get hard­ware: Use TASKING Blue­Box and winIDEA to con­nect to and debug sup­port­ed tar­gets.
  • Less man­u­al con­fig­u­ra­tion: Auto­mat­ic winIDEA work­space gen­er­a­tion will reduce setup time.

From Project Gen­er­a­tion to Pro­fes­sion­al Debug­ging

The com­bi­na­tion of Infi­neon Modus­Tool­box Project Cre­ator, TASKING winIDEA, and TASKING Blue­Box pro­vides a flex­i­ble work­flow from project gen­er­a­tion to soft­ware down­load, debug­ging, and ver­i­fi­ca­tion. Whether you work with vir­tu­al or phys­i­cal tar­gets, or both. You can con­tin­ue using your pre­ferred develop­ment envi­ron­ment while ben­e­fit­ing from winIDEA’s advanced debug­ging capa­bil­i­ties.

Learn how Modus­Tool­box Project Cre­ator can cre­ate projects files com­pat­i­ble TASKING winIDEA

Step-by-step guide
Learn more
Scroll to Top