JTAGIDE MkII not working with Studio 5

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

Hi All

I can program the AVR32 (UCA0512) with "avr32program" without any problems, but no chance of doing anything from Studio 5. The following is the error message:

Quote:
Unable to enter programming mode. Please verify that the programmer is correctly attached to the target and that target power has been switched on. Also verify that the correct device and interface settings have been specified.

The settings are all correct (the Jtag is recognised and its serial number is displayed normally) and the target voltage can be read.

In the output window the following additional information is given when trying to read the device's ID:

Quote:
23:44:15.646: [ERROR] Programming session setup failed: setParameter failed:
An unknown emulator error occured.
# JtagIceMkiiProtocol::assertResponse(): setParameter failed:
# An unknown emulator error occured.
# setParameter failed:
# An unknown emulator error occured.

Windows 7 - 32 bit.

AVR Studio 5 - release (not Beta). Disabling Firewall has no effect.

Any ideas??

Regards

Mark

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

This is an issue we have had reports on and is looking into.

Try this:

Enable the Use External Reset box either in the Programming Dialog or on the Debugging tab for Project Properties. If it does not work at once, try powering both the JtagMkII and the target on/off.

Lars K

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

Hi Lars

Thanks. I had already tried configurung the external reset option but couldn't detect any difference in operation. I also have just tried with a second JTAGICE several times; also powering board and JTAG down between attempts and setting changes, but the result remains the same.

What I have noticed is that, although the "avr32program" still works fine it looks as though the Studio 5 installation has also stopped AVR32 Studio 3/4 from being able to detect the JTAGICEs - when I scan for targets it doesn't find them anymore...;-( (this is with Studio 5 stopped)

What I then did was install Studio 5 on a Vista PC. From this PC I was never able to debug with AVR32 studio 3/4 (I gave up after many weeks of trying and moved to a Windows 7 computer at the time).

Unfortunately, although the JTAGMKII is seen in the device manager (under Jungo as JTAGICE mkII) Studio 5 can't see it, so this attempt didn't result in any progress.

So the state of affairs is:
- Studio 5 is a great editor and can build the projects (although it is much slower than just building with an external bat file)
- The newer GCC compiler packaged with Studio 5 is not as good as older GCC versions (it crashes with optimisation in some files and the TFT graphics in a reference project are distorted when comiled with this version - they are correct when compiled with the older versiona or with IAR)
- The generated code can be loaded reliably with "avr32program" and runs
- Studio 5 on Windows 7 can see the JTAGICE MKII but fails to be able to work with it (no loading and no debugging)
- Studio 5 on Vista can't see the JTAGICE MKII at all

Regards

Mark

P.S: I have been tring to work with AVR32 Studio for two years now but still no luck in actually doing anything productive with it (4 x JTAGICE MKIIs tried, three Windows OSs tried). Windows 7 came the closest with AVR Studio 3/4 but was not really that usable (printf type debugging still tended to be faster than trying to work with the debugger). Studio 5 looks to be the best effort to date but now the debugger has broken on my machines - there must be a lot of luck involved somewhere which I am simply missing...;-)

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

Do the Tools Firmware Upgrade (available under the Tools menu) detect the JTAGICE mkII? If so try to upgrade. Make sure the Force Upgrade is enabled, and try it even if it says Up to Date.

Lars K

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

Lars

With Studio 5 Beta the firmware upgrader was saying that the tools had the latest versions and didn't need to be updated.

With Studio 5 release I get the message "No tool is connected, please connect your tool and press the Refresh button". This means that I can't force an update because it doesn't get that far.

This is in fact consistent with the fact that I noticed that AVR32 Studio 4 was no longer finding any connected debuggers when scanning (after installing Studio 5).

However the AVR programming tool sees the JTAGICE "JTAGICE MkII 070000000CD5" and can read the board voltage - but nothing else.

I tried deinstalling the JTAGICE MKII driver and reinstalling it but this didn't change anything.

"avr32program" still works perfectly.

Note that I have 4 x JTAGICE MkIIs and 6 EVKs and they all behave the same so it is certainly at the PC. It seems as though Studio 5 killed the operation for itself and Studio 4 but didn't affect anything with "avr32program". It did this on Windows 7 and Windows Vista PCs.

Are there some special requirements for the Windows PC? I assume that it does work for some people? I work with laptops and not desktops. As mentioned before, also Studio 3/4 never could debug on a laptop before Windows 7 - but could on an old XP desktop. Still seems that there is some luck involved, which I just don't have...;-)

Regards

Mark

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

To be sure you have all Jungo files needed, try to install the AVR Jungo USB Installer. It can be found here:

http://www.atmel.no/beta_ware/

(it is not beta, but the same included in AVRStudio5 installation)

Lars K

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

Lars

You have made my day (in fact this is the best news in two years of trying to work with AVR32 Studio !!!)

I downloaded the package and performed a "repair".

