Atmega 8 development board

No, it means copy that whole section and paste it at the end of the file.
I'll take a look at boards.txt when I get home and see if I can make the NG reference more clear - can't do it from here.

This is the section I was talking about in boards.txt

##############################################################

atmega168.name=Arduino NG or older w/ ATmega168

atmega168.upload.protocol=arduino
atmega168.upload.maximum_size=14336
atmega168.upload.speed=19200

atmega168.bootloader.low_fuses=0xff
atmega168.bootloader.high_fuses=0xdd
atmega168.bootloader.extended_fuses=0x00
atmega168.bootloader.path=atmega
atmega168.bootloader.file=ATmegaBOOT_168_ng.hex
atmega168.bootloader.unlock_bits=0x3F
atmega168.bootloader.lock_bits=0x0F

atmega168.build.mcu=atmega168
atmega168.build.f_cpu=16000000L
atmega168.build.core=arduino
atmega168.build.variant=standard

CrossRoads:
Okay, this gets a little 'fun'.
The 328 has different signature bytes than the 328P.
328 0x1E 0x95 0x14
328P 0x1E 0x95 0x0F

The real way around this (doing this from memory, bear with me).

Download a copy of notepad++ so you have a good editor
http://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.txt

Find 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.

I do not understand for the bolded part ><

Okay, find your boards.txt file.

You will see that every section has a line like this:

atmega168.build.mcu=atmega168

You will not find one that end with =atmega328
That name is what ties in with a similar section in avrdude.conf to tell the programmer what it is dealing with.
So maybe you add this to your boards.txt file:

##############################################################

uno_noP.name=Arduino Uno for Atmega328
uno_noP.upload.protocol=arduino
uno_noP.upload.maximum_size=32256
uno_noP.upload.speed=115200
uno_noP.bootloader.low_fuses=0xff
uno_noP.bootloader.high_fuses=0xde
uno_noP.bootloader.extended_fuses=0x05
uno_noP.bootloader.path=optiboot
uno_noP.bootloader.file=optiboot_atmega328.hex
uno_noP.bootloader.unlock_bits=0x3F
uno_noP.bootloader.lock_bits=0x0F
uno_noP.build.mcu=atmega328
uno_noP.build.f_cpu=16000000L
uno_noP.build.core=arduino
uno_noP.build.variant=standard

avrdude.conf has a 328P section, but not 328 - so you need to copy/paste that section & make a 328 section so boards.txt can pull in the needed info.
Here's the top of it and what you need to change, the rest of the section gets copied as-is.

#------------------------------------------------------------
# ATmega328P   <<< remove the P
#------------------------------------------------------------

part
    id		= "m328p";  // <<< remove the P
    desc		= "ATMEGA328P"; // <<< remove the P
    has_debugwire	= yes;
    flash_instr	= 0xB6, 0x01, 0x11;
    eeprom_instr	= 0xBD, 0xF2, 0xBD, 0xE1, 0xBB, 0xCF, 0xB4, 0x00,
		  0xBE, 0x01, 0xB6, 0x01, 0xBC, 0x00, 0xBB, 0xBF,
		  0x99, 0xF9, 0xBB, 0xAF;
    stk500_devcode	= 0x86;
    # avr910_devcode	= 0x;
    signature		= 0x1e 0x95 0x0F; // <<< change these to the '328 bytes - maybe just 0F to 14??

Then I have to burn the bootloader ?

What I initially ask is that without bootloader.

Error

No, you don't need a bootloader.
Once you are set up for the '328 chip,
you select the new board type
Tools:Board
select your programmer
Tools:Programmer
then set the fuses
Tools: Burn Bootloader

and then overwrite the bootloaded
File:Upload Using Programmer.

CrossRoads:
No, you don't need a bootloader.
Once you are set up for the '328 chip,
you select the new board type
Tools:Board
select your programmer
Tools:Programmer
then set the fuses
Tools: Burn Bootloader

and then overwrite the bootloaded
File:Upload Using Programmer.

if you said I do not need bootloader, then why burn bootloader into thee chip ?

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.

uno_noP.bootloader.low_fuses=0xff
uno_noP.bootloader.high_fuses=0xde
uno_noP.bootloader.extended_fuses=0x05

uno_noP.build.f_cpu=16000000L

I am using the crystal 16MHz

Vincent19:
Error

What does this error means ?

How can I check for the fuse bits of my current atmega328 ?? Any software ? As you said, burning bootloader is just changing the fuse bits so that the USB can communicate with the atmega 328. So, if I burnt arduino UNO bootloader into the atmega 328, then if I erased the bootloader, will the fuse bits remain the same ?

CrossRoads:
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.

uno_noP.bootloader.low_fuses=0xff

uno_noP.bootloader.high_fuses=0xde
uno_noP.bootloader.extended_fuses=0x05

uno_noP.build.f_cpu=16000000L

After I burn the new bootloader, then I change the board back to arduino UNO then upload code ?

CrossRoads:
Okay, this gets a little 'fun'.
The 328 has different signature bytes than the 328P.
328 0x1E 0x95 0x14
328P 0x1E 0x95 0x0F

The real way around this (doing this from memory, bear with me).

Download a copy of notepad++ so you have a good editor
http://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.txt

Find 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.

Okay, after some experiment, I understand what you want to do now. You are actually creating a new board file so that I do not need to always change the signature of the arduino UNO bootloader signature from 0F to 14 right ? You straight creating a new board name arduino UNO for atmega 328 where when I want to burn the bootloader, I choose this board and with the signature of 14 instead of 0F. Okay. But then once I upload the bootloader, I cant upload the code through USB though. The error shown as like below :

Can anyone help ? Sir @CrossRoad

Thank you

Yes, I haven't got that figured out yet.

Ok, I have a solution with Coding Badly's help.

See reply #1. Follow all the steps, ignoring the ATtiny xx stuff in the middle.

This seems to be a more direct link to WinAVR

When done moving & renaming the directory, it should compile okay.
I even copied the ATMEGA328P section into a new ATMEGA328 section and changed the last signature byte from 0x0F to 0x14, and compiles now too.
And the Leonardo16 stuff I made for Atmega16U4 compiles now too.

Why do I need to have the winAVR software ?

Because of the following, which Coding Badly explained to me:

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 have
to 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 of
WinAVR 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 the
latest version of WinAVR supports the ATMEGA16U4 or the ATMEGA328.

It only took a few minutes to do the steps needed.

Is that means if I follow that, next time when I deal with atmega 328 rather than atmega 328P, for example like burning bootloadr, I do not need to change the signature anymore in the avrdude.txt ??