Copyright (c) 2007, 2012 Wind River Systems, Inc. Made available under the EPL v1.0
Direct comments, questions to the firstname.lastname@example.org mailing list
Eclipse can be used for developing clients for TCF in Java. TCF host side code is organized into several Eclipse plug-in projects, below are steps to create and populate Eclipse workspace with TCF projects:
git clone git://git.eclipse.org/gitroot/tcf/org.eclipse.tcf.git git clone ssh://<user>@git.eclipse.org/gitroot/tcf/org.eclipse.tcf.git git clone http://git.eclipse.org/gitroot/tcf/org.eclipse.tcf.git
eclipse.exe -vm <JDK path>/bin/javaw.exe -data <Workspace path> -vmargs -Xmx400M
TCF plugins source code is stored in
<TCF Root>/plugins directory.
Examples source code is stored in
<TCF Root>/examples directory.
<TCF Root>/examples/org.eclipse.tcf.examples.daytime.agentfor example code of a customized TCF agent, which implements DayTime service.
Pre-built TCF plugins are available at Eclipse Update site/p2 repositories. The repositories can be accessed from Eclipse using Help/Install New Software command.
Target Explorer plugins source code is stored in the
<TCF Root>/target_explorer/plugins directory.
Target Explorer 1.1 nightly build: http://download.eclipse.org/tools/tcf/builds/development/nightly
git clone git://git.eclipse.org/gitroot/tcf/org.eclipse.tcf.agent.git git clone ssh://<user>@git.eclipse.org/gitroot/tcf/org.eclipse.tcf.agent.git git clone http://git.eclipse.org/gitroot/tcf/org.eclipse.tcf.agent.git
CDT can be used to build TCF agent.
CDT .project file is located in
<TCF Root>/agent directory.
Linux: To build the agent:
obj/GNU/Linux/i686/Debug/agent -L- -l0Use other -l option values to increase agent log details level.
Windows: For building the agent, there are two possibilities:
make OPSYS=Msysin the agent directory.
<TCF Root>/agent/agent.slnand then build and run the agent using Development Studio commands. If getting an error about IPHlpApi.h missing, you'll need to install the latest MS Platform SDK. For the free Visual C++ Express Edition, the following changes in settings may be necessary:
On VxWorks, the SysMonitor service (needed for RSE Processes Demo) is not yet implemented.
To build the agent: Use Wind River Workbench 3.0 or 3.1, and VxWorks 6.6 or 6.7 to create a Kernel Module project out of source code in
<TCF Root>/agent directory. Use Workbench
commands to build and run the agent. To run the agent on VxWorks Simulator
you will need to setup a simulated network - see Networking with the VxWorks Simulator chapter
in Wind River VxWorks Simulator user's guide for details.
The TCF integration with Python allows writing TCF client and server programs in the Python programming lanugage. TCF Python code is stored in <TCF Root>/python directory.
The TCF integration with Lua allows writing TCF client and server programs in the Lua programming lanugage. See TCF Lua Integration for details.
On Windows, open Project Properties of the agent project, and under C/C++ General > Indexer switch the configuration to "Win32 - Cygwin" or "Win32 - DevStudio" as needed.
For VxWorks, browsing should be configured automatically through the WR Workbench Kernel Module Project.
The Target Explorer aims to create a lightweight but highly flexible and extensible remote system management framework. The focus is on TCF remote system management, but is by no means limited to it. The Target Explorer comes with full remote file system and remote process support, and allows to connect a terminal to the remote system using TCF, SSH, Telnet and serial line.
If building from source, import all org.eclipse.tcf.te.* plug-in's to enable the Target Explorer.
Since Eclipse version 3.8, Target Explorer is available for download from main Eclipse p2 repository. The feature name is "Mobile and Device Development / Target Explorer, TCF".
To connect a remote machine over TCF:
Plugins org.eclipse.tcf.debug and org.eclipse.tcf.debug.ui allow to start a debug session by connecting to a machine runnning TCF agent. Plugin org.eclipse.tcf.cdt.ui handles integration of the debugger with CDT UI.
Since Eclipse version 3.8, TCF Debugger is available for download from main Eclipse p2 repository. The feature name is "Mobile and Device Development / Target Communication Framework, CDT Extender".
To start a debug session over TCF:
The TCF Debugger implements advanced, asynchronous, transaction based retrieval and caching of remote data. The technology allows excellent data coherency and communication performance.
The debugger fully supports multi-threaded, multi-process, multi-core, whole system and multi-system debugging in a single debug session.
In TCF debug session, "Debug", "Breakpoints", "Registers", "Variables", "Expressions", "Memory" and "Modules" views are populated by the TCF debugger. "Disassembly" view and instruction level stepping are available if the agent supports it. Reverse execution is available if the agent supports it. TCF Trace view can be used to display TCF communication traffic. Remote process standard I/O is redirected to the Console view. Source level debugging is fully supported.
Remote System Explorer is an Eclipse based component that allows users to create connections to remote machines and explore their file systems, see list of processes and access some other resources, like remote shells. Remote System Explorer has been designed as a flexible, extensible framework to which Eclipse plug-in developers can contribute their own system definitions, actions, etc.
Plugin org.eclipse.tcf.rse enables use of Processes, Shells, Terminals and Files subsystems of Remote System Explorer over TCF. It also extends Processes subsystem to include CPU utilization data and some other process attributes in RSE views.
Since Eclipse version 3.8, TCF-RSE is available for download from main Eclipse p2 repository. The feature name is "Mobile and Device Development / Target Communication Framework, RSE Extender".
To connect a remote machine over TCF:
RSE features supported by TCF connection: