After DTSL was introduced, the DS-5 Debugger Software stack
changed. It is now as shown in the following figure:
Figure 15-3 Post DTSL DS-5 Debugger SW Stack
In addition to the layers that existed before DTSL, the stack now contains a
DTSL layer which does the following:
- Handles system initialization and DTSL-level component creation. This is
controlled by DTSL Jython scripts, which are typically contained in a platform
configuration database (configdb).
Note: Do not confuse DTSL Jython
Scripting with DS-5 Debugger Jython Scripting. Both of them use Jython, but they
operate at different levels in the software stack. However, a Debugger Jython
Script can use DTSL functionality.
- Provides a common connection interface for several client programs.
- Delivers trace streams to several trace clients.
- Uses the existing native RDDI infrastructure.
The DS-5 Debugger
uses DTSL to communicate with the lower layers of the stack. DTSL provides a set of
named objects for the debugger (or another tool) to use. The object set consists of the
- Debug objects, which control core execution. Their interface looks very
similar to the
- Trace source interfaces, which represent target components which can generate
- Trace capture interfaces, which are used to start and stop trace collection
and to provide notification events to clients.
- Other target components, such as other CoreSight™ devices or other third-party target devices.
- A Configuration and Connection interface, which instantiates and configures
the DTSL objects and queries the configuration to allow clients to discover which
top level interfaces are present.