I'm not familiar with the different types of LEDs.  One is red, one is amber.  The boards were given to me from another group.  I actually wouldn't know how to hook the LEDs up to different pins.  I was under the impression that the GPIO pins on the 40-pin header of the summit board all had 1.8v except ground.  Granted, I'm not a hardware guy, so I don't know much about that side of things.

On Fri, Feb 19, 2010 at 1:27 PM, Dave Hylands <dhylands@gmail.com> wrote:

On Fri, Feb 19, 2010 at 9:56 AM,  <coderdrone@gmail.com> wrote:
> I'm working on a similar issue with using LEDs connected to GPIO pins.  I
> had thought that as long as the GPIOs are configured as outputs that I could
> 'echo 1 > gpioXXX/value' or 'echo 0 > gpioXXX/value' to turn the LED on and
> off but it doesn't seem to be working.
> In u-boot's overo.h, I have tried the GPIOs configured as (IEN | PTD | EN |
> M4) and (IDIS | PTD | EN | M4).  The LEDs on the board simply don't change
> when I set the pins high/low via the filesystem in /sys/class/gpio.
> This is on overo earth btw.

What type of LEDs are you using?

Some, like the blue ones, require more than 1.8v to operate.

If you connect your LED up to 1.8v instead of the gpio pin does it light up?

Dave Hylands
Shuswap, BC, Canada

Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
gumstix-users mailing list