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

CCS 4 debugging iUniversal example

Danny Marsh
Intellectual 330 points

I have a custom board with a dm6446 running Linux.  I have included the dvsdk 2.00.00.22 and necessary tools to get the iuniversal examples (fir and random # generator) to build under Linux.  Now I am missing a big step, how do I debug this using CCS 4.1.2 and Spectrum Digital XDS560R.  I have found some information about how to debug it with CCS 3.3, but nothing with CCS 4.  BTW the CCS 3.3 really didn't help me much and building a sample project with CCS 4 didn't either. 

Does someone have a CCS 4 project already created for the iuniversal example or can lead me to a detailed document on how to do this?  Thanks.

  • 0
    TI__Guru**** 482781 points

    To use CCSv4 with the SD XDS560R, you will need some additional drivers from Spectrum Digital. You can contact them directly for further details

    Thanks

    ki

  • 0 in reply to Ki
    Intellectual 330 points

    I have the drivers and I can connect to my board through the emulator.  My question is how to debug the iUniversal application in CCS 4.   I need some type of document or example project.  Has someone at TI made an example project for the iUniversal example?  Should I try to use CCS 3.3? 

  • 0 in reply to Danny Marsh
    TI__Guru**** 482781 points

    This tutorial walks through creating a simple project (hello world) and debug it with CCSv4:

    http://processors.wiki.ti.com/images/2/27/CCSv4Tutorial-HelloWorld.pdf

    If there is a CCS v3.3 project for the iUniversal example, you can try using the import wizard to convert it into a v4 project

    Thanks

    ki

  • 0
    TI__Guru**** 171809 points

    Hi,

    iUniversal is based in Codec Engine and is commonly built using command-line tools in a Linux host PC, therefore we don't have any CCSv4 projects available.

    However, debugging any Codec Engine project in CCSv4 is entirely possible and the main reference is the wiki page below:

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

    Although the page was designed for CCSv3.3, the procedure for CCSv4 in the section Codec Debugging is very similar:

    1. Start CCS

    2. Create target configuration file for the DM6446/XDS560R target. Go to menu File --> New --> Target Configuration File  and start in step 2 of the procedure here

    3. Go to menu View --> Target Configurations. Open the User Defined, right-click on the file just created and select Launch Selected Configuration

    4. Once the debugger perspective opens, right-click on the DSP core and select Connect Target

    5. Go to menu Target --> Load Symbols and choose your dsp server executable as input file (should have .x64P file extension)

    (continue to steps 4 and 5 at the page)

    Hope this helps,

    Rafael

     

  • 0 in reply to desouza
    Intellectual 330 points

    Thank you.  I just got back to working on this and have a few more questions.  I am attempting to debug the iUniversal FIR application.  I got through all the steps and am able to set breakpoints and step through the code using the Disassembly window, but when I try to open the corresponding C file I can't set breakpoints or step through this file.

    Do I need to create a CCS project to get this to work?

    Do I need to build the iUniversal application with a debug option turned on?

  • 0 in reply to Danny Marsh
    TI__Guru**** 171809 points

    Hi,

    dmarsh10 said:

    Do I need to create a CCS project to get this to work?

    No, you don't need to create a project.

    dmarsh10 said:

    Do I need to build the iUniversal application with a debug option turned on?

    This is necessary as the debug option (-g) is key to allow the debugger locate the corresponding lines in the source code. However, if the optimizer is turned on the debugger may lose correlation between assembly instructions and source code, therefore impacting the debugging process.

    Hope this helps,

    Rafael

     

  • 0 in reply to desouza
    Intellectual 330 points

    I am trying to figure out how I can step through the C source code of the iUniversal example.  I am building with (-g) option.

    1.  If I was to make a project for the iUniversal example how would I do that and what type would it be?  Note that I am building all the code in Linux.   Would that help locate the source files?

    2.  I  tried to setup the Common Source Lookup Path and that didn't work either.  Any suggestions?

    Thanks.