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