Difference between revisions of "AVR"

From CCRMA Wiki
Jump to: navigation, search
Line 70: Line 70:
  
 
The avrlib-demos can reside anywhere, but they assume that the avrlib is in your home directory.
 
The avrlib-demos can reside anywhere, but they assume that the avrlib is in your home directory.
 
+
----
 
===Linux Machines at CCRMA===
 
===Linux Machines at CCRMA===
 
The Linux machines at CCRMA already have the AVR development tools installed, and in your path. All you need to do is get a copy of the AVRlib. The avrlib-demos are helpful in getting started.
 
The Linux machines at CCRMA already have the AVR development tools installed, and in your path. All you need to do is get a copy of the AVRlib. The avrlib-demos are helpful in getting started.
Line 94: Line 94:
 
</pre>
 
</pre>
 
You can update them with <tt>svn update</tt> as well. The avrlib-demos can reside anywhere, but they assume that the avrlib is in your home directory.
 
You can update them with <tt>svn update</tt> as well. The avrlib-demos can reside anywhere, but they assume that the avrlib is in your home directory.
 
+
----
 
+
 
===PlanetCCRMA Linux on your own PC===
 
===PlanetCCRMA Linux on your own PC===
  
Line 109: Line 108:
 
----
 
----
  
===Mac OS X / Other *nix===
+
===Mac OS X / Linux===
 
