| commit | ed1ae9910da5dba28e0e4b7ce161442af719b86a | [log] [tgz] |
|---|---|---|
| author | Eugene Tarassov <eugenet@xilinx.com> | Wed Feb 24 19:21:19 2021 -0800 |
| committer | Eugene Tarassov <eugenet@xilinx.com> | Wed Feb 24 19:21:19 2021 -0800 |
| tree | 736bdd9c1f5797dc70dea01fae243750f286695e | |
| parent | 366634503822bb1230c20e0c43fda807c7094945 [diff] |
TCF Agent: improved handling of long messages in the TCF channel implementation
TCF is a vendor-neutral, lightweight, extensible network protocol mainly for communicating with embedded systems (targets). On top of the protocol specification, which is the core of TCF, the project includes a plain-C implementation of a lightweight extendable target agent, Java client API (usable stand-alone or on top of Eclipse), Python and Lua client APIs, complete debugger UI implementation in Eclipse, integration with CDT, Target Explorer, documentation and usage examples.
agent : The reference agent, implementing debug related services e.g. Memory, RunControl, Registers, Stacktrace, Breakpoints, Symbols, LineNumbers, Expressions.
docker : Dockerfile image for host and cross builds of the debug agent.
examples : Implementation of a daytime service.
server : A proxy server sitting between the client on the host and an agent running/embedded on the target as part of the firmware or RTOS. It implements Symbols and LineNumbers services.
tests : Standalone tools for testing (e.g dwarf, extended commandline client)