I'm currently evaulating the the IAR tools that came with ATMEL's AT91SAM7S-EK eval kit(which uses the AT91SAM7S64). The IAR tools (using a Segger J-Link tool) don't appear to be able to debug ISR's very well, if at all. Before I go through all the hoops to get several $1000 to spend on evaulating the JTAG debugger enabled version of the KEIL tools, I was wondering if anyone out there who's using them would mind commenting on how well they work when debugging ISR's.
CORRECTION: I have a pile of "USB to JTAG conversion boxes designed for ARM cores", not JTAG debuggers. The only ARM debugger I have is the one that came with the IAR/ATMEL eval kit. I was trying to use one of these conversion boxes with the KEIL eval to try out the KEIL debugger. Even though we've purchased several products from KEIL over the years, when I inquiried about evaluating the ARM debugger the response was "you must buy it to try it... if you don't like it then we'll give you a full refund". However, I'm not trying to buy a pile of licenses either. I'm just a lone developer on a one man team project.
Just a clearfication: ULINK allows full debugging even in an Eval version. The Eval version only has code size limits. I do not know why it did not work for you. Reinhard
Thank you Mr. Keil, and sorry for my mistake. I had incorrectly assumed that the dialog box that popped up when I clicked on the start debug button meant that the debugger wasn't working. Dialog box text:
uVision3 MISSING DEVICE (SECURITY KEY NOT FOUND) Running in Eval Mode
The interrupt example worked as-is, right out of the box too. I was able to set a breakpoint in the timer ISR that toggled the state of an LED, and every time program flow broke there I could click the run button and the state of the LED would change... just like you'd expect it to. Wonderful, just wonderful. Dave.