• State Not Answered
  • Locked Locked
  • Replies 13 replies
  • Subscribers 22 subscribers
  • Views 4030 views
  • Users 0 members are here
Options
Related
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

KEIL versus IAR JTAG debugging...?

Dave Sudolcan

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.

Parents Reply Children
  • 0 in reply to Keil Software Support Intl.

    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

    In hindsight, I'm not sure why I had incorrectly interpreted that to mean that the debugger had been disabled in the eval version. I was able to run the KEIL/Atmel Blinky project as-is. I'll now try to add interrupts to the project and see how things go.

    Again... sorry for the confusion, and thanks for allowing folks to eval the JTAG debugger too!

    Dave.

  • 0 in reply to Dave Sudolcan

    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.