I've stumbled upon what I've later found it's quite common error, but there seems not to be simple troubleshooting way and solution (people often try various things, sometimes they succeed, sometimes not).

I am using DAGU mini driver, I was able to load sketch as described here - chose Arduino NG ATMega8 as board, connect to my PC via USB (with the driver listed on the product page).

Later on I've plugged RedBot wheel encoders sensor and write some simplistic program to check whether it works at all. I've summarized the steps in a github issue, so that it's easy to reference it.

When I tried to upload the sketch I've receiced stk500_initialize(): (a) protocol error, expect=0x14, resp=0x42, stk500_getparm(): (a) protocol error, expect=0x14, resp=0x41. The full log is included in comment on that github issue.

The D13 diode is making series of 3-blink bursts - 8 bursts after start. More diagnostic I did in the github issue as well.

My question (apart from obvious 'how to fix it!?!' ;) ) is whether there is some kind of documentation for this protocol? On the various topics I've found people seem to have somewhat different problems (the numbers and messages were different). I just want to know why the first few messages are exchanged OK (avrdude receives some basic info from the chip), but later ones (namely Send: A [41] . [81] [20]) are producing protocol errors.

  • Ordered programmer, will see if it's just corrupted bootloader
    – Bartosz
    Dec 1, 2014 at 11:04

1 Answer 1


AVR programmer helped.

Meaning the bootloader somewhat got corrupted and I had to burn new one.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.