BeagleBoard/GSoC/2010 Projects/Pulse Width Modulation

< BeagleBoard‎ | GSoC‎ | 2010 Projects
Revision as of 17:18, 15 August 2010 by Neo01124 (Talk | contribs)

Jump to: navigation, search

Project: Pulse Width Modulation

Student: Varun Jewalikar

Mentors: Søren Steen Christensen, Cristina Murillo



Latest blog entries: Extension:RSS -- Error: "" is not in the whitelist of allowed feeds. is the only allowed feed.


The main aim of this project will be to provide a high level interface for the Pulse Width Modulation output pins of the OMAP3 found on the BeagleBoard. Another aim will be to push this driver upstream(the Linux-OMAP tree). Two applications will be developed to demonstrate the use of this driver:

  • Motor control using PWM signals generated by the BeagleBoard using the PWM driver.
  • Writing a glue layer for ALSA to communicate with the PWM driver and output sound from the PWM output pins.

Build and Run instructions

  • Clone my git tree for the driver.This can be done using the following commands:
git clone git://
cd omap3-pwm/
  • A cross compiling environment will be needed for compiling the driver. Instructions below work with OpenEmbedded but can adapted for codesourcery as well.

$ <edit> beagle-source-me.txt Modify the OETREE path. OETREE should point to the OE folder. For me OETREE= ~/OE .

$ source beagle-source-me.txt This will set the environment variables for cross compilation.

$ make This will generate the requisite pwm.ko kernel module file.

  • Copy the pwm.ko to your target board.
  • Once on the system, use insmod to load using the optional frequency parameter. The default frequency is 1024 Hz. Use multiples of two with a max of 16384. pwm9_enable,pwm10_enable and pwm11_enable and frequency are load time parameters.
  • root@beagleboard# ls


root@beagleboard# insmod pwm.ko pwm9_enable=1

The driver implements a character device interface. When it loads, it will create a /dev/pwm9 entry.

  • To setup multiple pwm signals on the GPT9/10/11 you should use

root@beagleboard# insmod pwm.ko pwm9_enable=1 pwm10_enable=1

This will work similarly for any other (pwm_9/10/11) combinations as well.

  • There are two ways of modifying the parameters from userland.
 1. Using the sysfs interface (Not advised and fully supported) :
    Then to issue commands you can use any program that can do file I/O cat and echo will work. 
    root@beagleboard# cat /dev/pwm9
    PWM9 Frequency 1024 Hz Stopped
    root@beagleboard# echo 50 > /dev/pwm9
    root@beagleboard:~# cat /dev/pwm9
    PWM9 Frequency 1024 Hz Duty Cycle 50%
    root@beagleboard:~# echo 80 > /dev/pwm9

    root@beagleboard:~# cat /dev/pwm9
    PWM9 Frequency 1024 Hz Duty Cycle 80%
    You can put an oscope on pin 28 of the expansion board to see the signal.Use pin 15 for ground. Or you can measure the voltage on pin 28 and     
    you'll see the duty cycle percentage of 1.8v.
 2. Using the ioctl() calls :
    A fully supported ioctl() interface is available and it is advised to prefer this over the above sysfs interface. 
    Sample code to use the ioctl interface:
    #include <termios.h>
    #include <fcntl.h>
  1. include <errno.h>
  2. include <sys/ioctl.h>
  3. include <linux/ioctl.h>

//#define PWM_IOC_MAGIC 0x00

  1. define PWM_SET_DUTYCYCLE 1074003969
  2. define PWM_GET_DUTYCYCLE 1074003970
  3. define PWM_SET_FREQUENCY 1074003971
  4. define PWM_GET_FREQUENCY 1074003972
  5. define PWM_ON 1074003973
  6. define PWM_OFF 1074003974
  7. define PWM_SET_POLARITY 1074003975

main() { int fd, status, k, f, sc;

fd = open("/dev/pwm9", O_RDWR); scanf("%d", &k); scanf("%d", &f); scanf("%d", &sc);

if (ioctl(fd, PWM_SET_FREQUENCY, f) == -1) printf("TIOCMGET failed: %s\n", strerror(errno));

if (ioctl(fd, PWM_SET_DUTYCYCLE, k) == -1) printf("TIOCMGET failed: %s\n", strerror(errno));

if (ioctl(fd, PWM_SET_POLARITY, sc) == -1) printf("TIOCMGET failed: %s\n", strerror(errno)); printf("%d",ioctl(fd, PWM_GET_FREQUENCY, sc)); printf("\n%d",ioctl(fd, PWM_GET_DUTYCYCLE, sc));

close(fd); }