• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 98 subscribers
  • Views 379 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

TMS320C6455 CPU Cycle calculation with CCS3 Profile

Jeong Sang Gi
Intellectual 255 points
Other Parts Discussed in Thread: TMS320C6455

i use the CCS3 for the first.time.

Before continuing, i'm not good enough in english.

i wish to TMS320C6455 cpu process time before purchase DSP.

CCS3 setup and project create procedure are as below.

Please review it.

1. install CCS3

2. execute CCS3 Setup.exe

3. select C64xx CPU Cycle Accurate Simulator – TMS320C64xx – TMS320C6000

     Processor Properties is default.

4. execute CCS3.exe

5. create New project.

6. add to source file, header file, rms6400.lib in project.

7. build project

8. load execute file(.out)

9. profile setup

10. run project

as a result, cpu process time of total FFT2D is 2.0sec.

it astonishes to believe.

image size is 128x128.

 

Please review about the wrong and left off the procedure and tell me your views.

Thanks.

 

  • 0
    TI__Guru* 84110 points

    Jeong Sang Gi,

    Welcome to the TI E2E forum. I hope you will find many good answers here and in the TI.com documents and in the TI Wiki Pages. Be sure to search those for helpful information and to browse for the questions others may have asked on similar topics.

    My recommendation is to use CCSv5. CCS 3.3 is very old and support is not available broadly. There is no license fee for using CCSv5 for simulation or for connecting directly to EVM/DSK boards with on-board emulation.

    The C6455 has the C64x+ DSP core, not the C64 core, so you want to use 64plus libraries. And you want to use the correct simulator for the C64x+; I do not remember what that would be called for the C6455, but I recommend using a Device Simulator and not a CPU Core-only simulator for best timing accuracy.

    The rms6400.lib is not familiar to me. Did you mean rts6400.lib? If so, you should use rts64plus.lib instead.

    What does the 2.0sec represent? Is this wall clock time or CPU cycles?

    Regards,
    RandyP

  • 0 in reply to RandyP
    Intellectual 255 points

    Thank you very much.
    Ask a lot of advice in the future.