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.

Can not use the Embedded Trace Buffer (ETB) on a TIVA TM4C1294NCPDT with a xds100v2 JTAG

Other Parts Discussed in Thread: TM4C1294NCPDT

Hi,

I'm trying to track down a Sys/Bios stack corruption (see  TIVA SYS/BIOS FPU context switch corruption with zero latency interrupts) and I thought I would use the cortex M4 ETB hardware. According to the TI website I can use the ETB with a XDS100v2 JTAG. But after connecting to my target it doesn't seem to be possible.

I'm using CCS6.1.0.00104

My steps are

  • Press debug and wait for my code to be downloaded to the eval board.
  • Click Tools, Hardware Trace Analysis, Interrupt Profiling
  • Try and change the Transport Type. Only SWO Trace available when I think I need to use ETB

I just want to capture the trace of my software once it's hit my break point.

cheers

Chris

  • Hello Chris,

    CCS does not support Embedded Trace for Cortex M4 cores.

    Regards
    Amit
  • hi,
    Is there any plan to support this as some point?
    cheers
    Chris
  • Hello Chris,

    None that I know of. But Code Composer Studio Forum should be able to tell if there is something being planned.

    Regards
    Amit
  • Amit Ashara said:
    CCS does not support Embedded Trace for Cortex M4 cores.

    Do any of the TI Cortex-M4 devices include an Embedded Trace Buffer?

    There is no mention of an ETB in the TM4C1294NCPDT datasheet.

    [I have seen Cortex-M4 devices from other manufacturers which include an ETB]

  • Chester Gillon said:
    [I have seen Cortex-M4 devices from other manufacturers which include an ETB]

    Good that - and those (properly) investigating have (long) noted the same.   Absence of even (common) SWD, signals that, "best/brightest/most current" may not play here.

    Mating the (proper) tool to task should be a fundamental - and the (dual) limitations forced upon users by:

    • sub-performing, single vendor (only) IDE
    • MCUs - which do not fully/properly accommodate "vital and/or highly desired" functions/capabilities

    Poster may wish to survey & then (better) consider his, "weapon of choice."

    And sometimes - the methods, implementations, & examples of (others) may be adapted to your "less than stellar" device & lash-up.   At the minimum - (some) investigation proves worthwhile...

  • Hello Chester,

    At least in the TM4C12x device family, there is no ETB. There is only an ETM.

    Regards
    Amit