• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 82 subscribers
  • Views 333 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.

Original question:

LAUNCHXL-F28069M: Custom debugging tool (like gdb)

CCS/LAUNCHXL-F28379D: Followup on debugging executable not build with CCS

Torsten Robitzki
Expert 2504 points

Part Number: LAUNCHXL-F28379D

Tool/software: Code Composer Studio

Hello,

for various reasons, I want to setup a project that also contains some targets for C2000 microcontroller (F28379D and F28377S) using cmake. With the help of the documented Project Creating manuals, I was able to setup a cmake project that supports both chips and I was able to create a first binary. I was able to upload that binary, unfortunately it is not working and I have to debug it not.

Here (https://e2e.ti.com/support/microcontrollers/c2000/f/171/t/888388?tisearch=e2e-quicksearch&keymatch=gdb

  • 0
    TI__Guru* 93800 points

    Hello,

    in CCS it is possible to import a project based on a make file as follows:

    File -> import -> C/C++ -> Existing Code as Makefile Project

    Regards

    Lori 

  • 0 in reply to Lori Heustess
    Expert 2504 points

    Yes, I'm aware, that one can import an existing make based project into Eclipse. I've tried that route earlier this day (and was even able to build from Eclipse after adding a path for gmake) but I was not able to start the debugger. Now I'm reading through the Processor-Wiki to get some clue about the underlying debugger and if it would be possible to use it without Ecliplse (https://processors.wiki.ti.com/index.php/Debug_Handbook_for_CCS).

    Do you think it's a predicate to be able to build the targets to be debugged from within Eclipse?

    I tried to use CCS to create a Target Configuration and as the used chips where not listed, I've updated CCS, which then failed with Java Exceptions. Now I'm able to select the used Chip, but adding the existing make file project results now in a not openable project (see screenshot).

    best regards,

    Torsten

  • 0 in reply to Torsten Robitzki
    Expert 2504 points

    Deleting the workspace and adding the project again into a new, fresh workspace seems to work around the bug above. In the meantime, I've managed to start the debugger without adding a project to the workspace.