• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 54 subscribers
  • Views 362 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.

migrating project from VS2k8

Robert Martin
Prodigy 60 points

I'm cross-posting this to the DM64x forum because I'm not really sure where this goes.

Many years ago my company created a product that uses the DM6446. We originally used a JTAG interface to debug our codecs on the DSP and that was way back with CCS3.x. Since then, we've migrated our code to run in a simulator created using MS Visual Studio. This has all been well and good until we wanted to know found out that our algorithms were using too many cycles on the DSP side and our VS simulator couldn't get us that information. So I've got a few questions.

1) This really whole discussion stemmed from our use of Engine_GetCPULoad. That didn't seem to be giving us very reliable estimates of our DSP utilization and got results that didn't make sense. Is there anything better we could have tried?

2) Is there a way for us to take our code and directly import it into CCSv5 and get it to run, both the ARM and DSP side code? In the end we'd like to have cycle accurate knowledge of our DSP algorithms and where we can find improvements. Can I do this for the whole project, or can I do it for a subset of files, or do I need to copy code into a new CCS project?

2) How do we simulate incoming video data? Or images?

Any and all answers are helpful. Thanks

  • 0
    TI__Guru**** 479381 points

    Hi Robert,

    Robert Martin said:
    2) Is there a way for us to take our code and directly import it into CCSv5 and get it to run, both the ARM and DSP side code? In the end we'd like to have cycle accurate knowledge of our DSP algorithms and where we can find improvements. Can I do this for the whole project, or can I do it for a subset of files, or do I need to copy code into a new CCS project?

    Assuming you are currently working with MSVC projects, a straight import to CCSv5 is not so simple. You will need to create a new CCS project and add your source to the project, in addition to having the a proper linker command file. Since you have used CCSv3.x in the past, this should be nothing new. The DM6446 device cycle accurate simulator that comes with v5 is very good for benchmarking you DSP code. You can count all sorts of events like cycles, cache hits/misses, stalls, NOP, etc. The benchmarking for the ARM simulator is not as powerful, though you can still count cycles at least.

    Robert Martin said:
    2) How do we simulate incoming video data? Or images?

    On simulator you can use pin and port connect to simulate interrupts and data coming in:

    http://processors.wiki.ti.com/index.php/Pin_Connect

    http://processors.wiki.ti.com/index.php/Port_Connect

    Robert Martin said:
    1) This really whole discussion stemmed from our use of Engine_GetCPULoad. That didn't seem to be giving us very reliable estimates of our DSP utilization and got results that didn't make sense. Is there anything better we could have tried?

    I think this call is from codec engine or SDK. The DaVinci forums is best to ask for more information on this.

    Thanks

    ki