Hello experts,
I'm trying to maneuver between many rocks and hard places in this one:
Here is my setup:
Since the C6424 device does not support hardware profiling/trace, we are having to resort to the Simulator (Megamodule / little-endian / ti.platforms.evm6424).
Our goal is to run the entire system - RTOS and all (as large a subset as possible) in the Simulator. I have done this earlier for a C6472-based system with good results and elsewhere in elaborate ARM-based co-design environments...
# To that effect we are simulating I/O using PIN-connect and faux-HWIs. The simulator FAQ (http://processors.wiki.ti.com/index.php/Simulator_FAQ) seems unclear (spru600i.pdf) about the support for McBSP in C6424-sim. PLEASE CLARIFY.
# PLEASE CLARIFY on the ability to model and simulate external memory (DDR) width (16 vs 32) and timings
# The Cache Layout Tool workflow (http://processors.wiki.ti.com/index.php/Program_Cache_Layout)
Thanks!
I found what I was referring to earlier: SPRU187T.pdf / section 3.8.3 Feedback Directed Optimization API: TI_start_pprof_collection(), TI_stop_pprof_collection()
I looked at the corresponding RTS sources...
I call _TI_start_pprof_collection() at the beginning of main.... and in my idle loop I have as global boolean to check and call _TI_stop_pprof_collection(); at first glance, this does not seem to call _output_path_profile_info()... wonder why...
Is is because System.SupportProxy = xdc.useModule('xdc.runtime.SysMin'); ?
Hmm... looks like SysStd is the choice here... it seems to dump out pprofout.pdat. So far so good.