Changes between Version 85 and Version 86 of Developer/OpenProjects


Ignore:
Timestamp:
12/22/08 19:53:19 (15 years ago)
Author:
Sh
Comment:

Redirected to separate page

Legend:

Unmodified
Added
Removed
Modified
  • Developer/OpenProjects

    v85 v86  
    434434
    435435
    436 '''Status:''' Very active as of 14 December 2008.  Ask on the mailing list.
    437 
    438 [http://www.eclipse.org Eclipse] is an open source Integrated Development
    439 Environment (IDE) which has become very popular in the real-time embedded
    440 systems community.  For RTEMS to continue to compare favorably against
    441 its commercial proprietary competition, Eclipse support is an important
    442 feature.  Eclipse has a plug-in architecture and there are already
    443 multiple plug-ins and add-ons for embedded development.
    444 
    445 This is a very open ended project which has a number of steps based
    446 upon subprojects or plugins which need to be made available to RTEMS
    447 developers.
    448 
    449 See http://www.eclipse.org/home/categories/embedded_device.php as
    450 a reference.
    451 
    452 Since RTEMS has multiple targets, this project would focus on getting
    453 Eclipse working nicely with multiple targets.  There are over half a
    454 dozen simulators which are capable of supporting a multithreaded RTEMS
    455 application and a few of those simulate target hardware with networking
    456 capabilities. There are existing RTEMS BSPs that run on simulators so
    457 the person(s) working on this project would not require special target
    458 hardware or anything that costs to verify that their implementation
    459 works with multiple hardware configurations.
    460 
    461 '''Eclipse Integration Sub Projects:'''
    462 
    463 '''Basic cross development integration.''' This can currently be accomplished using Eclipse and the CDT ( C/C++ development toolkit ). There are at  least a few RTEMS users who use Eclipse for RTEMS cross development now. The possible work here ranges from documenting the process of setting it up, and  deciding how the RTEMS applications will be managed and built, all the way to providing RTEMS new project wizards and RTEMS application plugins: One requirement an RTEMS plugin would contribute is an RTEMS "nature" to a C/C++ project: this "nature" would inform Eclipse where to find RTEMS headers and libs, a cross-build toolchain, etc. Accompanying the RTEMS "nature" could be a set of one or more "preference pages" where a developer would configure fairly static items such as RTEMS install and source locations, PATH additions, etc. Finally, an RTEMS new-project "wizard" could be built. Among other duties, this wizard would prompt the user to select from a choice of available BSPs, modify or accept default application configuration parameters such as which RTEMS Managers and filesystems to include, RTEMS_TICKS_PER_MICROSECOND, etc. This sort of implies that a userConf.h template be created (which may be useful elsewhere)...
    464 
    465 The new-project wizard would require the most work, but may well be worth it: How nice would it be for new users to click a few buttons and POOF, an RTEMS "Hello World" application is instantiated from templates and ready to be loaded onto hardware or simulator ???
    466 
    467 '''GNU debugger integration.''' This can be accomplished using the Zylin Embedded CDT plugin:
    468 http://www.zylin.com/embeddedcdt.html
    469 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?
    470 
    471 '''Eclipse interaction with the target system:''' 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.
    472 
    473 '''Integration of RTEMS with the Eclipse Device software development platform:''' The Eclipse DSDP is an effort to use eclipse as a standard way of developing , debugging and otherwise interacting with embedded devices. [[BR]]
    474 Website here: http://www.eclipse.org/dsdp/
    475 
    476 There are many sub-projects in there, but some of the interesting ones are:[[BR]]
    477 Device Debugging: http://www.eclipse.org/dsdp/dd/[[BR]]
    478 Target management: http://www.eclipse.org/dsdp/tm/[[BR]]
    479 
    480 One of the interesting aspects of this is how Wind River has adopted Eclipse as the platform for vxWorks and Embedded Linux development. 
    481 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.
    482 
    483 '''Distribution/packaging:'''  Create an "update site" where Eclipse users can point their IDE at to obtain RTEMS plugins (e.g. http://www.rtems.com/updates).
     436See also: [wiki:Developer/Eclipse/Information RTEMS Eclipse Page].
    484437= CEXP =
    485438