Replies: 2 comments
-
I don't know what kind of bootloader your ATmega168 had, but the issue is usually that the selected baud rate is different than what the bootloader expects. When there is a baud rate mismatch, it's impossible to read the signature. However, if the bootloader expects the same baud rate that Avrdude is using, and you're using the correct bootloader protocol ( |
Beta Was this translation helpful? Give feedback.
-
I have checked what is the exact command that the Arduino IDE uses and you are right about the baud rate.
While for the ATmega328p it uses 56700 kbps:
Okay, so the idea I have come up with is already implemented, just not applicable in this case 👍 |
Beta Was this translation helpful? Give feedback.
-
I have just spent quite some time debugging issues with programming an arduino (promini) over UART getting the below error:
It's a quite common error for general connection issues to the MCU as I have found out.
I have almost burned the bootloader again to the chip (with USBasp) to fix this.
Only then avrdude told me that the chipID was wrong and the chip seems to be a ATmega168 and not the ATmega328p I have selected. ATmega168 it was indeed
Would it be possible to give the same error message for UART programming attempts too?
That would save significant time (and stackexchange posts) when people are trying to program with wrong chip settings.
Beta Was this translation helpful? Give feedback.
All reactions