I need to use my AVRISP MK ii device to program ATMEGA328P target using AVRDUDESS (AVRDUDE) software. The AVRISP MK ii device is successfully finding my target when I use Atmel Studio 7, however, it is not working properly with AVRDUDE.
Host system Windows 10 64-bit
AVRDUDESS version 2.13 installed (with AVRDUDE 6.3)
Programming device is AVRISP MK ii (clone) with version 1.18 firmware (Atmel Studio 7 automatically replaced existing version 1.c firmware with version 1.18 the first time the programmer was used on Atmel Studio 7.)
The target device is an ATMEGA328P with Fuse settings for crystal (attached to the target and working normally.) The target device has a 6.8K pull-up resistor to it's 5V supply.
When the AVRISP MK ii is attached to the host computer (but not to the target), the status LED in the AVRISP MK ii is steady red.
When the AVRISP MK ii is also attached to the host device, the AVRISP MK ii status LED is flashing orange.
When the AVRISP MK ii is attached to the host and target device, and when ATMEL Studio 7 is started, the AVRISP MK ii status LED changes to green.
When the AVRISP MK ii is attached to the host and target device, and when AVRDUDESS is started, the AVRISP MK ii status LED continues flashing orange.
AVRDUDESS Programmer (-c) option is set to Atmel AVR ISP mk II
AVRDUDESS Port (-p) option is set to usb
I ran AVRDUDESS with the most verbose setting and clicked "Detect" button and see the following messages (while the AVRISP MK ii status LED is flashing orange.)
>>>: avrdude -u -c avrisp2 -P usb -v -v -v -v -p m8
WARNING: Unable to detect MCU
avrdude.exe: Version 6.3, compiled on Feb 17 2016 at 09:25:53
Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/
Copyright (c) 2007-2014 Joerg Wunsch
System wide configuration file is "C:\Program Files (x86)\AVRDUDESS\avrdude.conf"
Using Port : usb
Using Programmer : avrisp2
avrdude.exe: usbdev_open(): did not find any USB device "usb" (0x03eb:0x2104)
avrdude.exe done. Thank you.
As I thought the issue might be with usb identifier, I checked with Windows device manager and do see the device recognized (attached screens shot of Wiindows Device manager shows the device with USB hardware ID 0x03EB 0x2104).
Any suggestions as to what issue I'm encountering?
Thanks very much!