When this was complete I started Studio 5. When Studio 5 opened it stopped and gave a warning that the Jungo installation hadn't completed sucessfully. But, rather than tell it to reinstall, I ignored the message.

Now Studio 5 detected the JTAGICE MkII that was connected and I could upgrade the firmware.

Then I could download code to the target and debug!!!

I didn't do much with it just yet but the feel was good. It is not as slow as AVR32 Studio (Eclipse) - that was just so sluggish that it was hardly usable. In fact just like a real debugger ;-)

I will need a few moments to get over the shock of being able to do what looks like real work with this. Once I have recovered, there are two new projects here (UC3A and UC3C) that may well get the Studio 5 treatment after all!!!!!!!

Thanks again

Regards

Mark

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

I have similar problem and this solution unfortunately is not working.

https://www.avrfreaks.net/index.p...

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

same here!

AVR Dragon, JTAG cable, Xplained UC3-A3, Windows 7, AVR Studio 5.0.1163, AVR Jungo USB installed, firmware reportedly successfully upgraded...

everything except reading target voltage fails
any ideas how to proceed...?

[ERROR] Programming session setup failed: TCF command: Device:startSession failed:  Code:1 ,Service:Device ,Message from peer:setDeviceData failed:
An unknown emulator error occured.
# An unknown emulator error occured.
# Second attempt to setup JTAG mode. Applying external reset
# JtagIceMkiiProtocol::assertResponse(): setParameter failed:
# An unknown emulator error occured.
# Second attempt to setup JTAG mode failed.
# JtagIceMkiiProtocol::assertResponse(): setDeviceData failed:
# An unknown emulator error occured.
# setDeviceData failed:
# An unknown emulator error occured.
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hi

After using AVR32 Studio 5 on a Windows 32 bit machine for some time now I can confirm that it is useable for real work. In my opinion it is a big improvement on the AVR32 Studio 4 (and older based on Eclipse) - in my experience, and those experiences of several other AVR32 developers I am in contact with who have been professionally developping AVR32 projects, AVR32 Studio 4 was rarely actually used for more than burning FLASH - most projects fell-back to printf() type debugging since it proved more productive than fighting with the debugger - which only actually worked on a few Windows based installations (seemingly randomly) but was so instable that it still was not of any real use.

However AVR32 Studio 5 is not yet perfect. I am also concerned that it doesn't always work as shown by the following example.

1) Me and a developer collegue were sitting next to each other, each with an EVK1105 board and a MkII debugger, using Windows 7 (one a 32 bit version and one a 64 bit version) and AVR32 Studio 5 - compiling the same project.

I could load code and debug. My collegue couldn't - there was an error suggesting that he verified that the HW was correctly connected and powered.

Jungo 64 bit drivers were upgraded to be sure - as was the MkII debugger SW but no success.

So, out of desparation, we swapped MkII debuggers.

Now both of us could load code and debug. I kept his debugger and he kept mine - we are both happy, but it suggests that there is something delicate between the PC and debugger...

2) When working with more that 1 debugger (that is swapping from one to another) the old one's ID keeps appearing as the one that AVR32 Studio 5 is trying to use, which fails of course. It is quite difficult to force it to use the correct one - the best technique that was found was to switch over to the AVR32 simulator and then back, which allowed the correct one to be selected again (for one debugging session before it fell back to the incorrect one again). Not a big problem but could be improved;-)

Some personal advice - not necessarily representing AVR32 users generally:

1) -(Professional, Windows based) Developers who want to stay with the Eclipsed based versions (eg. AVR32 Studio 4) but who just can't get its debugger to work could try the ATOLLIC version [http://www.atollic.com/]. This seems to work 'out-of-the-box' - I think it costs about €1'000 but would be a good investment for people who need something to work more streamlined, with (supposedly) good support. I remember suggestions that Atollic were taking over the AVR32 Studio 4 development from ATMEL - don't know whether there is any base to this though.

2) - For real trouble-free professional work IAR knocks spots off any of the free, or Eclipse based tools for Windows users. It may be a big investment for some but could be well worth it for companies interested in getting projects completed rather than occupying their employees with battling with tools.

3) - Once the AVR32 Studio 5 initial hurdles are overcome I am convinced that it will in fact prove to be a suitably powerful solution for the majority of hobby and professional users!!

Regards

Mark

www.uTasker.com

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

Quote:
) When working with more that 1 debugger (that is swapping from one to another) the old one's ID keeps appearing as the one that AVR32 Studio 5 is trying to use, which fails of course. It is quite difficult to force it to use the correct one - the best technique that was found was to switch over to the AVR32 simulator and then back, which allowed the correct one to be selected again (for one debugging session before it fell back to the incorrect one again). Not a big problem but could be improved;-)

Hi Mark, After seeing this thread i guess AS5 developers will take all these issues into account and solve it as soon as possible :-)

-Krishna Balan S

-------------------------------------------------------------------------

"Heroes are ordinary people with extraordinary commitment"