Sometime in the past, I was burning bootloaders on a fresh batch of four ATmega328-PU using the Arduino IDE (notice there's no P after 328 - it's the slightly cheaper non-picopower version of the MCU, not to be confused with the ATmega328P-PU with a P), and was surprised with the following message from avrdude:
avrdude: Device signature = 0x1e950F avrdude: Expected signature for ATMEGA328 is 1E 95 14 Double check chip, or use -F to override this check.
That means avrdude thought the chip was not what its label said. Then I changed the chip type on my Arduino IDE to ATmega328P-PU and avrdude burned the bootloader without complaints. What that means is that the chip was labelled as one MCU and internally it responded as another, slightly different.
What I would like to know is:
How rare is this event? Has anyone had a similar experience?(Original question, off-topic)
Is it possible to fix this? How can I fix the signature so that avrdude recognize the chip correctly?
This is a cross-post from EE.SE. I posted this question there but didn't attract much attention, so I wanted to see if anyone from our community had a similar experience.