© 2002 IBM Corporation Confidential | Date | Other Information, if necessary November 4, 2014 Copyright © 2008 Eclipse Foundation, Inc., Made available under the Eclipse Public License v 1.0 Target Communication Framework ECSI System Debug Workshop, Mar 10, 2008 Felix Burton

Copyright © 2008 Eclipse Foundation, Inc., Made available under the Eclipse Public License v 1.0 Agenda Background Out Line Motivation Core Design Ideas Example use cases Status 2

Copyright © 2008 Eclipse Foundation, Inc., Made available under the Eclipse Public License v 1.0 Background Cross development tools need communication link between host and target Many tools, each typically using its own agent and communication method Lots of overlap between these, e.g. how to communicate, retrieve/model target objects, manipulate target, etc 3

Copyright © 2008 Eclipse Foundation, Inc., Made available under the Eclipse Public License v 1.0 Out Line Define an open end to end tool to target communication mechanism for the purpose of development, debug, monitor, analysis and test Specification Transport channel supporting extensible set of services Typically on top of a TCP/IP stream, but other transports supported as needed but the target Services defining commands, progress, replies, events & semantics Discovery of available servers and services Prototype implementation Eclipse plug-ins C-based agent Scope Cross tools (i.e. host and target are different) benefits the most, but is applicable to native tools as well Target agent, OCD/JTAG and simulator connections 4

Copyright © 2008 Eclipse Foundation, Inc., Made available under the Eclipse Public License v 1.05 Existing Architectures 5 UI Target Tool A Tool B Tool C Tool D Agent A Agent B Agent C Value Add B Value Add C Host P1 P3 P2

Copyright © 2008 Eclipse Foundation, Inc., Made available under the Eclipse Public License v 1.0 Motivation Almost every cross development tool have their own infrastructure (agent, connection, protocol, setup, etc) This leads to: Poor user experience Each tools has its own target configuration Increased target intrusion (footprint, multiple agent interaction) Inconsistent product availability matrix No sharing between agents Duplicated maintenance effort New features have to be added in multiple places New tools have to start from ground zero Limited Eco-system 6

Copyright © 2008 Eclipse Foundation, Inc., Made available under the Eclipse Public License v 1.0 Core Design Ideas Service knows best how to represent the system – get information from there and data-drive layers above If not possible, put the knowledge in the lowest possible layer and data drive the layers above Use the same protocol end-to-end, but allow value-adding servers to intercept select services when needed and pass- through everything else Services as building blocks that can be used by multiple clients (tools) for different environments (target agent, OCD, simulator) Avoid tools specific agents Bridge gap with environment specific services to setup/configure common services Support high latency communication links 7

Copyright © 2008 Eclipse Foundation, Inc., Made available under the Eclipse Public License v 1.0 Architecture Overview 8 UI Target Tool A Tool B Tool C Tool D Service Manager Service 1 Value Add Host Service 2 Service 3 Service 4 Service 5 P1

Copyright © 2008 Eclipse Foundation, Inc., Made available under the Eclipse Public License v 1.0 Use Case: SimpleJtagDevice Debug (run-control, breakpoint, memory register) Possibly Others (flash programming, download, etc) 9

Copyright © 2008 Eclipse Foundation, Inc., Made available under the Eclipse Public License v 1.0 Use Case: TestExceutionAgent Process launch and kill Standard I/O redirection File system access 10

Copyright © 2008 Eclipse Foundation, Inc., Made available under the Eclipse Public License v 1.0 Use Case: LinuxUserModeAgent Debug (run-control, breakpoint, memory, register) OS Awareness (process/thread list, CPU utilization, etc) Process launch and kill Standard I/O redirection File system access Monitoring (event-config, event-log) 11

Copyright © 2008 Eclipse Foundation, Inc., Made available under the Eclipse Public License v 1.0 Prototype Status Eclipse plug-ins Remote file system access and simple top style monitoring integrated with RSE Basic debugging integrated with Eclipse Core Debug plug- ins DSF integration in the works C-based agent Services needed by Eclipse plug-ins Simple UDP based discovery Functional on Linux and VxWorks 12

Copyright © 2008 Eclipse Foundation, Inc., Made available under the Eclipse Public License v 1.0 Specification Status Transport Channel Current Services Run Control, Memory, Register, Breakpoint, Processes, Stack Trace, File System, System Monitoring Review of current and specification of additional services in power.org and Eclipse 13

Copyright © 2008 Eclipse Foundation, Inc., Made available under the Eclipse Public License v 1.0 Links Prototype source repository svn://dev.eclipse.org/svnroot/dsdp/org.eclipse.tm.tcf/trunk ot=DSDP_SVN ot=DSDP_SVN FAQ 14

Copyright © 2008 Eclipse Foundation, Inc., Made available under the Eclipse Public License v 1.0 QUESTIONS/COMMENTS? 15