Platform Configuration in Development Studio
You can configure your hardware platform and model platform targets using the configuration editors in the Development Studio perspective:
- The Platform Configuration Editor (PCE) enables you create or modify configurations and connections for hardware target platforms. For more information, see Platform Configuration Editor (PCE).
- The Model Configuration Editor enables you to to create or modify configurations and connections for model target platforms. For more information, see Model Configuration Editor.
Use these views to configure debug and trace support information for targets through DSTREAM, ULINK, or model connections.
If you are autodetecting hardware target information, sometimes it is not possible for Development Studio to read all of the information that it needs from a platform. This can be caused by a variety of issues which are described in Hardware platform bring-up in Development Studio.
If you experience autodetection issues and know the details about the debug system of the platform, use manual platform configuration. For more information, see Manual platform configuration.
The configuration database in Development Studio stores the platform configuration and connection settings in Development Studio. To extend the default Development Studio configuration database, you can create platform configurations in user configuration databases.
NoteIf your platform configuration is already in the configuration database, you can use the existing configuration to connect to the platform. For more information, see Configuring debug connections in Arm® Debugger. You do not have to use the Platform Configuration Editor unless you want to modify the platform configuration.
To create a new configuration, Development Studio uses information from:
- A configuration file for a platform, created and saved using the Platform Configuration Editor (PCE). See Create a platform configuration.
- A configuration file for a model that provides a CADI server, created and saved using the Model Configuration Editor. The model can be already running or you can specify the path and filename to the executable file. See Create a new model configuration.
You can create the following debug operations:
- Single processor and Symmetric Multi Processing (SMP) bare-metal debug for hardware and models.
- Single processor and SMP Linux kernel debug for hardware.
- Linux application debug configurations for hardware.
- big.LITTLE™ configurations for cores that support big.LITTLE operation, such as Cortex®-A15 and Cortex-A7.
NoteFor more information on SMP, see Debugging SMP systems.
Debug and Trace Services Layer (DTSL) options are produced for hardware targets with a trace subsystem. These can include:
- Selection of on-chip (Embedded Trace Buffer (ETB), Micro Trace Buffer (MTB), Trace Memory Controller (TMC) or other on-chip buffer) or off-chip (DSTREAM trace buffer) trace capture.
- Cycle-accurate trace capture.
- Trace capture range.
- Configuration and capture of Instruction Trace Macrocell (ITM) and System Trace Macrocell (STM) trace to be handled by the Development Studio Event Viewer.
The PCE does not create debug operations that configure non-instruction trace macrocells, except for ITM and STM.
For SMP configurations, the Cross Trigger Interface (CTI) synchronization is used on targets where a suitable CTI is present. A CTI produces a much tighter synchronization with a very low latency, in the order of cycles. Synchronization without using a CTI has a much higher latency, but makes no assumptions about implementation or usage.
NoteThe CTI must be fully implemented and connected in line with the Arm reference designs. The CTI must not be used for any other purpose.
For multiplexed pins, you might have to manually configure off-chip Trace Port Interface Unit (TPIU) trace, and also perform calibrations to handle signal timing issues.
NoteSometimes calibration needs to be performed even if the trace pins are not multiplexed.
If you experience any problems or need to produce other configurations, contact your support representative.