Figure 15-4 DTSL Configuration class hierarchy
DTSLConnection object is the top level DTSL object that
allows access to all the other DTSL objects using the platform configuration.
DTSLConnection allows access to the
ConfigurationBase instance, for example DTSLv1, which allows
access to the rest of the DTSL objects. The content of the platform configuration
depends on the associated
ConnectionParameters instance does not
specify a DTSL configuration script, then an object of type
DefaultConfiguration is created. The configuration content is constructed
by creating a
Device object for each device known to
RDDI-DEBUG. For DSTREAM, this means that a
object is created for each device declared in the .rvc file, but for other kinds of RDDI this might come from a different
data set. This allows for a simple connection to a platform with direct connections to
any target devices specified in the RDDI configuration file.
ConnectionParameters instance does
specify a DTSL configuration script, then that script is run to create an instance of a
configuration object derived from DTSLv1. When the configuration script is run, it is
expected to populate the configuration with the set of known device objects, trace
sources and trace capture devices.
- ARM® recommends using a
configuration script to create a DTSL configuration, because it allows much
greater flexibility when creating devices.
- DTSLv1 is named as such to show that the configuration is using the V1 interface
and object set. This is the current set. If ARM changes the
interface and object set, then it might start using DTSLv2. This allows ARM to maintain
backwards compatibility, but also to move forward with new or modified