Hi,
Our application background: CCS2.2 Emulator, SEED DEC6416 (DSP board), and the USB interface; the time needed to profile includes the data transformation between DSP and the PC host via USB interface and the data itself processing.
I have studied your application file Code Composer Studio IDE 2.2 Profiler (SPRA905), and have some questions ,hope to get your suggestions.
1, when using profile function in my program (about the data transformation between DSP and the PC host), I find that the data transformation happened less smoothly than without doing the profile action.
On the page 2/5, it says: the profiler sets breakpoints at the start and end of each profile area as well as before and after each branch or function call. Each breakpoint takes time to execute and for every breakpoint, the following actions occur: halt the target, gather information, and restart the target.
//Can I think the profile function in my CCS2.2 Emalator does not meet my needs on data communication between the PC host and the DSP?
2, on the page 4/5 in the SPRA905, it shows: In order for the emulator device drivers to communicate through the scan path, its instruction cycles are counted using the on-chip analysis interface of the DSP. Other device drivers may require the use of other types of timers.
//Could you let me know how to do the Emulator profile about the data transformation or how to use the on-chip analysis interface of the DSP, or need the other profile tools?
Thanks and Best Regards
