This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

AM2612: the fresh rate of debugger

Part Number: AM2612

Hi all,

we are useing the XDS110 with AM2612. Currently, we found ccs's watch and time graph only has the refresh rate of 500ms. This rate can not reach our requirements. Do we can reach faster refresh rate about 10ms? Like XDS200?

Regards,

Jenney

  • Hi all,

    Do we have any progress?

  • Hi Jenney,

    Appologies for the delayed response during the holiday weekend.

    When using standard Code Composer Studio (CCS) watch and graph windows, the refresh rate is primarily limited by the overhead of the debugger communication and the JTAG clock frequency 1.

    While I have looked into the documentation for the XDS110 and the AM2612, there is no official specification that guarantees a 10ms refresh rate for these debug windows. In practice, the refresh interval is determined by how quickly the IDE can perform a "read" operation through the JTAG interface, process the data, and update the GUI, which is often significantly slower than 10ms due to the nature of standard JTAG communication 1.

    To potentially improve your data throughput, you could consider these steps:

    • Check JTAG Frequency: While you are using the default frequency, you can often experiment with increasing the TCLK (JTAG clock) speed in your target configuration (.ccxml) file under the "Advanced" tab to see if it reduces the latency 1. However, ensure your board layout supports higher speeds to avoid communication errors 2.
    • Use Alternatives for High-Speed Data: If your application requires 10ms or faster monitoring, the standard Watch/Graph windows may not be the optimal tool. Developers often use Real-Time Data Exchange (RTDX) (where supported) or stream data out through a high-speed peripheral like UART or Ethernet to a host-side application for visualization.
    • Verify Firmware: Ensure your XDS110 firmware is up to date, as newer versions often include optimizations for connection stability and speed 2.

    If you are seeing consistent performance issues, I recommend checking the AM261x FAQ List for any specific community-driven optimizations or similar experiences with high-frequency telemetry.

    1. XDS110 Debug Probe User's Guide
    2. AM2612 E2E Forum: JTAG Errors and Debugging

    Best Regards,

    Zackary Fleenor