You burn the bootloader to get the fuses set up.You are not using a crystal? Then there is a change needed in the fuse selections.I can research that some tomorrow night if someone else does not step in before then. I'm off to bed.Code: [Select]uno_noP.bootloader.low_fuses=0xffuno_noP.bootloader.high_fuses=0xdeuno_noP.bootloader.extended_fuses=0x05uno_noP.build.f_cpu=16000000L
Okay, this gets a little 'fun'.The 328 has different signature bytes than the 328P.328 0x1E 0x95 0x14328P 0x1E 0x95 0x0FThe real way around this (doing this from memory, bear with me).Download a copy of notepad++ so you have a good editorhttp://notepad-plus-plus.org/Find avrdude.conf. Open it & find 'm328p'Copy that whole section, call it 'm328' and change the signature bytes per above.Change anything that ATMega328P to ATMega328. (no P at the end)Save that.Find boards.txtFind a section that says something like "traditional NG bootloader. "The NG boards used '168s and internal crystal."The initial design of the Arduino LilyPad had a 10-pin ICSP header and used the internal clock on the ATmega168 rather than an external oscillator. The bootloader on the initial design is the traditional NG bootloader. "So you want to set up like that.Copy that section, put in your new new board name, and put in the '328 signature bytes and memory limits.Burn the bootloader so the fuses are set for the internal crystal, and you should be able to load sketches after that.I've not tried this personally for anything but '1284s witt crystals, but it should get you pretty close.Come back and ask questions if you get stuck.
> There are entries specifically: > > Arduino Uno w/'328 > Leonardo16 > > They won't compile in 1.0.2, IDE complains about the MCU not being there. I have checked & rechecked, I created both in avrdude.conf At this point you're barking up the wrong tree. The compiler doesn't use avrdude.conf. All of its stuff is internal. avrdude.conf will haveto have entries for the processors when you upload but adding the entries won't help when compiling.The only solution is to swap out the AVR-GCC toolset for something newer. I've posted instructions for upgrading to the latest version ofWinAVR on the forum. If you can't find one of the posts or get stuck just let me know and I'll try to help. Warning: I have no idea if thelatest version of WinAVR supports the ATMEGA16U4 or the ATMEGA328.