November 11, 2019, 10:49:09 pm

News:

SMF - Just Installed!


Unable to connect to tool AVRISP mkII

Started by lhern034, January 15, 2015, 12:07:32 pm

Previous topic - Next topic

JohnS

Main change is that the IDE changed what it does when programming.

John

.Costin

I agree with you,JohnS, but the weird thing here it's the fact that my programmer doesn't works even with Avrdude6.2 despite the fact the Lub's one works with both Avrdude6.2 and IDE 1.6.7...But with IDE 1.0.6 and WIN10 works fine, so cables and connections are out of discussion in this case...

LubOlimex

April 27, 2016, 11:57:13 am #32 Last Edit: April 27, 2016, 01:01:51 pm by LubOlimex
Hey,

The whole thing with firmware and drivers is messy and specific for each system. I don't want to go into much details but the latest firmware for the tool doesn't require firmware change to use it with the latest AVRDUDE if you use Windows 10.

Just upload the latest firmware and test if Arduino IDE 1.6.7 works with it. I used the latest "AVR456-studio-AVRISP-MKII.hex". And I used these drivers: https://www.olimex.com/Products/AVR/Programmers/AVR-ISP-MK2/resources/DRIVER-MK2-AS-6-7-W10.zip

If anybody that reads this uses Windows XP - you still need to perform firmware change, and you also can't use Atmel Studio 7 under XP, so don't even try. And you need to use drivers up to Jungo 11.0.0.0.

Furthermore, you can't use Windows 10 and AVR Studio 4 (at least I couldn't find any way to do it). Under Windows 10 you need to use Atmel Studio x.

Best regards,
Lub/OLIMEX
Technical support and documentation manager at Olimex

.Costin

Lub, I have the same drivers and firmware as you mentioned in your reply,but still the same error in usb receive....I'm confused about you are using a non Avrdude firmware on the tool ...Like you said, some little things makes life messy...:)
Best regards,
Costin

PS where I can find the firmware loaded iinto "on-the shelf" tools ?

.Costin

Furthermore, I have another question for you...In the Device manager, for the driver installed is mentioned "libusb-win32" , as is specified in manual or here in this topic, but in the "Readme" for the firmware you said is loaded into your tool( AVR456-studio-AVRISP-MKII.hex),says this

"Make sure any libusb or libusb-win32 drivers are removed and uninstalled completly
before you install the Atmel USB drivers else you would encouter driver mismatches."

So which one drivers must be on the computer ?  :-\

LubOlimex

The driver should be the one from my previous post. It works for Windows 10 only. The image of "Windows Device Manger" with the driver installed is in this post: https://www.olimex.com/forum/index.php?topic=4065.msg21083#msg21083

We load the latest firmware during production. The latest firmware can be found in this archive: https://www.olimex.com/Products/AVR/Programmers/AVR-ISP-MK2/resources/AVR-ISP-MK2-Firmware-WindowsDrivers.zip - we use the elf file ("isp-mk2-06-01-2016.elf") and another programmer to download the elf to the boards. Then each board gets software tests and each programmer is tested if it actually programs a target.

Best regards,
Lub/OLIMEX
Technical support and documentation manager at Olimex

.Costin

OK, Lub...It seems I have two options. :)..Load the new elf into MKII or buy a new one, tested, and confirmed to work as specified (Ardu IDE 1.6.7, Atmel Studio 7 and Avrdude 6.2)...In the meantime, I'm wishing to you and to all readers of this topic,
Happy Easter,
Costin

LubOlimex

April 29, 2016, 11:39:12 am #37 Last Edit: April 29, 2016, 11:53:05 am by LubOlimex
Hey,

What happens when you try with Atmel Studio 7 (the recommended one for Windows 10)? Note that Atmel Studio 7 uses specific Windows 10 drivers that are incompatible with the drivers of previous studio versions. And if you want to use Atmel Studio 7 and Atmel Studio 6.x in the same machine you need to perform driver switch every time as explained officially here: http://atmel.force.com/support/articles/en_US/FAQ/Downgrading-tools-to-use-older-Jungo-driver

About AVRDUDE try with with the latest stand-alone AVRDUDE - not the one included in Arduino IDE. This would show if the problem is in the AVRDUDE configuration or somewhere else. I've shared a one compiled for Windows here: https://drive.google.com/open?id=0B7WHuNCASY8cOGV4dVVLdDlieVk

