This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

ICDI: programming succeeds but debugging fails

I've just received my stellaris LM4F120XL evaluation kit. I've written a small variation on the blinky program using Keil uVision, I can upload the program to the device and confirm it works as I expected.

If i try to debug my program however the debugger closes immidiately after starting up, I use identical settings for programming and debugging (Stellaris USB ICDI, JTAG, 1MHz, SYSRESETREQ, page-erase, program and verify).

Any ideas how to fix this? Because uVision immediatly jumps back from the debug view to the normal development mode I can't see what is happening.

  • I had the exact same problem with the LM4F120XL in my case I had plugged the board into a USB 3.0 port on my motherboard. When I switched to a USB 2.0 port this problem disappeared.

  • Thanks for the suggestion, but my machine has only USB 2.0 ports, so my problem must have a different cause.

    I've also tried different ports on my system, on different controllers (my mainboard has ECHI and UHCI), but no difference.

    Also worth mentioning is that the debugger from Code Composer Studio does work. So a hardware (connection) problem seems unlikely.