You copied the Doc URL to your clipboard.

components.xml file

Use the components.xml file to add component information to a custom configuration database.

The structure of the components.xml file is made up of several elements with associated attributes. For example:

<componentDatabase version="1.0">
                        <cluster_device name="TM">0x43B:0xD05:0x13</cluster_device>
                        <cluster_device name="CTI">0x43B:0xD05:0x14</cluster_device>
                        <cluster_device name="PMU">0x43B:0xD05:0x16</cluster_device>
                        <core_trace_link devices="CSETM" maxSlaves="1" minSlaves="1" position="master"/>
                        <cti_link devices="CSCTI" maxSlaves="1" minSlaves="0" position="master"/>


Table 14-9 Elements used in the components.xml file

Element name Description
<componentDatabase> The components.xml file definition. Use the version attribute to define file versions, for example: <componentDatabase version="1.0">
<manufacturer> The manufacturer elements contain the manufacturer name, the JEP code for the manufacturer, and one or more parts.
<name> The part manufacturer name.

The manufacturer JEDEC JEP-106 Manufacturer ID Code. JEP106 provides for a 7-bit "Identity Code" plus a mechanism for extending the range of codes by use of a "Continuation Code".

See What is the JEDEC JEP-106 Manufacturer ID Code and how is it used? for more information.

<part> Declaration of a component part. For an example, see Examples.

The part ID. This is required for the part to be successfully detected.

If your part has multiple IDs, you can list them separated by a semicolon (;). For example, <number>0x9D7;0xD14</number>.


The development architecture. This is optional.

If the part number is shared by multiple components, use <DEVARCH> to differentiate between various development architectures.


The part type. This is optional.

If the part number is shared by multiple components, use <DEVTYPE> to differentiate between various parts.

<name> The part name. If a firmware template does not exist for a part, then the CoreSight™ REG template is used for the part.
<description> A brief description of the part.
<family> The processor core family name.
<class> The device class of the component. This can be TraceSink, TraceSource, TraceLink, or CoreExecutable.
<architecture> The architecture of the core. For example, ARMv7-A, ARMv7-R, ARMv7-M, ARMv8-A, ARMv8-R, ARMv8-M.
<is_big_core> Indicates that this core is a big.LITTLE™ big core.
<is_little_core> Indicates that this core is a big.LITTLE little core.
<supports_mixed_clusters> Indicates that this core supports mixed-core type clusters (DynamIQ™).
<MPCore> Indicates that this component is a Symmetric Multi-Processing (SMP) capable core.
<uses_template> Alternate template for the part. Use this element to override any firmware template.
<cluster_devices> A list of cluster device elements.
<cluster_device> Name attribute ("TM"/"CTI"/"PMU") and values (ManufacturerID:PartID:DEVTYPE) used to generate a set of core cluster components.
<topology_info> A set of topology link constraint information items. This describes maximum and minimum number of connections, and the master and slave interface connections for any given interface type. For example, ATB, CTI_Trigger, or CoreTrace.
<core_trace_link> Information for minimum/maximum connections for CoreTrace interfaces.
<cti_link> Information for minimum/maximum connections for CTI interfaces.

The core definition. Used to indicate which Development Studio configuration database core definition must be used.

If this is not provided, <name> value is used for the core definition.

<device_info_list> A set of device_info items, which contain the information (key/value pairs) required for PCE to be able to create and configure the correct DTSL objects.
<Option> An option for the value of a device_info item. These are fixed for any given component type, that is, new ones cannot be added, and removing existing ones causes failures.
<atb_link> Information for minimum/maximum connections for ATB interfaces.


These examples provide some sample configurations.

  • Adds a CoreSight Performance Monitoring Unit (PMU) - 1

      <description>New CoreSight PMU part</description>
  • Adds a CoreSight Performance Monitoring Unit (PMU) - 2

      <description>New PMU Type</description>
      <uses_template>CSPMU </uses_template>
  • Adds a core

      <description>My new core type</description>
  • Adds a CoreSight Embedded Trace Macrocell

      <description>CoreSight Embedded Trace Macrocell</description>
        <device_info name="VERSION" description="ETM Version" type="string" value="4.0">
         <device_info name="SUPPORTS_CONTEXT_IDS" description="Context IDs supported" type="bool" value="True"/>
         <device_info name="SUPPORTS_CYCLE_ACCURATE" description="Cycle-Accurate tracing supported" type="bool" value="True"/>
         <device_info name="SUPPORTS_DATA_VALUE_TRACE" description="Data Value trace supported" type="bool" value="True"/>
         <device_info name="SUPPORTS_DATA_ADDRESS_TRACE" description="Data Address trace supported" type="bool" value="True"/>
         <device_info name="SUPPORTS_DATA_ONLY_MODE" description="Data-Only tracing supported" type="bool" value="True"/>
         <device_info name="SUPPORTS_TIMESTAMPS" description="Timestamps are supported" type="bool" value="True"/>
         <device_info name="SUPPORTS_TRACE_RANGES" description="Trace Ranges are supported" type="bool" value="True"/>
         <atb_link position="master" minSlaves="1" numMasterInterfaces="1"/>
         <core_trace_link position="slave" minMasters="1" maxMasters="1"/>
         <cti_link position="master" minSlaves="0" maxSlaves="1" devices="CSCTI"/>