Quote:
Originally Posted by Starglider 2
I'm getting somewhere! I'm not sure if it's because I turned the USB cable round, because today is Tuesday when yesterday I tried it was Monday (!), or what but suddenly Windows sees the device.
Not quite there yet though:
4 QUESTIONS:
A: Step 9 – Where do I find the "winavr/bin" folder?
B: Step 10 – This results in:
Code:
F:\avr>avrdude -p m32 -c avrispmkII -P usb
avrdude: usbdev_send(): wrote -116 out of 1 bytes, err =
avrdude: stk500_send_mk2(): failed to send command to serial port
avrdude: stk500v2_recv_mk2: error in USB receive
avrdude: usbdev_send(): wrote -5 out of 1 bytes, err =
avrdude: stk500_send_mk2(): failed to send command to serial port
avrdude: stk500v2_recv_mk2: error in USB receive
...
C: Should I be attaching the AVR-NET-IO power to the mains as well as having the AVRISPmkII connected, or does the AVRISPmkII provide all required power?
D: Also, am I meant to be changing any of the jumpers on the AVR-NET-IO itself? |
A. step 9 not needed as you are not using winavr..
B. what did step 8 give you?
C. Yes, the mk2 does not provide power to the target, so it must be powered separately. Note that step 8/10 should work without even connecting the mk2 to the target.
D. you will need to check its documentation - I'm not familiar with that device.
before following these instructions, make sure you don't have avr studio or any broken mk2 driver installs present in the system.