Revision History
Revision 442009-04-20 17:13:07Revised by: jdd
obfuscate e-mail at the author demand
Revision 432009-03-29 20:49:12Revised by: ranjeeth
Revision 422009-03-29 20:45:09Revised by: jdd
reverting after publication
Revision 412009-03-29 20:41:59Revised by: jdd
edit to export docbook
Revision 402009-03-28 21:07:57Revised by: RickMoen
Adjust style of mailto link to author's original preference.
Revision 392009-03-28 21:05:45Revised by: RickMoen
Revert e-mail obfuscation, supply some missing punctuation, [re-]fix capitalisation, fix and clarify new run-on sentence.
Revision 382009-03-23 18:21:24Revised by: ranjeeth
Revision 372009-03-23 18:19:51Revised by: ranjeeth
Revision 362009-03-23 17:20:32Revised by: ranjeeth
Revision 352009-03-23 17:19:47Revised by: ranjeeth
Revision 342009-03-23 10:26:00Revised by: jdd
publishing tests
Revision 332009-03-23 10:25:06Revised by: jdd
Revision 322009-03-23 10:24:24Revised by: jdd
use of macro to obfuscate e-mail
Revision 312009-03-23 10:11:47Revised by: jdd
change was only to export docbook without admonitions
Revision 302009-03-23 10:09:15Revised by: jdd
Revision 292009-03-23 10:05:07Revised by: jdd
Revision 282009-03-23 09:58:40Revised by: jdd
adding the wiki as link
Revision 272009-03-23 09:53:28Revised by: RickMoen
Insert needed space characters into "pin9", "pin10", "pin25" constructs
Revision 262009-03-23 09:49:05Revised by: RickMoen
Make markup of all the software items mentioned be consistent
Revision 252009-03-23 09:43:40Revised by: RickMoen
Remove a couple of stray commas.
Revision 242009-03-23 09:41:30Revised by: RickMoen
Polishing up a few last bits of punctuation
Revision 232009-03-23 04:11:31Revised by: ranjeeth
Revision 222009-03-23 04:10:34Revised by: ranjeeth
Revision 212009-03-23 04:09:07Revised by: ranjeeth
Revision 202009-03-17 16:20:27Revised by: ranjeeth
Revision 192009-03-17 16:18:33Revised by: ranjeeth
Revision 182009-03-16 19:10:30Revised by: RickMoen
Fix hyperlink, fix English diction of new sentence.
Revision 172009-03-16 18:50:19Revised by: ranjeeth
Revision 162009-03-16 11:36:49Revised by: RickMoen
A couple of punctuation nits
Revision 152009-03-16 11:21:14Revised by: RickMoen
Corrected numerous run-on sentences, punctuation and grammar errors, and questionable idiom.
Revision 142009-03-15 10:27:24Revised by: BordenRhodes
Cleaned up basic grammar and spelling
Revision 132009-03-15 09:52:41Revised by: jdd
Revision 122009-03-15 09:51:37Revised by: jdd
add link to the manual of avr-libc
Revision 112009-03-14 21:47:18Revised by: jdd
end of basic conversion
Revision 102009-03-14 21:40:18Revised by: jdd
Revision 92009-03-14 21:39:26Revised by: jdd
Revision 82009-03-14 21:33:04Revised by: jdd
add the image
Revision 72009-03-14 21:27:59Revised by: jdd
Revision 62009-03-14 21:26:48Revised by: jdd
Revision 52009-03-14 21:25:13Revised by: jdd
Firts step - conversion fro html by jdd and basic format edition
Revision 42009-03-14 21:22:37Revised by: jdd
Revision 32009-03-14 21:18:25Revised by: jdd
Revision 22009-03-14 21:13:09Revised by: jdd
Revision 12009-03-14 21:10:33Revised by: jdd

Table of Contents
2. AVR Microcontrollers in Linux HOWTO
2.1. Licence
2.2. What Is a Microcontroller?
2.3. Software Required
2.4. Hello World
2.5. Author
2.6. Last version


AVR Microcontrollers in Linux HOWTO, Copyright (C) 2009 Ranjeeth p t (ranjeeth_gecmail[at]yahoo[dot]com)

This HOWTO is for readers wishing to program an AVR microcontroller using a GNU/Linux machine. For burning your code, we will be using a parallel port. You may need other electronics components (like a few resistors, capacitors, parallel port connector, etc.), which can be bought from any electronics shop.

2. AVR Microcontrollers in Linux HOWTO

2.1. Licence

      Permission is granted to copy, distribute, and/or modify this
      document under the terms of the GNU Free Documentation License,
      Version 1.2, or any later version published by the Free Software
      Foundation; with no Invariant Sections, no Front-Cover Texts, and
      no Back-Cover Texts.  A copy of the license is included in the
      section entitled "GNU Free Documentation License".

GNU Free Documentation License

2.2. What Is a Microcontroller?

A microcontroller is a single-chip computer. It has internal RAM, ROM, timers, counters, interrupt circuitry, I/O ports, analog comparators, serial USARTs, analog to digital converters, watchdog timers, and a RISC architecture. When you are using a microprocessor, you cannot program it alone. You need other components, like RAM, ROM, timers, etc. For programming, you should know its architecture thoroughly: You must read the datasheet for your microcontroller.

