Many people that are deeper into programming AVRs and use higher-level languages in their daily work recommend that beginners start with learning assembly language. The reason is that sometimes, namely in the following cases: if bugs have to be analyzed, if the program.

How to load programs to an Arduino UNO from Atmel Studio 7 Meet Atmel Studio 7!!! So you want to have a friendly IDE to encode your projects in arduino?

This instructables is usefull if: * you've got your arduino with atmega168 and you bought an atmega328 at you local electronics store. It doesn't have an arduino bootloader * you want to make a project that doesn't use arduino - just a regular AVR chip (like the USBTinyISP) - you have a clean attiny2313/attiny48 etc that you want to burn firmware on. Normally you would have to have an ISP (In System Programmer) like USBTinyISP to program your new chip. Having the arduino you can teach it to be a programmer thank to a great work done by Randall Bohn. He created - an arduino sketch that works like a programmer. There are two ways to connect your Arduino to program a chip.

You can plug your avr chip to a breadboard and connect 5v and GND to the respective pins (check the datasheet!) + a pullup resistor to reset and wire pins from you arduino to the chip. These are the lines on Arduino and their function 13 - SCK 12 - MISO 11 - MOSI 10 - RST (Reset) Or you can make a 2x3pin ISP header that you can plug into a board that provides one (another arduino board). The pinout for the ISP header is on the third image There are 3 leds to indicate the status of the programmer. Pin 9 - blue led - its the hearbeat of the programmer.

Pin 8 - red led - indicates an error pin 7 - green led - indicates that the programming is taking place (i was lazy so i didn't match the colors in my setup) Here are the drawings made in You can alsa make a MEGA-isp shield. Yaroslav Osadchyy designed the shield in eagle. You can get the eagle files on his site: Attachments •. To use with avrdude (and all GUIs that use it) you have to select the 'avrisp' programmer. The safest bitrate is 19200. To test your your new atmega168 from commandline try: $ avrdude -p m168 -P /dev/ttyUSB0 -c avrisp -b 19200 /dev/USB0 is the port that arduino is connected to my linux box (your's may be com5). This can be checked in arduino IDE in Tools ->Serial Port.

You should get: [kabturek@hal-9000 ~]# avrdude -p m168 -P /dev/ttyUSB0 -c avrisp -b 19200 avrdude: AVR device initialized and ready to accept instructions Reading ################################################## 100% 0.13s avrdude: Device signature = 0x1e9406 avrdude: safemode: Fuses OK avrdude done. That means everything is ok. If you get errors - check the last step. The USBTinyISP is a great programmer from LadyAda thats really cheap - 22$. I had a spare attiny2313 and some parts so i decided to make one myself. If you don't have any experience in making PCB i advice you buy the kit cause it's higher quality than you can make yourself:).

At least buy the PCB if you want to build one. You can get it from.

Connect the ATtiny2313 In the last picture you can see the attiny2313 with the pins used for ISP in red. The picture is from. Burning the firmware: Unpack the USBTinyISP firmware.

Go to the spi dir and run $ avrdude -p pt2313 -P /dev/ttyUSB0 -c avrisp -b 19200 to check if everything is ok with the chip. Now set the fuses: $ avrdude -P /dev/ttyUSB0 -c avrisp -b 19200 -pt2313 -U hfuse:w:0xdf:m -U lfuse:w:0xef:m Now you should attach the 12mhz external oscillator to the chip. And burn the firmware: $ avrdude -B 1 -pt2313 -U flash:w:main.hex -P /dev/ttyUSB0 -c avrisp -b 19200 Voila. Your attiny2313 has the USBTinyISP firmware. Connecting I cheated a bit cause i used a RBBB to simplify the connections. The schema is on picture #2. If you use 2 arduinos use the picture #3 and connect the ISP pin to the ICSP 2x3header on the second(slave) arduino.Only connect the usb power to the first board.

The GUI way This is a little tricky cause you can't just use Tools->Burn Bootloader ->w/ AVR ISP cause the default speed is too big for mega-isp. Avrdude errors: avrdude: ser_open(): can't open device '/dev/ttyUSB0': No such file or directory You have the wrong port (-P) specified or your arduino isn't connected. Check the connection avrdude: Device signature = 0x000000 avrdude: Yikes! Invalid device signature. Double check connections and try again, or use -F to override this check. This is kind of general error.

