12 <p><strong>TCF</strong> (Target Communication Framework) is a vendor-neutral, lightweight, extensible network protocol used mainly for communicating with embedded systems (targets). Its most distinguishing feature is that TCF is designed to transparently plug in value-adding servers between the tool and the target. TCF is protocol agnostic in that it does not depend on a specific transport like TCP/IP, serial, SSH tunnel, or other. It also supports auto-discovery of targets and services, so any tool can determine which services are available from the target.</p> |
12 <p><strong>TCF</strong> (Target Communication Framework) is a vendor-neutral, lightweight, extensible network protocol used mainly for communicating with embedded systems (targets). Its most distinguishing feature is that TCF is designed to transparently plug in value-adding servers between the tool and the target. TCF is protocol agnostic in that it does not depend on a specific transport like TCP/IP, serial, SSH tunnel, or other. It also supports auto-discovery of targets and services, so any tool can determine which services are available from the target.</p> |
13 <p>Carbide.c++ uses TCF to communicate with <a href="trk.htm">TRK</a>, Trace, and other services on a target device. For example, the Carbide debugger uses TCF to communicate with the TRK remote agent to control debuggable programs running on the target. Other Carbide plug-ins can also use TCF to communicate with their specific services.</p> |
13 <p>Carbide.c++ uses TCF to communicate with <a href="trk.htm">CODA</a>, Trace, and other services on a target device. For example, the Carbide debugger uses TCF to communicate with the CODA remote agent to control debuggable programs running on the target. Other Carbide plug-ins can also use TCF to communicate with their specific services.</p> |