• State Accepted Answer
  • Replies 4 replies
  • Subscribers 20 subscribers
  • Views 562 views
  • Users 0 members are here
Options
Related
How was your experience today?

XMC7200D TRACE

Rainer Kaufmann

Hi,

I use the ULinkpro to trace execution of the XMC7200D CM7_0 using uVision. Does anyone have an idea how I can get rid of the "Trace Data Overflow" message and why percental execution time stay at 0%?

I used 62,5 MHz as CLOCK_PERI which is used for the CPU debug module. What is this setting "PC Sampling - Prescaler" for?

"Data Overflow The Trace Port was too busy, and not all trace packets could be transmitted. This happens when too many trace data are captured. Decrease the number of trace events. The Instruction Trace Window shows where the overflow occurred."

I increased the trace clock to 72MHz and now I have: 

 "HW Buffer Overrun The USB port cannot accept data at the speed the adapter is sending them. Turn off trace events you do not need, or skip PC Sampling."

I activated nothing, playing around with different clocks brought no success. how can I use the trace feature in a reliable manner with full CPU speed of 340MHz?

Any hints  welcome 

Thanks + best regards, Rainer

Parents
  • +1 Arm Employee Badge in reply to Rainer Kaufmann
    Rainer Kaufmann said:
    I will propose a 4-bit interface to the team.

    Yes, this is definitely necessary for ETM Trace.\

    Rainer Kaufmann said:
    What about the ULINKPro, would the situation better e.g. with a J-Link?

    Segger has a J-Trace debug adapter and there is a driver it for µVision. µVision does not support streaming trace and the performance analyzer with J-Trace. According to the Segger website, J-Trace supports up to 150 MHz Trace clock, which means 300 MHz CPU clock.
    On the other hand, we have seen many microcontroller devices where the trace port output pins do not support higher clock rates. Check this with the device specification before you select a different debug/trace adapter.

    Rainer Kaufmann said:
    Ok, I guess we should just use a debugger that officially supports the XMC7200D.

    ULINKpro supports this Infineon device, but most Cortex-M7 devices use CPU clocks higher than 200 MHz.
    Arm has other debug adapters with trace. Please see: https://developer.arm.com/Tools%20and%20Software/DSTREAM-ST?#Editions
    Unfortunately, uVision does not support them. You would have to use Arm DS.

Reply
  • +1 Arm Employee Badge in reply to Rainer Kaufmann
    Rainer Kaufmann said:
    I will propose a 4-bit interface to the team.

    Yes, this is definitely necessary for ETM Trace.\

    Rainer Kaufmann said:
    What about the ULINKPro, would the situation better e.g. with a J-Link?

    Segger has a J-Trace debug adapter and there is a driver it for µVision. µVision does not support streaming trace and the performance analyzer with J-Trace. According to the Segger website, J-Trace supports up to 150 MHz Trace clock, which means 300 MHz CPU clock.
    On the other hand, we have seen many microcontroller devices where the trace port output pins do not support higher clock rates. Check this with the device specification before you select a different debug/trace adapter.

    Rainer Kaufmann said:
    Ok, I guess we should just use a debugger that officially supports the XMC7200D.

    ULINKpro supports this Infineon device, but most Cortex-M7 devices use CPU clocks higher than 200 MHz.
    Arm has other debug adapters with trace. Please see: https://developer.arm.com/Tools%20and%20Software/DSTREAM-ST?#Editions
    Unfortunately, uVision does not support them. You would have to use Arm DS.

Children
No data