| | 42 | = GNU Debugger Integration = |
| | 43 | |
| | 44 | |
| | 45 | This can be accomplished using the [http://www.zylin.com/embeddedcdt.html Zylin Embedded CDT plugin]. There may be other RTEMS specific items that could enhance the debugger interface in Eclipse. Perhaps when using CEXP and the RTEMS GDB stub, you can build a module and click a button to download it to the target? CDT also supports the GDB. |
| | 46 | = Interaction with the Target System = |
| | 47 | |
| | 48 | |
| | 49 | There are Eclipse plug-ins that provide serial terminal emulation, Telnet, and FTP connections to the remote target. Using these would provide a more integrated RTEMS development/debug environment. This functionality is currently provided by the Eclipse Remote Systems Explorer (RSE) plugin. |
| | 50 | = Integration Eclipse Device Software Development Platform = |
| | 51 | |
| | 52 | |
| | 53 | The [http://www.eclipse.org/dsdp Eclipse DSDP] is an effort to use eclipse as a standard way of developing, debugging and otherwise interacting with embedded devices. |
| | 54 | |
| | 55 | There are many sub-projects in there, but some of the interesting ones are: [http://www.eclipse.org/dsdp/dd Device Debugging] and [http://www.eclipse.org/dsdp/tm Target management]. |
| | 56 | |
| | 57 | One of the interesting aspects of this is how Wind River has adopted Eclipse as the platform for vxWorks and Embedded Linux development. It appears that they are putting significant effort into contributing code back to the DSDP platform and trying to help create open standards for this type of development environment. It would be nice if this work ends up meaning that an Eclipse platform could talk to a target server on either vxWorks, Linux or RTEMS. |
| | 60 | = Repository = |
| | 61 | |
| | 62 | |
| | 63 | The [http://www.rtems.com/cgi-bin/cvsweb.cgi/rtems-eclipse-plug-in/#dirlist project repository] is hosted by OAR and is available via <tt>:pserver:anoncvs@www.rtems.org:/usr1/CVS</tt> and module <tt>rtems-eclipse-plug-in</tt>. It contains the following submodules: |
| | 64 | * <tt>org.rtems.cdt</tt>: Plug-in for further development |
| | 65 | * <tt>org.rtems.feature</tt>: Deployable components |
| | 66 | * <tt>org.rtems.update</tt>: Update site |
| | 67 | * <tt>org.rtems.cdt.toolchain</tt>: Initial plug-in |
| | 68 | * <tt>org.rtems.cdt.toolchain2</tt>: Temporary development plug-in (obsolete) |
| | 69 | = Current Status = |
| | 70 | |
| | 71 | |
| | 72 | The plug-in is usable and tested on Cygwin, MinGW, MacOS X and UNIX. See also the [wiki:Developer/Eclipse/Plugin user guide]. |
| | 73 | = Features = |
| | 74 | |
| | 75 | |
| | 76 | * Extends the CDT GNU toolchain with the RTEMS tools (cross-compiler, linker, assembler, archiver) |
| | 77 | * No dependency on special environment variable settings (including PATH) |
| | 78 | * Automatic detection of tool options via the standard Makefile interface |
| | 79 | = TODO List = |
| | 80 | |
| | 81 | |
| | 82 | * Project types for libraries and loadable modules (CEXP) |
| | 83 | * Project templates |
| | 84 | * Automatic detection of default paths for platforms (Cygwin and MinGW) and RTEMS base installation and BSPs |
| | 85 | * RTEMS manager inclusion/exclusion via the Project Properties Pages (applies to executables only) |
| | 86 | * GDB and Qemu Launch Configurations: attach debugger or launch simulator/emulator with your project's product |
| | 87 | * Ability to disable the usage of the discovered compiler search path and/or options |
| | 88 | * Check of user input (paths) and proper error notification if something goes wrong |
| | 89 | * More stable scanner configuration (this is more a CDT internal issue) |
| | 90 | * Per configuration platform and BSP paths (this simplifies migration) |
| 78 | | # Make initial implementation work on one host platform (Status: Done) |
| 79 | | # Make it work on more host platforms (Status: almost done, it's working on Windows, Mac and Linux) |
| 80 | | # Instead of getting configuration parameters via environment variables, try to retrieve such information from configuration files of RTEMS BSP installation. (Status: Daron and Sebastian are working on it.) |
| 81 | | # Get feedback from RTEMS community for further improvements (Status: ongoing) |
| | 127 | * 2008-11-23: Daron Chabot made it work on Mac and Linux. |
| | 128 | |
| | 129 | * 2008-11-21: Sebastian Huber started an [http://www.rtems.com/cgi-bin/cvsweb.cgi/rtems-eclipse-plug-in/org.rtems.cdt.toolchain2 alternative implementation]. |
| | 130 | |
| | 131 | * 2008-11-20: OAR provided a [http://www.rtems.com/cgi-bin/cvsweb.cgi/rtems-eclipse-plug-in/#dirlist repository] for development |
| | 132 | |
| | 133 | * 2008-11-20: Robert Fu published the [wiki:Initial_RTEMS_Eclipse_Plug-in initial implementation], which was only tested on Windows. |
![[RTEMS Logo]](/images/logo.png){kind=logo}
