PID2008 Lab 1

From CCRMA Wiki

(Difference between revisions)
Jump to: navigation, search
Line 3: Line 3:
The goal of this lab is to become familiar with the ins and outs of programming on the AVR mini.
The goal of this lab is to become familiar with the ins and outs of programming on the AVR mini.
-
'''0. Set up your environment to use the AVR'''
 
-
'''a. Follow OS specific instructions for installing the [[AVR]] environment'''
+
==Set up your environment to use the AVR==
 +
 
 +
===Follow OS specific instructions for installing the [[AVR]] environment===
* In all cases, this entails downloading the avrlib to your home directory. At CCRMA, it is easiest to use subversion:
* In all cases, this entails downloading the avrlib to your home directory. At CCRMA, it is easiest to use subversion:
Line 12: Line 13:
     ~> svn checkout file:///usr/ccrma/group/pid/avr/svn/avrlib ./avrlib
     ~> svn checkout file:///usr/ccrma/group/pid/avr/svn/avrlib ./avrlib
-
'''b. Create a pid2007 directory and copy the avrlib-demos to it'''
+
===Create a pid2007 directory and copy the avrlib-demos to it===
     ~> mkdir pid2007
     ~> mkdir pid2007
Line 18: Line 19:
     ~/pid2007> svn checkout file:///usr/ccrma/group/pid/avr/svn/avrlib-demos ./avrlib-demos
     ~/pid2007> svn checkout file:///usr/ccrma/group/pid/avr/svn/avrlib-demos ./avrlib-demos
-
'''c. Make a directory for Lab 1 in your pid2007 directory'''
+
===Make a directory for Lab 1 in your pid2007 directory===
     ~/pid2007> mkdir lab1
     ~/pid2007> mkdir lab1
-
'''d. Set up AVR connection to PC'''
+
===Set up AVR connection to PC===
*Connect power cable, connect USB cable, and power-up the AVRmini
*Connect power cable, connect USB cable, and power-up the AVRmini
-
'''e. Test AVR setup with "flash" test code'''
+
===Test AVR setup with "flash" test code===
*Make yourself a copy of the FLASH demo from avrlib-demos:
*Make yourself a copy of the FLASH demo from avrlib-demos:
Line 46: Line 47:
*If everything is working, an LED on the AVRmini board should start flashing.
*If everything is working, an LED on the AVRmini board should start flashing.
-
'''1. AVRMini Input/Output'''
+
==AVRMini Input/Output==
-
'''a. Review architecture and programming, as necessary'''
+
===a. Review architecture and programming, as necessary===
* [[Microcontroller Architecture]]
* [[Microcontroller Architecture]]
* [[AVR Programming]]
* [[AVR Programming]]
-
'''b. Momentary pushbutton'''
+
===b. Momentary pushbutton===
* Copy the BUTTON program from the avrlib-demos to your Lab 1 folder:
* Copy the BUTTON program from the avrlib-demos to your Lab 1 folder:
Line 78: Line 79:
Optional: Toggle pushbutton using debounce.
Optional: Toggle pushbutton using debounce.
-
    * Compile and load TOGGLE from the avrlib-demos
+
* Compile and load TOGGLE from the avrlib-demos
-
                       ~> cd ~/250a/lab2
+
                       ~> cd ~/pid2007/lab2
-
             ~/250a/lab2> cp -r ../avrlib-demos/toggle .  
+
             ~/pid2007/lab2> cp -r ../avrlib-demos/toggle .  
-
             ~/250a/lab2> cd toggle
+
             ~/pid2007/lab2> cd toggle
-
       ~/250a/lab2/toggle> make load
+
       ~/pid2007/lab2/toggle> make load
-
    * Look at the code in an editor. Compare button.c and toggle.c. Why is there a debounce mechanism in toggle.c but not in button.c? How does the debounce mechanism work?
+
* Look at the code in an editor. Compare button.c and toggle.c. Why is there a debounce mechanism in toggle.c but not in button.c? How does the debounce mechanism work?
-
    * What happens if you change the debounce threshold to 1? (hint - try toggling the LED 10 times)
+
* What happens if you change the debounce threshold to 1? (hint - try toggling the LED 10 times)
-
    * What happens if you change the debounce threshold to 30000?
+
* What happens if you change the debounce threshold to 30000?
-
    * Can you change it to 100000? (hint - you need to change something else, too. DO NOT SPEND MORE THAN 5 MINUTES TRYING TO FIGURE THIS OUT!)
