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.

F29H850TU: Automating ERAD core traces on F29H85x devices

Part Number: F29H850TU

After investigating the ability to enable, collect and view a core trace within CCS on an F29H85x device, I would like to know if this can be done this from the command line rather than interacting manually via the IDE, I therefore had the following questions regarding this:

  • Can the ERAD module be configured to perform a core trace via the scripting interface for a debug session? Are there any examples of this?
  • Once the trace has been captured, how can the data be exported to a file on the host for post processing?
  • Is there documentation describing the core trace format so that the data can be decoded?

Regards,

Rich

  • Hi,

    Can the ERAD module be configured to perform a core trace via the scripting interface for a debug session? Are there any examples of this?

    It is possible to use CCS scripting to enable PC trace and dump the PC trace register from scripting console - https://software-dl.ti.com/ccs/esd/documents/users_guide_ccs_20.1.1/ccs_debug-scripting.html. Can create separate thread if help needed from CCS team on the CCS scripting.

    I am not aware of such an existing example.

    Once the trace has been captured, how can the data be exported to a file on the host for post processing?

    This has been requested to CCS software team, will be added to upcoming release. Should have export option to csv or txt file for the trace table displayed in CCS.

    Optionally you can dump memory view of the PC trace to txt file and post process with script offline

    Is there documentation describing the core trace format so that the data can be decoded?

    PC trace buffer base and registers are documented in ERAD registers section.

    PC trace memory view is shown above.

    Thanks

  • Hi Prarthan,

    Thank you for the quick response and helpful information. That will be more than enough to get me going and if needed I will raise a separate thread as you suggested with the CCS team regarding the scripting.

    I am pleased to hear that the export of the trace has been requested and will be in an upcoming release of CCS.

    Regards,

    Rich