ARM Technical Support Knowledge Articles

How do I import hardware platforms using the Platform Configuration Editor in DS-5?

Applies to: DS-5

Answer

DS-5 Debugger provides many platform configurations within its configuration database to debug and trace on specific hardware. However, if a configuration is missing from the DS-5 configuration database, it is necessary to add this using the tools provided. You can use the Platform Configuration Editor in DS-5, and a supported debug probe/VSTREAM client to autodetect and import models and hardware platforms. 

Importing a platform creates a configuration database entry in the location you specify. After importing a platform, the Debug Configuration in DS-5 shows the platform configuration which you can use to connect and debug the platform. 

Note: Importing platforms using the Platform Configuration Editor provides better support, such as Cortex-A53 and Cortex-A57 cache support, than when using the Debug Hardware Configuration and cdbimporter utilities.

This article describes how to use the Platform Configuration Editor in DS-5.

  1. Open the DS-5 Configuration Perspective by clicking Window -> Open Perspective -> Other and select DS-5 Configuration. 
  2. You must have a project to create a new platform configuration in. Create a new project in your workspace by clicking File ->New -> Project and then select General -> Project. Give a project name, for example MyConfigdb. The project file is created in the specified location when you click Finish.
  3. In the Project Explorer view, right-click on the project MyConfigdb and select New -> Other. Then select DS-5 Platform Configuration Editor -> Platform Configuration File. Click Next and then enter a name for the configuration file, for example MyPlatform. When you click Finish, this shows the Platform Configuration Editor.
  4. The tabs at the bottom of the Platform Configuration Editor (Platform Overview, Device Table, Device Tree, System Configuration, and Platform Import) reflect the platform import process. The process enables you to autodetect the devices, manually configure the platform, and then save and import the platform into the DS-5 Configuration Database.
  5. In the Platform Overview tab, you can provide details for the platform (manufacturer name, platform name, and a URL for more information on the platform, which is visible in the launcher panel) and the debug probe (connection address with the TCP: or USB: prefix). If you browse to select a DSTREAM, RVI, or VSTREAM, it also shows the probe's name and firmware version. If you manually enter the connection name, click Detect to detect the probe settings.
  6. You can also set common detection settings. The probe settings have a default of 10MHz clock speed and use adaptive clock if detected. You can increase or decrease the clock speed if the default does not detect the probe.
  7. In the Platform Overview tab, click Autodetect Platform to detect the platform configuration and its components. Ensure to select the Read CoreSight ROM Tables box, otherwise only the scanchain devices are detected. The verbose logging option is useful for autodetection when reporting any detection problems to ARM support, as the additional information might highlight potential failure causes.
  8. During autodetection, appropriate logging appears in the Autodetection pane. After successful detection, the platform devices can be seen in the tree view of the Devices section.
  9. In the Device Table tab, you can review the read-only table of device information.
  10. In the Device Tree tab, you can change the details of the detected components on the platform. In this tab, you can highlight devices on the platform separately, and change their configuration in the Configuration Items pane. Usually, there is no need to modify the configuration items. You cannot edit the device details in Details pane.
  11. The System Configuration tab enables you to change the way the debug probe interacts with the target platform, such as reset behavior and pin configurations. Usually there is no need to modify these values.
  12. The Platform Import tab enables you to import the platform configuration into the DS-5 Configuration Database. You must first save your platform configuration (.rvc file).
  13. Use the Extension Database Location field to specify the location to save the imported platform configuration database entry.
  14. It is also possible to modify the capabilities of the created configuration, for example bigLITTLE support, and CTI sync. The available options depend on the devices found when autodetecting.
  15. Click Import Platform to import the configuration database entry for the platform into the specified location.
  16. To make DS-5 aware of the imported platform configuration database, you must add this to the DS-5 Configuration Database using Windows -> Preferences -> DS-5 -> Configuration Database. Add the location of your new configuration database if it does not already exist in the User Configuration Databases. Then click Rebuild database. This enables the Debug Configurations window to show the new platform configuration. You can test the imported platform by clicking Test Platforms.

After successfully importing and rebuilding the new platform configuration database, you can use DS-5 Debugger to connect to the new platform. To do this, first select the DS-5 Debug perspective from Windows -> Open Perspective -> Other. Then select Run -> Debug Configurations. Find your imported platform configuration from the list of target connections to connect and debug.

Attachments: ds5_configuration_perspective.png , platform_tab.png , paltform_import_tab.png , device_table_tab.png , device_tree_tab.png , platform_list_of_devices.png , autodetection.png , connection_debug_probe.png , configuration_of_platforms.png

Article last edited on: 2014-10-27 11:36:35

Rate this article

[Bad]
|
|
[Good]
Disagree? Move your mouse over the bar and click

Did you find this article helpful? Yes No

How can we improve this article?

Link to this article
Copyright © 2011 ARM Limited. All rights reserved. External (Open), Non-Confidential