• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 98 subscribers
  • Views 365 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.

Can not step through in C code when it was compiled as a debug option.

Hyung Paik
Prodigy 20 points


I have TIC6486 and EVM.  I complied TI video codec and ran ok.  But I compiled using -g and able to step through in the assembly code, not in the code.  I am using CCS3.3 SR11 patch.  I was able to step through in one of earlier version of TI codec.  If possible, i do not want to migrate to CCS4.0.

This has two parts, one is codec library and the other one is App.  It is ok in App, but not in Library code ( we have library source code).  Both are compiled as a debug option.

  • 0
    TI__Guru* 84110 points

    Hyung Paik,

    With CCS3.3, which emulator are you using? And how did you configure CCSetup for the EVM?

    If you are including the TI video codec from a library, that portion of the program will not be recompiled when you change your compiler options to -g. This is actually one of the benefits of a library, that it can be delivered with all of the functionality without requiring you to deal with all of the code that went into building that library.

    If this is not what you mean when you say "codec library", then please explain more. If a library (.lib file) was not already compiled for -g debug when it was built into the .lib file, then it will not be available for source debug.

    Is the library source code listed in your .pjt project file or in the Project pane under Source?
    Do you find .obj object files in your configuration's output folder, usually Debug or Release?

  • 0 in reply to RandyP
    Prodigy 20 points

     

     

    Hi Randy,

    I am using TMS320TCI6486EVM made by TI.  I have two projects, h264vencAlg.pjt and TestAppEncoder.pjt.   Both projects has Source directories which contains all the source code.  I removed h264venc_ti.l64P (library) and TestAppEncoder.out, then clean/build with -g option.

    I asked this to TI codec customer engineer and he also had same problem.  He said it is a problem in CCS, not in the codec.  He suggested to get a help from here.

    I had a simliar problem while ago.  I could step through in assembly, not in C. Also I could only step through in C only in the main program and could not watch any local variable except global variables.   A regional customer app engineer cam in and put some patches in CCS and frame_work (may be more ?). Since then it has been ok.