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

Problem debugging codec code on DM6467T EVM

Helmut Forren
Mastermind 6805 points

By Jan 25 2011, I was able to debug my codec with CCS, per instructions I posted at http://e2e.ti.com/support/embedded/f/356/t/90292.aspx

Now it doesn't work anymore.  I suspect the problem has to do with my build environment, but I'm unsure because I have been unsuccessful at rebuilding under the old, still present, environment.  I may try some more to rebuild under that environment, but for now I'd rather try to fix the problem with the new environment.

Currently (new environment) I build my codec .a64P file with CCS on my WindowsXP(MachineB).  Then I copy that .a64P file to an appropriate folder on my Ubuntu/VMWare/WindowsXP(MachineA), where I build the codec server .x64P file, as well as my application that invokes them.  When I follow my instructions for debugging with CCS and try to set a breakpoint, I get various errors that I won't go into right now.

My previous environment still had the app being built on Ubuntu/VMWare/WindowsXP(MachineA), but instead BOTH the codec .a64P and codec server .x64P were being built with CCS on WindowsXP(MachineB).  To summarize, the different is strictly where the codec server .x64P is built.  The codec .a64P and application remain being built where they have always been built.

So, is it perhaps the case that my makefile on Ubuntu/VMWare/WindowsXP(MachineA) is not correct?  Is it not setting appropriate "debug" flags or generating additional symbols above and beyond those coming out of the .a64P file still originating from CCS WindowsXP(MachineB)?  Note that this makefile is derived from the dvsdk make demos makefile, so I can't imagine that it would have had debug flags set.

To rephrase, how do I set debug flags in the makefile?  Which debug flags specifically?  (After I get this working, if I do, I'll add an addendum to my reference post above clarifying this situation in case someone else encounters it.)

Thanks VERY much,

Helmut

  • 0
    TI__Genius 17215 points

    Helmut,

    Where you able to get over this ? Asked few people abt the dvsdk makefile, looks like it has right settings to debug on CCS.

    regards

    Yashwant

  • 0 in reply to Yashwant Dutt
    Mastermind 6805 points

    Yashwant,

    Thanks for your help.  I have not gotten back onto this task yet, and have no solution yet.  I'll would like to get a solution soon, so I can debug for real rather than pepper my code with logging commands!

    Regarding the dvsdk makefile, is it ALREADY providing settings to facilitate CCS debugging, or is it merely prepared and I have to provide something else (like an env var) to cause those settings to get used?

    Thanks again,

    Helmut