• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 99 subscribers
  • Views 336 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.

Tools required to develope DSP side apllication in OMAP35x

Prad
Expert 1125 points
Other Parts Discussed in Thread: OMAP3530

Hi,

 

We want to OMAP35x EVM to develop an audio application.

 

When developing DSP side code(supporting DSPLink) do we need to have CCS and an external emulator like XDS510?

And in that case can we use CCS for free with the EVM

 

 

Thankyou in advance.

Prad.

 

  • 0
    TI__Mastermind 41665 points

    Prad said:
    When developing DSP side code(supporting DSPLink) do we need to have CCS and an external emulator like XDS510?

    Having CCS and an emulator is not absolutely necessary, but it can make debugging things easier. Keep in mind that CCS and the emulator is really best for debugging the DSP directly (including DSP/BIOS) but is less suited to debugging the full Linux environment, so it makes for a good work flow of developing your DSP algorithm code with CCS directly on the DSP and than later porting that code into a DSPLink solution. I would recommend at least giving it a shot to see if you prefer CCS based development.

    Prad said:
    And in that case can we use CCS for free with the EVM

    Unfortunately no, the OMAP35xx EVM does not include CCS or an emulator, so you will need to at least buy an emulator. If you want to try this out on the cheap, there is the XDS100 class of emulator, which can be had for $79. The advantage of this emulator is not only the low initial cost of the emulator hardware, but that it will work with CCSv4 without any costly CCS license, so you can get a CCS emulation environment up for $79. The down side of the XDS100 is performance, it is a relatively slow emulator by comparison to the higher end XDS510 or XDS560 class emulators, but it is still functional for basic debugging and makes a good place to start.

  • 0 in reply to Bernie Thompson TI
    Expert 1125 points

    Hello Thompson

     

    Thankyou so much for the detailed reply,

    please let me ask one more question about selecting IDE.

     

    We are confused which IDE (CCSv3.3 or CCSv4) to select,

    I think most of the present sample codes and related software are built with CCSv3.3,

    when searched the forum, I found many users are finding difficult to import projects to CCSv4.

     

    Even the latest DSP/BIOS™ LINK release notes mentions about CCS 3.3.

    3.2.2.5 For working with OMAP3530

    · Standalone DSP/BIOS™ 5.32.04.

    · DSP CG Tools version v6.0.18 or greater

    · CCS 3.3 IDE

     

    In our case we are using the DVSDK-3.01.00.10 and the DSP/BIOS、XDAIS seems to be older version,

    if we choose CCSv4 as the IDE, is it possible to use the older versions of the software like DSP/BIOS.

     

    Regards,

    Prad.

  • 0 in reply to Prad
    TI__Mastermind 41665 points

    Prad said:

    We are confused which IDE (CCSv3.3 or CCSv4) to select,

    I think most of the present sample codes and related software are built with CCSv3.3,

    when searched the forum, I found many users are finding difficult to import projects to CCSv4.

    This is a good question, either will work, much of it is personal preference, along with the type of projects you plan on working with, if everything you have is already for CCS 3.3, and you are familiar with CCS 3.3, than I would probably use CCS 3.3.

    The first down side of CCS 3.3 is the cost, unlike CCSv4 with an XDS100 emulator, using CCS 3.3 requires a license of around $3594 as seen here. In addition to the license cost, CCS 3.3 has less support for the XDS100 emulator, it only supports an older XDS100v1 revision which may not be readily available and has limited devices support (will not interface to the Cortex-A8 for example), which means you may need a full blown XDS510 emulator (~$1k). CCS 3.3 is also less updated, so newer devices are not supported on it, this does not impact OMAP3 directly but may impact you down the road if you migrate your designs to newer devices.

    In general I would recommend starting with CCS v4, and than if it is deemed to be causing too many problems step back to CCS 3.3.

  • 0 in reply to Bernie Thompson TI
    TI__Expert 4930 points

    Just to add some more info:

    DSPLink does not use CCS to build. DSPLink has its own gmake based build system which is used to build the DSPLink dsp side side libraries and sample applications. Customers can use the DSPLink build system to build their own applications. However most customers tend to use CCS based pjt's to build their apps.

    Debugging DSP side using CCS is the easiest option. However, we do support debugging using NOTIFY IPC for scenarios where CCS is absent/XDS is absent etc. See here :http://processors.wiki.ti.com/index.php/Debugging_DSP_side_using_DSPLink_NOTIFY_module

    Deepali