• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 31 subscribers
  • Views 95 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

TMS570LC4357: XDS560v2 Pro Trace does not show tracing options in Code Composer

Txema Soroa
Prodigy 135 points

Part Number: TMS570LC4357
Other Parts Discussed in Thread: TMDX570LC43HDK

Hi.

We have recently acquired a XDS560v2 Pro Trace debugger in order to trace some code executed in the TMS570LC4357 processor.

When Tools->Hardware Trace Analyzer -> [whatever] is clicked in Code Composer is clicked, nothing happens.

We need assistance to make the [expensive] debugger work and get real tracing data from the target.

For this test we are using the TMDX570LC43HDK development board, which includes a MIPI connector.

Thank you in advance.

  • 0
    TI__Guru* 77426 points

    Txema,

    Could you please try below methods suggested by our internal AI tool first?

    1. XDS560v2 PRO TRACE is required for trace over pins (Core Pin Trace). The standard XDS debug probes only support Core and System Trace using the Embedded Trace Buffer (ETB), not external trace via pins.

    2. MIPI HSPT 60-pin connector is the primary interface for the XDS560v2 variants to support all types of Pin Trace (Instruction and System).(1, 2)

    3. The XDS560v2 PRO TRACE features a 1GB external memory buffer for capturing trace data.(2, 4)

    Common Issues and Solutions:

    Based on your symptom (Hardware Trace Analyzer menu does nothing when clicked), here are the most likely causes and solutions:

    1. Target Configuration (.ccxml) Setup

    The most common issue is that the target configuration file may not be properly set up for trace:

    Action Required:

    • Open your target configuration file (.ccxml)
    • Verify that you've selected the XDS560v2 PRO TRACE emulator (not just XDS560v2 System Trace)
    • Check that trace receiver settings are enabled in the advanced settings

    Steps:

    1. In CCS: View → Target Configurations
    2. Right-click your .ccxml file → Open
    3. In the "Connection" dropdown, ensure you selected the XDS560v2 PRO TRACE variant
    4. Click "Advanced" tab
    5. Look for trace-related settings and enable them

    2. ETM Trace Pin Configuration

    The TMS570LC4357 requires proper pin multiplexing to enable ETM trace pins. The trace pins must be configured in your initialization code.

    Action Required: You need to configure the PINMUX registers to enable the ETM trace functionality. The TMS570LC4357 has dedicated ETM trace pins (TRACECLK and TRACEDATA[0:3]) that need to be muxed correctly.(0, 1)

    Typical pins involved:

    • TRACECLK (trace clock output)
    • TRACEDATA[0:3] (trace data outputs)

    Add this configuration in your GEL file or startup code:

    c
    Collapse
    SaveCopy
    1
    2
    3
    // Example pinmux configuration for ETM trace
    // Check TMS570LC4357 datasheet for exact register addresses
    // This is typically done via PINMMR registers

    3. Physical Connection Verification

    Action Required:

    • Verify the MIPI 60-pin connector on the TMDX570LC43HDK is properly connected to the XDS560v2 PRO TRACE
    • Ensure you're using the correct adapter (if any) between the debugger and the board
    • Check that the board is powered when attempting to use trace

    4. CCS Version and Trace Receiver Support

    Action Required:

    • Ensure you're using Code Composer Studio v4 or newer (preferably v6 or later for better trace support)
    • Verify that the trace receiver drivers are properly installed
    • Check Windows Device Manager (if on Windows) to ensure the XDS560v2 is recognized

    5. Debug Session Requirements

    The Hardware Trace Analyzer menu items are typically only active when:

    • A debug session is active (you must be connected to the target)
    • The target is running or has been run at least once
    • Trace has been properly configured

    Action Required:

    1. Connect to target
    2. Load your program
    3. Run the program (even briefly)
    4. Then try accessing Tools → Hardware Trace Analyzer

    6. Trace Receiver Configuration in CCS

    Action Required:

    1. In CCS, go to: Window → Show View → Other → Debug → Trace Receiver
    2. This should show the trace receiver status
    3. Verify it shows as connected and ready

    Step-by-Step Troubleshooting Procedure:

    1. Verify Hardware:

      • XDS560v2 PRO TRACE is connected via USB/Ethernet to PC
      • MIPI 60-pin cable is connected to TMDX570LC43HDK MIPI connector
      • Board is powered

    2. Check Target Configuration:

      • Open .ccxml file
      • Verify XDS560v2 PRO TRACE is selected (not System Trace variant)
      • Save and use this configuration

    3. Enable Trace Pins:

      • Add ETM pin configuration to your initialization code or GEL file
      • Consult TMS570LC4357 Technical Reference Manual for PINMMR register settings

    4. Test Connection:

      • Launch debug session
      • Verify connection to target
      • Load and run a simple program

    5. Access Trace:

      • With program running, try Tools → Hardware Trace Analyzer
      • Check if Trace Receiver view shows activity

    Additional Resources Needed:

    To provide more specific guidance, you would benefit from:

    • TMS570LC4357 Technical Reference Manual (for exact ETM pin configuration)
    • TMDX570LC43HDK User's Guide (for MIPI connector pinout and trace setup)
    • XDS560v2 PRO TRACE User's Guide (for detailed trace receiver configuration)

    --
    Thanks & regards,
    Jagadish.