Introduction

Eclipse/CDT is an IDE which allows developers to create, edit and debug projects based on C/C++. Its name is better understood by considering its constituent parts: Eclipse is an open-source framework and workbench for the implementation of Integrated Development Environments (IDEs). CDT - the C/C++ Development Toolkit - is a set of additional code modules (plug-ins) for the Eclipse framework which allow projects based on C or C++ to be created, developed and managed.

In a similar way to CDT providing plug-ins to Eclipse in order to provide specific functionality, eCosCentric provides additional plug-ins which adapt Eclipse/CDT to configure and build eCos applications, and debug them on target hardware. These plug-ins are collectively known as the eCosPro Eclipse/CDT plug-in.

Enhancements provided by the eCosPro Eclipse/CDT plug-in include the following:

  • The ability to create eCos C/C++ Application Projects. Projects of this type are associated with a specific eCos Configuration Project.

  • The ability to configure and build the eCos real-time operation system (RTOS) as well as the eCosPro components provided with the RTOS. This is achieved through eCos Configuration Projects within the Eclipse framework. With these projects it is possible to edit eCos configurations, and Eclipse will manage rebuilding not only the eCos libraries, but also any dependent eCos Application Projects. An eCos Configuration Project is a distinct project type which allows a single eCos configuration to be conveniently reused across multiple Application and/or static library projects. It can also be shared via the Eclipse Team Provider mechanism which interfaces with various source control systems.

  • Downloading and debugging of executable applications to remote target hardware. The hardware may be running RedBoot or GDB stubs, or it is possible to use a hardware debugger which supports the GDB protocol including JTAG debuggers such as the Ronetix PEEDI. On specific supported targets, BDM may also be available.

  • Robust handling of remote target communication failures

  • The provision of information about eCos kernel threads while debugging

  • The facility to insert hardware-assisted breakpoints where supported by the GDB stub or hardware debugger

  • Associating eCos application projects with a GNU cross development toolchain. Rather than the developer needing to select a specific toolchain, a meta-toolchain termed the eCos toolchain may be used. This meta-toolchain automatically identifies the correct underlying GNU toolchain to use for compilation and debugging, based on information derived from the eCos configuration project associated with this eCos application project.

[Note]Note

Please refer to the chapter “Upgrading from an earlier eCosPro Eclipse/CDT plug-in” if you are upgrading from a release prior to the Juno release of the eCosPro Eclipse/CDT plug-in.