Do you have:1. Xtal connected to the brand new 328p?
2. Vcc connected?
3. double check wirings..
4. decoupling capacitors?
..the black-box situation
I see, you are using the arduino as the programmer for a new chip.. If the arduino is at 16MHz and SPI is /128 it could be too high (125KHz), sure. It would be better to go down to ~1kHz for the new chip fuses reflash.
CLKPR = (1<<CLKPCE); // enable clock divider CLKPR = (1<<CLKPS0); // divide f_cpu by 2
avrdude -c arduino -p atmega328p -P COM4 -b 19200 -e -u -U efuse:w:0xff:m avrdude -c arduino -p atmega328p -P COM4 -b 19200 -e -u -U hfuse:w:0xd9:mavrdude -c arduino -p atmega328p -P COM4 -b 19200 -e -u -U lfuse:w:0x62:m
Quote from: pito on Jun 20, 2012, 11:18 amDo you have:1. Xtal connected to the brand new 328p?Yes.
A way of ruling out programming problems, albeit high-risk, would be to set the fuses of the working ATmega328p to their factory defaults and then try reprogramming it.
You could always try using the clock pre-scaler
could you post a photo of your setup?
The board detector program detects a known good chip fine. With one of the new chips, it doesn't detect it at all.
Atmega chip detector.
So those two chips were bad. Wow.
Insert target AVR and press button.Existing fuse values:LFUSE: 3FHFUSE: 3FEnter desired LFUSE hex value (ie. 0x62): FFEnter desired HFUSE hex value (ie. 0xDF): DEBurning fuses...Read LFUSE: 36Read HFUSE: 15Burn complete.It is now safe to remove the target AVR.