Profiling L2 stalls in CodeComposer 3.3

Tamir Einy

Prodigy 20 points

Hi,

I am using Code Composer 3.3 and TI card, DM642,

I would like to get measurments of the stalls occurs due to L2 Cache misses,

I found only an option do check L1 stalls, but i know the card has L2 chache as well,

Can you help me please ?

Thanks,

Tamir

over 14 years ago

0 Ki over 14 years ago

TI__Guru**** 482571 points

Looks like for the DM642, only L1 activities are exposed to be counted. Sorry

0 Tamir Einy over 14 years ago in reply to Ki

Prodigy 20 points

Thanks for you answer, In this case, what's the recommended way to measure the time the ALUs arewaiting due to L2 stalls?'

0 Ki over 14 years ago in reply to Tamir Einy

TI__Guru**** 482571 points

The simulators have much more debug visibility and you can count more events on them. There is a DM642 simulator that comes with 3.3. It offers a lot more events that can be counted - including many L2 events. I didn't see anything specific to L2 stalls but you may be able to use one of the other events to help you get the information you need.

Hope this helps

Code Composer Studio™︎

Code Composer Studio forum

Profiling L2 stalls in CodeComposer 3.3