The import utility, cdbimporter, aims to provide an easy method to import platform information into DS-5, and so provide limited debug and trace support for the platform through RVI/DSTREAM or model connections.
A target database holds the platform information for the DS-5. The import utility creates a new platform entry in a target database using information from:
A configuration file created and saved using the Debug Hardware Configuration utility, dbghwconfig or rviconfig.
A running model with a CADI server. The model can be already running or you can specify the launch path and filename in the command-line options.
ARM® recommends that you build new platform entries in a fresh directory to produce a new target database. This is because the DS-5 target database might install in a read-only location and when DS-5 updates, any changes to the DS-5 target database are lost. You can specify multiple target databases in DS-5 using the Preferences dialog. This enables platforms in the new database to use existing processor and register definitions.
Note
DS-5 is not yet capable of creating RVI/DSTREAM configuration files from within Eclipse, the Debug Hardware Configuration utitlity is currently the only method of doing this.
The import utility creates the following debug operations:
Single processor bare-metal and Linux kernel debug for hardware and models.
Symmetrical MultiProcessing (SMP) bare-metal and Linux kernel debug operations for targets with two or more identical processors.
Embedded Trace Buffer on-chip (ETB) trace and Trace Port Interface Unit off-chip (TPIU) trace configuration for hardware targets containing ETB/TPIU devices. If a Cross Trigger Interface (CTI) is present, the import utility configures it to carry trace triggers.
Note
ETMv1.x is not supported.
Linux applications debug configurations for hardware and models. ARM7TDMI® or Cortex™-M series processors are not supported.
The import utility does not create:
debug operations that configure non-instruction trace macrocells
big.LITTLE configurations.
For SMP, duplicate debug operations are produced for synchronisation with or without using CTI devices. Using CTIs produces a much tighter synchronization with a very low latency in order of cycles but the CTIs must be fully implemented and connected in line with the ARM reference designs, and must not be used for any other purpose. Synchronization without using CTIs has a much higher latency, but makes no assumptions about implementation or usage.
You might have to manually configure off-chip TPIU trace for multiplexed pins and also perform calibrations to cope with signal timing issues.
If you experience any problems or need to produce other configurations, contact your support representative.
AssumptionsThe import utility makes the following assumptions when creating debug operations:
There is a linear mapping between trace macrocells and CoreSight™ trace funnel ports.
The Embedded Trace Macrocell (ETM)/Program Trace Macrocell (PTM) versions are fixed for each type of processor.
Table 1. ETM/PTM versions for each type of processor
Processor Type ETM/PTM Cortex-A15 PTM Cortex-A7 ETMv3.5 Cortex-A8 ETMv3.3 Cortex-A9 PTM Cortex-R4 ETMv3.3 Cortex-R5 ETMv3.3 Cortex-R7 ETMv3.3 Cortex-M3 ETMv3.4 Cortex-M4 ETMv3.4 ARM9 series ETMv1.x is not supported. ARM11 series ETMv3.1 The CTI devices are not used for other operations.
In a target containing multiple CoreSight ETBs, TPIUs or trace funnels, the import utility produces configuration for the first example of each trace funnel, ETB, and TPIU with the lowest base address.
It is only possible to import platforms that can be auto-configured using the Debug Hardware Configuration utitlity or from a model.
DS-5 supports only a certain number of processors. To see a list of the supported processors, run the import utility using the --list-cores option (-l).
The import utility produces a basic configuration with appropriate processor and CP15 register sets but this might not always be perfect. For example, showing TrustZone® registers on all Cortex-A9 processors is not always appropriate, and NEON registers are never shown for an imported platform.
PDF version