Hi Dave,

I figured out the problem. As I mentioned in my original post, I had to use a precompiled i2c-Bootloader because I got a message that the bootloader was too new. I went back to my original buildroot directory and grabbed the i2c-io.hex and i2c-Boot-m128-16MHz.hex from there. I installed those and everything works great.

Thanks for the help,

On Mon, Aug 30, 2010 at 1:50 PM, Dave Hylands <dhylands@gmail.com> wrote:
Hi Russ,

On Sat, Aug 28, 2010 at 5:42 AM, Russ Morin <russmorin@gmail.com> wrote:
> Hi Dave,
> Yes, I did program the fuses using pgm-fuses-bootloader. I also edited
> bootcmd to run robostix_pwr_run on startup. One thing I've noted is that
> after blinking for a couple seconds, the red light turns off rather than
> going to solid red.

So it sounds like i2c-io isn't running.

The normal blink pattern with i2c-io loaded is as follows:

1 - When power is applied, the bootloader runs for 5 seconds. During
this period, the red led should blink on and off about 5 times per
2 - Once i2c-io is loaded, then the blink pattern changes to a double
blink followed by a longer pause, with one double-blink per second.

Modifying u-boot to power on the robostix will only work properly if
the LCD driver isn't enabled in the kernel. If the LCD driver is
compiled in, then when it configures the LCD pins (which are shared
with the pins controlling the robostix), then the robostix may go into
weird states.

Try using the robostix command line program to power on the robostix.

robostix power on

This page:
describes various methods to control the robostix power.

This page:
talks about how to disable the framebuffer.

Dave Hylands
Shuswap, BC, Canada

This SF.net Dev2Dev email is sponsored by:

Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
gumstix-users mailing list