|
|
Тема здесь неоднократно поднималась, наткнулся в форуме:
Can you tell me some inside detail information on how profiling the application code in Code Composer Studio is implemented by TI?
To be more specific: When profiling a piece of code (range), how is the code then modified (instrumented) in order to perform this profiling? Are (invisable) breakpoints added to just the start and end of the range to be profiled? Or is more done (more instructions inserted/performed) when a profile range is hit?
Are interrupts being disabled while the processor is executing code inside a profiled range? And can profiling have an influence on DMA or debugging (via XDS5xx) in general.
I hope you can share some info on how profiling is implemented on C5000 and C6000 DSP's.
Solution:
Texas Instruments answer:...
Yes, the profiling function uses profile points (breakpoints) which "halts" the target before pulling the profiling information. This is an intrusive process which will have impact on real-time debugging. The following FAQ mentions this.
http://www-k.ext.ti.com/sc/technical-support/knowledgebase.asp?kb=dsp&obj=4770
The best way to monitor your code in real-time is to use the RTDX module as explained in the following FAQ:
http://www-k.ext.ti.com/sc/technical-support/knowledgebase.asp?kb=dsp&obj=11998
Another alternative which provides more profiling functionalities when using DSP/BIOS is the STS module. This allows you to make an un-intrusive (no breakpoint) profiling but has the drawback to add a bit of code to your application. The following FAQ refers to this module:
DSP/BIOS instrumentation calls and real-time system information.
http://www-k.ext.ti.com/sc/technical-support/knowledgebase.asp?kb=dsp&obj=14990
Those 3 techniques are independant from the emulator type usesd as long as they are compliant with XDS510 or XDS560 standard. Please contact emualtor manufacturer for detailed information.
|
|
