• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 98 subscribers
  • Views 379 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.

CCSTUDIO: How to determine if a function within the debugger is within a library

jimj2713
Expert 2385 points

Part Number: CCSTUDIO
Other Parts Discussed in Thread: AM2634

Tool/software:

I am debugging an AM2634 example, and as I step through the software functions, I arrive at a C-file that is not in my compiler paths. The file icon at the top banner of the editor(?) window has a small folder icon above the C-file icon. I have a couple of questions:

1. Is there a pdf-version of the CCS 12 user manual (that might explain details like the file icons)? The on-line guide is not very searchable.

2. When I am in a function, I can find the file location (by hovering over the file name), but can I determine how it is linked to the project? As I wrote this file is not in my compiler search path, but there are a few libraries in the linker search path.

Thanks,

Jim

  • +1
    TI__Genius 13105 points

    Jim,

    1. The on-line guide, or the built in 'Help -> Help Content' inside CCS should be your main source for info lookup. Both guides should support text searches, and I can see a icon table in the Help inside CCS, although I'm not sure if it contains the one you saw. You can also try the Eclipse help (ie; https://help.eclipse.org/latest/index.jsp?topic=/org.eclipse.jdt.doc.user/reference/ref-icons.htm), since CCS 12 is based on the Eclipse IDE. 

    2. I'm not sure this will provide the exact information you need, but for files that are in the project, there is one feature you can use.  i.e. click the little button with the 2 arrows in project explorer.  Then when you have a tab open it will highlight the file in the project as well. 

    Thanks,

    Ricky