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.

CCS/66AK2G12: Can't to get the ETB from the ARM

Part Number: 66AK2G12
Other Parts Discussed in Thread: 66AK2H12

Tool/software: Code Composer Studio

I am using CCS 6.1.2 and gcc-arm-none-eabi-4_8-2014q3 and SYS/BIOS 6.45.1.29.  I connect through an XDS-200.

When I connect to the ARM (stopped) and select tools-> hardware trace analyzer->PC trace I get the message "Unable to load GEL script function Enable_Funnel_For_PTM".  Is this a known issue?  Is there a work-around?  I can get the ETB trace from the DSP.

  • Hi,

    In order for Trace to work on K2G devices, you will have to update two components of your CCS: the Keystone 2 Device support and the TI Emulators. If you click on menu Help → Check for Updates and select the two components as shown below:

    That should workaround the GEL script issue.

    Hope this helps,

    Rafael

  • I upgraded these two components in my CCS 6.1.2 and I was able to load the trace analyzer on a clean boot. But so far there is nothing in the trace log when I stop the ARM. I'm going to upgrade some other components, including going to CCS 7.1.0 as requested by the PASDK that I am using. Stay tuned.
  • I have now upgraded to CCS 7.4, the specified packages above and the packages listed below. But still when I open the HW PC trace and stop the ARM there is nothing in the trace window. What else could be wrong?
    ti-cgt-c6000_8.1.0
    gcc-arm-none-eabi-4_8-2014q3 (gnu 4.8.4)
    XDC Tools 3.32.01.22
    SYS/BIOS 6.46.5.55
    System Analyzer (UIA Target) 2.0.6.52.
    XDAIS 7.24.0.04.
    DSPLIB C66x 3.4.0.0.
    IPC 3.46.00.02
    EDMA3 LLD 2.12.4.
    k2g PDK 1.0.6.
    libarch_k2g_1_0_1_0
  • Chuck Peplinski said:
    What else could be wrong?

    I don't have a 66AK2G12 to investigate, but using CCS 7.4.0.00015 with Keystone2 device support 1.2.0 and looking at the 66AK2G12 target configuration there is no PTM_0 entry under the cortexA15_0 subpath:

    On a 66AK2H12, which is another keystone 2 device, found that a missing PTM entry meant that was unable to collect any Processor Trace from a Cortex A-15 core. See Unable to collect PC Trace for ARM A15 core in 66AK2H14 using CCS 6.1.3 and XDS200 USB Onboard Debug Probe. In the case of the 66AK2H12 device, one workaround detailed by  was to add PTM nodes to the existing ccxml target configuration.

    Maybe adding the PTM_0 node to your 66AK2G12 target configuration file, with the address as detailed in the referenced thread will also fix the problem with the 66AK2G12. I don't know the internals of the keystone 2 devices to know if a 66AK2G12 uses the same address for PTM_0 was the 66AK2H12.

  • Hi,

    Please apologize; despite several issues were fixed in release 1.2.0, I failed to notice that specifically ETB for K2G devices was only released in version 1.2.1 of the Keystone package.

    This package was bundled with CCSv8.0.0 but an update to CCSv7.x releases was never properly created.

    I just did this and it will be available later today or tomorrow as a CCS Update.

    If you want to try this out today, you can follow the instructions available at the page below to perform an offline install of this package:

    processors.wiki.ti.com/.../Device_support_files

    I apologize for the confusion.

    Hope this helps,
    Rafael

  • I'll look forward to the CCS update. I'm running CCS v7.4 now.
  • Hi,

    The Keystone 2 device support package 1.2.1 update is already available. Feel free to go to menu Help --> Check for Updates.

    Regards,
    Rafael