When I enabled it, the program execution became very slow, and the profiling result was obtained hardly.
(The ccs version is 3.3)
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.
Hello Ed,
Ed Shieh said:When I enabled it, the program execution became very slow
When profiling large programs on hardware, this can be the case since the CCS profiler is breakpoint based. Hence it is intrusive and can set many breakpoints (one set for each branch in the program) and all the halts can really slow things down.
What target and emulator are you using?
ki
Ed Shieh said:the more important is how can i do profiling under dm6437 for optimization.
Sorry, there are not a lot of options on C6000 HW. I don't think your device supports trace.
You can try using the profile clock:
http://processors.wiki.ti.com/index.php/Profile_clock_in_CCS
or using some compiler instrumented profiling:
http://www.ti.com/lit/ug/spru187o/spru187o.pdf (Section 3.8)
Thanks
ki