Hi all,
I have built my AVRdoper it works fine in CDC mode. But i am not able to program my chips in HID mode.
I am using Windows XP with SP2.
Whenever i give cmmand for programming like below
avrdude -c stk500v2 -P com3 -p atmega32 -U flash:w:xyz.hex it works perfectly for me.
but whenever i put HID jumper my device is identified as a HID device in the device manager and then when i put command
avrdude -c stk500v2 -P avrdoper -p atmega32 -U flash:w:xyz.hex it gives a error on my system.
I am using WINAVR 20070525 version.
AVR-DOPER HID mode
1. Have you installed linusb for windows? (http://libusb-win32.sourceforge.net/#downloads - the first filter driver)
2. If that does not help - post the error message.
Hope it works!
2. If that does not help - post the error message.
Hope it works!
AVR-DOPER HID mode
I tried installing the libusb which you gave and at the end of the installation i am also getting my pogrammer device in run test.
This is the message i receive when i use my prgrammer in HID mode:
avrdude -p atmega16 -P avrdoper -c stk500v2 -U flash:w:xyz.hex
avrdude: avrdoper_open(): Device not found.
make.exe: *** [program] Error 1
This is the message i receive when i use my prgrammer in HID mode:
avrdude -p atmega16 -P avrdoper -c stk500v2 -U flash:w:xyz.hex
avrdude: avrdoper_open(): Device not found.
make.exe: *** [program] Error 1
There is a test program installed with libusb: it should be called just "Test Program" in the start menu folder somewhere or in the libusb installation folder. (ex. C:\Program Files\LibUSB-Win32\bin\testlibusb-win.exe)
You should see this device among all other:
If you see it, then I don't see a reason why avrdude shouldn't.
I tried the same version of WinAVR and it works for me. If the device is found by libusb, you can post the output.
You should see this device among all other:
Code: Select all
bus-0/\\.\libusb0-0005--0x16c0-0x05df 16C0/05DF
- Manufacturer : obdev.at
- Product : AVR-Doper
wTotalLength: 34
bNumInterfaces: 1
bConfigurationValue: 1
iConfiguration: 0
bmAttributes: 80h
MaxPower: 100
bInterfaceNumber: 0
bAlternateSetting: 0
bNumEndpoints: 1
bInterfaceClass: 3
bInterfaceSubClass: 0
bInterfaceProtocol: 0
iInterface: 0
bEndpointAddress: 81h
bmAttributes: 03h
wMaxPacketSize: 8
bInterval: 10
bRefresh: 0
bSynchAddress: 0
If you see it, then I don't see a reason why avrdude shouldn't.
I tried the same version of WinAVR and it works for me. If the device is found by libusb, you can post the output.
You don't need libusb for AVR-Doper in HID mode. That's the advantage of this mode and why we implemented it this way!
Some avrdude binaries have broken support for AVR-Doper in HID mode. See the following thread:
http://forums.obdev.at/viewtopic.php?t=614
Some avrdude binaries have broken support for AVR-Doper in HID mode. See the following thread:
http://forums.obdev.at/viewtopic.php?t=614
duni wrote:There is a test program installed with libusb: it should be called just "Test Program" in the start menu folder somewhere or in the libusb installation folder. (ex. C:\Program Files\LibUSB-Win32\bin\testlibusb-win.exe)
You should see this device among all other:Code: Select all
bus-0/\\.\libusb0-0005--0x16c0-0x05df 16C0/05DF
- Manufacturer : obdev.at
- Product : AVR-Doper
wTotalLength: 34
bNumInterfaces: 1
bConfigurationValue: 1
iConfiguration: 0
bmAttributes: 80h
MaxPower: 100
bInterfaceNumber: 0
bAlternateSetting: 0
bNumEndpoints: 1
bInterfaceClass: 3
bInterfaceSubClass: 0
bInterfaceProtocol: 0
iInterface: 0
bEndpointAddress: 81h
bmAttributes: 03h
wMaxPacketSize: 8
bInterval: 10
bRefresh: 0
bSynchAddress: 0
If you see it, then I don't see a reason why avrdude shouldn't.
I tried the same version of WinAVR and it works for me. If the device is found by libusb, you can post the output.
Hi Duni,
I am getting following instructions while i use my USB DOPER. Is it ok or something is wrong with my programmer since it is not as like you??
Code: Select all
bus-0/\\.\libusb0-0005--0x16c0-0x05df 16C0/05DF
- Manufacturer : obdev.at
- Product : AVR-Doper
wTotalLength: 67
bNumInterfaces: 2
bConfigurationValue: 1
iConfiguration: 0
bmAttributes: 80h
MaxPower: 100
bInterfaceNumber: 0
bAlternateSetting: 0
bNumEndpoints: 1
bInterfaceClass: 2
bInterfaceSubClass: 2
bInterfaceProtocol: 1
iInterface: 0
bEndpointAddress: 83h
bmAttributes: 03h
wMaxPacketSize: 8
bInterval: 100
bRefresh: 0
bSynchAddress: 0
bInterfaceNumber: 1
bAlternateSetting: 0
bNumEndpoints: 2
bInterfaceClass: 10
bInterfaceSubClass: 0
bInterfaceProtocol: 0
iInterface: 0
bEndpointAddress: 01h
bmAttributes: 02h
wMaxPacketSize: 8
bInterval: 0
bRefresh: 0
bSynchAddress: 0
bEndpointAddress: 81h
bmAttributes: 02h
wMaxPacketSize: 8
bInterval: 0
bRefresh: 0
bSynchAddress: 0