Please note: We are aware of an issue affecting replies on the Arm Community forums, which may not be loading as expected.
We apologize for any inconvenience and appreciate your patience while we investigate and work to resolve the issue.
Thank you for your understanding.
Hi, Occasionally my code gets stuck at address 0x00000344 - I'm having trouble figuring out what's going on in the debugger. The disassembly list in uVision seems suspect as I page up and down (output looks like it's a loop of some other different memory locations?), and the call stack is empty... Perhaps this is a 'protected' interrupt or another unused interrupt that the default Startup.s sets up to loop-in-place, but I'm having trouble figuring out where/what that is, I need some guidance, kind of a newb with Keil tools and the LPC210x... yikes!
0x00000344 FFFE (???) 0x00000346 EAFF ???
thanks! Marc
Thanks for the basics but... I'm a newb at the toolset, not at debugging :)
I was hoping 0x00000344 was a 'magic number' that someone might recognize.
1) make all "hang me in a dead loop" aborts distinguishable from each other (e.g. put something in a register or global before entering the loop, or better still, make the dead-loop write that value).
If I could catch it at that point then I wouldn't have needed to post anything, I would have found it already!