Strange behaviour while stopping Jtag-debugging

Go To Last Post
4 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hello,

currently I'm debugging an application on an MegaRF128 with AVR-Studio 4.19 Build 730 and Jtag ICE MK2. To watch the program flow I set two breakpoints which update the variables and continue. As long as the Ice is connected the apllication is running properly. If I disconnect the Ice carfully without reseting the apllication seems to hang and can not be restarted even not by a power cycle.

I watch another strange behaviour which is related to problem described above. After a PC reboot I started the Studio with the Ice attached to the same AVR-board as above. I started debugging and the application runs. The same two update breakpoints were active again. I stopped debugging by pressing the square icon of the menu (no reset before) and the screen update continues.

My expectation is: The Jtag ICE removes all breakpoints from the controller etc and the CPU acts as if the was no breakpoint.
Does anyone else made the same observation - so how should this be treated - as a bug or feature of the Studio, Jtag Ice or Mega?

Cheers
Knut
ps: I'm not expecting any correction from Atmel :?

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Surely you should stop debugging gracefully?

i.e. Break / Stop_Debugging and then disconnect the mkII.

If you clear all breakpoints, you may be able to disconnect the mkII from a running program. I can't see the point though.

David.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:
My expectation is: The Jtag ICE removes all breakpoints from the controlle
WRONG expectation.
Just click on the "remove all breakpoints" or reprogram the chip.

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

js wrote:
Quote:
My expectation is: The Jtag ICE removes all breakpoints from the controlle
WRONG expectation.
Just click on the "remove all breakpoints" or reprogram the chip.

Thanks for pointing me - that's always the point with expectations - very often they ARE wrong :D.