You copied the Doc URL to your clipboard.

Create a DSTREAM-HT enabled platform configuration

Use the New Platform dialog in Development Studio to create a new platform configuration with DSTREAM-HT support.

Warning

Generating a new platform configuration overwrites any DTSL scripts and other platform files that might exist for your current configuration. Backup your configuration if you have an existing configuration and have applied manual changes to your configuration.

Prerequisites

  • Install the latest release of Arm® Development Studio which contains support for the latest debug hardware from Arm.
  • Ensure your DSTREAM-HT system has the latest firmware version installed.
  • If you autodetect your target, ensure that you connect your debug adapter and targets, or that you have the connection address.
  • If you import an existing RDDI configuration file, SDF file (.rcf, *.rvc, *.sdf), CoreSight Creator file (*.xml), or CMM script (*.cmm), ensure that you have access to these files.

Procedure

  1. Open the new project dialog. In the Project Explorer, right-click, and select File > New > Other > Platform Configuration.
  2. Select Configuration Database > Platform Configuration and then click Next to view the Create Platform Configuration dialog box.

    Figure 14-45 Select create a platform configuration.

    Select create a platform configuration.

  3. Select a method to create the configuration for your platform and click Next.

    Figure 14-46 Platform creation options

    Platform creation options

    Choose from:

    • Automatic/simple platform detection

      Note

      Arm recommends this option.

      Automatically detects devices that are present on your platform, use this option. After autodetection, you can add more devices and specify how the devices are interconnected.

    • Advanced platform detection or manual creation

      This option gives you control over the individual stages that are involved in reading the device information from your platform. This option is useful, for example, to read certain device information that might make the platform unresponsive. For more information, see Manual platform configuration.

    • Import from an existing RDDI configuration file or SDF file (*.rcf, *.rvc, *.sdf), or CoreSight Creator file (*.xml)

      Use this option if you already have a configuration file for your platform.

      Imports minimal information about the components available on your platform, such as the base address. After importing, you can manually provide additional information and links between the components to enable full debug and trace support.

    • Import from a *.cmm file

      Imports a platform configuration from a CMM script (*.cmm) file.

      CMM scripts can contain target description information such as:

      • JTAG pre- and post- IR/DR bit information.
      • Core types.
      • Device base addresses.
      • CoreSight topology information.

      The PCE uses this information to create a Development Studio platform configuration, complete with custom DTSL control tabs for trace configuration.

      Depending on the value of parameters that are passed to the script, some CMM scripts describe different targets, or different cores and trace devices in the same target. If a CMM script requires parameters, enter them in the CMM script parameters field.

      Figure 14-47 Enter CMM script parameters

      Enter CMM script parameters

      If you are autodetecting using Automatic/simple platform detection or Advanced platform detection or manual creation (using Autodetect Platform in **Debug Adapter panel), Development Studio connects to the platform and reads all the device information that it can from the platform.

    Warning

    Depending on your target, you might receive warnings and errors. When Development Studio cannot obtain this information from the platform, it does not make any assumptions about how the devices are connected. You must provide this information in the PCE view.

    Debug functionality succeeds if all cores are correctly detected. Where the connections between cores are not detected, debug succeeds, but trace and cross-triggering functionality might be limited or missing.

  4. (Optional - Automatic/simple platform detection only) Save or edit your autodetected configuration. The following list describes the next steps available for your autodetected platform:
    • Save a Debug-Only Arm DS Platform Configuration

      Saves a debug-only configuration to your configuration database.

    • Save a Debug and Trace Arm DS Platform Configuration

      Saves a debug and trace configuration to your configuration database. You can open this in Development Studio later to modify it, or you can use it to connect to and debug the platform later.

    • Edit platform in Arm DS Platform Configuration Editor

      Saves the configuration to your configuration database and opens the PCE view.

      In the PCE view, you can provide information about the platform that Development Studio was unable to autodetect.

      For more information, see Edit a platform configuration.

      Note

      • All Development Studio platform configurations must be stored in a configuration database.
      • You can open the configuration in Development Studio later to modify it, or you can use it to connect to and debug the platform.

    Select an option and click Next.

    The New Platform dialog box opens.

  5. Select an existing configuration database from the list, or create a new one. To create a new configuration database, click Create New Database, provide a name for your new configuration database in the prompt, then click OK to save your configuration database.

    Figure 14-48 Create new configuration database

    Create new configuration database

  6. Click Next >.

    The Platform Information dialog box opens.

  7. Enter the Platform Manufacturer, for example Renesas. Enter the Platform Name, for example R-Car-M3-Salvator-X. Optionally, if you want to provide a URL link to information about the platform, enter it in Platform Info URL.

    Note

    When you select a debug activity for the platform, the URL appears in the Debug Configurations panel.

    Figure 14-49 New platform information

    New platform information

  8. Click Finish.
  9. (Optional - Advanced platform detection or manual creation only) Complete your configuration:
    • Configure your debug hardware in Debug Adapter panel.
    • Autodetect your platform. In Debug Adapter panel under Autodetect tab, click Autodetect Platform.

    Warning

    Depending on your target, you might receive warnings and errors. When Development Studio cannot obtain this information from the platform, it does not make any assumptions about how the devices are connected. You must provide this information in the PCE view.

    Always review the information that has been collected before deciding what further action to take. If Development Studio fails to read information, it might indicate a deeper problem. For more information, see Hardware platform bring-up in Development Studio.

    • Check, edit, and save your configuration. If required, edit the configuration then select File > Save.

The Platform Configuration Editor (PCE) view opens in the right-hand panel. You can view the configuration database and platform in the Project Explorer.

Next Steps

After successfully creating the platform configuration with DSTREAM-HT support, the next step is to modify the configuration usecase scripts to accept target-specific values.