+
* Can you change it to 100000? (hint - you need to change something else, too. DO NOT SPEND MORE THAN 5 MINUTES TRYING TO FIGURE THIS OUT!)
-
    * Especially optional section: instruction counting and timing
+
* Especially optional section: instruction counting and timing
-
          o Really, we mean it, don't waste time on this unless it fascinates you
+
** Really, we mean it, don't waste time on this unless it fascinates you
-
                      # Create the file button.ss by typing make button.ss
+
*** Create the file button.ss by typing make button.ss
-
                      # Look at button.ss - these are the instructions that are actually written to the microprocessor.
+
*** Look at button.ss - these are the instructions that are actually written to the microprocessor.
-
                      # Look in the two sections <checkButton> and <main>. Each line corresponds to one instruction of the microprocessor. What debounce threshold value would give approximately 1 second of delay between the button press and the LED lighting up? (Hint: you will need to look at the Atmel Instruction Set documentation.)
+
*** Look in the two sections <checkButton> and <main>. Each line corresponds to one instruction of the microprocessor. What debounce threshold value would give approximately 1 second of delay between the button press and the LED lighting up? (Hint: you will need to look at the Atmel Instruction Set documentation.)
-
    * Why is using a very high debounce threshold a bad way to implement a 1 second delay? (There are at least three good reasons.)
+
* Why is using a very high debounce threshold a bad way to implement a 1 second delay? (There are at least three good reasons.)
-
    * The best way to implement a 1 second delay is with the timer library in avrlib. Put the debounce threshold back to a reasonable value for debouncing and reintroduce the 1 second delay properly:
+
* The best way to implement a 1 second delay is with the timer library in avrlib. Put the debounce threshold back to a reasonable value for debouncing and reintroduce the 1 second delay properly:
-
          o Add #include "timer.h" at the top of toggle.c
+
** Add #include "timer.h" at the top of toggle.c
-
          o Add timerInit(); to the beginning of your main() procedure but after your varaible declariations..
+
** Add timerInit(); to the beginning of your main() procedure but after your varaible declariations..
-
          o Add a call to the timerPause() procedure in the right place in your program.
+
** Add a call to the timerPause() procedure in the right place in your program.
-
          o In your makefile, add $(AVRLIB)/timer.c to the list of files in the definition of SRC
+
** In your makefile, add $(AVRLIB)/timer.c to the list of files in the definition of SRC
             The new makefile line should look like this: SRC= $(TRG).c $(AVRLIB)/timer.c  
             The new makefile line should look like this: SRC= $(TRG).c $(AVRLIB)/timer.c  
-
    * Find the maximum delay time before you can notice a pause between the button press and the LED illuminating.
+
* Find the maximum delay time before you can notice a pause between the button press and the LED illuminating.
-
c. Four buttons:
+
=== Four buttons===
-
    * Write a program to control 4 LEDs with 4 buttons. It's up to you to do some "interaction design": think of your own way for actions with the four buttons to control the states of the LEDs. Feel free to write this program from scratch, but we recommend that you start with the FOURTOGGLE demo.
+
* Write a program to control 4 LEDs with 4 buttons. It's up to you to do some "interaction design": think of your own way for actions with the four buttons to control the states of the LEDs. Feel free to write this program from scratch, but we recommend that you start with the FOURTOGGLE demo.
-
d. Beep:
+
=== Beep ===
-
    * Load BUTTONBEEP as you did BUTTON and FLASH above.
+
* Load BUTTONBEEP as you did BUTTON and FLASH above.
-
    * Make sure the blue wire from your speaker is connected to pin D5 and the black wire from the speaker to ground.
+
* Make sure the blue wire from your speaker is connected to pin D5 and the black wire from the speaker to ground.
-
    * You should hear a beep when you press SW4.
+
* You should hear a beep when you press SW4.
-
    * Try inserting a pause between turning on the LED and playing the beep. In case you didn't do part 3b, here are the step-by-step instructions for using the avrlib's timer facilities:
+
* Try inserting a pause between turning on the LED and playing the beep. In case you didn't do part 3b, here are the step-by-step instructions for using the avrlib's timer facilities:
-
          o Add #include "timer.h" at the top of buttonbeep.c
+
** Add #include "timer.h" at the top of buttonbeep.c
-
          o Add timerInit(); to the beginning of your main() procedure.
+
** Add timerInit(); to the beginning of your main() procedure.
-
          o Add a call to the timerPause() procedure in the right place in your program.
+
** Add a call to the timerPause() procedure in the right place in your program.
-
          o In your makefile, add $(AVRLIB)/timer.c to the list of files in the definition of SRC
