#AVRDUDE GUI WINDOWS SERIAL#

The is either flash or eeprom (or hfuse, lfuse or efuse for the chip configuration fuses, but we aren't going to mess with those). Its the one that actually does the programming. -U :r|w|v: : OK this one is the important command.-e: This erases the chip, in general we don't use this because we auto-erase the flash before programming.The test is strongly recommended as it tests the connection, so don't use this switch. -F: This overrides the signature check to make sure the chip you think you're programming is.

#AVRDUDE GUI WINDOWS SERIAL#

It might be COM1 for serial or LPT1 for parallel or USB for, well, USB. -P : This is the communication port to use to talk to the programmer.We don't want that so don't use this command switch. -D: This disables erasing the chip before programming.-c : Here is where we specify the programmer type, if you're using an STK500 use stk500, if you're using a DT006 programmer use dt006, etc.Theres a default configuration file, so lets just use that: don't use this command switch

-C : The config file tells avrdude about all the different ways it can talk to the programmer.

It'll be discussed later, for now don't use it. If your chip is being clocked very slowly you'll need to talk slowly to it to let it keep up.

-B : This is for changing the bitrate, which is how fast the programmer talks to the chip.

Don't use this switch, the default is correct.

-b : This is for overriding the serial baud rate for programmers like the STK500.

For example, if you are programming an ATtiny2313, use attiny2313 as the partnumber

-p : This is just to tell it what microcontroller its programming.

Don't try to memorize them, just get a sense of what some of them may do. There are a lot of options, lets review them quickly.

Avrdude gui windows