AS 6.1ß / Dragon no debugging

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

I cannot debug anymore after upgrading to AS 6.1ß

As expected, the Dragon frimware was upgraded, but I cannot do any debugging at the moment.

Reading JTAG ID and programming fuses seems okay,

but hitting F10 only gives me the following error message:
18:50:08: [ERROR] , ModuleName: TCF (TCF command: StackTrace:getChildren failed.)
18:53:04: [ERROR] Invalid context Mk2_5,, ModuleName: TCF (TCF command: Tool:tearDownTool failed.)

My project is definitively set to "AVR Dragon" with only 376kHz.
I wonder the "Mk2_5" in the error message

I program like a man:
COPY CON: > firmware.hex

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

Try rebooting. I had problems with JTAGICEmkII. It worked after I installed THEN rebooted. (sadly the 6.1 installer doesn't force a reboot even though it seems to be necessary).

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

Quote:

(sadly the 6.1 installer doesn't force a reboot even though it seems to be necessary).

It shouldn't be, since I upgrade all the time and never reboot - perhaps you had a strange setup or something, or your Virtual Box environment's USB stack got confused somehow.

Make sure you power cycle your tool after an upgrade.

- Dean :twisted:

Make Atmel Studio better with my free extensions. Open source and feedback welcome!

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

I tried the same with my JTAGICE mk II. It works, but I get always these errors when stopping the DEBUG session:
09:22:43: [ERROR] Invalid context Mk2_2,, ModuleName: TCF (TCF command: Tool:tearDownTool failed.)
Seems that Mk2_x is counting up each session

I program like a man:
COPY CON: > firmware.hex

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

I use 6.1B with dragon & 1Wire debug on tiny25 and working find...
Thierry

Thierry Pottier

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

I'm having the same problem. I can no longer debug using AVR Dragon and get the same error:
[ERROR] Invalid context Mk2_12,, ModuleName: TCF (TCF command: Tool:tearDownTool failed.)

I also get the following error:
Error: An unknown emulator error occurred. Debugger command leaveProgMode failed.

I updated the Dragon firmware as instructed and have tested this on 2 Dragons, both give exactly the same error.

Is there any way in AS6.1 to force update or at least version check the Dragon firmware ? I cannot find any option.

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

I was asked to update the firmware when doing the first debugging/programming attempt.

The process was the same for Drafon and for my MkII.
Nevertheless MkII works (for most of the time) while Dragon is not working as expected.

I program like a man:
COPY CON: > firmware.hex

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

Quote:

Is there any way in AS6.1 to force update or at least version check the Dragon firmware ? I cannot find any option.

Go to View->Available Tools. Find the dragon and right click and select upgrade.

The Dragon firmware in 6.1 beta is 7.1e (can be found by using the tool information tab in the programming dialog.

Just to make sure, disconnect and reconnect the dragon after a firmware upgrade and try again.

:: Morten

 

(yes, I work for Atmel, yes, I do this in my spare time, now stop sending PMs)

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

update:

I uninstalled everything related to Atmel, including the Jungo Windriver from the device manager. Then I re-installed Atmel Studio 6.1B (including restarts) and still got exactly the same error and cannot use the Dragon for debugging.

Finally I uninstalled everything once again, installed Atmel Studio 6.0 and the Dragon is now working fine again.

So there definitely seem to be some compatibility issue between AS6.1B and the AVR Dragon.

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

Is this a know issue with 6.1 and Dragon?

 

I can usually get it to work, but it takes what seems fooling with a lot of random things--sometimes I have to use a different project on the same hardware then things start working again.

 

Is there an exact step by step process on what should work to enter-exit-enter debugWire mode?  Nothing seems to work consistently, but sometimes it does.

 

Thanks,

 

Dave Thomas