Well, it looks like the fuses got written successfully. Does it do anything after that?If not, you could try running the next command manually:bin/avrdude -p m168 -b 115200 -P usb -c avrispmkII -D -U flash:w:ATmegaBOOT_168.hex:i
I had a similar problem: a very long delay when I first ran avrdude before it started to do anything. I had to actually patch avrdude to fix it. Arduino 0009 (which should come out tomorrow) will include the patched version and a "Burn Bootloader" command.I submitted a bug to avrdude: https://savannah.nongnu.org/bugs/?19882 but haven't heard anything. You might want to add a comment explaining your experience (with the long delay on startup). These things sometimes get fixed faster if multiple people report them.
51 seconds to burn and 512 seconds to verify the flash does seem very long. That sounds like it might be a result of what kg4wsv suggested: that the avrispmkii is configured with a slow clock period. The delay at startup though, is because (assuming it's the same as it was in my case) avrdude tries to sync with the avrispmkii 33 times, and each one has a long timeout.
OK, but is there any way to put the "sck 10" into a command line option for a script?
QuoteOK, but is there any way to put the "sck 10" into a command line option for a script? If I understand correctly, issuing that command causes it to be written to EEPROM in the avrispmkII, so it should be a one shot deal.FYI, on a recent project I flashed and verified a 7k program in a few seconds from a PPC powerbook, so what you are seeing isn't normal (but I think you already knew that ). I was burning directly from the powerbook's USB port, while on battery even.You may also want to check the firmware on your avrispmkII.-j