Usb Vid 090c Pid 1000 Rev 1000 Demo. Your chip isn't recognized. Check the connection on the board (GND/5V connected to pins?) You will get this error when your chip is configured to use an external oscillator and it isnt working (there isn't one or it isn't oscillating properl - 22pf caps missing?). There is an alternative set of instructions that works if you have an Arduino Uno and want to transform it into an universal programmer for any stand alone AVR.

Read this tutorial: 'Arduino Uno R3 as a true ISP programmer for any Attiny and Atmega AVR' see: • • No boot-loader has to be first loaded into your target AVR. You can simply program the Attiny or Atmega micro-controllers, existent on the breadboard, directly with the hex file generated from the source code you wrote (Blink a led, for example).

OK now you have a target board and a programmer next you will use the software you installed in step 2 to talk to the chip. This software is very powerful but its also difficult to use the first time. However, you should persevere and after a few times it will become (easier) to use.

Comments? Suggestions? Post to the forum!

Avrdude is a command line program, so you'll have to type in all the commands (later you'll find out how to shortcut this with a Makefile)

Under Windows, you'll need to open up a command window, select Run... from the Start Menu and type in cmd and hit OK.

Under MacOS X, you can use the Terminal program to pull up a command line interface, its in the Utilities folder

Now in the new terminal window type in avrdude you should get this response, which is basically a simple list of what avrdude can do...

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

