Getting started

Beginning with the ModusToolbox™ tools package version 3.4.0, Eclipse for ModusToolbox™ is no longer included by default. Instead, it is a separate package that you can install via the ModusToolbox™ Setup program.

The Setup program is located on our website here: https://softwaretools.infineon.com/tools/com.ifx.tb.tool.modustoolboxsetup. It is used to install base packages and additional packages on Windows, Linux, and macOS. Refer to the ModusToolbox™ software installation guide for specific instructions.

Eclipse is installed in the following directory, by default:

C:\Users\<UserName>\Infineon\Tools\ModusToolboxEclipse

To launch Eclipse:

• On Windows, select Eclipse for ModusToolbox™ <version> item from the Start menu.
• For other operating systems, run the "modustoolbox" executable file.
• You can also launch Eclipse from the dashboard for all operating systems. For more information refer to the dashboard user guide.

When launching Eclipse, it provides an option to select the workspace location on your machine. This location is used by Eclipse for creating and storing the files as part of application creation for a particular platform. The default workspace location is a folder called "mtw" in your home directory. You may add additional folders under the "mtw" folder or to choose any other location for each workspace.

For more details about Eclipse, refer to Eclipse documentation, as well as the Eclipse survival guide.

To configure Tools and Toolchains, open the Preferences menu and select ModusToolbox™ Tools.

To select your preferred toolchain, open the Properties menu and choose between the different toolchain options.

See the table below for more specific information on available tools and toolchains.

Common auto-discovery search directories for each OS include:

Windows:

Linux:

macOS:

Click the New Application link in the Eclipse Quick Panel.

You can also select File > New > ModusToolbox™ Application.

These commands launch the Project Creator tool, which provides several applications for use with different development kits. The kits available may change over time.

For more details about using this tool, refer to the Project Creator user guide.

After loading an application, build it to generate the necessary files. Select a project. Then, in the Quick Panel, click the Build Application link. The following images show the Quick Panel for a typical PSOC™ MCU application and an AIROC™ Bluetooth® application.

Messages display in the Console, indicating whether the build was successful or not. For more details about building applications and the various Consoles available, see the Build applications chapter.

There are many more details about programming an application. This section only covers it briefly. For more detailed information, see the Program and debug chapter.

In the Project Explorer, select the desired project. Then, in the Quick Panel, click the <app-name> Program (KitProg3_MiniProg4) link for a PSOC™ MCU application, and <app-name> Program for an AIROC™ Bluetooth® application.

There are several ways to share a ModusToolbox™ application. Refer to the ModusToolbox™ tools package user guide in the "Version Control and sharing applications" chapter for more general details.

Using Eclipse, you can use the export function to essentially make a copy of your application that you can share with a colleague. There are several ways to export using Eclipse. The option we recommend is to select the application and then use File > Export > General > Archive File, which creates a ZIP file.

Keep in mind that a typical ModusToolbox™ application includes many libraries that are available on GitHub. These get regenerated during the make getlibs command. Therefore, you can substantially reduce the size of your exported application by excluding the libraries. Plus, the exported mtb_shared folder might retain hard-coded paths that would cause issues after importing the application.

For multi-core applications, Eclipse export function shows the core project folders along side the main application folder. These project folders are included in that main application folder, so you should exclude them from the export process as well.

On the Export dialog, select only the main application folder(s) to export. You may need to review your application in Eclipse to determine which folders you should exclude. By default, subproject folders include an extension after the application name.

Click Browse… to navigate to the location to save the archive and provide a file name.

Click Finish to generate the archive file.

If you have a ModusToolbox™ application that you want to import into Eclipse, run the make getlibs command before importing it into Eclipse.

Then, either use the Import Existing Application In-Place link on the Quick panel or open through the File > Import ModusToolbox™ > Import Existing Application In-Place option.

Note:

This option does not copy or move the application location on disk; it only makes a reference for Eclipse to the current application location.

On the next page, click the Browse… button, navigate to the application directory, and click Select Folder.

Click Finish to begin the import process. This will take a few moments, and then the application will display in Eclipse Project Explorer.

If the Console displays a message, such as "Error creating Eclipse configurations," open the Library Manager and click Update. This runs the make getlibs operation to generate the necessary files and libraries.