![using atmel dragon arduino programmers.txt using atmel dragon arduino programmers.txt](https://visualgdb.com/w/wp-content/uploads/2018/08/02-jtag1.jpg)
Don't bother memorizing it, just glance through the list.ĭasa3 = serial port banging, reset=!dtr sck=rts mosi=txd miso=cts ĭasa = serial port banging, reset=rts sck=dtr mosi=txd miso=cts To get a list of supported programmers, type in avrdude -c asdf ( asdf is just some nonsense to get it to spit out the list of programmers) Here is my output, yours may vary a little. The ones you'll use 99% of the time are highlighted in red. In general we won't use it but maybe after a while you wold like to. -q: This is the opposite of the above, makes less output.If you want you can use it, but in general we won't. -v: This gives you 'verbose' output.in case you want to debug something.-E: This lists some programmer specifications, don't use it.Don't use this, it is confusing to beginners. -t: This is a 'terminal' mode where you can type out commands in a row.-u: If you want to modify the fuse bits, use this switch to tell it you really mean it.We want to verify when we write to flash so don't use this. -V: This turns off the auto-verify when writing.-n: This means you don't actually write anything, its good if you want to make sure you don't send any other commands that could damage the chip, sort of a 'safety lock'.If you wanted to read the eeprom memory into the file "eedump.hex" you would use -U eeprom:r:eedump.hex:i If you wanted to write the file test.hex to the flash memory, you would use -U flash:w:test.hex:i.
![using atmel dragon arduino programmers.txt using atmel dragon arduino programmers.txt](https://wa2mze.files.wordpress.com/2021/11/20211117_160847.jpg)
We will always be using "Intel Hex" format, so use i and means theres an optional format flag. The is, well, the file that you want to write to or read from. the r|w|v means you can use r (read) w (write) or v (verify) as the command. 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.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.