Latest Studio won't use my JTAGICE2

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

My Studio 6.0.1882 uses my JTAGICE2, but Studio 6.1.2440 won't use it. Does this mean I should buy a JTAGICE3?

Attachment(s): 

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

Have you done any firmware upgrade between 6.0 and 6.1?

What hardware revisions are Studio 6.1 reporting (choose jtag interface to get to the tool page)

:: Morten

 

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

 

The postings on this site are my own and do not represent Microchip’s positions, strategies, or opinions.

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

Steve, what's the serial number printed on the bottom of the JTAG-ICE MKII? That error would indicate that Studio thinks you have a first revision unit, which (physically) can't do PDI. Knowing the serial would help Morten figure out if it could be incorrectly tripping the hardware revision sanity checks.

- Dean :twisted:

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

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

Image of how the hardware revision serial should look like is shown at http://www.atmel.no/webdoc/jtagicemkii/jtagicemkii.introduction_hardware_revisions.html

:: Morten

 

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

 

The postings on this site are my own and do not represent Microchip’s positions, strategies, or opinions.

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

Never mind, I'm blind and forgot the serial number is shown in the first screenshot on the working installation.

- Dean :twisted:

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

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

Do you have a more verbose log in the output window below?

:: Morten

 

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

 

The postings on this site are my own and do not represent Microchip’s positions, strategies, or opinions.

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

And, just a hunch;

Can you use the mk2 and pdi outside of the programming dialog? E.g. starting a debug session?

:: Morten

 

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

 

The postings on this site are my own and do not represent Microchip’s positions, strategies, or opinions.

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

meolson, the serial number is shown on the first attachment of my original post. The sticker on the bottom also has what looks like a date. 20070706

The only firmware update I can think of occurred the first time I connected it to Atmel Studio 5. Maybe it also happened the first time I used it with Studio 6.0, I don't remember.

The link you posted shows two stickers on revision 1. My device only has the first sticker. I don't have the smaller sticker with FC and CE. The link says revision 1 has a green light that turns on when plugged into USB. Wrong, mine has a green light that turns on when the target it is connected to is powered on.

The link says revision 1 is ROHS compliant. I bought mine several years ago from Arrow Electronics that was selling them for half the regular price. My guess is the low price was because it is not ROHS compliant. The box it came in has a sticker that says "NOT RoHS COMP". The box contains a xeroxed sheet that says Version 1.00.

My JTAGICE2 does support PDI.

Attachment(s): 

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

And are you able to launch a debug session over pdi?

:: Morten

 

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

 

The postings on this site are my own and do not represent Microchip’s positions, strategies, or opinions.

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

meolsen wrote:
Do you have a more verbose log in the output window below?
I get this popup window first. When I close it, I get the "hardware revision does not support ..." popup I attached in my first post. That is all I get.

Attachment(s): 

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

meolsen wrote:
And, just a hunch;

Can you use the mk2 and pdi outside of the programming dialog? E.g. starting a debug session?

I don't think so. I can debug, but I think it is always with the simulator.

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

Ah, if it can't connect to the tool, then all bets are off. Try a firmware upgrade, as it sounds like either the firmware is corrupt/old or your USB driver installation isn't quite right.

- Dean :twisted:

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

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

abcminiuser wrote:
Ah, if it can't connect to the tool, then all bets are off.
It must connect a little bit because it reports the serial number.

Quote:
Try a firmware upgrade, as it sounds like either the firmware is corrupt/old or your USB driver installation isn't quite right.

- Dean :twisted:

How do I do a firmware upgrade?

The firmware is okay when I run Studio 6.0. on another Win7 installation. See the first attachment in this thread.

The Jungo driver is a newer version on my Studio 6.1 installation. Maybe that is the difference. Maybe I could somehow try using the old Jungo driver.

Attachment(s): 

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

I've got an A-series ICEmkII (A0000000948 in fact). Let me try that with 6.1 and report back...

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

Quote:

How do I do a firmware upgrade?

The firmware is okay when I run Studio 6.0. on another Win7 installation. See the first attachment in this thread.

There is definitely a newer JTAG ICE MKII firmware inside Atmel Studio 6.1, so you should have been asked to upgrade it the first time you tried to connect to it. You can trigger an upgrade by opening the Tools window (View->Available Atmel Tools) right-clicking your JTAG-ICE MKII and clicking the "Upgrade..." menu item.

- Dean :twisted:

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

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

abcminiuser wrote:
There is definitely a newer JTAG ICE MKII firmware inside Atmel Studio 6.1, so you should have been asked to upgrade it the first time you tried to connect to it. You can trigger an upgrade by opening the Tools window (View->Available Atmel Tools) right-clicking your JTAG-ICE MKII and clicking the "Upgrade..." menu item.
I tried it and I got an error. I guess I should try uninstalling Studio 6.1 and then re-installing.

