Now it mysteriously murky again has happened.
I placed my ATmega328P-PU on my UNO Rev3 and then I used AVRISP Mkii programmer to burn the sketch. While I burn in the sketch with AVRISP Mkii programmer it overwrites the bootloader. I do not use the 16 Mhz crystal, ony 8 Mhz crystal who are include the ATmega328P-PU
Then i plug away the ATmega328P-PU from the UNO Rev3 board and place it on a circut. I now use my programmer to burn the sketch onto the ATmega328P-PU by set up the MISO, MOSI, SCK, GND, VCC pins but i got this error.
Wrong microcontroller found.
Binary sketch size: 2 602 bytes (of a 30 720 byte maximum)
avrdude: Expected signature for ATMEGA328P is 1E 95 0F
Double check chip, or use -F to override this check.
I have tried this solution but that did not work for me.
The sketch
/*
AnalogReadSerial
Reads an analog input on pin 0, prints the result to the serial monitor.
Attach the center pin of a potentiometer to pin A0, and the outside pins to +5V and ground.
This example code is in the public domain.
*/
// the setup routine runs once when you press reset:
void setup() {
// initialize serial communication at 9600 bits per second:
Serial.begin(9600);
}
// the loop routine runs over and over again forever:
void loop() {
// read the input on analog pin 0:
int sensorValue = analogRead(A0);
// print out the value you read:
Serial.println(sensorValue);
delay(1); // delay in between reads for stability
}
atmega328bb.name=ATmega328 on a breadboard (8 MHz internal clock)
atmega328bb.upload.protocol=stk500
atmega328bb.upload.maximum_size=30720
atmega328bb.upload.speed=57600
atmega328bb.bootloader.low_fuses=0xE2
atmega328bb.bootloader.high_fuses=0xDA
atmega328bb.bootloader.extended_fuses=0x05
atmega328bb.bootloader.path=arduino:atmega
atmega328bb.bootloader.file=ATmegaBOOT_168_atmega328_pro_8MHz.hex
atmega328bb.bootloader.unlock_bits=0x3F
atmega328bb.bootloader.lock_bits=0x0F
atmega328bb.build.mcu=atmega328p
atmega328bb.build.f_cpu=8000000L
atmega328bb.build.core=arduino:arduino
atmega328bb.build.variant=arduino:standard
While you had the chip in the UNO did you select "ATmega328 on a breadboard (8 MHz internal clock)" and do a Burn Bootloader? If you don't do that part and your chip was set to use a crystal you will need a crystal in your circuit. Part of the Burn Bootloader process is to set the fuses. That isn't done when you upload a sketch.
I now use my programmer to burn the sketch onto the ATmega328P-PU by set up the MISO, MOSI, SCK, GND, VCC pins but i got this error.
You need Reset connected as well. The MKii taking holding Reset low is what lets the MKii taking over programming mode via the SCK, MOSI, MISO pins.
johnwasser:
While you had the chip in the UNO did you select "ATmega328 on a breadboard (8 MHz internal clock)" and do a Burn Bootloader?
No. I did not and i do not need to. If i use the AVRISP Mkii programmer i don't need to use a bootloader.
I have now set up my circuit with a 16 Mhz crystal and choose the ATmega328 UNO board w/ 16 Mhz.
I still got the same error. I can't even burn a bootloader.
If you don't do that part and your chip was set to use a crystal you will need a crystal in your circuit. Part of the Burn Bootloader process is to set the fuses. That isn't done when you upload a sketch.
Well, you don't need a bootloader if you are using the Mkii programmer.
CrossRoads:
I now use my programmer to burn the sketch onto the ATmega328P-PU by set up the MISO, MOSI, SCK, GND, VCC pins but i got this error.
You need Reset connected as well. The MKii taking holding Reset low is what lets the MKii taking over programming mode via the SCK, MOSI, MISO pins.
If i set up like this it works....
But if i setup like this it not gonna work..
Well, I can run the program who is in the ATmega, but not change the sketch. I don't know why. Speed of Mkii?
Who can tell what is wired up there? Is there a schematic?
Turn on verbose upload, to see which signature you're actually getting. (I think that will do it. If not, probe directly with avrdude commands from a command line.)
Something "close" to 1E 95 0F indicates perhaps the chip isn't what you expect, or the chip you're talking to isn't the one you expected. Something like 0 0 0 or FF FF FF indicates a wiring or clock problem.
