Some basic question about AVR chips and Arduino

1: Sorta. Burning a bootloader, via the Arduino IDE, means that it'll change some fuses and add a program to the chip that waits a few milliseconds when the chip first gets power and listen for a command over serial that'll cause it to accept new code.

"program the chip through a USB cable" can mean a lot of things. Even without a bootloader you can do this, assuming you have something like an AVR ISP MKII. (If you do, you can hold shift and click upload to use it instead of the "normal" routine Arduino does). I'm really not sure what you're asking here so if you want more information you'll need to word that better.

The fuse bits will be changed if you use the Arduino IDE's "burn bootloader" feature. If you want to avoid this then you'll need to edit the boards.txt file, or learn to use avrdude and get an AVRISPMKII.

2: You don't /need/ to change the fuse bits. By default it'll work, but it'll run off its own internal clock and such. You're used to 16 mhz, but it'll ship at 128 khz. Obviously this throws things off, like the delay() function.

If you're trying to make a "standalone breadboard", so to speak, have a look at http://www.arduino.cc/en/Main/Standalone . It'll explain pretty much everything. (Note: The parts it lists are requirements, not suggestions, if you want to be sure your sketches work the same. Also, get an AVR ISP MKII. Do not use a second Arduino as a programmer. That tends to cause issues.)

3: There's a second AtMega on the Arduino boards that actually convert USB to Serial for the main CPU. You'll need a special device (Something like SparkFun USB to Serial Breakout - FT232RL - BOB-12731 - SparkFun Electronics ) to do serial communication again, or use the Arduino IDE "normally" again (Not having to hold shift while clicking upload). A single chip won't do the trick.

That being said, the new Arduino Due actually communicates directly via USB, but you'll have to solder SMD to use it so the point's pretty moot in your case.

Nofew:
1: Sorta. Burning a bootloader, via the Arduino IDE, means that it'll change some fuses and add a program to the chip that waits a few milliseconds when the chip first gets power and listen for a command over serial that'll cause it to accept new code.

"program the chip through a USB cable" can mean a lot of things. Even without a bootloader you can do this, assuming you have something like an AVR ISP MKII. (If you do, you can hold shift and click upload to use it instead of the "normal" routine Arduino does). I'm really not sure what you're asking here so if you want more information you'll need to word that better.

The fuse bits will be changed if you use the Arduino IDE's "burn bootloader" feature. If you want to avoid this then you'll need to edit the boards.txt file, or learn to use avrdude and get an AVRISPMKII.

2: You don't /need/ to change the fuse bits. By default it'll work, but it'll run off its own internal clock and such. You're used to 16 mhz, but it'll ship at 128 khz. Obviously this throws things off, like the delay() function.

If you're trying to make a "standalone breadboard", so to speak, have a look at http://www.arduino.cc/en/Main/Standalone . It'll explain pretty much everything. (Note: The parts it lists are requirements, not suggestions, if you want to be sure your sketches work the same. Also, get an AVR ISP MKII. Do not use a second Arduino as a programmer. That tends to cause issues.)

3: There's a second AtMega on the Arduino boards that actually convert USB to Serial for the main CPU. You'll need a special device (Something like SparkFun USB to Serial Breakout - FT232RL - BOB-12731 - SparkFun Electronics ) to do serial communication again, or use the Arduino IDE "normally" again (Not having to hold shift while clicking upload). A single chip won't do the trick.

That being said, the new Arduino Due actually communicates directly via USB, but you'll have to solder SMD to use it so the point's pretty moot in your case.

Erm, I mean if I burn the bootloader to the chip, it will change the fuse bits of the AVR chip right ? So how about if I delete the existing bootloader in the AVR chip ??Will the HIGH fuse and LOW fuse changed or remain the same as in the bootloader file ?

respected sir/madam,

i am new to arduino i want to make a arduino board (Arduino Single-Sided Serial Board (version 3)). i have few questions

  1. i have atmega8L. will i have to burn something known as firmware or boatloader in it.

  2. if yes please give me links for that and also tell me how do burn them.

  3. can i burn them with serial usb programers for avr chips.

please help me i really want to learn it.

thanking you

Erm, I mean if I burn the bootloader to the chip, it will change the fuse bits of the AVR chip right ? So how about if I delete the existing bootloader in the AVR chip ??Will the HIGH fuse and LOW fuse changed or remain the same as in the bootloader file ?

The fuses and the bootloader are not directly related. Although the fuses usually are set when "burning" the bootloader, they can also be set independant of that as well as the opposite: updating a bootloader without changing the fuses.
You cannot delete a bootloader but you may overwrite it. So if you overwrite the Arduino bootloader with anything (a program or simply zeros), the fuses are not changed except you explicitly specify to do so. The fuses are not specified in the bootloader file, that's only program code. If you use the Arduino IDE to update a bootloader, the fuse bits are specified in the boards.txt file where you also find the bootloader file used when you select "Burn Bootloader" from the menu.

