This section provides a brief overview of the programming features of AVR Studio 4 that were not covered in Section 3.c. You will not typically need to use these advanced features, but it is good to know about them for the rare occasions when you will need them. Please see the Atmel’s AVR Studio 4 documentation for more detailed descriptions of these features.
In the ISP window, under the Main tab, the Programming Mode and Target Settings section lets you set the frequency of the clock used when programming the target device. The higher the ISP frequency, the faster the target AVR will be programmed, but . Click Read to read the frequency from the programmer and click Write to write the selected frequency to the programmer. It is important to note that the frequencies in the ISP Freq list are not correct when you are using the Pololu USB AVR programmer. See Section 3.e for a list of the actual frequencies and more information about selecting the ISP frequency.
Fuses (proceed with caution!)
Clicking on the Fuses tab automatically causes the programmer to read the fuse settings of the target AVR. If the programmer is not connected to the target AVR when you select this tab, AVR Studio displays an error message. Fuses allow you to configure certain persistent, fundamental aspects of your AVR such as boot flash size, brown-out detection level, and the clock off of which it should run (e.g. external crystal or internal oscillator). To learn more about the fuses and what they do, see the datasheet for your specific AVR.
Warning: You can permanently disable your AVR by setting the fuses incorrectly. Only advanced users who know precisely what they are doing should change the fuse settings!
Clicking on the Lock Bits tab automatically causes the programmer to read the lock bits of the target AVR. If the programmer is not connected to the target AVR when you select this tab, AVR Studio displays an error message. Lock bits allow you to secure your AVR by preventing further flash writing or reading. The lock bits can be reset to a fully unlocked state by performing a chip erase (i.e. by clicking the Erase Device button in the Main tab). Lock bits are usually only important if you wish to release a product to other people without giving them access to the program it is running, or if you wish to make it more difficult to accidentally overwrite a programmed chip.