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.

How to model memory performance

Hi

I want to simulate DM8148 DSP. For the same i am using C674x cycle accurate simulator in CCsv5. Here are my queries:-

1.  Since the simulator available in CCSv5 is cycle accurate not device accurate then how can i simulate  the cache and other memory cycles in profile?

2. When i use the DM8148 EVM then there is no profile support available. In such a case i am unable to actually analyze the cache and memory stalls for program and data memory.  They how can i model he memory performance of my algorithm on DSP?

In sum, I am unable to know my algorithm's memory performance on simualtor and EVM.

Please help

Thanks

Abhishek

 

  • Hello,

    Abhishek Singh Sisodia said:
    1.  Since the simulator available in CCSv5 is cycle accurate not device accurate then how can i simulate  the cache and other memory cycles in profile?

    You must use a device simulator that models cache and other peripherals. Note that there are cycle accurate device simulators. These would model cache. It is a CPU simulator that does not model cache.

    The C674x simulator is a CPU simulator.

    Abhishek Singh Sisodia said:
    2. When i use the DM8148 EVM then there is no profile support available. In such a case i am unable to actually analyze the cache and memory stalls for program and data memory.  They how can i model he memory performance of my algorithm on DSP?

    CCS function profiling is not supported on C6000 or Cortex HW. One option is to use the profile clock to count events like cycles and stalls and such (the C6000 has more events available to count than ARM).

    Thanks

    ki

  • Hello Ki-Soo

    Since there are no C674x device accurate simulator so this is for sure that i can not model the memory performance. Now coming to profiling clock then the same has some break-point problem as explained in one of wiki pages.

    I guess we cannot profile for memory and always keep on guessing. Bad support from TI for algorithm developers on DM8148 DSP. :(

    Anyways thanks a lot for your reply.

    Regards

    Abhishek