|
70
|
1 |
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
|
|
|
2 |
<html>
|
|
|
3 |
<head>
|
|
|
4 |
<title>Target Communication Framework</title>
|
|
|
5 |
</head>
|
|
|
6 |
<body>
|
|
|
7 |
<h1>Target Communication Framework </h1>
|
|
|
8 |
|
|
|
9 |
<p>Copyright (c) 2007, 2008 Wind River Systems, Inc. and others. Made available under the EPL v1.0
|
|
|
10 |
(Agent portion made available under your choice of EPL v1.0 or EDL v1.0 dual-license).
|
|
|
11 |
<p>Direct comments, questions to the <a href="mailto:dsdp-tcf-dev@eclipse.org">dsdp-tcf-dev@eclipse.org</a> mailing list
|
|
|
12 |
|
|
|
13 |
<h2>Available Documentation</h2>
|
|
|
14 |
|
|
|
15 |
<table border=1 cellpadding=8>
|
|
|
16 |
<tr>
|
|
|
17 |
<td><a href='TCF Project.html'>TCF Project Overview</a>
|
|
|
18 |
<td width=500>TCF project goals and results
|
|
|
19 |
<tr>
|
|
|
20 |
<td><a href='TCF Getting Started.html'>TCF: Getting Started</a>
|
|
|
21 |
<td width=500>Getting started with TCF - creating Eclipse workspace, building agent, making a first connection
|
|
|
22 |
<tr>
|
|
|
23 |
<td><a href='TCF Specification.html'>TCF Specifications</a>
|
|
|
24 |
<td width=500>Design goals, requirements and format of TCF communication protocol,
|
|
|
25 |
framework API and software design considerations
|
|
|
26 |
<tr>
|
|
|
27 |
<td><a href='TCF Services.html'>TCF Services Definitions</a>
|
|
|
28 |
<td width=500>TCF communication model is based on the idea of services.
|
|
|
29 |
A service is a group of related commands, events and semantics.
|
|
|
30 |
New services are expected to be defined by developers of tools and target agents.
|
|
|
31 |
To achieve certain level of compatibility of tools/targets TCF inclides definitions
|
|
|
32 |
of common services
|
|
|
33 |
<tr>
|
|
|
34 |
<td><a href='TCF Context Identifier Explanation.html'>TCF Context Identifier Explanation</a>
|
|
|
35 |
<td width=500>Most if not all TCF services functions need some way to identify what entity e.g. process,
|
|
|
36 |
thread, task, device on JTAG scan chain, etc they should operate on.
|
|
|
37 |
To do this TCF uses a context identifier (aka ContextId). This document is attempting to explain how
|
|
|
38 |
ContextIds are intended to be used
|
|
|
39 |
<tr>
|
|
|
40 |
<td><a href='TCF Linux Agent Prototype.html'>TCF Agent Prototype</a>
|
|
|
41 |
<td width=500>
|
|
|
42 |
Brief description of the TCF target agent prototype implementation
|
|
|
43 |
<tr>
|
|
|
44 |
<td>
|
|
|
45 |
<a href='TCF Agent Porting Guide.html'>TCF Agent Porting Guide</a>
|
|
|
46 |
<td width='500'>A guide for porting and customizing TCF agent code
|
|
|
47 |
</table>
|
|
|
48 |
|
|
|
49 |
</body>
|
|
|
50 |
</html>
|