+
** In your makefile, add $(AVRLIB)/timer.c to the list of files in the definition of SRC
-
    * At what point does the delay become noticeable? What if the beep comes before the light?
+
** At what point does the delay become noticeable? What if the beep comes before the light?
-
    * Try finding the largest unnoticeable delay time as in #3 using the beep as feedback. Is it different?
+
* Try finding the largest unnoticeable delay time as in #3 using the beep as feedback. Is it different?
-
3. Compile, Run and Play the AVRsimon:
+
== Compile, Run and Play the AVRsimon==
-
    * Compile the code and program the AVR:
+
* Compile the code and program the AVR:
-
       cd ~/250a/lab2
+
       cd ~/pid2007/lab2
       cp -r ../avrlib-demos/avrsimon .  
       cp -r ../avrlib-demos/avrsimon .  
       cd avrsimon  
       cd avrsimon  
       make load
       make load
-
    * You should now be able to play the Simon game provided. Pay attention to things you like and dislike about the flow of the game and the interaction.
+
* You should now be able to play the Simon game provided. Pay attention to things you like and dislike about the flow of the game and the interaction.
-
    * The first sequence that is played should be random. Why isn't it? Fix it (without using a random number generator in C).
+
* The first sequence that is played should be random. Why isn't it? Fix it (without using a random number generator in C).
-
    * Improve the game to make it more interesting and engaging. Here are some suggestions, but feel free to come up with others:
+
* Improve the game to make it more interesting and engaging. Here are some suggestions, but feel free to come up with others:
-
          o Keep stats - this is an easy addition involving adding two counters for correct and incorrect performance, and adding a way to start a new game without the reset button.
+
** Keep stats - this is an easy addition involving adding two counters for correct and incorrect performance, and adding a way to start a new game without the reset button.
-
          o Add levels of play - make it get progressively more difficult (e.g., longer patterns, increasing tempo)
+
** Add levels of play - make it get progressively more difficult (e.g., longer patterns, increasing tempo)
-
          o Add additional buttons and LEDs using the solderless breadboard
+
** Add additional buttons and LEDs using the solderless breadboard
-
          o Make it more interactive - give the user more choices on the style of the game (e.g., select a level)
+
** Make it more interactive - give the user more choices on the style of the game (e.g., select a level)
-
          o Add timing - Try to evaluate the user's rhythmic accuracy
+
** Add timing - Try to evaluate the user's rhythmic accuracy
-
          o Change the nature of the game somehow
+
** Change the nature of the game somehow

Revision as of 20:22, 22 June 2007

AVR Programming
Assigned: Monday, June 25

The goal of this lab is to become familiar with the ins and outs of programming on the AVR mini.

Contents

Set up your environment to use the AVR

Follow OS specific instructions for installing the AVR environment

  • In all cases, this entails downloading the avrlib to your home directory. At CCRMA, it is easiest to use subversion:
   ~> cd
   ~> svn checkout file:///usr/ccrma/group/pid/avr/svn/avrlib ./avrlib

Create a pid2007 directory and copy the avrlib-demos to it

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

Make a directory for Lab 1 in your pid2007 directory

   ~/pid2007> mkdir lab1

Set up AVR connection to PC

  • Connect power cable, connect USB cable, and power-up the AVRmini

Test AVR setup with "flash" test code

  • Make yourself a copy of the FLASH demo from avrlib-demos:
        ~> cd ~/pid2007/lab1
        ~/pid2007/lab1> cp -r ../avrlib-demos/flash .
        ~/pid2007/lab1> cd flash
  • Compile the code to the AVRmini. Type:
        ~/pid2007/lab1/flash> make
  • Download the code onto the AVRmini. Press the RESET button on the AVRmini and within 2 seconds type:
        ~/pid2007/lab1/flash> make load
  • You should see a sort of makeshift progress bar as a bunch of "#" characters print. If the program transferred successfully, then press RESET again. Connect the PBLED header to the PORTB header.
  • If everything is working, an LED on the AVRmini board should start flashing.

AVRMini Input/Output

a. Review architecture and programming, as necessary

b. Momentary pushbutton

  • Copy the BUTTON program from the avrlib-demos to your Lab 1 folder:
                         ~> cd ~/pid2007/lab1
            ~/pid2007/lab1> cp -r ../avrlib-demos/button . 
            ~/pid2007/lab1> cd button 
  • Load the program onto the AVR
     ~/pid2007/lab1/button> make load
  • When you press SW4 ("Switch number 4"), LED0 ("Light Emitting Diode number 0") should light
  • Look at the code in an editor:
     gedit button.c 
  • In particular, note that there's a comment near the top of the code that tells you
     //  USING THE AVRMINI DEVELOPMENT BOARD, CONNECT
     //  THE LED/PUSHBUTTON JUMPER TO THE PORT B JUMPER.
  • All of the demo programs in avrlib-demos have a comments like this.

