Bought new Atmega328-PU
Burned bootloader with Atmega328 on BB 8Mhz internal clock.
After burning bootloader, programme upload shows
"not in sync:resp = 0x94". This happens for any sketch.
Works for previous atmega328 I bought, but not this one.
What is 0x94 error?
Any help?
0x94 is not an error code. That's the uploader saying I received a byte containing 0x94 when I expected to receive a different value. Something is wrong.
Looks like maybe a baud rate missmatch? Did you select the board "Atmega328 on BB 8Mhz internal clock" before trying the upload? Do you have the right serial port selected?
It worked for a different IC. Am I forgetting something?
Here are the messages.
Sketch uses 450 bytes (1%) of program storage space. Maximum is 30,720 bytes.
Global variables use 9 bytes of dynamic memory.
avrdude: stk500_getsync() attempt 1 of 10: not in sync: resp=0x94
avrdude: stk500_getsync() attempt 2 of 10: not in sync: resp=0xfc
avrdude: stk500_getsync() attempt 3 of 10: not in sync: resp=0x94
avrdude: stk500_getsync() attempt 4 of 10: not in sync: resp=0x8c
avrdude: stk500_getsync() attempt 5 of 10: not in sync: resp=0x84
avrdude: stk500_getsync() attempt 6 of 10: not in sync: resp=0x94
avrdude: stk500_getsync() attempt 7 of 10: not in sync: resp=0xfc
avrdude: stk500_getsync() attempt 8 of 10: not in sync: resp=0x94
avrdude: stk500_getsync() attempt 9 of 10: not in sync: resp=0xfc
avrdude: stk500_getsync() attempt 10 of 10: not in sync: resp=0x94
My money is on a baud rate mismatch, possibly due to oscillator inaccuracy. The internal oscillator on the Atmel chips can be pretty far from 8mhz - sometimes too far off for serial to work.
DrAzzy:
My money is on a baud rate mismatch, possibly due to oscillator inaccuracy. The internal oscillator on the Atmel chips can be pretty far from 8mhz - sometimes too far off for serial to work.
So. should I give 16MHz external a try?
You could try using a lower voltage if your USB-to-Serial supports it. The internal oscillator is calibrated at the factory at 3.3V.
