Using the ELA-500 with Arm DS

A tutorial showing how to use the CoreSight ELA-500 with Arm Development Studio (Arm DS) to debug a real-world deadlock scenario


Introduction Before you begin Importing the ELA-500 DTSL use case scripts Configuring the ELA-500 use case scripts Running the ELA use case scripts Capturing the ELA trace data Analyzing the ELA trace capture

Capturing the ELA trace data

  1. The core is unable to enter halt mode debug in our debug scenario, so we must stop the ELA:
    1. Navigate to Scripts view > Use case > Scripts in <path to Arm Development Studio Workspace>\DTSLELA-500 > ela_control.py > Stop ELA-500.
    2. Right-click Stop ELA-500 and select Run ela_control.py::Stop ELA-500.
  2. Dump and decode the ELA trace:
    1. Navigate to: Scripts view > Use case > Scripts in <path to Arm Development Studio Workspace>\DTSLELA-500 > ela_example.py > Decode trace data.

    Note: To run the Decode trace data script, name the JSON file for the ELA example_ela_connection.json. Also, the example_ela_connection.json JSON file must be available in the DTSLELA-500 project directory.

    1. Right-click Decode trace data and select Configure… .
    2. Under Signal groups, set State 0 to 0 and click OK.

      Note: In the platform configuration, you must name the CoreSight ELA-500 device as ELA-500. This naming is done so the ELA-500 device name in the platform configuration matches the ELA-500 device name in the Decode trace data script. Decode the trace data use case script settings

    3. Right-click Decode trace data and select Run ela_example.py::Decode trace data.
    4. Result: Arm DS collects the captured ELA trace data, decodes it, and outputs into Development Studio.

Previous Next