You copied the Doc URL to your clipboard.

Creating an extension configuration database in DS-5

Article ID: 165515978

Published date: 13 Feb 2018

Last updated: -

Applies to: Software Development Tools

Problem/Question

How can I create an extension configuration database in DS-5?

Scenario

The devices defined in DS-5 are used to configure how to debug the platform.

Devices which are known by DS-5 are defined in the components.xml files. This is not exposed by default.

New customer 3rd party devices are not recognized by DS-5 and shown as "Unknown". That becomes a problem because it makes it harder for DS-5 to control these devices

Answer

To mitigate this, you can create an extension configuration database which will includes custom devices. Use the following steps to create this database:

1. Create a new components.xml file and edit it to include the device's peripheral ID.

You can get the peripheral ID from the devices TRM or User Guide.

Please refer to the attached components.xml file and modify the peripheral ID based on your devices in the following part in the xml file.

<cluster_device name="TM">0x43B:0x95D:0x13</cluster_device>

<cluster_device name="CTI">0x43B:0x9A8:0x14</cluster_device>

<cluster_device name="PMU">0x43B:0x9D3:0x16</cluster_device>

2. Create the "Components" folder in the <DS-5_install_dir>\sw\debugger\configdb directory or create an extension DB with the "Components" folder as shown in the attached picture. Then add the components.xml file into this folder.

Now you should be able to see the device in the PCE view when you auto-detect the platform by PCE.

If this does not work, please contact Arm support by sending email to support-sw@arm.com.

Workaround

N/A

Example

The example for components.xml file

images/Create_extension_cdb.png

   
  
    ARM
    0x43B
    
    
      0x100
      0x15
      Cortex-A53
      Cortex-A53
      Cortex
      CoreExecutable
      ARMv8-A
      True
      True
      True
      
        0x43B:0x95D:0x13
        0x43B:0x9A8:0x14
        0x43B:0x9D3:0x16
      
      
        
        
      
    
  

Related Information

N/A

Was this page helpful? Yes No