Target Communication Framework

Copyright (c) 2007-2019 Wind River Systems, Inc. and others. Made available under the EPL 2.0
Agent portion made available under your choice of EPL 2.0 or EDL v1.0 dual-license.

Direct comments, questions to the mailing list

Available Documentation

TCF Project Overview TCF project goals and results
TCF: Getting Started Getting started with TCF - creating Eclipse workspace, building agent, making a first connection
TCF Specifications Design goals, requirements and format of TCF communication protocol, framework API and software design considerations
TCF Services Definitions TCF communication model is based on the idea of services. A service is a group of related commands, events and semantics. New services are expected to be defined by developers of tools and target agents. To achieve certain level of compatibility of tools/targets TCF inclides definitions of common services
TCF Context Identifier Explanation Most if not all TCF services functions need some way to identify what entity e.g. process, thread, task, device on JTAG scan chain, etc they should operate on. To do this TCF uses a context identifier (aka ContextId). This document is attempting to explain how ContextIds are intended to be used
TCF Agent Prototype Brief description of the TCF target agent prototype implementation
TCF Agent Porting Guide A guide for porting and customizing TCF agent code
TCF UDP Discovery TCF UDP Discovery protocol specifications
TCF Lua Integration Using Lua programming language with TCF