These instructions are excerpted from [http://www.nongnu.org/avr-libc/user-manual/install_tools.html avr-libc" Installing the GNU Tool Chain].
 
These instructions are excerpted from [http://www.nongnu.org/avr-libc/user-manual/install_tools.html avr-libc" Installing the GNU Tool Chain].
 
====Mac OS X: The Easy Way====
 
====Mac OS X: The Easy Way====
Line 138: Line 137:
 
~> sudo mv avr /usr/local
 
~> sudo mv avr /usr/local
  
4. Add /usr/local/avr/bin to your Unix path. For example, if you use the tcsh shell, add this line to the file .cshrc in your home directory:
+
3. Add /usr/local/avr/bin to your Unix path. For example, if you use the tcsh shell, add this line to the file .cshrc in your home directory:
 
<pre>
 
<pre>
 
set path=($path /usr/local/avr/bin)
 
set path=($path /usr/local/avr/bin)
Line 151: Line 150:
  
  
====
+
====Linux / Mac OS X (the not-so easy way)====
Required Tools:
+
This requires compiling the tools from source. It is not too difficult, but may take some time, depending on your bandwidth and CPU speed. On a Mac, this assumes you have the [http://developer.apple.com/tools Apple's developer tools] installed. On Linux, it assumes you have gcc and a basic operational build setup.
 +
 
 +
First, you need to download the following sources (either .tar.gz or .tar.bz2):
 
*GNU Binutils (currently at version 2.17)
 
*GNU Binutils (currently at version 2.17)
 
[http://sources.redhat.com/binutils/ http://sources.redhat.com/binutils/]
 
[http://sources.redhat.com/binutils/ http://sources.redhat.com/binutils/]

Revision as of 17:34, 20 February 2007

AVR Microcontrollers

AVR 8-bit RISC microcontrollers by Atmel are currently at the heart of the embedded technology platform we use in Physical Interaction Design research and courses at CCRMA. These chips have a modern Harvard Architecture, executing most instruction cycles in a single clock cycle. An extremely efficient open source C compiler is available, and these devices are used and supported by a large community of developers. The AVR architecture and instruction set is available in a large family of 8-bit devices that come in a variety of packages. AVR-series chips come with as little as 1 Kbyte of Flash program memory, up to 256 Kbytes; 32 bytes to 8 Kbytes of RAM; and up to 20 MHz clock speeds. Specialized AVR devices exist for automotive, LCD and lighting control, USB and radio applications. Code is easily portable between devices.

AVR Hardware at CCRMA

ATMega32

We currently use the ATMega 32 (Product Page). It features:

  • 32 Kbyte self-programming Flash Program Memory
  • 2 Kbyte SRAM
  • 1 Kbyte EEPROM
  • 8-Channel 10-bit A/D-converter
  • Up to 16 Mhz clock
  • I2C, SPI interfaces
  • 1 USART, 2-channels PWM, 2 ext. interrupts

ATMega 32 Documentation:

AVRmini Development Board

The AVRmini development board, made by Pascal Stang, is a general purpose prototyping board that provides easy access to the AVR's I/O and programming interfaces, along with a number of useful peripheral devices. We are currently using the AVRmini v4.0. The AVRmini v4.0 provides:

  • Support for most 40-pin AVR processors
  • Ethernet, USB, SD/MMC, RS-232 I/O
  • I2C header
  • Character LCD header
  • 10-pin I/O headers
  • 4 buttons and 4 LEDs
  • 5-V regulator

AVRmini Documentation:

CCRMA's AVR Prototyping Kit

For our PID courses at CCRMA, we assemble a prototyping kit based on the AVRmini. We mount the AVRmini on a sheet of 1/8" acrylic, and add solderless breadboard strips, an LCD display and a small loudspeaker. Pins 9 and 10 of the AVRmini v4.0's "AUX" header (JP13) are connected to the ground and +5V power rails of the breadboard strips.

  • kit Photo

Spyglass User Interface Board

The LCD display on CCRMA's prototyping board is part of the Spyglass User interface Board, which communicates with the AVR via I2C. We purchased these on eBay, and from a few other places, but they are hard to come by these days. Pascal Stang has written a brief Spyglass User Guide. He has also developed a replacement I2C button module/LCD driver (no documentation available) to which we can connect an LCD display and use just like the Spyglass.

  • Spyglass photo
  • buttonmodule photo


AVR Software at CCRMA

AVRLib

avr-gcc

Setting up your Computer to do AVRLib / CCRMA-Style AVR Development

ALL PLATFORMS

avrlib

No matter what platform you use, you need to get the avrlib. If you are using a Linux machine at CCRMA, see the next section for the best way to do this. Otherwise, you can download the avrlib here:

and decompress it into your home directory. On a Linux or Mac system you can do this with:

~> tar xzf avrlib_ccrma20070124.tar.gz

avrlib-demos

A set of demo programs to demonstrate the basic functionalities of the AVRlib and AVRmini are also available:

Again on Linux or Mac, you can decompress them with:

~/somewhere> tar xzf avrlib-demos20070124.tar.gz

The avrlib-demos can reside anywhere, but they assume that the avrlib is in your home directory.


Linux Machines at CCRMA

The Linux machines at CCRMA already have the AVR development tools installed, and in your path. All you need to do is get a copy of the AVRlib. The avrlib-demos are helpful in getting started.

To get the most up-to-date versions, use subversion.

avrlib

In a terminal, change into your home directory, and then type:

~> svn checkout file:///usr/ccrma/group/pid/avr/svn/avrlib ./avrlib

This will create an avrlib directory in your home directory. You can update it anytime from a terminal, by changing into the avrlib directory and typing:

~/avrlib> svn update

avrlib-demos

To get the avrlib-demos with subversion:

~/somewhere> svn checkout file:///usr/ccrma/group/pid/avr/svn/avrlib-demos ./avrlib-demos

You can update them with svn update as well. The avrlib-demos can reside anywhere, but they assume that the avrlib is in your home directory.


PlanetCCRMA Linux on your own PC

AVR Development Tools

If you have PlanetCCRMA installed on your PC, then you just need to make sure that you have the AVR development packages installed, using yum or apt.

For Fedora Core 4, the AVR compiler tools are under Applications/Development. The AVR downloading/programming tools are under Development/Tools.

AVRlib and avrlib-demos

Download the avrlib and avrlib-demos as described above. Note that you need to get the .tar.gz files, as the svn repository is not available outside of CCRMA.


Mac OS X / Linux

These instructions are excerpted from avr-libc" Installing the GNU Tool Chain.

Mac OS X: The Easy Way

1.You need the gnumake program, and you also need a symbolic link to it called make.

There are two options: i) Install Apple's developer tools, which include gnumake and much, much, much more. If you want to develop OSX applications you probably want or already have these anyway. They have a fancy easy-to-use installer.

ii) Alternately, you could just download my copy of gnumake: For PPC: osx-gnumake.tar.gz For Intel:

Then, unstuff it, and install the resulting file like this:

~> tar xzf osc-gnumake.tar.gz
~> sudo mv gnumake /usr/bin
~> sudo ln -s /usr/bin/gnumake /usr/bin/make

2. Download, un-stuff this archive and put the resulting avr directory in /usr/local, which you may need to create if it doesn't exist:

  • usr-local-avr_ppc.tar.gz (35 MB - PowerPC)
  • usr-local-avr_intel.tar.gz (xx MB - Intel)

You will probably need to do this as administrator, i.e.

~> tar xzf usr-local-avr_ppc.tar.gz
~> sudo mv avr /usr/local

3. Add /usr/local/avr/bin to your Unix path. For example, if you use the tcsh shell, add this line to the file .cshrc in your home directory:
<pre>
set path=($path /usr/local/avr/bin)

If you use the bash shell, add these two lines to the .bash_profile file in your home directory:

PATH=$PATH:/usr/local/avr/bin
export PATH


Linux / Mac OS X (the not-so easy way)

This requires compiling the tools from source. It is not too difficult, but may take some time, depending on your bandwidth and CPU speed. On a Mac, this assumes you have the Apple's developer tools installed. On Linux, it assumes you have gcc and a basic operational build setup.

First, you need to download the following sources (either .tar.gz or .tar.bz2):

  • GNU Binutils (currently at version 2.17)

http://sources.redhat.com/binutils/

  • GCC (currently at version 4.1.2)

http://gcc.gnu.org/

  • avr-libc (currently at version 1.4.5)

http://savannah.gnu.org/projects/avr-libc/

  • avrdude (currently at version 5.3.1)

http://savannah.nongnu.org/projects/avrdude/

Windows

Communicating with Pd via OSC over USB

Linux Machines at CCRMA

PlanetCCRMA Linux on your own PC

Mac OS X

Windows

Communicating with Max/MSP via OSC over USB

Mac OS X

Windows

Communicating via OSC over udp