Best regards,
Lub/OLIMEX

Technical support and documentation manager at Olimex

.Costin

April 30, 2016, 06:53:51 am #38 Last Edit: April 30, 2016, 07:31:57 am by .Costin
Well, it works fine with Atmel Studio 7 with the firmware uploaded as you said ( AVR456-studio-AVRISP-MKII.hex),it recognize it from the start and I was able to write an Arduino board with a sketch transferred into Studio 7. Regarding Avrdude I had tried the stand-alone 6.2 version ( after changing the apropriate firmware in the tool and the drivers for Avrdude- libusb-win32), but the error was there.Anyway the picture for the correct driver is the same with yours..I'll try today again and I'll let you know.The main program I'm using is Arduino's IDE...
Best regards,
Costin

aneeshn.etrx@gmail.com

Hi,

I am unable to connect the avr MkII to avr studio 6.2.
IT gives error when i click on apply in the device programming.
the device manager shows the device (MkII) but cannot connect..
I am using windows 7 and studio 6.2. I even tried zadig but it creates some error in the device manager..
mkii with yellow marking..

JonnyK

Quote from: aneeshn.etrx@gmail.com on April 30, 2016, 03:15:54 pm
I am unable to connect the avr MkII to avr studio 6.2.


I couldn't get online and followed all the steps (flip to update firmware, use libusb-win32, studion 7 latest build, win 7). Turns out I was reading the pin out wrong. I was following the diagram below...

https://www.olimex.com/Products/AVR/Programmers/AVR-ISP-MK2/resources/isp-mk2-layout-connectors.png

Which is the pin out ON THE PROGRAMMER looking at it. But looking at the cord to hook in jumpers you get the mirrior.

So a TPI connection for a ATtiny goes from...

ON THE PROGRAMMER
|1,2|
[3,4|
|5,6| 

ON BH6S CONNECTOR
|2,1|
|4,3-]
|6,5]

Same mirror with the ICSP10 and PDI. Yea... pretty stupid of me. 

Kvazzy

Hi.
I have did all procedures, but have no good result. I'm getting this message:

Timestamp:   2016-07-27 15:40:26.065
Severity:      ERROR
ComponentId:   20000
StatusCode:   0

Unable to connect to tool context: 'Atmel.VsIde.AvrStudio.Services.TargetService.TCF.Internal.Services.Remote.ToolProxy+ToolContext'.

Please, help me with that.

Quote from: Ant2N on May 19, 2015, 12:53:33 pm
I might have a simpler solution to the problem. The reason of this error is that Atmel Studio 6.2 expects the AVRISP to run the libusb drivers, which apparently wasn't the case previously.

To fix this error:

- Download Zadig: http://zadig.akeo.ie/. Zadig is a USB driver manager for Windows, and saved me a hundred times this year. The last version comes with the libusb-win32 (v1.2.6.0) driver embedded.

- Open Zadig, Options, List All Devices. The AVRISP mkII device should appear in the list.
- Replace its current driver by libusb-win32 (v1.2.6.0)

That's it! No restart required :)

Let me know if somebody had the same issue and was able to solve it this way.

LubOlimex

Hey Kvazzy,

Please share more info.

1. What is your operating system exactly?

2. What is the exactly Atmel Studio version that you use?

Best regards,
Lub/OLIMEX
Technical support and documentation manager at Olimex

tngotran

Quote from: Ant2N on May 19, 2015, 12:53:33 pm
I might have a simpler solution to the problem. The reason of this error is that Atmel Studio 6.2 expects the AVRISP to run the libusb drivers, which apparently wasn't the case previously.

To fix this error:

- Download Zadig: http://zadig.akeo.ie/. Zadig is a USB driver manager for Windows, and saved me a hundred times this year. The last version comes with the libusb-win32 (v1.2.6.0) driver embedded.

- Open Zadig, Options, List All Devices. The AVRISP mkII device should appear in the list.
- Replace its current driver by libusb-win32 (v1.2.6.0)

That's it! No restart required :)

Let me know if somebody had the same issue and was able to solve it this way.


Perfect solution :) thanks