Jtagice3 not working after upgrade

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

Upgraded AS6.1 to the just released version.

The firmware for the Jtagice3 was upgraded.

Windows XP can't find the driver.

The Jtagice3 can program but not debug.

In hardware manager it shows "JTAGICE3 Data Gateway" with yellow question mark. Driver not installed. I can't find the driver.

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

Somehow similar picture here: Win7/64bit and hardware manager can't assign a driver for "JTAGICE3 Data Gateway". However I was able to assign a driver manually; picked "Jungo/JTAGICE3".

Didn't check the function in all detail, but I'm able to load and debug code on ATmega via JTAG.

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

Ignore the data gateway, it's not needed for programming and debugging. The new JTAG firmware should create a new HID device for the program and debug channel.

- Dean :twisted:

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

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

I reinstall all Atmel software. IE. I deleted all and then reinstalled the download.

Initially, device manager still showed the "Jtagice3 Data Gateway" with yellow "?". In AS6 same symptoms, that is could program, but not debug.

Went to the "add hardware" in the control panel and the wizard found a driver for "Jtagice3 Data Gateway". Install the driver. Now in device manager the Jungo driver shows up and no more "Jtageice3 Data Gateway".

However, in AS6 still have the same symptoms. Can program, but not debug. Same error as before. Note I am trying to debug a ATmega328p with Debugwire. Always worked before the upgrade.

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

If you don't intend to use SAM D20 with your Jtagice3, and the new firmware is causing trouble, one option is to downgrade your Jtagice3 to the old v2 firmware again, using this firmware tool:
http://www.filedropper.com/atmelatfwsetup-61133
MD5:1d278f8bb958e688a61839f7a615b8fd
SHA1:ec45e001e3b4348c299b39375a72ddcdce5557d0

After you install the tool, you will find a new entry "Downgrade connected JTAGICE3 to Firmware V2" on your start menu. Connect you Jtagice3, and select this entry.

To prevent AS6.1.2730 from upgrading your Jtagice3 again, you will have to replace
[program files]\Atmel\Atmel Studio 6.1\tools\JTAGICE3\jtagice3_fw.zip
with
[program files]\Atmel\AtmelAtfw\jtagice3_fwv2.zip
Rename the zip to match the original name (remove v2 from the file name).

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

Thanks for the quick reply. Made things worse. I notice that the version of the driver is 10.1 and on my unupgraded system it is 11.0.

That said, I still get the same error when trying to debug in AS6, however now I cannot program either.

I get the same errors on my unupgraded system.

I followed your directions. From the windows start menu "Atmel > downgrade ..."

the command window opened and got the output identifying my JTAGICE3, then the MCU upgrade line.

recap:

Now debugging with debugWIRE doesn't work, on the upgraded system or the unupgraded system.

Also now I programming does not work on either system.

so something did change :?

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

I removed all ATMEL software and reinstalled AS6SP2. The JTAGICE3 FW was upgraded and I can program but not debug with debugWIRE.

I notice that the driver name has changed from JTAGICE3 to WinDriver. Also the "JTAGICE3 Data Gateway" entry didnot appear.

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

Just tested with ATmega328P and an upgraded Jtagice3 on AS6.1 SP2. For some reason the DWEN is not set automatically when I try to launch, but is triggered by the "Start Without Debugging" (Ctrl+Alt+F5) command. Now, when I toggle power on the target and start debugging (F5) it works as expected.

For the downgraded Jtagice3 and SP2 (following the procedure described above), the same is true.

Side note: If you want to upgrade your Jtagice3 again after downgrading as described, just replace the v2 version of the firmware
[program files]\Atmel\Atmel Studio 6.1\tools\JTAGICE3\jtagice3_fw.zip
with the v3 firmware found under
[program files]\Atmel\Atmel Studio 6.1\tools\JTAGICE3PLUS\jtagice3_fw.zip

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

I tried "start without debugging". It worked one time. The next time I cannot debug with debugWIRE nor program with the JTAGICE3.

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

Now able to debug and program. JTAGICE3 on Windows XP using AS6 SP2.
1. Rebuild solution.
2. Delete all breakpoints.
3. Select from Debug dropdown menu, "Start without debugging. (should ask to toggle power on target).
4. Select from Debug dropdown menu, "Start debugging and break".
.....................
Seems to behave as previous to SP2
.....................
5. Select from Debug dropdown menu "Disable debugWIRE and close".

With debugWIRE disabled, I am able to program the device.

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

Original problem is back. Now on two machines. Windows XP. Jungo driver seems to be install correctly. the JTAGICE3 can't debug or program. See attached error messages.

The "start without debugging" doesn't help.

Attachment(s): 

  • 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...

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

Bumping this as firmware downgrade of JtagIce3 is now required to have the JtagIce3 work on Windows 8.1 computers.

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

I have jtag3 working with windows 8.1.one issue I found was if I close a debug session and open a second solution and try to connect I get an error message that the jtag3 cant be found. A reboot doesn't fix. Only fix is to uninstall usb driver then reinstall then all is good

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

How do you downgrade the firmware? The link posted above doesn't work anymore.

This really ****ing sucks. What a waste of time.

Edit: For my non-working JTAGICE3, this worked:

1) Install this: http://gallery.atmel.com/Products/Details/30543dd1-3e5b-4b2d-943a-8e53a5ab9d33?