Optional: Toggle pushbutton using debounce.

  • Compile and load TOGGLE from the avrlib-demos
                     ~> cd ~/pid2007/lab2
            ~/pid2007/lab2> cp -r ../avrlib-demos/toggle . 
            ~/pid2007/lab2> cd toggle
     ~/pid2007/lab2/toggle> make load
  • Look at the code in an editor. Compare button.c and toggle.c. Why is there a debounce mechanism in toggle.c but not in button.c? How does the debounce mechanism work?
  • What happens if you change the debounce threshold to 1? (hint - try toggling the LED 10 times)
  • What happens if you change the debounce threshold to 30000?
  • Can you change it to 100000? (hint - you need to change something else, too. DO NOT SPEND MORE THAN 5 MINUTES TRYING TO FIGURE THIS OUT!)
  • Especially optional section: instruction counting and timing
    • Really, we mean it, don't waste time on this unless it fascinates you
      • Create the file button.ss by typing make button.ss
      • Look at button.ss - these are the instructions that are actually written to the microprocessor.
      • Look in the two sections <checkButton> and <main>. Each line corresponds to one instruction of the microprocessor. What debounce threshold value would give approximately 1 second of delay between the button press and the LED lighting up? (Hint: you will need to look at the Atmel Instruction Set documentation.)
  • Why is using a very high debounce threshold a bad way to implement a 1 second delay? (There are at least three good reasons.)
  • The best way to implement a 1 second delay is with the timer library in avrlib. Put the debounce threshold back to a reasonable value for debouncing and reintroduce the 1 second delay properly:
    • Add #include "timer.h" at the top of toggle.c
    • Add timerInit(); to the beginning of your main() procedure but after your varaible declariations..
    • Add a call to the timerPause() procedure in the right place in your program.
    • In your makefile, add $(AVRLIB)/timer.c to the list of files in the definition of SRC
           The new makefile line should look like this: SRC= $(TRG).c $(AVRLIB)/timer.c 
  • Find the maximum delay time before you can notice a pause between the button press and the LED illuminating.

Four buttons

  • Write a program to control 4 LEDs with 4 buttons. It's up to you to do some "interaction design": think of your own way for actions with the four buttons to control the states of the LEDs. Feel free to write this program from scratch, but we recommend that you start with the FOURTOGGLE demo.

Beep

  • Load BUTTONBEEP as you did BUTTON and FLASH above.
  • Make sure the blue wire from your speaker is connected to pin D5 and the black wire from the speaker to ground.
  • You should hear a beep when you press SW4.
  • Try inserting a pause between turning on the LED and playing the beep. In case you didn't do part 3b, here are the step-by-step instructions for using the avrlib's timer facilities:
    • Add #include "timer.h" at the top of buttonbeep.c
    • Add timerInit(); to the beginning of your main() procedure.
    • Add a call to the timerPause() procedure in the right place in your program.
    • In your makefile, add $(AVRLIB)/timer.c to the list of files in the definition of SRC
    • At what point does the delay become noticeable? What if the beep comes before the light?
  • Try finding the largest unnoticeable delay time as in #3 using the beep as feedback. Is it different?

Compile, Run and Play the AVRsimon

  • Compile the code and program the AVR:
     cd ~/pid2007/lab2
     cp -r ../avrlib-demos/avrsimon . 
     cd avrsimon 
     make load
  • You should now be able to play the Simon game provided. Pay attention to things you like and dislike about the flow of the game and the interaction.
  • The first sequence that is played should be random. Why isn't it? Fix it (without using a random number generator in C).
  • Improve the game to make it more interesting and engaging. Here are some suggestions, but feel free to come up with others:
    • Keep stats - this is an easy addition involving adding two counters for correct and incorrect performance, and adding a way to start a new game without the reset button.
    • Add levels of play - make it get progressively more difficult (e.g., longer patterns, increasing tempo)
    • Add additional buttons and LEDs using the solderless breadboard
    • Make it more interactive - give the user more choices on the style of the game (e.g., select a level)
    • Add timing - Try to evaluate the user's rhythmic accuracy
    • Change the nature of the game somehow
Personal tools