Hi All
I have something strange with my uVision4 (4.01). I compiled a program, loaded it on my board (LPC1700) and started the debugger. The debugger started briefly but almost immediately returned to the compiler again. I tried the usual, restarting uVision, no luck, restarting windows, no luck Then I removed the tick at "Run to Main" and then the debugger staid. But single stepping caused the same effect, return to compiler, after 5 steps. Then I loaded Blinky just to witness that Binky did exactly the same. Now I this slowly drives me crazy. I noticed there was an update (4.03) and I loaded that. My uLink needed a firmware update after that so i considered that a good sign. But still, no luck. It still crashes. I checked a lot a entries in the forum, i removed memory windows, changed the USB connections but it is still the same. I am pretty desperate now.... Someone with a good idea out there?
The problematic instruction is part of the NXP ROM bootloader and writes to a special memory location which disables debug pins. Therefore after debugger steps over it the communication is lost.
Either skip this instruction when single stepping or run through the bootloader.
Robert,
Could you please elaborate a little more on this issue? The circumstances described by you and the OP and the instruction involved look strangely familiar to the source of my current headache (see here:http://www.keil.com/forum/docs/thread16421.asp). Thank you.
Hi
With the help of Alex from Keil I solved the issue. The NXP jtag tool for the LPC17xx needs the flag SWJ to be set. The Field Port must be on SW. Then it works. Don't ask why, I have no idea. Thanks for all the replies
Walter