2.3. Software Required

binutils: Tools like the assembler, linker, etc.

gcc-avr: The GNU C compiler (cross-compiler for avr).

avr-libc: Package for the AVR C library, containing many utility functions.

uisp: A Micro In-System Programmer for Atmel's AVR MCUs (for burning code to MCUs' memory).

The following Atmel microcontrollers are supported by avr-gcc in Linux:

at90s Type Devices

at90s2313, at90s2323, at90s2333, at90s2343, at90s4414, at90s4433, at90s4434, at90s8515, at90s8515, at90s8515, at90s8535, at90s1200.

atmega Type Devices

atmega103, atmega603, atmega8, atmega48, atmega88, atmega8515, atmega8535, atmega16, atmega161, atmega162, atmega163, atmega165, atmega168, atmega169, atmega32, atmega323, atmega325, atmega3250, atmega64, atmega645, atmega6450, atmega128.

attiny Type Devices

attiny22, attiny26, attiny26, attiny13, attiny13, attiny13, attiny13, attiny2313, attiny11, attiny12, attiny15, attiny28.

Other AVR Devices

avr2, at90c8534, at86rf401, avr3, at43usb320, at43usb355, at76c711, avr4, avr5, at90can128, at94k, avr1.

binutils: Programs to manipulate binary and object files that may have been created for Atmel's AVR architecture. This package is primarily for AVR developers and cross-compilers.

gcc-avr: The GNU C compiler, a fairly portable optimising compiler that supports multiple languages. This package includes C language support.

avr-libc: Standard library used for developing C programs for Atmel AVR microcontrollers. This package contains static libraries, as well as needed header files.

uisp: Utility to program AVR chips with object code created by gcc-avr. It supports in-system programming.

You download the above packages untar, configure, and install it. If you are using Debian or Ubuntu, these packages are available in your distribution: Install them using apt or synaptic package manager.

2.4. Hello World

We are writing hello world for the atmega8 microcontroller, which has a 28-pin, 8-bit, RISC architecture.

Before proceeding, have a look at this manual about __avr-libc__, which will help you program better, and understand. Also, refer to the datasheets for the various AVR microcontrollers.

Here is our first program:

/* ledblink.c, an LED blinking program */
void sleep(uint8_t millisec)

                _delay_ms(1);/* 1 ms delay */

        DDRC |=1<<PC2;  /* PC2 will now be the output pin */
                PORTC &= ~(1<<PC2);/* PC2 LOW */
                sleep(100);/* 100 ms delay */

                PORTC |=(1<<PC2); /* PC2 HIGH */
                sleep(100);/* 100 ms delay */

2.4.1. Code Explanation

The GNU C compiler for the Atmel family identifies all functional units within the microcontroller with meaningful names. Thus, writing `PORTC=0xff' will result in the compiler generating machine code that writes 0xff to I/O port C, which will set all port C pins to logic high. Because ports are bidirectional, we must decide whether each pin should act as input or output. If the i'th bit of a register called DDRC (data direction register C) is 1, then the i'th pin of PORTC's i'th pin will be an output. Otherwise, it will act as an input pin. (Note that pin and bit numbers start at zero.) To make an LED blink, you have to make a pin high, then low. (Here, we use PORTC's 2nd port. That is, PC2 will be the 25th pin.) There should be a delay between the two. This is what the rest of the code does. For the delay, we use built-in function _delay_ms(1), which causes a 1 ms delay.

2.4.2. Compilation

avr-gcc -mmcu=atmega8 Os ledblink.c o ledblink.o

which will result in object file ledblink.o. Now, we will covert it to hex file, suitable for burning to the microcontroller's memory.

avr-objcopy -j .text -j .data -O ihex  ledblink.o  ledblink.hex

We are converting it to a hex file because, for burning the code to atmega8, we will use uisp, whose input file must be a .hex file.

Notice that you can less the ledblink.hex file.



2.4.3. Burning the Code Hardware

We will be using the parallel port for burning. First, we have to develop a burning circuit for it.

This is the circuit for the atmega8 microcontroller. Pin 9 & pin 10 are connected by a 4 MHz crystal oscillator, which is the external clock. The bottom right connector is for a parallel port.

If you are using any other microcontroller, as mentioned above, you should change accordingly. }}}

You should watch for RESET,XTAL1,XTAL2,SCK,MISO,MOSI pins, and connect. Software

Now, we will burn ledblink.hex to the microcontroller.

uisp -dprog=dapa -dlpt=0x378

You should get message Atmega8 Found.

dprog is the programming method specifier, which in this case is dapa, i.e., Direct AVR Parallel Access. dlpt is for the parallel device setting, which is 0x378, the parallel port's device address.

uisp -dprog=dapa -dlpt=0x378 --erase

Will erase the microcontroller's code.

uisp -dprog=dapa -dlpt=0x378 --upload if=ledblink.hex

Will upload the Input File ledblink.hex

Notice that you can see the LED at pin 25 blinking.

2.5. Author

Comments to: mailto:ranjeeth_gecmail[at]yahoo[dot]com

Ranjeeth Weblog

Govt Engg College Sreekrishnapuram,

Palakkad,Kerala India.

2.6. Last version

You may find the last up-to-date version of this HOWTO on the LDP wiki.