Hi all. HELP !
AVR Studio can't find USB AVRISP programmer. Have tried to remove the whole program, and the reinstall.
After reinstall, plugged the USB AVRISP to the USP port. PC find AVRISP and telling "Ready to user" and in the control panel it seeem OK. BUT NO. When opening the AVR Studio, it will not find the USB priogrammer. Have just bought a new one, but stil same problem. How can it bee ??? Hope for help. :cry:
Thanks
Per
PS: Windows XP
Have a look in Device Manager - do you see the Jungo USB driver listed there and beneath the AVRISPmkII?
Hi again..Yes under Device Manager is Jungo USB driver listed there and beneath the AVRISPmkII, and driver sayes OK.
What can be wrong ?
Thaks Per
Have you tried to change the drive manually? Point it to the driver in the avr studio directory (don't remember exactly where it is, but you should be able to find it). The last time I installed it, Windows installed the wrong driver for it as well.
Hi again. Yps I have done that, so tthe driver must be the right one.
Br
Per
Hi all. Have total removed V4.17, and then reinstalled V4.15 and everythings is now OK, so there must be something with V4.17.
Have a nice weekend
Br
Per
We have seen some issues with registration of our own communication module. Locate the file scomm.dll in the AVRStudio installation, open a command window in the folder and give the command regsvr32 scomm.dll Scomm.dll handles both serial communication and communication with the jungo usb-driver.
Lars Kvenild
Atmel Norway
I'm going to make this sticky for a while so that Lars' advice remains visible for others afflicted by this.
hi,
try to reset the setting of the programmer,maybe that will be ok.
regards.
I read this thread with interest since I have been having a similar problem with AVRStudio connecting to my Dragon board. I have been running Studio 4, build 17 and have simply been unable to connect to my Dragon board over USB. I reinstalled Studio, reinstalled the Jungo driver, and finally tried running "regsvr32 SComm.dll as suggested by tech support in this thread.
=====
I uninstalled V4.17 and installed V4.16 and I can now connect to my Dragon board.
I just installed 4.18 and AVR Studio can no longer connect with my AVRISP MKII - completely locks up the program. I tried the suggestions above - nothing has worked.
I tried upgrading the firmware to the AVRISPmk2, but AVR Studio 4.18 just couldn't see the device. I uninstalled 4.18, installed 4.16, upgraded the firmware, and now I'm back in business.
I thought I was the only one with this trouble, now I realise it's endemic. I too have v4.18 Studio 4 and it refuses to connect to my AVRISP II - in fact, I can't even put it into boot mode and upgrade the firmware on the AVRISP.
I am running Windows Vista Home Premium, and Lars' advice (regsvr32 scomm.dll) does not work. It generates the Windows error 0x80070005.
Downloading the MGR tool to remedy that bug doesn't work either. Still no further forward. Next step uninstal, then go back to v4.15 or thereabouts. Atmel, what gives? Don't these releases get tested before release?
Will C
Cambridge, UK
ATMega 2560 user
Further to this, I uninstalled, downloaded v4.16 (*WHY??* do you have to register every damn time you download something, no matter how many times you've done it before?) and...
Still no joy. Studio 4 is officially incommunicado.
Will C
Thinking of migrating to a competitor's platform.... :-(
Hi,
after two days of installing and deinstalling drivers, programs,... Here are my points:
- I use XP with latest SP, Studio4, version 4.18, SP build 694
- from HW side, I use AVRISP mkII and STK600
- Device manager of XP shows USB Jungo group, WinDrv for Studio and both drivers for HW attached
- I can upgrade FW for both programmers (AVRISP, STK600)
- AVRprog, as native programer for Studio, can not find any board attached
- My project is on hold... :-(
As I can read, switching to versions prior 4.18 dont help. Or? I want to program xMega16A4.
Tnx for help,
Andrej
- AVRprog, as native programer for Studio,
Ok, I can agree, that AVRprog is not native. When I go tools/AVR prog..., I receive message window from AvrProg:
No supported board found!
AVRprog version 1.40
From this I assumed obvious mistake about AVRprog.
But fact is, that I do not receive any selection to choose from.
Andrej
give the command regsvr32 scomm.dll
In addition, I tried this registration but no success.
Please, can anyone help me with info, which version of Studio or any other programmer works with AVRISP mkII and STK600 using Xmega's?
Tnx, Andrej
Andrej,
Suggest you actually READ what John wrote. If you are using an AVRISPmkII then AVRProg is NOT, repeat NOT, the program you use to drive it. That's an old add-on program to Studio for use with really ancient programmers. The support for the AVRISPmkII is accessed via the [Connect] button on the toolbar (perhaps not surprisingly this IS what the manual says)
[continue discussion in the separate thread you started - this noise is off-topic for this sticky]
We lost three days to this but got ourselves going again by simply finding 4.15.623 from another source (not Atmel), removing 4.18, and installing the 4.15.
We also had to overnight in two new MK IIs because two were killed by trying to upgrade firmware using 4.18.
Here is the process we used:
Control Panel/Add Remove Programs
Locate Studio
Uninstall
When askd to delete or preserve user setting and prefs we choose to delete them (we did that to assure nothing stuck around that might jeopardize getting this work around going - it may not be necessary)
When that process was complete we downloaded 4.15 from
http://en.stkshop.com/download--...
and installed it.
We could not find 4.15 on the Atmel web site.
After installing 4.15 we used a new MK II. Studio provide a message indicating the firmware in it was out of date but we did not upgrade it fearing killing yet another MK II.
Comments and questions:
- Why is there not more hue and cry from people who lost time and money on this Atmel screw up? It cost our small shop three days of lost development productivity. So larger shops have other ways to program boards? Is there a better way to ISP boards during development than Studio and the Mk II? One that is stable and supported?
- This thread started nearly a year ago. Why is there not a fix to 4.latest for this problem? The MK II continues to be in production. I would venture there are tens of thousands in use. What are we missing that makes is OK for Atmel not to fix this?
Jim
hi
i cant connect to my avrisp mkii with avr studio ver16.im using win 7-64bit.may it has problem with my os? when im trying to connect this message shown"connect failed" what can i do?
Your Studio is two versions and three service packs out of date. Did it really not cross your mind to make sure that your software was up to date?
i downloaded avr studio ver.15 and installed it. but i have same problem with it.and it is up to date.whats the problem with it??
i downloaded avr studio ver.15 and installed it
I also had problems with an AVRISP mkII clone not connecting with AVRStudio V4.18 (actually it's the LUFA XplainBridge), I found some updated Jungo USB drivers on Atmel's beta site:
http://www.atmel.no/beta_ware/
Note the text description "Jungo USB installer version 10.2. This installer will fix USB connection issues with AVR Studio 4.18 SP3 and improve Windows 7 64-bit stability.". So there do seem to be issues with 4.18 connecting to AVRISPs...
Curiously this driver created an additional entry in the Jungo section in the Device Manager called 'WinDriver'. I also had an 'AVRISP mkII' entry, and AVRStudio now connects. It does seem to require both entries to work, if I disable either of them there's no connection. HTH.
Mark.
Curiously this driver created an additional entry in the Jungo section in the Device Manager called 'WinDriver'.
That's the main Jungo driver kernel. The way the Jungo drivers work is that they all use the same common driver kernel (WinDriver) for the platform, with the device specific portion loaded on top of that. You need both for it to work, and yes, the lack of the WinDriver on x64 used to cause me and other x64 users trouble when installing new tools.
- Dean :twisted:
Hi Dean!
Thanks for that explanation. Also thanks for your LUFA work, the XPLAIN Bridge project has saved me several days of development time :)
(BTW I'm the guy who made the last post in your blog about programming external xmegas with your code:
http://fourwalledcubicle.com/blog/2010/02/mein-server/).
This Jungo thing is worth mentioning on your blog I think (along with having to reset the USB chip when loading drivers which is the only other thing that caught me out), there is at least one entry that seemed to be having a similar problem.
Mark.
Help! Wasted many hours today and yesterday reinstalling.
Like others, my 4.18 SP3 installation does not find the programmer, AVRISP mkii. Where can the download v4.15 be found? It seems this is the only fix. Very frustrating.
WELL, I'M HAVING THE SAME PROBLEM WITH MY AVRISP mKll..
I GOT STUDIO 4 INSTALLED, I WAS LOOKING AT THE PLUGIN MANAGER, BUT I DON'T SEE THE mKll LISTED ON IT.
I WAS LOOKING AT THE FILES FROM ATMEL(STUDIO4), AND I FOUND OUT THAT THE FILES FOR mKll DON'T EXIST, I LOOKED EVERYWHERE, BUT CAN'T FIND THE FILES FOR ISP TO GET MY ISP WORKING... OBVIOUSLY IF I DON'T HAVE THOSE FILES IT WON'T WORK, I SEE FILES FOR DIFFERENT PROGRAMERS BUT NOT FOR mKll.
I REINSTALLED THE STUDIO4, I EVEN REINSTALLED THE JUNGO, AS IT'S MEANTIONED ON HELP FILES.. BUT NOW I SEE IF THOSE FILES FOR ISP ARE NOT THERE, IT'S NOT GONNA WORK!
SHOULD I DOWNLOAD JUST THE V.16 MENTION ABOVE?
i just downloaded the AVRjungo 10.2. but still can't get connect to my driver...
please help!! :D
HELP.
THANKS FOR YOUR HELP! :(
I did not see it mentioned in this thread that if you have LibUSB-Win32 installed then Studio won't find the AVRISP-mkII, even if you did upgrade to the latests and greatest Jungo drivers.
This may be case of whichever driver was installed first wins?
I had LibUSB-Win32 installed long ago.
I uninstalled LibUSB-Win32 and then AVRStudio was happy, however AVRDude doesn't work as it relies on the LibUSB-Win32 drivers for USB.
The WinAVR-user-manual has this to say about the issue:
LibUSB-Win32 is a USB library that is linked into AVRDUDE and AVaRICE to allow them to connect to the Atmel JTAG ICE mkII and the Atmel AVRISP mkII...AVR Studio can install and use the USB drivers from Jungo (which is included as part of the AVR Studio installation). However, the Jungo drivers and the LibUSB-Win32 drivers are mutually exclusive; if one set is installed the other set will not work.
You can uninstall the driver by plugging in the device (and making sure it is powered on), use the Device Manager to find and select the device (under Jungo or LibUSB-Win32, depending on which driver is installed), right click and select "Uninstall". Then, install the other driver according to the correct procedures.
LibUSB also has a "filter" driver that is available, however, using this is not recommended by the LibUSB author.
I'm trying to set up a station on my production floor where I need to program many different AVR's, Tiny88 and XMega128A1 among many others. As Atmel has not released the full programming specifications for the XMega [WHY?] I'm stuck using Studio4 (Studio5 has no hope of ever running on the machines supplied by our IT department, to slow and not enough RAM). Everything but the XMega based products are using AVRDude to program them.
What is the solution to getting Jungo and LibUSB to co-exist (Why should the filter driver not be used?)?
I am having a slightly different problem. I would like to use the AVRISP MKII in Studio 4 and Arduino IDE.
I can make the programmer work in one program at a time by loading the correct driver, but I cannot get it to work in both programs without unloading one of the drivers.
Jungo and LibUSB seem to be mutually exclusive. Is there a solution to getting Jungo and LibUSB to co-exist so that I can use both programs with the same programmer?
I am running AVR4 Version 4.19 & Windows7 64bit
I know the thread is old, but for those still lurking for the solution, I'll post the variant, which worked for me (including the versions of software I used).
How to get AVRISP drivers working in
AVR Studio (4.19 Build 730)
Atmel Studio (6.0.1843)
AVRDUDE (WinAVR-20100110)
on Windows (7 64bit):
1) Install AVR Studio
2) Install Atmel Studio
3) Install libusb filtered* driver
4) Unplug USB device, then plug it back (or reboot)
* libusb filtered:
libusb-win32-devel-filter-1.2.6.0.exe
http://sourceforge.net/projects/...
Note:
Other versions of the software probably would work.
Note:
Installing not filtered version of libusb "overwrites" Atmel's drivers. This happened to me and I was too lazy to reinstall the whole Atmel Studio package, so I extracted* the drivers installer (AtmelUSB.exe) from the installer and used "Repair" to install them back.
* To extract files from Atmel Studio installer:
run from command line (cmd.exe):
as6installer-6.0.1843.exe /extract_all:C:\Path_to_some_folder
SOURCEs:
Offhand comment. I had to go back to AVR Studio 4.16, for some reason AVR Studio 418 would load code, would show the files in the project, but I couldn't set break points. (And no break point on startup either)
What I found was when installing 4.16 raw on my Win7 64bit machine, something was goofed with the Jungo Drivers for both my JtagIceMkII and AVRIspMkII.
What seemed to work was to let AVR Studio 6 install the drivers, but cancel the install at that point, and then installing AVR Studio 4.16.
Can anyone help, ISP MKII gives an error "target appears to have lost power, or the ISP connector was disconected". I have connected external power supply to microchips VCC pin, and everything connected to programmer (VCC, GND, MISO, MOSI, RESET). Any suggestions?
Thank you for your answers.
Now 2014!!!
I am running Studio at home with no problem. Using the AVRISP mkII I can read and write to the board. I installed Studio on a students computer and the AVRISP is not visible! We are frustrated and have a tight timetable.
HELP
Here are the installation details
Atmel Studio 6 (Version: 6.2.1502 - Service Pack 1)
© 2014 Atmel Corp.
All rights reserved.
OS Version: Microsoft Windows NT 6.2.9200.0
Platform: Win32NT
Installed Packages: Shell VSIX manifest - 6.2
Shell VSIX manifest
Version: 6.2
Package GUID: 5aa6ea3e-da7b-48c1-9b2a-cab2329d32ac
Company: Atmel Corporation
Installed Packages: Atmel ARM GNU Toolchain - 4.8.4.1437
ARM Toolchain
Version: ARM_Toolchain_Version:4.8.4.371 GCC_VERSION:4.8.4
Package GUID: D83C9208-1D2D-4665-9760-EB9EE264CF8F
Company: Atmel
HelpUrl:
Release Description: ARM Toolchain
CMSIS
Version: 3.20
Package GUID: D83C9208-1D2D-4665-9760-EB9EE264CF8F
Company: Atmel
HelpUrl:
Release Description: ARM Support File Version
Installed Packages: AVR macro Assembler - 2.1.57.1175
AVR Assembler
Version: 2.1.57.16
Package GUID: 03CB4AE1-80EA-40C7-B561-98CC87EA539C
Company: Atmel
HelpUrl:
Release Description: AVR Assembler For 8-Bit Devices
Installed Packages: Atmel AVR (32 bit) GNU Toolchain - 3.4.2.1067
AVR Toolchain 32
Version: AVR32_Toolchain_Version:3.4.2.435 GCC_VERSION:4.4.7
Package GUID: DB6D383F-C5D9-4E7E-BBF9-F37C6EEB59FD
Company: Atmel
HelpUrl:
Release Description: AVR Toolchain For 32-Bit Devices
Installed Packages: Atmel AVR (8 bit) GNU Toolchain - 3.4.5.1061
AVR Toolchain 8 Bit
Version: AVR8_Toolchain_Version:3.4.5.1522 GCC_VERSION:4.8.1
Package GUID: 2C7AA7CF-94C6-463C-81DA-4AA03B613C3B
Company: Atmel
HelpUrl:
Release Description: AVR Toolchain For 8-Bit Devices
Installed Packages: Atmel Gallery - 1.3.1
Atmel Gallery
Version: 1.3.1
Package GUID: AtmelStudioExtensionManager
Company: Atmel
Installed Packages: Atmel Software Framework - 3.19.0.1347
ASF
Version: 3.19.0
Package GUID: 1E567EA3-6E83-4C11-8734-684F4581B25D
Company: Atmel
HelpUrl: http://asf.atmel.com/3.19.0
Release Description: ASF - 3.19.0 Release
ASF
Version: 3.18.1
Package GUID: 1E567EA3-6E83-4C11-8734-684F4581B25D
Company: Atmel
HelpUrl: http://asf.atmel.com/3.18.1
Release Description: ASF - 3.18.1 Release
ASF
Version: 3.18.0
Package GUID: 1E567EA3-6E83-4C11-8734-684F4581B25D
Company: Atmel
HelpUrl: http://asf.atmel.com/3.18.0
Release Description: ASF - 3.18.0 Release
ASF
Version: 3.17.0
Package GUID: 1E567EA3-6E83-4C11-8734-684F4581B25D
Company: Atmel
HelpUrl: http://asf.atmel.com/3.17.0
Release Description: ASF - 3.17.0 Release
ASF
Version: 3.16.0
Package GUID: 1E567EA3-6E83-4C11-8734-684F4581B25D
Company: Atmel
HelpUrl: http://asf.atmel.com/3.16.0
Release Description: ASF - 3.16.0 Release
ASF
Version: 3.15.0
Package GUID: 1E567EA3-6E83-4C11-8734-684F4581B25D
Company: Atmel
HelpUrl: http://asf.atmel.com/3.15.0
Release Description: ASF - 3.15.0 Release
ASF
Version: 3.14.0
Package GUID: 1E567EA3-6E83-4C11-8734-684F4581B25D
Company: Atmel
HelpUrl: http://asf.atmel.com/3.14.0
Release Description: ASF - 3.14.0 Release
ASF
Version: 3.13.1
Package GUID: 1E567EA3-6E83-4C11-8734-684F4581B25D
Company: Atmel
HelpUrl: http://asf.atmel.com/3.13.1
Release Description: ASF - 3.13.1 Release
ASF
Version: 3.12.1
Package GUID: 1E567EA3-6E83-4C11-8734-684F4581B25D
Company: Atmel
HelpUrl: http://asf.atmel.com/3.12.1
Release Description: ASF - 3.12.1 Release
ASF
Version: 3.11.0
Package GUID: 1E567EA3-6E83-4C11-8734-684F4581B25D
Company: Atmel
HelpUrl: http://asf.atmel.com/3.11.0
Release Description: ASF - 3.11.0 Release
ASF
Version: 3.10.1
Package GUID: 1E567EA3-6E83-4C11-8734-684F4581B25D
Company: Atmel
HelpUrl: http://asf.atmel.com/3.10.1
Release Description: ASF - 3.10.1 Release
ASF
Version: 3.9.1
Package GUID: 1E567EA3-6E83-4C11-8734-684F4581B25D
Company: Atmel
HelpUrl: http://asf.atmel.com/3.9.1
Release Description: ASF - 3.9.1 Release
ASF
Version: 3.8.1
Package GUID: 1E567EA3-6E83-4C11-8734-684F4581B25D
Company: Atmel
HelpUrl: http://asf.atmel.com/3.8.1
Release Description: ASF - 3.8.1 Release
ASF
Version: 3.7.3
Package GUID: 1E567EA3-6E83-4C11-8734-684F4581B25D
Company: Atmel
HelpUrl: http://asf.atmel.com/3.7.3
Release Description: ASF - 3.7.3 Release
ASF
Version: 3.6.0
Package GUID: 1E567EA3-6E83-4C11-8734-684F4581B25D
Company: Atmel
HelpUrl: http://asf.atmel.com/3.6.0
Release Description: ASF - 3.6.0 Release
Installed Packages: Atmel Kits - 1.7.310
Atmel Kits
Version: 1.7.310
Package GUID: B624D6C6-CB86-4887-A57F-327D248085A9
Company: Atmel
Installed Packages: AtmelToolchainProvider - 6.2.678
AtmelToolchainProvider
Version: 6.2.678
Package GUID: AtmelToolchainProvider.Atmel.0780A430-065B-4EFD-B0D1-FC957262E6DF
Company: Atmel
Installed Packages: LiveWatch - 6.2.140
LiveWatch
Version: 6.2.140
Package GUID: 07290e21-75bd-4363-8d07-a5fa8e32876e
Company: Atmel
Installed Packages: MemoryLogger - 6.2.171
MemoryLogger
Version: 6.2.171
Package GUID: 99A2A244-8218-4868-A0D1-A1683E6FCC53
Company: Atmel
Installed Packages: Percepio Trace for Atmel Studio - 1.2
Percepio Trace for Atmel Studio
Version: 1.2
Package GUID: fe274744-c496-42fc-9e52-f77b92d669b1
Company: Percepio AB
Installed Packages: Visual Assist for Atmel Studio - 10.8.2023.3
Visual Assist for Atmel Studio
Version: 10.8.2023.3
Package GUID: 7997A33C-B154-4b75-B2AC658CD58C9510
Company: Whole Tomato Software
Installed Packages: GdbConsole - 6.2.132
GdbConsole
Version: 6.2.132
Package GUID: d616f47a-811f-4a7e-bcb8-8fe696222d92
Company: Atmel
Hi all,
Do all ATmel Studio support Win 8.1?
I had some code written using AVR Studio 5, working on my laptop Win 7.
Now I need to install it into Win 8.1.
Cannot use Studio 6.2 as some of the ASF not working.
CS
I ran Atmel Studio 5 on Windows 8.1. Having said that, why would you want to run Studio 5? Unless they have done a lot of work on it, it is still full of bugs!
Studio 6.2 is a much better alternative. What issues are you having with ASF in 6.2? Perhaps we can help you overcome them.
Hi Larry,
Is that this PC is a x-64 running on Windows 8.1.
Problem with the driver.
CS
Okay CS, you need to be more specific and descriptive in your posts. First you said ASF was not working. Now you said that there is a problem with a driver.
Describe in detail what is not working and what you have tried. Then we may be able to help you.
Hi Larry,
1) I had problem with AVR Studio 5.0 code compile using ATmel Studio 6,2.
This is the one that I suspect the ASF is not compatable, or I use the wrong ASF.
As the product is on site, I not sure what other side effect will happen if I change the ASF.
The main code is not written by me.
2) Lately I install the ATmel Studio 6.2 on a new Win 8.1, x64 PC, still not working.
I had problem with the drivers, which I think is a 16-bits.
CS
CS, see this post https://www.avrfreaks.net/forum/morten-see-fail-atmel-studio62sp11502-and-atmelusbinstaller-62342-fail-windows-81.
If that is what you saw happen then it is not a real problem. The drivers did install. The installer is buggy.
Hi Larry,
The same problem or bug
cs
2) Lately I install the ATmel Studio 6.2 on a new Win 8.1, x64 PC, still not working.I had problem with the drivers, which I think is a 16-bits.
The same problem or bug
In that case the driver problem is a non-issue. The drivers are installed and working fine.
1) I had problem with AVR Studio 5.0 code compile using ATmel Studio 6,2.This is the one that I suspect the ASF is not compatable, or I use the wrong ASF.
As the product is on site, I not sure what other side effect will happen if I change the ASF.
The main code is not written by me.
As for the ASF problem, there may be some things that are slightly different in the ASF version used to originally develop the code and the newer version of ASF. What version of ASF was the program written with?
If you were to try using Atmel Studio v6.2sp1 again and then post the problems that you encounter with ASF then we could probably help you fix those problems. I am willing to help you with that.
Info from German ATMEL Support:
"Dieser Bug ist bekannt und ist bei uns unter AVRSV-6022 hinterlegt.
Der nächste Studio release (ungefähr Sept 2015) wird dieses Problem beseitigen!"
in english:
"This bug is known and has been deposited with us under AVRSV-6022.
The next studio release (approximately Sept 2015) will eliminate this problem!"
Best Rolf
I also have the same issue but with AVRISP mkII. After upgrading to windows 10, this device is no longer available as a tool in the programming menu. (JTAGICE3 still is available and working ). I've taken the same approach as most folks, Uninstall the drivers, uninstall atmel studio, clean the registry, delete all residual directories etc - all to no avail.
My situation is just a bit different. When I first installed windows 10, everything seemed to be working. They I would get intermittent times when the programmer was not visible, now it is never visible. I was hoping an upgrade to Atmel Studio 7 would fix the issue. No, same problem.
I believe my problem started when I experimented with the Arduino interface in Studio. I initially didn't like it so I deleted it. I believe that is when my issues started. Since then, I thought I might just reinstall the Arduino interface - but some how, once installed and uninstalled, you can never get it back.
The double curious thing is that none of the Arduino interfaces work any longer. the USB or the Programmer or even the ATTINY programmer. They are all recognized, but not will work with any interface.
Windows and device drivers - a joy to all and guaranteed employment to those that created that monster.
I had the same problem described by many above with Windows 10 and Studio 6.2/7.0: could not see mkII programming tool even though all drivers appeared to be installed correctly. After spending an afternoon trouble shooting with suggested driver updates and re-installs to no effect, I ran the Windows 10 system Reset and re-installed Studio 7; while a bit drastic, it worked.
ES
Just did the same thing (windows 10 system reset) and the issue did go away. Painful way to solve a problem but at least for now rhe problem is solved.
So, as I consider the leap to Win 10, is the AVR ISP mkII not working under Win 10 a generally reproducible problem that everyone is expected to encounter, or have the majority of users not had a problem with this?
I understand the two posters above found a work-around, I just wondered about what problems I might encounter...
Thanks,
JC
Hello All,
I am using the AVRISP-MKII tool for programming ATTINY828 but once the link is been setup via command prompt window then i go to the next step of programming it with micro controller.elf at that time it shows [ERROR] unable to communicate with the tool TCF error code 1 , but my hardware manger shows jungo connectivity all the time .
I am using windows 7 professional system with Atmel 7.0 with full system drivers even tried with atmel 6.2 but the result is same .
Please help me its a very important project for me & defines my career in life ahead .
Thanks ,
Ankit Agrawal
Do you see the ISPMk2 in the Available Tools view in Studio ? If not, you may be affected by a bug with Studio 7 installer.
You could try some of the workarounds detailed here https://www.avrfreaks.net/forum/a... or here #2
Dan
hi, am writing in response because I have also wasted 200 mand-days with studio. it is so bad! these issues have been going on for over 10 years. right now studio7 won't write fuses and lock bits, but does write flash and ee. studio 6.2 won't erase, but do flash or ee.
ANY atmel programming board has severe USB connectivity and programming issues, and I mean SEVERE--don't bother with any atmel programmer. uninstalling/re-installing never works, it is atmel's usb software that is corrupt and THEY WON'T FIX IT!!
Justin Mattair, www.mattairtech.com, made a USB timing fix in one day, provided a firmware update on his website, then studio had better USB connectivity. ONE DAY, in one day he fixed one issue! atmel is so ungodly stubborn. I stay with atmel becasue the xmegas are absolutely wonderful. avrdragons are only good for smashing with ahammer, literally. that is the ony way to get any pleasure from the dragons. bought 18. stk600 has never never ever worked!
I use Olimex avrisp mii and MattairTech.com ZeptoProg_II https://www.mattairtech.com/inde...$22.99 avrisp mkii, they will work better than anything else. plus it has a serial port, scope type functions, and more. all studios have severe issues, so nothing works well, but ZeptoProg_II works the best. the olimex works mostly, but it won't write the 1st 32 bytes of ee!
Hi,
I also have this problem since months now. I am using Studio 7(tried 4 and 6 previously), Win10 with JTAG ICE MK2 and have tried everything a dozen times. Clean deinstall everything and reinstalled Studio 7. Reseting windows just to resolve this is no option. If the problem occurs again the whole procedure would be usless. It would take days to get all the software installed again.
What happend to "This bug is known and has been deposited with us under AVRSV-6022. The next studio release (approximately Sept 2015) will eliminate this problem!"??? Is it forseeable that the issue will actually be resolved or is atmel incapable? I mean it is a major bug. I guess I have to switch to Pics or somtheing else that works.
Sorry but this issue is really nagging me slowy. The JTAG works on a different system so it is clearly a software problem.
So, is it going to be resolved soon or not ???
Hi Nickelgrass,
If your problem is "missing jtagice mk2 in tools dialog" , and the problem occurs again, please apply the patch procedure described here #2 . It has so far worked for 100% of folks that reported back.
Also note that this (Jungo driver) problem does not affect HID based debuggers such as the Atmel Ice
HTH,
Dan
It finally worked!!! Thank you so much!!!
Sorry i missed that post.
This worked for me! After wasting a day on it!
FYI i'm running windows 10 64bit, with now studio 7 and a JtagICE mk2.
All was working fine the other day, then suddenly yesterday when i plugged in my ICE Studio 6.2 which i was running didn't see it. It was visible in device manager and all. Plus the Ice worked on an old xp machine so i know it was not my ice. I tried updating to studio 7 / reinstalling drivers etc.
I think the issue is studio or windows chooses to wrong driver to use for the ice driver.
See link post #53 above
Thanks danv
P.S.in 2015 Christmas This problem in AS7 was fixed in build 634 with Jungo driver 12.0.
Hello. I had the same problem on Win10 and I reset my PC, but after 20~25 days, AS7 couldn't find AVRISPmkii again.
I found this Japanese page, and this solution solve the problem.
http://qiita.com/yoshihiroo/items/70357cfc3a266f1970be
Translate to English
1. Download and install the latest USB driver
2. Download and install libusb-win32-devel-filter-1.2.6.0.exe from here.
3. Launch FilterWizard and select AVRISPmkii.
I think it's better to do this solution before system reset.
I switched to windows 10 some time ago and today I wasn't able to work with my JTAGICEmkII and AVR Studio 4.
I checked in device manager and I only see a Windriver under Jungo section with an exclamation mark on it and no JTAGICEmkII driver.
I tried to uninstall avr studio 4, clean the registry and reinstall it from scratch up to v4.18 sp3, but still no luck.
If I plug the JTAGICEmkII I can't ear any usb sound and there isn't any change on the device manager window.
I need to stay on studio 4, studio 6 or 7 are not an option, also resetting windows is not an option too.
I really need to make it work, I'm stuck with my office project.
Any idea?
Plus, is there any official support channel I can contact beside this forum?
I seem to have the same problem on Windows 10. Can you please share a detailed procedure on how to overcome this problem?
I seem to have the same problem on Windows 10. Can you please share a detailed procedure on how to overcome this problem?
update your AS7, they released new drivers on last update and everything is working fine. im pretty sure there was dialog saying these drivers wont work on older versions of studio.
I solved my problem installing the latest Studio 7 and then this drivers: https://gallery.atmel.com/Produc...
With them I can now run Studio 4 for my olf JTAGICE mkII and Studio 7 for the new Atmel ICE.
I can also use the JTAGICE mkII with Studio 7, after the firmware upgrade proposed by the program at start.
I'm having these exact same issues too - only with Atmel Studio 7 and AVRDragon on Windows 10 :-/
Everything works then suddenly after a restart ATStudio wont find the dragon, even though everything is in order according to the drivers etc.
I've had it happen a few times now - solved it by totally reinstalling drivers and ATStudio the first few times, but that didn't do it last time. Fixed it last night, by finding a Jungo USB driver download for Atmel Studio 7 on the Atmel site - these drivers were a little newer than whats included in the ATStudio installer. Only time will tell if I've lost my dragon connection for the last time.
So my recommendation, go search for newer drivers on the Atmel Gallery site.
Our Win10 machine had some auto software update recently & now we find Studio 7 does not see our MK II programmer no matter what we try (uninstall, reinstall, reboot, etc)...hence no boards can be programmed. Hammering on the upper corner of the motherboard for 5 minutes gave us hope, but ended up with the same result. We may try "Dany #2" after we rest.
Hardware manager shows "the" jungo driver present & working & shows a MK II is plugged in & ready to use. Studio shows nothing available to use.
Atmel should just go back to selling rs-232 serial programmers (that always worked), until they get figure out how to make a working USB device...this has been going on for at least a year now. If there are no serial ports to plug into, at least it will be clear why it's not working/
.hence no boards can be programmed.
Oh what a shame! Do you mean you actually need to use Atmel tools to make a living just like me and not just to look at the pretty colours on the screen and get excited about new releases of Studio? 
Welcome to the wonderful world of 'free' software.
The free software I use works just fine, thank you.
I am frankly astonished at the deluge of "AS7 is broken" and "AS7 broke my machine" threads these last few months, with more or less no reaction from Atmel (with a few important exceptions, of course). How this monster made it out of internal Alpha, let alone public Beta, is a mystery to me.
How do any of you get any work done? ;-)
|
"Experience is what enables you to recognise a mistake the second time you make it." "Good judgement comes from experience. Experience comes from bad judgement." "Wisdom is always wont to arrive late, and to be a little approximate on first possession." "When you hear hoofbeats, think horses, not unicorns." "Fast. Cheap. Good. Pick two." "We see a lot of arses on handlebars around here." - [J Ekdahl] |
 |