• -p <partno>: This is just to tell it what microcontroller its programming. For example, if you are programming an ATtiny2313, use attiny2313 as the partnumber
• -b <baudrate>: This is for overriding the serial baud rate for programmers like the STK500. Don't use this switch, the default is correct.
• -B <bitrate>: This is for changing the bitrate, which is how fast the programmer talks to the chip. If your chip is being clocked very slowly you'll need to talk slowly to it to let it keep up. It'll be discussed later, for now don't use it.
• -C <config-file>: The config file tells avrdude about all the different ways it can talk to the programmer. Theres a default configuration file, so lets just use that: don't use this command switch
• -c <programmer>: 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.
• -D: This disables erasing the chip before programming. We don't want that so don't use this command switch.
• -P <port>: This is the communication port to use to talk to the programmer. It might be COM1 for serial or LPT1 for parallel or USB for, well, USB.
• -F: This overrides the signature check to make sure the chip you think you're programming is. The test is strongly recommended as it tests the connection, so don't use this switch.
• -e: This erases the chip, in general we don't use this because we auto-erase the flash before programming.
• -U <memtype>:r|w|v:<filename>[:format]: OK this one is the important command. Its the one that actually does the programming. The <memtype> is either flash or eeprom (or hfuse, lfuse or efuse for the chip configuration fuses, but we aren't going to mess with those). the r|w|v means you can use r (read) w (write) or v (verify) as the command. The <filename> is, well, the file that you want to write to or read from. and [:format] means theres an optional format flag. We will always be using 'Intel Hex' format, so use i
  So, for example. If you wanted to write the file test.hex to the flash memory, you would use -U flash:w:test.hex:i. If you wanted to read the eeprom memory into the file 'eedump.hex' you would use -U eeprom:r:eedump.hex:i
• -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'.
• -V: This turns off the auto-verify when writing. We want to verify when we write to flash so don't use this.
• -u: If you want to modify the fuse bits, use this switch to tell it you really mean it.
• -t: This is a 'terminal' mode where you can type out commands in a row. Don't use this, it is confusing to beginners.
• -E: This lists some programmer specifications, don't use it.
• -v: This gives you 'verbose' output...in case you want to debug something. If you want you can use it, but in general we won't.
• -q: This is the opposite of the above, makes less output. In general we won't use it but maybe after a while you wold like to.

The ones you'll use 99% of the time are highlighted in red. Let's review them in more detail

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. Don't bother memorizing it, just glance through the list.

C:>avrdude -c asdf

avrdude: Can't find programmer id 'asdf'

Valid programmers are:
dasa3 = serial port banging, reset=!dtr sck=rts mosi=txd miso=cts [C:WinAVRbinavrdude.conf:763]
dasa = serial port banging, reset=rts sck=dtr mosi=txd miso=cts [C:WinAVRbinavrdude.conf:750]
siprog = Lancos SI-Prog <http://www.lancos.com/siprogsch.html> [C:WinAVRbinavrdude.conf:737]
ponyser = design ponyprog serial, reset=!txd sck=rts mosi=dtr miso=cts [C:WinAVRbinavrdude.conf:724]
frank-stk200 = Frank STK200 [C:WinAVRbinavrdude.conf:689]
blaster = Altera ByteBlaster [C:WinAVRbinavrdude.conf:676]
ere-isp-avr = ERE ISP-AVR <http://www.ere.co.th/download/sch050713.pdf> [C:WinAVRbinavrdude.conf:666]
atisp = AT-ISP V1.1 programming cable for AVR-SDK1 from <http://micro-research.co.th/> [C:WinAVRbinavrdude.conf:656]
dapa = Direct AVR Parallel Access cable [C:WinAVRbinavrdude.conf:645]
xil = Xilinx JTAG cable [C:WinAVRbinavrdude.conf:632]
futurlec = Futurlec.com programming cable. [C:WinAVRbinavrdude.conf:615]
abcmini = ABCmini Board, aka Dick Smith HOTCHIP [C:WinAVRbinavrdude.conf:605]
picoweb = Picoweb Programming Cable, http://www.picoweb.net/ [C:WinAVRbinavrdude.conf:595]
sp12 = Steve Bolt's Programmer [C:WinAVRbinavrdude.conf:584]
alf = Nightshade ALF-PgmAVR, http://nightshade.homeip.net/ [C:WinAVRbinavrdude.conf:568]
bascom = Bascom SAMPLE programming cable [C:WinAVRbinavrdude.conf:558]
dt006 = Dontronics DT006 [C:WinAVRbinavrdude.conf:548]
pony-stk200 = Pony Prog STK200 [C:WinAVRbinavrdude.conf:536]
stk200 = STK200 [C:WinAVRbinavrdude.conf:520]
bsd = Brian Dean's Programmer, http://www.bsdhome.com/avrdude/ [C:WinAVRbinavrdude.conf:509]
pavr = Jason Kyle's pAVR Serial Programmer [C:WinAVRbinavrdude.conf:501]
dragon_dw = Atmel AVR Dragon in debugWire mode [C:WinAVRbinavrdude.conf:494]
dragon_hvsp = Atmel AVR Dragon in HVSP mode [C:WinAVRbinavrdude.conf:486]
dragon_pp = Atmel AVR Dragon in PP mode [C:WinAVRbinavrdude.conf:478]
dragon_isp = Atmel AVR Dragon in ISP mode [C:WinAVRbinavrdude.conf:470]
dragon_jtag = Atmel AVR Dragon in JTAG mode [C:WinAVRbinavrdude.conf:462]
jtag2dw = Atmel JTAG ICE mkII in debugWire mode [C:WinAVRbinavrdude.conf:454]
jtag2isp = Atmel JTAG ICE mkII in ISP mode [C:WinAVRbinavrdude.conf:446]
jtag2 = Atmel JTAG ICE mkII [C:WinAVRbinavrdude.conf:438]
jtag2fast = Atmel JTAG ICE mkII [C:WinAVRbinavrdude.conf:430]
jtag2slow = Atmel JTAG ICE mkII [C:WinAVRbinavrdude.conf:422]
jtagmkII = Atmel JTAG ICE mkII [C:WinAVRbinavrdude.conf:414]
jtag1slow = Atmel JTAG ICE (mkI) [C:WinAVRbinavrdude.conf:407]
jtag1 = Atmel JTAG ICE (mkI) [C:WinAVRbinavrdude.conf:399]
jtagmkI = Atmel JTAG ICE (mkI) [C:WinAVRbinavrdude.conf:391]
avr911 = Atmel AppNote AVR911 AVROSP [C:WinAVRbinavrdude.conf:385]
avr109 = Atmel AppNote AVR109 Boot Loader [C:WinAVRbinavrdude.conf:379]
butterfly = Atmel Butterfly Development Board [C:WinAVRbinavrdude.conf:373]
usbtiny = USBtiny simple USB programmer [C:WinAVRbinavrdude.conf:367]
usbasp = USBasp, http://www.fischl.de/usbasp/ [C:WinAVRbinavrdude.conf:361]
avr910 = Atmel Low Cost Serial Programmer [C:WinAVRbinavrdude.conf:355]
stk500hvsp = Atmel STK500 V2 in high-voltage serial programming mode [C:WinAVRbinavrdude.conf:349]
stk500pp = Atmel STK500 V2 in parallel programming mode [C:WinAVRbinavrdude.conf:343]
stk500v2 = Atmel STK500 Version 2.x firmware [C:WinAVRbinavrdude.conf:337]
stk500v1 = Atmel STK500 Version 1.x firmware [C:WinAVRbinavrdude.conf:331]
stk500 = Atmel STK500 [C:WinAVRbinavrdude.conf:325]
avrisp2 = Atmel AVR ISP mkII [C:WinAVRbinavrdude.conf:315]
avrispmkII = Atmel AVR ISP mkII [C:WinAVRbinavrdude.conf:309]
avrispv2 = Atmel AVR ISP V2 [C:WinAVRbinavrdude.conf:303]
avrisp = Atmel AVR ISP [C:WinAVRbinavrdude.conf:297]

You'll note that the programmers mentioned before are listed here, including the avrisp, avrispv2, stk500, dragon, dasa/dasa3/ponyser (serial port bitbanging programmers), dapa/dt006/stk200 (parallel port bitbanging programmers)

Look up the name of the programmer you're using, and commit it to heart!

To get a list of parts supported by avrdude, type in avrdude -c avrisp (it doesnt matter if you're not useing an avrisp programmer) without a part number into the command line. Don't memorize this list, just glance over it to get an idea of the chips that are supported.

C:>avrdude -c avrisp
avrdude: No AVR part has been specified, use '-p Part'

Valid parts are:
m6450 = ATMEGA6450 [C:WinAVRbinavrdude.conf:10974]
m3250 = ATMEGA3250 [C:WinAVRbinavrdude.conf:10785]
m645 = ATMEGA645 [C:WinAVRbinavrdude.conf:10596]
m325 = ATMEGA325 [C:WinAVRbinavrdude.conf:10407]
usb1287 = AT90USB1287 [C:WinAVRbinavrdude.conf:10219]
usb1286 = AT90USB1286 [C:WinAVRbinavrdude.conf:10030]
usb647 = AT90USB647 [C:WinAVRbinavrdude.conf:9841]
usb646 = AT90USB646 [C:WinAVRbinavrdude.conf:9651]
t84 = ATtiny84 [C:WinAVRbinavrdude.conf:9468]
t44 = ATtiny44 [C:WinAVRbinavrdude.conf:9286]
t24 = ATtiny24 [C:WinAVRbinavrdude.conf:9104]
m2561 = ATMEGA2561 [C:WinAVRbinavrdude.conf:8911]
m2560 = ATMEGA2560 [C:WinAVRbinavrdude.conf:8718]
m1281 = ATMEGA1281 [C:WinAVRbinavrdude.conf:8530]
m1280 = ATMEGA1280 [C:WinAVRbinavrdude.conf:8341]
m640 = ATMEGA640 [C:WinAVRbinavrdude.conf:8153]
t85 = ATtiny85 [C:WinAVRbinavrdude.conf:7972]
t45 = ATtiny45 [C:WinAVRbinavrdude.conf:7793]
t25 = ATtiny25 [C:WinAVRbinavrdude.conf:7613]
pwm3 = AT90PWM3 [C:WinAVRbinavrdude.conf:7431]
pwm2 = AT90PWM2 [C:WinAVRbinavrdude.conf:7247]
t2313 = ATtiny2313 [C:WinAVRbinavrdude.conf:7060]
m168 = ATMEGA168 [C:WinAVRbinavrdude.conf:6872]
m88 = ATMEGA88 [C:WinAVRbinavrdude.conf:6686]
m48 = ATMEGA48 [C:WinAVRbinavrdude.conf:6499]
t861 = ATTINY861 [C:WinAVRbinavrdude.conf:6311]
t461 = ATTINY461 [C:WinAVRbinavrdude.conf:6122]
t261 = ATTINY261 [C:WinAVRbinavrdude.conf:5933]
t26 = ATTINY26 [C:WinAVRbinavrdude.conf:5776]
m8535 = ATMEGA8535 [C:WinAVRbinavrdude.conf:5618]
m8515 = ATMEGA8515 [C:WinAVRbinavrdude.conf:5460]
m8 = ATMEGA8 [C:WinAVRbinavrdude.conf:5300]
m161 = ATMEGA161 [C:WinAVRbinavrdude.conf:5160]
m32 = ATMEGA32 [C:WinAVRbinavrdude.conf:4985]
m6490 = ATMEGA6490 [C:WinAVRbinavrdude.conf:4792]
m649 = ATMEGA649 [C:WinAVRbinavrdude.conf:4607]
m3290 = ATMEGA3290 [C:WinAVRbinavrdude.conf:4424]
m329 = ATMEGA329 [C:WinAVRbinavrdude.conf:4239]
m169 = ATMEGA169 [C:WinAVRbinavrdude.conf:4059]
m163 = ATMEGA163 [C:WinAVRbinavrdude.conf:3916]
m162 = ATMEGA162 [C:WinAVRbinavrdude.conf:3720]
m644 = ATMEGA644 [C:WinAVRbinavrdude.conf:3530]
m324 = ATMEGA324 [C:WinAVRbinavrdude.conf:3338]
m164 = ATMEGA164 [C:WinAVRbinavrdude.conf:3146]
m16 = ATMEGA16 [C:WinAVRbinavrdude.conf:2968]
c128 = AT90CAN128 [C:WinAVRbinavrdude.conf:2777]
m128 = ATMEGA128 [C:WinAVRbinavrdude.conf:2599]
m64 = ATMEGA64 [C:WinAVRbinavrdude.conf:2418]
m103 = ATMEGA103 [C:WinAVRbinavrdude.conf:2278]
8535 = AT90S8535 [C:WinAVRbinavrdude.conf:2157]
8515 = AT90S8515 [C:WinAVRbinavrdude.conf:2043]
4434 = AT90S4434 [C:WinAVRbinavrdude.conf:1960]
4433 = AT90S4433 [C:WinAVRbinavrdude.conf:1836]
2343 = AT90S2343 [C:WinAVRbinavrdude.conf:1712]
2333 = AT90S2333 [C:WinAVRbinavrdude.conf:1627]
2313 = AT90S2313 [C:WinAVRbinavrdude.conf:1514]
4414 = AT90S4414 [C:WinAVRbinavrdude.conf:1401]
1200 = AT90S1200 [C:WinAVRbinavrdude.conf:1286]
t15 = ATtiny15 [C:WinAVRbinavrdude.conf:1153]
t13 = ATtiny13 [C:WinAVRbinavrdude.conf:980]
t12 = ATtiny12 [C:WinAVRbinavrdude.conf:847]
t11 = ATtiny11 [C:WinAVRbinavrdude.conf:783]

That's all the chips that avrdude knows about. Almost all of them are ISP programmable.

Watch out: t2313 and 2313, m8 and m88, c128 and m128, etc look very similar but they are in fact quite different chips! For that reason I suggest you type out the name of the chip, that is, instead of t2313 use attiny2313 or m8 use atmega8. Avrdude is smart enough to know what you mean if you type out the full name.

We're going to use the ATtiny2313 so use the part number attiny2313 or (t2313)

Double check what chip you are using by looking at the top of the chip, these say ATTINY2313 and ATMEGA8 (respectively) the -20PI and -16PC are just the speed ratings and package descriptions so ignore them for now.

This switch tells avrdude where to look for your programmer. If you are using a USB connected device, you can just use -P usb or, leave it out. The programmer automatically knows when the programmer is a USB device.

If you are using a parallel port or serial port programmer, you should use this option to indicate what port the programmer is connected to. 99% of the time its lpt1 (parallel) or com1 (serial) but you can always check it by looking under the Device Manager. Open the System Properties control panel

Click on Device Manager, and open up the Ports submenu.

All of the serial and parallel ports are listed. There may be multiple COM ports but there's usually only one parallel (printer) port.