2) Install this: http://gallery.atmel.com/Products/Details/c578bdc7-3f6a-4ff1-b2c1-8419ba25dce7

3) Open a command prompt and cd to "C:\Program Files (x86)\Atmel\AtmelAtfw"

4) Run this command: atfw.exe -t jtagice3 -a jtagice3_fwv2.zip

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

bandtank, No Tool is found with the yellow exclamation mark.

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

cralx2k wrote:
bandtank, No Tool is found with the yellow exclamation mark.

I don't understand what you mean. Can you post a screen shot or a more concise description?

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

Uploaded with ImageShack.us

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

You're going to have to provide a lot more information if you want help. I can't debug your issue if you literally tell me nothing except it doesn't work.

Which steps did you follow?
What else is in that directory?

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

Here are what i have tried so far:

- Installed AtmelUSB (new version 11.8) driver manually and flash the JTAGICE3 with firmware version 2.

- Flashed the JTAGICE3 with firmware version 2.15 and reinstalled AVR studio 6.1.

- I have removed all USB from my desktop to make no conflicts in device manage.

I don't know what I have to do now to get the JTAGICE3 working in windows 7 bits

http://img593.imageshack.us/img593/599/1ygy.png

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

My Win7/32bit and hardware manager can't assign a driver for "JTAGICE3 Data Gateway" too.

But I was able to erase/program code on AT90CAN128 via JTAG or ISP.

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

Quote:

My Win7/32bit and hardware manager can't assign a driver for "JTAGICE3 Data Gateway" too.

And that is perfectly OK, the JTAGICE3 version 3 is a composit device, and the debug and program is done over HID, not over the Data Gateway interface.

:: Morten

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

I'm in the same situation. atfw.exe give me the error "No Tool is found", but the JTAGICE3 is really connected.

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

How do you downgrade the firmware?

1) Open JTAGICE3 case and - BLDR short.

2) Run firmware download : avrfwupgrade or atfw

3) BLDR open.

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

I've been having all the problems described in this thread after updating to the latest AS6 today.

I have some additional problems.

When I start debugging, the EEPROM is not being written.
Perhaps there is a setting that was cleared after the update? Or maybe another bug?

I tried downgrading the firmware on the JTAGICE3, I tried using the new drivers described in the sticky post, but the problem persists.

The EEPROM file is being generated correctly, and the map file shows the EEPROM variables.

And another problem in AS6, on the Solution Explorer, I can no longer view the Dependencies, and Output Files. Nothing happens when double clicking these items in the project tree.

Another thing, if I leave the firmware downgraded, then I can't use the "Device Programming" function, if the firmware is not the latest, it will not let me program a chip unless it upgrades.

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

Everything works using the JTAGICE mkII. Good thing I didn't sell it. My JTAGICE3 will be waiting until the next AS6 update. :(

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

An firmware upgrade to 3.8 or higher is cause of this behaviour: http://www.atmel.com/webdoc/jtagice3/jtagice3.whats_new.html
The Product ID has changed from 0x2110 to 0x2140: http://savannah.nongnu.org/bugs/?40615

So Atmel Studio >= 6.1 SP2 (build 2730) has to be installed. Older versions don't support this new firmware.

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

I have Atmel Studio 6 version 6.2.1.1152 installed which also upgraded the JTAGICE3, but I am not sure what it was upgraded to. I can use the programmer to read the chip ID, but can't debug via JTAG. It loads to about 95% and then dies. You have to unplug/plug the USB cable to get the JTAGICE3 to respond again. It seems that >= 6.1 SP2 is not sufficient in my case ...

Do I need to dump 6.2 and go back to 6.1 SP2? (JTAGICE2 works just fine ...) Other suggestions?

Thanks

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

Downgrade tool for the jtagice3 : https://gallery.atmel.com/Products/Details/c578bdc7-3f6a-4ff1-b2c1-8419ba25dce7

Remember to read the text to avoid it being automatically upgraded by studio after downgrade.

(and, I'll delete your comment from the sticky post, as it has nothing to do with this, so that we avoid a crosspost)

:: Morten

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

az10sbum wrote:

I have a problem with JTAGICE3 with 6.2, but we are not using an ARM. We are using an atmega2560. I can plug the JTAGICE3 in as read the device ID, but debugging fails (freezes) after loading about 95% of the program. It never breaks at the first line and the JTAGICE3 must be unplugged to un-freeze it. Is this related to the dll issue or is that only for ARMS? (I don't have access to the computer until tomorrow so I can't check for the dlls now.)

reomved from http://www.avrfreaks.net/index.php?name=PNphpBB2&file=viewtopic&t=144425&start=0&postdays=0&postorder=asc&highlight=

:: Morten

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

meolsen wrote:
(and, I'll delete your comment from the sticky post, as it has nothing to do with this, so that we avoid a crosspost)

Thanks -- sorry about that.

I thought this might be different or a driver issue since others had found that the problem was fixed in revisions greater than 6.1 SP2 and I have 6.2.1.1152. I will try it when I get in this morning.

Dave

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

I am thinking this is a different issue. 6.2.1.1153 doesn't seem to work with a downgraded JTAGICE3 at all. I am going to post this as a new topic.

Thanks

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

I just automatically upgraded my JTAGICE3 to firmware: 2.15 and now I can not read my device.

I'm sure that all my connections are properly made.

My target voltage is 4.8V. What is going on?

Very Respectfully,

ΣςLϓPΖΣ