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.

How to debug sample applications in Linux SDK using Linux CCS ?

Hi TI,

In Linux SDK, I always type "make" to build the sample applications.

These sample applications have complicated makefiles which involve other software tools.

How can i move these sample applications into Linux CCS so that I can debug the applications using emulator ?

Is there a procedure whereby CCS can make use of the makefiles to build the sample applications ?

Or must I manually add all the required source files in CCS and manually input all the content in the makefiles into CCS ?

Please advise.

Thanks,

Mr Tan

  • Hi Mr. Tan

    First off, I suggest looking at the Linux Debugger section of the below presentation (starting at slide 108)

    http://software-dl.ti.com/dsps/dsps_public_sw/sdo_ccstudio/workshops/CCSv5/CCSv5_AdvancedWorkshop.pdf

    I assume that for you application debugging, you will be using GDB as that is recommended. People use a JTAG emulator for kernel / low-level debug.

    You can set it up so that CCS builds the makefile. But if are happy with your current build system outside CCS, there is no need to import it into CCS. You can take the generated executable and load it using CCS and when debugging, CCS will ask you where the source files are. Once you direct CCS to the first source file, it should be able to find the rest.

    Thanks

    ki

  • Hi Ki-Soo,

    Thanks.

    2 more questions :

    1) Where can I find the procedure so that CCS builds the makefile.

         The makefile looks complicated to me as it involves a lot of other tools.

    2) Am I correct to say that I should use the stop mode debug to debug TI SDK ?

        From the workshop, this is the method that will ask for the location of the source file during debugging.

     

  • std said:

    1) Where can I find the procedure so that CCS builds the makefile.

         The makefile looks complicated to me as it involves a lot of other tools.

    CCS simply calls gmake on the makefile. The makefile is generated by CCS. If you are looking for more information on how makefiles are used by CCS/Eclipse, checkout the Eclipse CDT documentation;

    http://help.eclipse.org/indigo/index.jsp?topic=%2Forg.eclipse.cdt.doc.user%2Fconcepts%2Fcdt_o_home.htm

    The below doc is a bit outdated but it should give you an idea about the makefile generator part of Eclipse:

    http://download.ronetix.info/eclipse/C_C++_Development_Toolkit_User_Guide.pdf

    Search for "Makefile Generator"

    std said:

    Am I correct to say that I should use the stop mode debug to debug TI SDK ?

        From the workshop, this is the method that will ask for the location of the source file during debugging.

    Like I mentioned it really depends on what kind of visibility you need. I think you want to do app debug which means you would use run-mode GDB.

    Thanks

    ki