TMDSCNCD28335: Model execution time

Hello Ki,

Where can they add or set the breakpoints to their code to measure the execution time?

Regards,
Carlo

Carlo Cabaccan said:

Where can they add or set the breakpoints to their code to measure the execution time?

This would depend on the sections of code they which to profile. The profile clock usage is quite simple as it simply counts the cycles it takes to reach the next halt point. They can set one breakpoint at the start of the code where they whish to start profiling. When the PC is at that point, they can remove (or disable) that breakpoint and enable the profile clock. Then they can set the next breakpoint at the end of the range of code that they wish to profile.

Note that it is important to only enable breakpoints and the profile clock when needed if the code is in Flash. This is due to the limited number of hw breakpoint resources available on 28x. The profile clock also uses a hw breakpoint resource to operate.

Hope this helps

ki

Hi Ki, thank you for your response. For example, can the customer set the breakpoints between the two lines highlighted in yellow (attached file)?

code (2).pdf

Regards,
Carlo

The customer can use breakpoints to profile that range of code. But again, remember that if you are profiling code in flash, you are limited to two hardware breakpoints. And also, the profile clock uses a hardware breakpoint resource. Hence if you set two hardware breakpoints in your code, you will not be able to enable the profile clock due to lack of available hardware breakpoint resources. Hence you can set one breakpoint at the start, run to it, then disable it and set one breakpoint at the end of the range and enable the profile clock. Then you can run to the next breakpoint and get the cycle count.

There are also other potentially "hidden breakpoints" that may be good to disable. Please see:

http://software-dl.ti.com/ccs/esd/documents/c2000_profiling-on-c28x-targets.html#profiling-solutions-for-c28x-targets

https://software-dl.ti.com/ccs/esd/documents/troubleshooting_no-aet-resources.html#be-aware-of-hidden-debug-operations-that-can-use-such-resources-

On a separate note, note that if the code is optimized, the source lines may not correctly line up with the actual generate code. Hence you may have issues setting breakpoints on an exact source line. Please see:

https://dev.ti.com/tirex/explore/node?node=AEm7LJjS34iFPa5fpT7ttQ__FUz-xrs__LATEST

Thanks

ki