• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 97 subscribers
  • Views 274 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.

Howto debug into Codec engine on DM6467 ?

Mike Davies
Prodigy 130 points

Hi,

I have a test application which runs on the DSP side only of a DM6467 (no ARM code involved).  There are 2 .pjt files,  one for the test application which sets up a codec and runs it,  and the other for the codec (MPEG2 decoder). This works fine and I have source level debugging for the test application in CCS (v3.3.81.6).  My problem is that I cannot seem to debug into the codec engine.   I have tried setting the Compiler Options / Basic / Generate Debug Info to "Full Symbolic Debug (-g)" and Opt Level and Program Level Opt both to "none" fir the codec (which are the settings needed for the test application to give symbolic debugging) but to no avail.

Am I missing something here, or can anyone tell me what I have to do to debug my codec engine in a DSP only application ?

Many thanks,

Mike

 

 

  • 0
    Prodigy 130 points

    That's a "no" then, is it ?

     

    Mike

  • 0
    TI__Genius 17205 points

    This certainly should be possible.  Do you mean debugging into the Codec Engine APIs (e.g. Engine_open(), VIDDEC_create(), etc)?  And/or do you mean debugging into your codec library?

    The Codec Engine (and underlying Framework Components) provide source as well as pre-built debug libraries to enable single-step debugging into them.  You probably just need to (during the config step) cause these debug libraries to be linked into your executable.  (FYI, the list of libraries to link in falls out of the config step, and is in the generated linker command file - likely with an .xdl extension.)

    Which version of Codec Engine and/or Framework Components are you using?  (Newer releases have easier - but different - ways to configure these debug libraries into your executable, so unfortunately the version matters.)

    Chris

  • 0 in reply to Chris Ring
    Prodigy 130 points

    Well, I found it in the end :  the answer is to set “Disable Conditional Linking” and “Disable Debug Symbol Merge” under the “Linker->Advanced” tab in the build settings.

    Hope this helps someone else,

    Mike