I have two strange debugging issues in ccs Version: 4.1.3.00034.
The first issue has to do with the debugging state at startup. When I load one of TI's examples such as "blinky" into the LM3S2965 Eval Board, it stops at main() as I would expect. However, if I create a simple project similar to blinky, the debugger does not stop at main() when I load the debugger. I've checked most of the options in the project's properties and I saw no obvious difference, including the "Run to main" Auto Run option. Is there some option I should check?
The second issue may or may not be related to the first. I have another project I'm trying to port to the Stellaris. I'm using the LM3S2965 Eval Board to load the program into my target hardware which is using an LM3S2965 cpu. This project does not seem to load at all. The debugger claims it is running when I load it (same as above) but I do not belive it is. I set a breakpoint on main() and it never gets there. When I Halt the debugger, then Restart (same procedure I use in the above issue) I still do not reach main(). Instead, I get this message:
CORTEX_M3_0: Can't Run Target CPU: Timed out while waiting for target powerup/polling a hardware resource.
First I assumed the code was messing with the JTAG port. But I seriously doubt that. The code doesn't seem to run at all. If I insert test code to turn on an LED, it doesn't switch on. However, if I comment out all startup code -- code that I doubt is even being executed -- the program can be halted and I can single-step. So there seems to be a problem with the load module itself. I've also tried loading this same code directly into the LM3S2965 Eval Board with the same results. Any ideas?