Attachment(s): 

Last Edited: Tue. Mar 5, 2013 - 10:10 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Are you by any chance using a USB hub between your mk2 and pc? Or are you running Atmel Studio on a virtual pc?

Also, try to check that you have the latest USB drivers for your chipset

:: Morten

 

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

 

The postings on this site are my own and do not represent Microchip’s positions, strategies, or opinions.

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

meolsen wrote:
Are you by any chance using a USB hub between your mk2 and pc? Or are you running Atmel Studio on a virtual pc?

Also, try to check that you have the latest USB drivers for your chipset

No hub and no virtual pc.

I will check for the latest USB drivers now.

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

I have the latest USB drivers.

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

Oh dear. I connected to JTAGICEmkII and 6.1 said 7.1d firmware needed to be upgraded to 7.21 so I let that occur. Now when I try to debug I get...

Attachment(s): 

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

If I now go back to 6.0 SP2 (thank Goodness I kept it!) and attempt to start debugging then it's using the same USB driver that 6.1 installed, the same firmware that 6.1 installed (it did not say it needed to downgrade as I was expecting?) but debugging works.

So there's clearly something screwy in the 6.1 Beta support for JTAGICEmkII and it's not the ICE firmware or the USB driver.

BTW I am using Win XP SP3 inside a VirtualBox VM on a Linux host - but this is a setup that works very successfully with 6.0 SP2.

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

I got mine working. I uninstalled 6.1 and then reinstalled. Studio 6.1 updated the firmware and works okay.

When I reinstalled, I put it in the usual "Program Files (x86)" folder. Originally I installed elsewhere, actually in another partition.

Maybe it needs to be in the usual "Program Files (x86)" location, or maybe it just needed a reinstall because the first one screwed up.

I'm sorry for all the trouble I caused.

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

clawson wrote:
If I now go back to 6.0 SP2 (thank Goodness I kept it!) and attempt to start debugging then it's using the same USB driver that 6.1 installed, the same firmware that 6.1 installed (it did not say it needed to downgrade as I was expecting?)
That doesn't surprise me. After upgrading the JTAGICE2 firmware for Studio 5, I could still use it with Studio 4.

I get the feeling there is no going back to earlier firmware, and no reason to do it.

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

I don't believe the communication protocol in the JTAG MKII is changing, it's just compatibility and bug fixes.

Cliff: I'm using my JTAG-ICE MKII just fine with it, so I suspect it's the USB driver installation on your PC. Can you try a repair install of the USB driver?

- Dean :twisted:

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

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

Quote:

Can you try a repair install of the USB driver?


I'll try but can you explain how it is that it works with 6.0SP2 and not 6.1Beta?

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

Silly question but doe the 430MB download file actually contain USB drivers? I cannot see any sign of .sys or .inf files in the 6.1 installation.

Like Steve's picture above my "Windriver" is that later version but there's also an entry under Jungo for JTAGICEmkII and the data/version shown on that is 02/09/2009 and 10.1.1.0 which sounds hugely out of date but maybe this is just "stable" and never changes?

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

Quote:

Silly question but doe the 430MB download file actually contain USB drivers? I cannot see any sign of .sys or .inf files in the 6.1 installation.

C:\Program Files (x86)\Atmel\AVR Jungo USB

Quote:

Like Steve's picture above my "Windriver" is that later version but there's also an entry under Jungo for JTAGICEmkII and the data/version shown on that is 02/09/2009 and 10.1.1.0 which sounds hugely out of date but maybe this is just "stable" and never changes?

Same here on my working installation.

- Dean :twisted:

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

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

On my machine, under \Program Files\Atmel\ there is no "\AVR Jungo USB"\" entry. Was that supposed to be delivered/installed by AtmelStudio-6.1.2440-beta.exe

I just ran that and let it do the "repair files" thing but as far as I can see nothing changed.

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

clawson wrote:
Silly question but doe the 430MB download file actually contain USB drivers? I cannot see any sign of .sys or .inf files in the 6.1 installation.
Yes, the 430MB file does contain the USB drivers. Actually my file size is 434.653 MB.

Installing the USB stuff is a prerequisite of installing Studio 6.1. However my installation is on a clean Win7 installation that has never had Studio installed. In your case, it probably saw that the USB stuff was already installed, so it just left it alone.

My JTAGICE mkII driver is the same version and date as my Jungo WinDriver.

Attachment(s): 

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

