• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 53 subscribers
  • Views 605 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/TMS320F28069: CCS Debugger (with) TMS320F28069: Debugger will not start (or runs but is inoperable)

Goetz Borkowski7
Intellectual 410 points
Part Number: TMS320F28069


Tool/software: Code Composer Studio

Hello community,

with one of my CCS projects, debugging won't work:

When the debugger is invoked, erasing the flash as well as downloading the SW
works well, but:

The debugger perspective appears, in the "debug" window, "debug probe / C28xx (Running)" is indicated.
But the only enabled button is the red  "quit debugger" button.
"Break", "Step into" etc. are disabled.

"Break at address 0x3ff788" (!!) is reported in the "source not found" window.  (3ff788 is boot ROM...)

Short time ago, everything went fine, I don't know what happened...

Has anybody an idea what might be on??

Best regards, Goetz

  • 0
    TI__Guru**** 173310 points

    Goetz Borkowski7 said:
    The debugger perspective appears, in the "debug" window, "debug probe / C28xx (Running)" is indicated.

    This means that the core is running instead of the default behavior of being halted at main. This could happen due to a number of reasons. Either the code is stuck in the boot routines and does not even reach main, or it ran freely past main because the CCS setting did not tell it to halt at main (setting described here). Check the Debug Properties of your project to see if that might be the case.

    If the debugger setting is not the issue, then you need to debug where and why your code is running. You should be able to "suspend" execution, then Restart and try to debug what is happening.

    Goetz Borkowski7 said:
    Short time ago, everything went fine, I don't know what happened...

    Did you change anything in the project code or settings? 

  • 0 in reply to AartiG
    TI__Guru**** 173310 points
    Since I haven’t heard back from you, I’m assuming you were able to debug the issue or move past it. If not, please feel free to post a reply with an update and additional details. Thanks!
  • 0 in reply to AartiG
    Intellectual 410 points
    Hello from Ubstadt / GER,

    you're right, I should clarify what was on... ;-)

    The offending mistake was in my linker command file:
    Somehow, the entry
    "normal : > FLASH<xy>, PAGE = <z>" was lost.
    Section "normal" designates the section of code which begins with the label "_c_int00"and is the standard code
    that is executed prior to "main()".
    Since there was no explicite assignment "section <==> address", the linker assigned this section to a RAM address.
    So, after the RAM sequence, execution ran to nowhere...
    ===> For the debugger, there were no more occasion to stop...

    In addition, I should mention that the assignment
    "normal ===> RAM address"
    is not inevitable if an explicite assignment is missing: In earlier attempts, the linker apparently placed the "normal" section
    anywhere (I don't know where), but it must have been located to flash memory -- the program worked in these cases...

    Ok, so far 4 today
    Best regards, Goetz