I am frankly astonished at the deluge of "AS7 is broken" and "AS7 broke my machine" threads these last few months,
Because you were not around when "AS4 is broken" and "AS4 broke my machine and "AS5 is broken" and "AS5 broke my machine" ......But then we got AS6 and AS7, nothing still works correctly but that's the wonderful world we live in.
I suspect most of the blame should go to Microsoft on which Studio relies so much on.
Let's play a guessing game: How much has Atmel paid for all the broken Studios since AS4.18? What's that, about 5 years now?
edit oh look what I found! Haah the memories https://www.avrfreaks.net/forum/a...
Cute :)
Indeed I was not around for 4 or 5. I >>was<< around for 6.0 (ish), but I was no more a AS user then than I am now, and I spent no time reading AS threads.
|
"Experience is what enables you to recognise a mistake the second time you make it." "Good judgement comes from experience. Experience comes from bad judgement." "Wisdom is always wont to arrive late, and to be a little approximate on first possession." "When you hear hoofbeats, think horses, not unicorns." "Fast. Cheap. Good. Pick two." "We see a lot of arses on handlebars around here." - [J Ekdahl] |
|
Is this non-tool working issue being fixed or not? We uninstalled studio 7, installed the very latest & still no detection of the mkII (even though it shows present in the hardware manager & WORKING FINE).
should they switch to a different brand of driver?
I suspect most of the blame should go to Microsoft on which Studio relies so much on.
But whose decision was it to use Visual Studio?
To be fair Image Craft is having all sorts of problems with their debugger also from what I can see.
But they are using Atmel "guts" which of course relies on M$.
Thank you.
This fixed the problem for me.
Fast forward from my previous message stating I got a solution to present day and again no way to have mkII recognized by windows.
I spoke with a local atmel support and they told me that JTAGICE mkII is not supported anymore in windows 10.
I can't see it in the device manager when I plug the USB.
Tried to change the jungo driver to version 12, 11 and the previous one, still no luck.
Tried the workaround in the other topic linked up here and no luck.
Now I have to replace all my JTAGICE mkII with the ICE and use AS7 instead of AS4 with all the discomfort it takes.
Atmel, you just lost a customer for all my future projects, good job!
Well actually Microshaft did this to you... Atmel just held their coat while they violated you.
To be fair the JTAGICE mkII over 10 years old and things have moved on since then. I know it is annoying as it still works but at some stage support is dropped.
David
From a partial read of two of the posts at the top of that list :
One of the work-arounds has a fix dated 2016.01.22 for Visual Studio 2015 which is the parent of Studio 7 :
https://github.com/pbatard/libwdi/blob/master/ChangeLog
There are those who like the JTAGICE mkII (myself) so am keen.
Waveshare makes a clone and states it's compatible up to Studio 6 and maybe 7.
Mcuzone makes a function-alike that's likewise; it might have firmware for Studio 7 (yet to search for it).
May one's original JTAGICE mkII have a long life.
http://www.waveshare.com/product/mcu-tools/avr/programmers-debuggers/usb-avr-jtagice-xpii.htm
http://stores.ebay.com/mcuzone
http://www.mcuzone.com:8080/dokuwiki/doku.php?id=english_home_page#usb_avr_jtagice_mkii-cn
To be fair the JTAGICE mkII over 10 years old and things have moved on since then. I know it is annoying as it still works but at some stage support is dropped.
David
There is a big difference between "stopping further support" and "destroying existing product".
For example. The JTAGICE-1 firmware has not been upgraded since about 2006 and the STK500 has not been upgraded since about 2008.
They did not detect a JTAGICE-1 or STK500 and prompt you to "Upgrade" in order to destroy the working product.
I had assumed the JTAGICE-mkII destruction was a mistake. If it does not work on Win10, do they need to stop it working on Win7 ?
They could simply say "no longer supported in AS7.0.790". Then it could still be used in AS4, AS6, IAR, Rowley, ...
David.
Well http://atmel.force.com/support/a... seems to suggest Atmel haven't dropped support for JTAGICE-mkII so maybe this is an overreaction.
David
May one's original JTAGICE mkII have a long life.
Or a JTAG Mk1! 
So my JTAG Mk2 is ONLY used with AS4.18 and I have M$ update turned OFF in all my 4 win 7 machines, only updating when I want to and making sure that the KB3035583 is not installed so that I don't get the Win10 nag.
Don't know what I'll do when I can no longer work with Win 7, but that's still a few years down the line.
I am running AS 6.2 with a JTAG MKII and I am having the same problem. Device shows up in device manager but not in AS 6.2. I had this problem several months ago and I can't remember what I did to get it working. It's been about 4 months since I have used anything Atmel so I don't really know what broke it.
At the time I installed it 6.2 was all that worked with Code Vision so unless that's changed I can't update AS.
Downgrade ur MKII driver to support in AVR studio 4.17
I've been developing against a tight schedule with AS6.2 and AVRISPMKII quite successfully, (albeit with driver issues I could get around). After Windows 10 updates yesterday, AS6.2 won't see my AVRISPMK2 at all, although I can see it in Device Manager okay. Tried to download and install AS7 twice, hoping that has better Windows 10 support, but both times the installation hung mid way. My AVRISPMKII is fine, it programs fine using a batch file running on an old WinXP machine. Has anyone else had problems since recent Windows updates? I've lost a day already and have just a week to develop a shed-load of functionality. I can't afford to be without a working IDE and programmer combination.
Edit: Oh, and I've also taken Atmel's driver advice and changed the driver for my AVRISPMKII to libusb0 using Zadig, and now my AVRISPMKII won't even enumerate as a USB device :-(
After Windows 10 updates yesterday, AS6.2 won't see my AVRISPMK2 at all, although I can see it in Device Manager okay.
Windows 10 updates can be rolled backed within 10 days.
Windows 10 version 1607 is not in Current Branch for Business; it's recommended to use version 1511.
Once a PC has a reasonably functional Windows 10, lock down Windows 10; then, Windows Update about a month after a new build, re-lock, and test that build.
https://technet.microsoft.com/en-us/windows/mt679505.aspx (Windows 10 release information - current branch, build history)
https://www.askwoody.com/automatic-updates/ ('Windows 10')
Has anyone else had problems since recent Windows (10) updates?
Transparency - don't (yet) operate Windows 10.
Edit: Oh, and I've also taken Atmel's driver advice and changed the driver for my AVRISPMKII to libusb0 using Zadig, and now my AVRISPMKII won't even enumerate as a USB device :-(
via
http://atmel.force.com/support?q=%22Windows%2010%22
Tried to download and install AS7 twice, hoping that has better Windows 10 support, but both times the installation hung mid way.
A fall-back :
https://www.avrfreaks.net/forum/atmel-studio-7-distribution-experimental-0 by charla
Yep still having connectivity problems in 2017.
Some may think this is just a hobby forum but if they expect me to use AVR in product design they need to attend to these bugs.
The Arduino people seem to have it right, not complicated or bloated but simple IDE interface with no bugs, why cant Atmel see the beauty in this approach.
The difference in these two approaches is in IDEs similar to old problem between a CISC and a RISC all over again?
So you have been a member since 2011, and this is your first post and you demand Atchip/Micromel attend to bugs if they expect you to use their products.... Nice first impression.
The Arduino people seem to have it right, not complicated or bloated but simple IDE interface with no bugs, why cant Atmel see the beauty in this approach.
The Arduino is made with Atmel products, the USB interface I think(not sure) is a product (LUFA) of our own Dean(abcminiuser) Camera. While the interface is simple, it was designed to be so as it only works with a select few Atmel products as opposed to AtmelSudio which is designed to work with EVERY component Atmel produces.
You are comparing apples and oranges.
So with regards to your issue with your MKII... Most of us had to turn in our crystal ball to Microchip when they took over so if you could provide some information regarding what errors you are seeing in Studio, or in Device Manager of your PC it would be appreciated. ALso the Operating System, and version of Studio you are using would be a plus as well.
Cheerio!
Jim
