Ithy - Is Eclipse IDE Support Vanishing from ModusToolbox? The Truth Behind the Changes

Highlights

Continued Support: Infineon ModusToolbox™ continues to fully support the Eclipse IDE as a development environment. There are no plans to discontinue it.
Optional Installation: Starting with ModusToolbox™ version 3.5, the Eclipse IDE and GCC toolchain are no longer mandatory, bundled packages. They must be installed optionally via the ModusToolbox™ Setup program if desired.
Multi-IDE Flexibility: This change enhances flexibility, allowing developers to choose their preferred IDE (like VS Code, IAR, Keil µVision) while maintaining Eclipse as a robust, supported option.

The Current State of Eclipse IDE in ModusToolbox™

Contrary to any potential concerns, Infineon's ModusToolbox™ software development kit (SDK) is not stopping support for the Eclipse Integrated Development Environment (IDE). As of the latest information available (May 2, 2025), the Eclipse IDE remains a fully supported, actively maintained, and well-integrated option within the ModusToolbox™ ecosystem.

Evolution, Not Termination: Understanding the Shift

Recent changes, particularly starting with ModusToolbox™ version 3.5, have altered how the Eclipse IDE is distributed, but not its availability or support status. Previously, Eclipse might have been more tightly bundled. Now, the installation process is more modular:

Optional Installation: The Eclipse IDE and the GCC toolchain are no longer included as mandatory components in the base ModusToolbox™ package.
ModusToolbox™ Setup Program: Users who wish to use the Eclipse IDE must select it for installation through the dedicated ModusToolbox™ Setup program.
Rationale: This shift aims to provide developers with greater flexibility. Recognizing that many developers utilize other IDEs such as Visual Studio Code (VS Code), IAR Embedded Workbench, or Arm Keil µVision, ModusToolbox™ now allows users to install only the components they need, reducing installation footprint and catering to diverse workflow preferences.

This change reflects an evolution towards an IDE-agnostic framework, empowering users rather than phasing out a popular tool.

Overview of the ModusToolbox™ software environment.

Continued Integration and Robust Feature Set

Despite the change in installation method, the Eclipse IDE for ModusToolbox™ continues to offer a comprehensive development experience. It remains tightly integrated with the SDK's tools and features:

Project Management: Create, build, and manage ModusToolbox™ applications directly within Eclipse.
Configuration Tools: Seamlessly access various configurators (Device Configurator, BSP Assistant, Library Manager, etc.) to set up peripherals, manage libraries, and configure middleware.
Debugging: Utilize robust debugging capabilities, including support for multi-core debugging (e.g., for PSoC™ 6 MCUs), setting breakpoints, and inspecting variables.
Documentation Access: Easily access relevant documentation, code examples, and user guides through integrated features like the Quick Panel.
Dedicated User Guides: Infineon maintains and updates specific documentation, such as the "Eclipse IDE for ModusToolbox™ User Guide," detailing its usage and features.

ModusToolbox™: A Flexible Multi-IDE Ecosystem

ModusToolbox™ is designed to integrate into various development workflows. The support for Eclipse IDE exists alongside robust support for other popular environments. This flexibility allows development teams to choose the tools that best suit their needs and expertise.

Supported Development Environments

ModusToolbox™ officially supports several IDEs, ensuring broad compatibility:

Eclipse IDE for ModusToolbox™
Microsoft Visual Studio Code (VS Code) with ModusToolbox™ extensions
IAR Embedded Workbench
Arm Keil µVision
Command-Line Interface (CLI) for build and programming automation

IDE Comparison within ModusToolbox™

The choice of IDE often depends on developer preference, project requirements, and familiarity. The following chart provides a subjective comparison of the primary graphical IDEs supported by ModusToolbox™ across several factors:

This chart illustrates that while Eclipse offers strong integration and features, alternatives like VS Code excel in areas like community support, ease of use, and extensibility. IAR and Keil µVision are powerful, industry-standard tools particularly known for their compiler and debugger performance, often favored in specific embedded contexts.

Visualizing the ModusToolbox™ IDE Ecosystem

The following mind map provides a visual representation of how Eclipse IDE fits into the broader ModusToolbox™ development environment alongside other tools and components.

mindmap root["ModusToolbox™ Ecosystem"] id1["Development Environments"] id1a["Eclipse IDE
(Supported, Optional Install)"] id1a1["Features:
- Project Management
- Configuration Tools
- Debugging
- Documentation Access"] id1a2["Installation:
Via ModusToolbox™ Setup Program"] id1b["Visual Studio Code (VS Code)"] id1b1["Requires ModusToolbox™ Extension"] id1c["IAR Embedded Workbench"] id1d["Arm Keil µVision"] id1e["Command Line Interface (CLI)"] id2["Core Components"] id2a["Software Development Kit (SDK)"] id2b["Configuration Tools"] id2c["Build System"] id2d["Device Support (PSoC™, XMC™, AIROC™)"] id3["Installation & Updates"] id3a["ModusToolbox™ Setup Program"] id3a1["Installs/Updates Core Tools"] id3a2["Installs Optional IDEs (Eclipse)"] id3a3["Installs Toolchains (GCC, ARM)"] id4["Target Hardware"] id4a["Infineon Microcontrollers (MCUs)"] id4b["Development Kits"]

Programming and Debugging in ModusToolbox™

Regardless of the chosen IDE, ModusToolbox™ provides the necessary tools and software libraries to program and debug Infineon microcontrollers effectively. The workflow typically involves using the IDE to build the application, which utilizes the ModusToolbox™ build system and toolchain, and then using the IDE's debugger interface (often leveraging OpenOCD or J-Link) to flash the device and step through code.

This video, part of the official "Welcome to ModusToolbox™" series, demonstrates the fundamental concepts of programming and debugging applications within the ModusToolbox™ environment. While it may showcase a specific IDE, the underlying principles and tools (like the build system and debug configurations) are applicable across supported environments, including the Eclipse IDE.

ModusToolbox Debug Configuration Example

Example of Debug Configurations within an IDE for ModusToolbox™.

Summary Table: ModusToolbox™ Supported IDEs

This table summarizes the key characteristics of the main graphical IDEs supported by ModusToolbox™:

IDE	Integration Level	Installation Method	Key Strengths	Primary User Base
Eclipse IDE for ModusToolbox™	Deep integration, specific plugins	Optional via Setup Program	Mature platform, comprehensive features, good ModusToolbox™ tool access	Existing Eclipse users, developers preferring traditional C/C++ IDEs
Visual Studio Code (VS Code)	High integration via extensions	Separate install + ModusToolbox™ extension	Modern interface, highly extensible, large community, lightweight	Developers preferring modern editors, cross-platform development, strong extension ecosystem
IAR Embedded Workbench	Supported, project generation	Separate commercial license/install	Highly optimized compiler, industry standard, advanced debugging	Professional embedded developers, safety-critical applications
Arm Keil µVision	Supported, project generation	Separate commercial license/install	Strong Arm ecosystem support, industry standard, robust debugger	Professional embedded developers, primarily Arm-based projects