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.

ETB data format

Hi,

in the context of my diploma thesis I'm trying to permanently collect runtime information of the C6678 Multicore DSP using the Embedded Trace Buffers (ETB).

For my application it is essential to interpret the collected data without Code Composer Studio and/or any other TI Tools. That's because the software is intended to run on a embedded system with a FPGA, which should decode and process the DSP Trace information.

Until now I have not found any information/documentation about the ETB data format. I only found some Windows-Tools to convert the ETB binary data like TD (http://processors.wiki.ti.com/index.php/TD) and BIN2TDF (processors.wiki.ti.com/index.php/BIN2TDF).

Is there any specification available for this binary format?

Regards Fabian

  • Fabian,

    I don't think we have a published specification for the binary format itself, but you may want to take a look at the ETBLib in the page below as it allows the target to collect this data and it may allow you to set specific output data formats.

    http://processors.wiki.ti.com/index.php/CToolsLib

    Another source that may indirectly help you is the page below, but that also does not contain specifics about the binary format itself, though.

    http://processors.wiki.ti.com/index.php/Embedded_Trace_Buffer

    I will keep looking for anything that could dig further on this, and will post back if I find anything, ok?

    Hope this helps,

    Rafael

  • Thanks for the quick answer.

    I already know the CToolsLib. Im generating and exporting the trace data with it, but I've found nothing about the output format in there. I can only specify, which parameters I want to record using AETlib.

    For me it is extremely important to understand the binary format of the ETB or of the tdf-files, since it seems to me that both are the same, except from the header of the tdf-file.

    Thank you for searching some more details about this.

  • Fabian,

    I confirmed and we don't publish the binary format publicly. Sorry.

    I am curious, though: why the .csv format does not work for you? For practical purposes it is a very simple format that can be easily opened in any third-party software or post-processed by any scripting language.

    Regards,

    Rafael

  • Again thanks for this quick reply.

    My problem is that I plan to decode the information directly on the embedded board. So I cannot go the way through a Windows-PC with TD-Tool to convert the binary data to csv-Format.

    If you have any source-code or libraries of the TD-Tool, which I might use directly on the C6678 or a FPGA this would be very helpfull.

    If this is not possible it would also be sufficient in a pinch, to have a standalone version of the TD-Tool without the need of a complete CCS installation and CCS license. Since our allplication is intended to be used as in-field profiling, we cannot provide a CCS installation with every system we are producing.

    Or is it possible to make an exception for a university research project?

    Regards Fabian

  • Fabian,

    Sorry, I don't think we will be able to provide this information. This information is buried inside design documentation that is TI internal, therefore cannot be sent out.

    Regards,

    Rafael