Fundamental issues with AVR-Doper, but usb & wiring ok
Posted: Sun Sep 02, 2007 7:11 pm
I've just build AVR-Doper, the original one from the obdev.at website. I flashed the mega8-16 with a simple parallel programmer including the both fuse bytes.
Now AVR-Doper connects in both modes and is being recognized:
usb 2-1: new low speed USB device using ohci_hcd and address 2
usb 2-1: configuration #1 chosen from 1 choice
drivers/hid/usbhid/hid-core.c: ctrl urb status -75 received
hiddev96: USB HID v1.01 Device [obdev.at AVR-Doper] on usb-0000:02:00.0-1
--> in HID-mode
usb 2-1: new low speed USB device using ohci_hcd and address 3
usb 2-1: configuration #1 chosen from 1 choice
usbcore: registered new interface driver cdc_acm
drivers/usb/class/cdc-acm.c: v0.25:USB Abstract Control Model driver for USB modems and ISDN adapters
--> in COM-mode
But when I execute avrdude -c stk500v2 -P avrdoper -p t45 -U flash:w:firmware.hex:i , I get:
Warning: cannot query manufacturer for device: error sending control message: Operation not permitted
avrdude: avrdoper_open(): I/O Error.
--> in HID mode and
avrdude -c stk500v2 -P /dev/ttyACM0 -p t45 -U flash:w:firmware.hex:i
avrdude: stk500v2_command(): command failed
avrdude: initialization failed, rc=-1
Double check connections and try again, or use -F to override
this check.
--> in COM mode
(The last message I get in both modes under windows).
About the voltages:
The HVSP voltage is 12.47V. Very very strange is, that the MOSI,SCK,MISO,RST lines are 0V. I want to program my target - tiny45 - in the HVSP socket, but although the 12.47 voltage is ok all voltages in the both sockets stay at 0V.
In the first test I've overseen that 3 traces under the 20 pin HVSP are connected, because they were not entirely etched. Those were pin1&2 from the connector - the ground, the hvsp reset and atmega's pin17, witch trace passes by. So I got 0V on the D3 diode. Now everything is fine, but my concerns are, whether the avr's pin is fine, but the 13V were "grounded"...
Could this be the problem for the programmers entire behavior?
What else could cause such problems and where should I start to look for them?
Now AVR-Doper connects in both modes and is being recognized:
usb 2-1: new low speed USB device using ohci_hcd and address 2
usb 2-1: configuration #1 chosen from 1 choice
drivers/hid/usbhid/hid-core.c: ctrl urb status -75 received
hiddev96: USB HID v1.01 Device [obdev.at AVR-Doper] on usb-0000:02:00.0-1
--> in HID-mode
usb 2-1: new low speed USB device using ohci_hcd and address 3
usb 2-1: configuration #1 chosen from 1 choice
usbcore: registered new interface driver cdc_acm
drivers/usb/class/cdc-acm.c: v0.25:USB Abstract Control Model driver for USB modems and ISDN adapters
--> in COM-mode
But when I execute avrdude -c stk500v2 -P avrdoper -p t45 -U flash:w:firmware.hex:i , I get:
Warning: cannot query manufacturer for device: error sending control message: Operation not permitted
avrdude: avrdoper_open(): I/O Error.
--> in HID mode and
avrdude -c stk500v2 -P /dev/ttyACM0 -p t45 -U flash:w:firmware.hex:i
avrdude: stk500v2_command(): command failed
avrdude: initialization failed, rc=-1
Double check connections and try again, or use -F to override
this check.
--> in COM mode
(The last message I get in both modes under windows).
About the voltages:
The HVSP voltage is 12.47V. Very very strange is, that the MOSI,SCK,MISO,RST lines are 0V. I want to program my target - tiny45 - in the HVSP socket, but although the 12.47 voltage is ok all voltages in the both sockets stay at 0V.
In the first test I've overseen that 3 traces under the 20 pin HVSP are connected, because they were not entirely etched. Those were pin1&2 from the connector - the ground, the hvsp reset and atmega's pin17, witch trace passes by. So I got 0V on the D3 diode. Now everything is fine, but my concerns are, whether the avr's pin is fine, but the 13V were "grounded"...
Could this be the problem for the programmers entire behavior?
What else could cause such problems and where should I start to look for them?