• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 53 subscribers
  • Views 777 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:

CCS/TMS320F28379D: Break at address "0x3fe493" with no debug information available, or outside of program code.

CCS/LAUNCHXL-CC2640R2: Error when trying to connect the target in Debug mode in LAUNCHXL-CC2640R2

Frederic Philips
Prodigy 120 points
Part Number: LAUNCHXL-CC2640R2

Tool/software: Code Composer Studio

During the debugging of an application, I get the following error:

Break at address "0x1000060a" with no debug information available, or outside of program code.

As I read the other forum posts with similar issues, the problem arises due to the CPU getting halted at a program address where no source code correlation or debug information is found.

Can anyone help me in pointing out how to solve this problem?

  • 0
    TI__Guru**** 463961 points
    Hello Frederic,

    In your case, it appears there is no debug information available at the address you are halted on. My question to you is this: is that a valid address to be halted on? Should there be code at that address? If so, then the debug symbol information is missing. If that is not a valid address for code, then the next question is why did it halt there? This is an application specific issue (and not a tools debug issue) - looks like some exception was encountered.

    thanks
    ki
  • 0 in reply to Ki
    Prodigy 120 points
    Hello Lee,
    Could you please explain what you mean by "no debug information"? Thanks!

    Regards
    Frederic
  • 0 in reply to Frederic Philips
    TI__Guru**** 463961 points

    Debug information is needed by the debugger to provide source level debug visibility when debugging the program. Assuming debug symbol generation is not suppressed, debug information for a source file is generated when the file is compiled. This allows the debugger to correlate a program address with a source line among other things. If that information is not there, then the debugger will not be able to do that correlation and you will not be able to do source line level debug. 

    Let's look at your error:

    Break at address "0x1000060a" with no debug information available, or outside of program code.


    Either that address is a valid address with valid code but the debug information for that address is missing

    OR

    That the debug information is all there but that address is not valid or does not have any code associated with it.