This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Using ARM-DS to capture ITM traces

Hi there,

We have a Cortex-M33 and the coresight module is configured such that ITM traces are output on 2 pins of trace port TRACECLK and TRACEDATA[0], rather than the more traditional SWO pin.

So I have two questions please:

Is there any way (trace window or GUI) to capture ITM traces in ARM Development Studio using DStream for example? Or can this only be done on Keil MDK (uvision IDE) using Ulink-pro?

How do we configure the IDE trace capture to use only one bit (i.e. TRACEDATA[0]) of the four-pin trace port (on the connector)?

Thanks

Sarah

Parents
  • Hi

    My name is Stephen and I work at Arm.

    Yes, Arm DS and DSTREAM-family debug units can be used to capture ITM data from a target and display it in the Events view:

    see developer.arm.com/.../Events-view

    but Arm DS has no equivalent to the Serial Wire Viewer or Trace Records view as found in Keil MDK uVision.

    There is an example (named "ITM_Cortex-M4_MPS2") provided with the Arm DS examples that illustrates this.

    Depending on your target board and type of DSTREAM unit (e.g. -ST or -PT), there may be a ready-made debug configuration available that offers a variety of TPIU port widths.  This is selected from the "DTSL Options" button.

    For example, this screenshot is for the Cortex-M33 SSE-200 platform:




    To compare DSTREAM Editions, see https://developer.arm.com/Tools%20and%20Software/DSTREAM-ST?#Editions


    Hope this helps,

    Stephen

Reply
  • Hi

    My name is Stephen and I work at Arm.

    Yes, Arm DS and DSTREAM-family debug units can be used to capture ITM data from a target and display it in the Events view:

    see developer.arm.com/.../Events-view

    but Arm DS has no equivalent to the Serial Wire Viewer or Trace Records view as found in Keil MDK uVision.

    There is an example (named "ITM_Cortex-M4_MPS2") provided with the Arm DS examples that illustrates this.

    Depending on your target board and type of DSTREAM unit (e.g. -ST or -PT), there may be a ready-made debug configuration available that offers a variety of TPIU port widths.  This is selected from the "DTSL Options" button.

    For example, this screenshot is for the Cortex-M33 SSE-200 platform:




    To compare DSTREAM Editions, see https://developer.arm.com/Tools%20and%20Software/DSTREAM-ST?#Editions


    Hope this helps,

    Stephen

Children