clawson wrote:
I just ran that and let it do the "repair files" thing but as far as I can see nothing changed.
If you run the installation file and check "Remove" instead of "Repair" it will show you a list of things you can leave intact. I don't remember, but I guess one of them is the USB stuff. If you don't see that, it may be because the USB was installed by an installation of an earlier version of Studio.

If you really want to uninstall the Atmel USB, you could probably do it from ControlPanel > Uninstall a program.

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

I pinged a guru at the office with this today as I'm not in office until next monday.

He has gone through tests with both the 0 and 1 revision of the mk2 and he has not been able to trigger anything like this. The only reason he could see is a bad firmware flash the first time that lead to the instabilities.

Firmware can be updated by choosing upgrade on the device in the available tools dialog. Also, if you do not reset the mk2 (by disconnecting) then it may report incorrect data.

Quote:

On my machine, under \Program Files\Atmel\ there is no "\AVR Jungo USB"\" entry. Was that supposed to be delivered/installed by AtmelStudio-6.1.2440-beta.exe

Not neccesarily. It is checked as a dependency for the installer, but if a "similar" version is already installed then the installation of the USB drivers are skipped. This should be obvious during the installation as the USB drivers are installed using a separate installer.

:: Morten

 

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

 

The postings on this site are my own and do not represent Microchip’s positions, strategies, or opinions.

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

meolsen wrote:
He has gone through tests with both the 0 and 1 revision of the mk2 and he has not been able to trigger anything like this. The only reason he could see is a bad firmware flash the first time that lead to the instabilities.
Maybe, but the old firmware worked well for Studio 6.0.

I'm guessing it was one of the possibilities I mentioned earlier. A bad original installation or the fact that I chose not to install Studio in the suggested "Program Files (x86)" folder when I installed it the first time.

Anyway, a re-install to the suggested folder made it work.

Since I've gotten it to work, I've tried the Tools > Device Programming" thing about 15 times. It has worked every time except around the third time I tried it I got the dreaded "This hardware revision of your tool does not support this interface" popup. I've tried it a dozen times since with success. So I'm satisfied it is working, but maybe there is a bit of flakiness there yet.

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

Sounds like it... The firmware upgrade system has had a deep overhaul for 6.1 as the main crash reason in 6.0 was the old firmware upgrade system.

:: Morten

 

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

 

The postings on this site are my own and do not represent Microchip’s positions, strategies, or opinions.

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

Quote:

If you run the installation file and check "Remove"

I don't like uninstalling software. It seems like an utter failure if the only way to make something work is uninstall/reinstall.

However as far as JTAGICEmkII debugging goes it would appear that 6.1B is a complete failure so in for a penny...

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

OK so I uninstalled AS6.1 but it did not remove the USb support for ICEmkII (I figured this might be the case - I thin kit was delivered by AS4.19 or similar so it wasn't 6.1's to uninstall).

I noticed in Control Panel-Add/Remove Programs there was a separate entry for "Atmel USB" to I elected to uninstall that. (this probably means that uninstalling/reinstalling AS6.1 was not actually necessary and I could have just uninstalled "Atmel USB" then run "repair" in the AS6.1 installer which would then spot that there was no USB and offer to install it.

Anyway after all that it still would not work.

In desperation I then rebooted the XP virtual machine in case a mix of old and new USB support was still active and this time, after it restarted the JTAG debugging in AS56.1 worked.

Now I can remember the days when you'd run an installer in Windows and at the end it would always say "OK, now we must reboot to finish installation". AS6/6.1 like many modern installers (presumably trying to ape the ease of installation you find in Linux?) does not do this.

I would suggest it probably should.

(anyway I'm a happy camper again as I have ICEmkII debugging working in 6.1 now!).

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

Just another user here having JTAGICE mkII problems with the latest AS6 update. Right now, I can successfully program in the "Device Programming" window. But when I try to debug, I see the tool blinking the LEDs initially, and then AS6 seems to be in debugging mode (stop and pause buttons are enabled). But nothing happens on the target.

The problem seems to be intermittent, when I first installed AS6 6.1.2440, it didn't work. A few experiments (downgrading the firmware with AS4, then upgrading on AS6, rebooting the computer) got it to work. But today it isn't working again...

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

ganzziani wrote:
(downgrading the firmware with AS4, then upgrading on AS6, rebooting the computer) got it to work. But today it isn't working again...
Did you upgrade to AS6.1 firmware or AS6.0?

Attachment(s): 

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

Upgraded using AS6.1. My screen looks just like yours, with the exception of the debug port and the serial number.

After my post, I downgraded/upgraded the firmware again without luck, rebooted the computer, and nothing.

But today the debugger is working again.

Anyway, I need a dependable tool, I bought JTAGICE3 hoping that it will not have this problem.

Conspiracy theory: Make the old tool stop working to make people buy the new one...