• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 31 subscribers
  • Views 436 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/TMS570LC4357: CCS Debugger never completes initialization

Ulf Samuelsson
Expert 1010 points
Part Number: TMS570LC4357


Tool/software: Code Composer Studio

CCS is behaving in a really strange way.

I go through the development cycle, edit, compile and debug using an XDS200 probe.

Suddenly when I start the debugger, it erases the chip, downloads the code, resets the processor and just hangs.

The program does not appear to be running.

There is no active button to stop, and no active button to run, single step or even reset the processor.

The only active button of significance is the red square - terminate the debug session.

What could cause such behaviour.

I have seen it before, and the only thing that seems to help is to create a new project,
using exactly the same files, and same options. Then it works again - for a while.

Another problem I ran into is that the interrupt vectors suddenly is garbage.
The code shown as source in the debugger is OK, but disassembly
of the first sector shows that is it is garbage.

The map file shows that the interrupt vectors are in the first 32 bytes
as they should. They have not changed.

Regenerating the project, with the same source made the problem go away.

What could explain this?

Is there a simpler way to handle this, like deleting some work directory?

BR
Ulf Samuelsson

  • 0
    Expert 1010 points

    I discovered the problem.

    When the debugger starts, I had a console view, not a debug view.

    Apparently  when the project is selected, no commands are available.

    When I select the debugging session, the commands are available.

    I think that this is something that should be fixed, the debugger should always put the focus on the debugging session. Maybe it does so after it stops the first time, but I get an ESM Group 3 notification with channel = 8, whatever that means, so the program stops in a loop before main is reached.

  • 0 in reply to Ulf Samuelsson
    TI__Guru**** 474421 points

    Hello Ulf,

    Your screenshots did not get uploaded correctly but I understand the issue you are describing:

    http://software-dl.ti.com/ccs/esd/documents/users_guide/ccs_faqs.html#after-connecting-to-target-and-loading-the-program-why-are-the-menus-icons-for-target-execution-resume-suspend-step-etc-not-available-greyed-out-

    Yes, the debug view is essential and must be open to have access to target execution commands.

    Ulf Samuelsson said:
    I think that this is something that should be fixed, the debugger should always put the focus on the debugging session

    It normally does, but sometimes the Debug view is manually closed, or focus is put elsewhere. There is no perfect solution for this. With earlier versions of CCS, we used to have pop-ups that reminded users that the Debug view is closed and that they should reopen it. People complained about the pop-ups so they were removed (even despite that fact that the pop-up had an option to "never show this warning again"). 

    Ulf Samuelsson said:
    Maybe it does so after it stops the first time, but I get an ESM Group 3 notification with channel = 8, whatever that means, so the program stops in a loop before main is reached.

    This seems to be a separate issue unrelated to the first. I suggest starting a new thread in the device forum (Hercules). The experts there can help you best.

    Thanks

    ki

  • 0 in reply to Ki
    Expert 1010 points

    Thanks,

    I discovered what the underlying problem was.

    A test feature in an attached FPGA screwed everything up, so we disabled the test feature.