• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 53 subscribers
  • Views 798 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.

Unable to limit capture (vs circular) in Hardware Trace Analyzer's Custom System Trace for ETB receiver

Piyush_
Expert 5235 points

CCS version:  6.1.0.00104

TI Emulator Version: 5.1.641.0

The receiver/Transport settings for choosing Buffer Type (and several others) as stop on full vs circular are blanked out for ETB receiver (they are not for 560 V2 Trace). Is this because the on-chip ETB h/w cannot fundamentally allow for this configurability?

  • 0
    Guru 92251 points

    Piyush_ said:
    Is this because the on-chip ETB h/w cannot fundamentally allow for this configurability?

    http://processors.wiki.ti.com/index.php/Debugging_With_Trace#Trace_Debug_Examples says:

    Because ETBs are shallow (7K to 10K samples typical) and only support circular buffer mode, the best method for capturing a bug is to use an End All Trace job to stop trace export either as the problem is occurring or shortly after the problem has occurred.

  • 0 in reply to Chester Gillon
    TI__Expert 5235 points
    Internal follow-up on this topic showed that older devices were not capable of limiting but k2 devices are capable of limiting, so this is a problem of driver/CCS not exposing the feature. An internal ticket has been filed so the capability (of stop-on-full for ETB) will be addressed in a future CCS version that closes this ticket.
  • 0 in reply to Piyush_
    Guru 92251 points

    Piyush_ said:
    Internal follow-up on this topic showed that older devices were not capable of limiting but k2 devices are capable of limiting, so this is a problem of driver/CCS not exposing the feature.

    Is there a list of which devices the ETB allows stopping the trace capture when the buffer is full?

    The reason is that on subsequent investigation I found that the ARM ETB definition specifies a trigger option to stop the trace capture when full, but that the ETB fitted to a AM335x didn't support the trigger. See https://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/441770

  • 0 in reply to Chester Gillon
    TI__Expert 5235 points
    Chester,

    I am sorry I shouldn't have generalized to k2 devices, I was only talking about the 66x DSP cores on the devices. I don't do ARM work and have never tried the ETB on ARM so I don't know anything about it, so I would let other TIers who officially support this answer the question on the link you posted. Reading there I see your point - it isn't clear if the h/w capability exists in the version of ARM we have in our devices and in the case it does exist, if it does not work because of software (driver, GUI etc) or the h/w capability does not exist and the software has not grayed it out, either way it needs to be addressed. Thanks.

    Piyush