Jtagice3 not working after upgrade

42 posts / 0 new
Last post
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I got the JTAGICE3 to work in debugWIRE mode again. Started the debugger with "Start without debugging". When the error message appeared I toggled the power on the target. Then started debugging with the "Start debugging and break" option. Note the error message was not the one that asks the operator to toggle the target.

Also on close, I got the attached error messages in the background agent window

Attachment(s): 

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

I got the same problem.
Did anyone find a solutions?

Timestamp: 2013-09-03 12:15:50.116
Severity: ERROR
ComponentId: 20100
StatusCode: 131107
ModuleName: TCF (TCF command: Processes:launch failed.)

debugWIRE physical error. Debugger command Activate physical failed.

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

I tried the suggested solution, ie. downgrade the JTAGICE3, but it didn't seem to work reliably.

I went back to 6.1 build 2562 (tmel Studio 6.1 (build 2562) Installer) from the Studio Archive. I would have gone to Atmel Studio 6.1 update 1.1 (build 2674) Installer, but the file was corrupted.

This seems to work for me. I can debug ATmega328P using DebugWIRE and ATmega2560 using JTAG.

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

I just checked and Atmel Studio 6.1 update 1.1 (build 2674) Installer looks ok. So I will upgrade soon.

Thanks Kevin

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

2674 is not the latest version, 2730 is.

 

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

Yes, I think if you would read from the beginning you would see that I originally upgraded to AS6sp2, or build 2730. For some reason, my JTAGICE3 did not work correctly. Note that AS6 changed, firware for the JTAGICE3 changed as did the windows xp drivers for the usb connection to the JTAGICE3. A downgrade to earlier firmware for the JTAGICE3 was recommended. I tried that, but still had numerous issues. I then downgraded AS6 to build 2562 and am working again. I would have gone to build 2674, but the file for the installer version was corrupted. This has since been fixed and I will go to build 2674 soon since I didn't have problems with that build before.

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

Hi guys,

I'm more or less into the same situation I got JTAGICE3 Data Gateway issue in Device Manager, after a firmware upgrade...is there a know, tested and working solution for this issue?

Thanks,
Mircea.

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

Quote:
is there a know, tested and working solution for this issue?

Not that I know of.

I cleaned the registry on a XP machine (all Atmel and Avr references) and reinstalled AS6.1 SP2. Now works with DebugWIRE and an ATmega328P. Also the simulator works. Still cannot query the JTAGICE3 to get the version number. I upgraded the JTAGICE3 to version 3.

Didn't try JTAG again.

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

This got my JTAG sort of working with SP2 http://www.avrfreaks.net/index.php?name=PNphpBB2&file=viewtopic&t=136608

The issue is still with Atmel to be resolved but probably not untill a new SP is released.

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

I had the same issue with my JTAGICE3 when I upgraded to the newest version of Atmel Studio on an XP SP2 machine. I also got the "JTAGICE3 Data Gateway" with the yellow exclamation mark. So I had to downgrade the JTAGICE3 firmware back to 2.C. Then I uninstalled the latest version of Atmel Studio, and installed the older Atmel Studio 6.0.1996 SP2 version. Only then did Atmel Studio recognize the JTAGICE3.
This is most frustrating. I wonder why Atmel hasn't done more testing to make sure this is bulletproof. What surprises me the most is that it is always possible to re-program the firmware on the JTAGICE3, so they must be using some sort of fairly reliable USB protocol for that task. Why can't they do the same for programming and debugging?
Oh well...

Pages