DM3730: Enabling DSPLink Log from Codec Engine application

Prateek Bansal

Other Parts Discussed in Thread: OMAP3530, DM3730

Hi,

I am trying to find DSP clock rate at run time on DM3730 device. As I look into dsplink/gpp/src/arch/OMAP3530/shmem/Linux/omap3530_dspclk.c directory, I see OMAP3530_getDspClkRate() function with TRC2_Enter and TRC1_Leave calls. How do I enable this trace log from Codec Engine application? I understand CE_DEBUG=3 does not provide this information. I can only think of rebuilding DSPLink using printk function in that file or by enabling trace. I am not sure if there is another easier way to enable DSPLink related log from CE application. Please advise.

Thanks

Prateek

over 13 years ago

0 Arnie Reynoso over 13 years ago

TI__Expert 6860 points

The is no hook between the DSPLink TRC level and Codec Engine. To get DSPLink tracing, you need to enable the level of tracing you need and re-build DSPLink.

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

0 Arnie Reynoso over 13 years ago in reply to Arnie Reynoso

TI__Expert 6860 points

Looking further into what was available via CE_DEBUG, you may be to get what you need by using CE_DEBUG=2.

In the CE package, the ipc/dsplink/Processor_dsplink.c has a dumpLinkCfgObj() function that prints the config with GT_3CLASS (is that done with CE_DEBUG=2?). One of these config elements is dspObject->cpuFreq, along with the memory maps and other settings.

This should get you what you need.

Processors

Processors forum

DM3730: Enabling DSPLink Log from Codec Engine application