• Locked Locked
  • Replies 3 replies
  • Subscribers 54 subscribers
  • Views 733 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.

Debug Active Project - it does not halt the CPU

Calum Mackinnon
Genius 4155 points


I have a a customer with the following problem - I've seen a few posts with similar problems but not exactly the same. They are using a 6747 and CCS V4.

I compile and build the executable .out file in the DOS command window. Then I create a “Standard Make Project” in the CCS, and a target configuration file. To test the code, I select “Debug Active Project” under “Target” menu. CCS is supposed to load the .out file to the target, and halt the CPU. But After I select “Debug Active Project”, it does not halt the CPU, and the “Terminate All” button is on.

 Any help would be appreciated.

Cheers

Calum

  • TI__Guru**** 162895 points

    Calum,

    By default CCS will run to main on a program load or restart.  It could be that your app is not getting to main.

    You can disable this option.  When you are in a debug session, go to Tools-> Debugger Options->Generic Debugger Options.  Scroll down to the Auto Run section.

    Regards,

    John

  • in reply to JohnS
    Genius 4155 points

    Hi - Unfortunately this did not help - see response below

    "I am giving up. I just couldn’t solve this problem. It wastes me a lot of time. If I use the same source code, and create a CCS project, i.e. compile and link in the CCS. It works fine. The .out file is loaded to the target, and I can step through.

    I am not sure what the “Standard Make Project” will do. Does it try to build the .out file? If the build fails, does it stop load the .out file which I already build it. I don’t want CCS to rebuild it. I just want to use the CCS to debug my code."

    Cheers

    Calum

  • in reply to Calum Mackinnon
    TI__Guru**** 162895 points

    Calum,

    A standard make project does what you tell it to do.  With a standard make project you must supply the makefile and say what build command to run.  If they haven't supplied a makefile to build the .out then it won't do anything when they build.  There will be a call to gmake but it is not going to touch his .out as it doesn't know anything about his .out.  There is a short video on setting up a standard make project here: http://processors.wiki.ti.com/index.php/Quick_Tips#Getting_Started.C2.A0

    Clicking on the bug button for a standard make project will:

    1. run whatever build command was specified (if nothing has been specified then there will be a call to gmake "make -k all" but without a makefile it does nothing)
    2. launch the debugger using either a target configuration in the project or the default one
    3. If there is a .out in the project it will load it (if there is more than one it prompts you which one to load)

     

    Really the only thing different from a regular project is step #1.  In a regular project it will build whatever source files are in the project.

     

    If they don't want to use a CCS project they may just want to launch the debugger and then load the .out once they are in the debug session.

     

    Regards,

    John