• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 54 subscribers
  • Views 664 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.

CCS/LAUNCHXL-CC2640R2: Why does debugger only work with main.c?

michael mathiasmeier
Intellectual 520 points
Part Number: LAUNCHXL-CC2640R2


This thread is a continuation of a previous thread at:
https://e2e.ti.com/support/tools/ccs/f/81/t/786197 

Tool/software: Code Composer Studio

Can someone explain what I am doing wrong with the debugger?

Debugging the slave Launchpad with the BOOSTXL-AOA SDK. Everything works fine, but I can only trap or reference code within main.c.

All other code, such as rtls_ctrl.c or rtls_ctrl_aoa.c either is disabled due to 'No Code Associated...' which I find hard to believe or just never traps.

I've been coding for 20 years and lots of RTOS but never used TI-RTOS before. Is there some debug configuration I'm missing preventing it from working properly? I have set optimization to 'off' with same result?

  • 0
    TI__Guru**** 474421 points

    Hello,

    michael mathiasmeier said:

    Everything works fine, but I can only trap or reference code within main.c.

    All other code, such as rtls_ctrl.c or rtls_ctrl_aoa.c either is disabled due to 'No Code Associated...' which I find hard to believe or just never traps.

    When you refer to "trap", are you referring to source code correlation with the debugger (i.e. you halted the target in code from rtls_ctrl.c but the debugger does not associate with the source file)? If my assumption is correct, it could be that the symbols for those source files have not been loaded. Are those files directly part of your project? Or are they coming from part of a library? 

    Thanks

    ki

  • 0 in reply to Ki
    Intellectual 520 points
    Good idea...I'll check it out.

    By 'trap' I mean able to set a breakpoint and have the program actually run and halt upon reaching that code.

    The files are actually part of the main application code. Some of the routines which I'm sure must be utilized never allow breakpoints to be set. They are just grayed out and disabled as "No Code Associated...". Other files allow me to set breakpoints but they are never triggered.

    It seems all these support files for this app are like this, so that's why I thought something it missing.

    Thanks, I'll check the symbols. Hopefully that's it.
  • 0 in reply to michael mathiasmeier
    TI__Guru**** 474421 points

    michael mathiasmeier said:
    The files are actually part of the main application code. Some of the routines which I'm sure must be utilized never allow breakpoints to be set. They are just grayed out and disabled as "No Code Associated...". Other files allow me to set breakpoints but they are never triggered.

    This definitely sounds like a source code correlation issue. One tool that is helpful to use is the Modules View:

    http://dev.ti.com/tirex/#/?link=Development%20Tools%2FIntegrated%20Development%20Environments%2FCode%20Composer%20Studio%2FDebug%2FDocuments%2FFeature%20Overviews%2FBrowse%20loaded%20debug%20symbols%20with%20the%20Modules%20view%20(YouTube)

    See if the source files are listed in the Modules view. If they are, see if you can click on it to open the source file

    Thanks

    ki

  • 0 in reply to Ki
    Intellectual 520 points
    Thanks k,

    Modules did sound like a good bet, but none of the files or functions were listed for this one. Thinking now this may be an application specific thing. So, I'll turn in a AOA technical support ticket.

    Thanks!