NOTICE: The Processors Wiki will End-of-Life on January 15, 2021. It is recommended to download any files or other content you may need that are hosted on processors.wiki.ti.com. The site is now set to read only.
Talk:SoC Analyzer
Using SoC Analyzer to Post-Process DSP/BIOS System Logs
According to spru403o.pdf, the BIOS 5.32 API reference guide (September 2007), in section 2.15, it is possible to enable "timestamped logs". However, the document points out that the CCS plug-ins cannot handle the time-stamped logs. But, they are supported by the System Analyzer Tool. I have two questions regarding this:
1. What does it means that the CCS plug-ins cannot handle the time-stamped logs? Does it mean they cannot be transferred to the PC or displayed by CCS? If not, how can these files be transferred to a PC and post-processed?
2. I assume that the "System Analyzer Tool" is SoC Analyzer. If not, what is it? If so, can it be used to view / post-process DSP/BIOS system logs without the rest of the SoC infrastructure (i.e., all of the data transfer from DSP to ARM to Linux file-system to PC)? If not directly, is it possible that a system log could be reformatted to enable this? I primarily interested in the equivalent of the CCS task execution graph with timestamps, and browsing capability.
Re:1. CCS Plug-in simply does not show the extra args and timestamp fields. Using a TCP/IP Plug-in or a memory read, the buffer content may be retrieved/saved into a file. DSP/BIOS' command line utility rtadecode supports decoding these extra fields creating a CSV file
Re:2. Yes, at one one point in time, "SoC Anaylzer" was called "System Analyzer". "SoC Analyzer" can be used in file mode without all SoC infrastructure.
--Pegah 15:03, 4 June 2009 (CDT)