pylon:

Erm, I mean if I burn the bootloader to the chip, it will change the fuse bits of the AVR chip right ? So how about if I delete the existing bootloader in the AVR chip ??Will the HIGH fuse and LOW fuse changed or remain the same as in the bootloader file ?

The fuses and the bootloader are not directly related. Although the fuses usually are set when "burning" the bootloader, they can also be set independant of that as well as the opposite: updating a bootloader without changing the fuses.
You cannot delete a bootloader but you may overwrite it. So if you overwrite the Arduino bootloader with anything (a program or simply zeros), the fuses are not changed except you explicitly specify to do so. The fuses are not specified in the bootloader file, that's only program code. If you use the Arduino IDE to update a bootloader, the fuse bits are specified in the boards.txt file where you also find the bootloader file used when you select "Burn Bootloader" from the menu.

Ya, I can manually change the fuse bits also without uploading the bootloader, for eg the UNO bootloader. I can refer to the board.txt file to see what should I change to for the HIGH fuse and LOW fuse configuration. Correct ? Oh, so means once I burnt a bootloader inside, it for example changed the fused . But how do I remove the bootloader ? Any method ? Because once I tried before, I upload the bootloader, then the atmega 328 I can upload code into it through USB. But once I delete it, I cant upload through USB. But I noticed that the fuse bits remain the same. If the fuse bits is the same, why I cant upload using USB once deleted ?

Thank you

Vincent19:
But how do I remove the bootloader ? Any method ?

Updload your code through the ICSP, and it will get rid of the bootloader.

But once I delete it, I cant upload through USB.

Delete what?

But I noticed that the fuse bits remain the same. If the fuse bits is the same, why I cant upload using USB once deleted ?

Delete what?

The bootloader allows you to program the chip through the serial pins on the micro. Without the bootloader, you will need to program it through the ICSP pins.

Delete the bootloader.

Well, the bootloader is to enable serial communication through USB ? Not to change the fuse bits so as to use the external 16MHz crystal ?? LOL

Well, the bootloader is to enable serial communication through USB ?

Again, no.

The bootloader allows you to program the micro using the serial pins. That doesn't specifically mean it has to be done through USB. Also, just because the bootloader is not on there, doesn't mean it can't be programmed through USB (See USB ICSP Programmers).

Not to change the fuse bits so as to use the external 16MHz crystal ?? LOL

Burning the bootloader is the Arduino way of changing the fuse bits. It can be done in AVR Studio without burning the bootloader. I don't see the big deal in burning the bootloader on there just to set the fuse bits. Unless you are programming it using the bootloader (meaning using the serial pins), then the bootloader will get wiped out the next time you program it.

ern, can i say the bootloader as serial to USb downloader? enable the code to be downloaded through usb

Vincent19:
ern, can i say the bootloader as serial to USb downloader?

Grammatically, no.

enable the code to be downloaded through usb

You would actually be uploading it through USB, not downloading it.

uploading it to 5he chip right ? if no then what is bootloader actually?

Vincent19:
uploading it to 5he chip right ? if no then what is bootloader actually?

See reply #8

Vincent19:
uploading it to 5he chip right ? if no then what is bootloader actually?

Yes, code is uploaded to the chip.

How can I know that 2kb is used for the bootloader file ? I want to see for the difference when I upload bootloader and remove bootloader but I cant see it ><

The optiboot (used on an UNO) is 1467 bytes (hardware/arduino/bootloaders/optiboot/optiboot_atmega328.hex). That's how you can know it.

I mean for the total available size for the sketch. When I burn bootloader, the chip memory would be reduced by approximate 2kb right ? But where can I see it ?

Vincent19:
How can I know that 2kb is used for the bootloader file ? I want to see for the difference when I upload bootloader and remove bootloader but I cant see it ><

See the difference in what? The size? Add 2K if you are using the bootloader to upload the sketch, don't if you are not.

I mean I want to see the difference in the size..LOL. Cause I want to experiment something..Heheh..

Vincent19:
I mean I want to see the difference in the size..LOL. Cause I want to experiment something..Heheh..

Well you could always look at the maximum upload memory size defined for each entry in the arduino core file 'boards.txt'.

You can see that the Uno has a value of:
uno.upload.maximum_size=32256

While the Duemilanove has a value of:
atmega328.upload.maximum_size=30720

The difference is the size of the bootloader memory size protection options used to hold the two different bootloaders used by these too boards.

Lefty

I mean I want to see the changes on the same chip..Is it possible ?

The situation is like this :

Now I have a fresh atmega 328, So I want to see the maximum memory

Next, I burn bootloader into the fresh atmega chip. Then I want to see the maximum memory for now.

Is it possible ?