Community
Participate
Working Groups
For target management we need an infrastructure for creating descriptions of arbitrary targets. Targets man span many things: remote Linux/AIX/Windows/etc server, embedded RTOS via Ethernet, bare iron core via JTAG, the host workstation, etc. We need to define: -how target descriptions are used -interfaces for target descriptions -how factories for target descriptions are cataloged -how all of this fits with RSE -how target descriptions can be passed to other components to be used, e.g. passing a target description to a debugger to use. "Close to the hardware" target descriptions have specific needs regarding specification of -what cores are in a target -layout of memory (per core, shared) -registers in a core -bits in registers -groups of registers -peripherals (memory mapped registers) It has been suggested that we use SPIRIT as a file format for this information, because SPIRIT already has much of this information. A set of requirements and discussion has been placed here: http://wiki.eclipse.org/index.php/DSDP/DD/Spirit
Some of the needs for target descriptions (especially with respect to multicore) might be addressable by a concept of Target Groups or Connection Groups. There is a technology subgroup for this at http://wiki.eclipse.org/index.php/DSDP/TM/Connection_Groups. Dave Dykstal wrote up an example of how device information could be shown in the RSE UI hierarchy, see http://wiki.eclipse.org/index.php/DSDP-TM_Proposal_for_RSE_Hierarchy_by_Dave_Dykstal_2005x11x09 Tom Hochstein also had some ideas what a hierarchy for Multicore could look like: http://dev.eclipse.org/mhonarc/lists/dsdp-tm-dev/msg00161.html With respect to the "close to hardware" descriptions, the simplest way of describing a target could be that a property of the target is a file path that points to a SPIRIT file holding the description. I do think, however, that there are at least some properties that would make sense representing in the form of Java data structures and interfaces (though not all of them). And then there are target properties that are interesting in the context of shared board labs -- allowing users to search a target from a list of cataloged ones, based on some search criteria like CPU architecture, amount of RAM, physical location etc.
This will be considered again for RSE 2.0
Need to investigate - Implementation not planned yet.
