Thanks! I got GPIO to work using fopen fread fwrite instead of the code on the website. I will try the other stuff out

----- Original Message ----
From: Ned Forrester <>
To: General mailing list for gumstix users. <>
Sent: Friday, 29 February, 2008 6:38:14 PM
Subject: Re: [Gumstix-users] GPIO mmap() issues on verdex

Christopher Jones wrote:

> 2- The second problem is the buildroot. I am using the Verdex exactly
> as it came out of the box. I have not reflashed the buildroot. There
> appears to be some sort of issue with the gumstix buildroot I have
> installed on my linux system because when I follow the instructions:
> -download
> -make defconfig
> -make menu config -save
> -make

Unless things have changed since the release containing 2.6.20, I though
the commands were:

svn co gumstix-buildroot
cd gumstix-buildroot
make defconfig
make menuconfig

> It always fails halfway through the last make instruction. It seems
> to download a tar file called GPS 2.3 or something and then dies
> because a directory doesn't exist. I have no idea whats going on and
> would love some kind of explanation on this.

Likely something has changes, so I can't help.

> 3 - From the above how important is it to reflash the buildroot?
> Surely you should be able to get basic functionality out of the
> computer without having to go through this process.

Only necessary (probably not even really necessary, but easier) if you
want to change the contents of the kernel, busybox, or uClibc.  Any user
space code can just be transfered by other means (scp if you have
network, mmc of cf disk, if you have that, or on the serial port).

However, if you are going to make more than one system, you will
probably find it convenient to have a customized buildroot, and just
flash each system with your complete set of code and configuration.

> 4- How can I make the Verdex skip the login stage and just go from
> uboot and initialization to the command line?

I got curious, and fiddled around with this, since I might want to do
that myself.

In /etc/inittab, comment out one line and the two following lines:

#::respawn:/sbin/getty -L ttyS0 115200 vt100
::sysinit:stty -F /dev/ttyS0 115200 cooked

There are other parameters to stty and sh that might be useful, but this
will get you started.

> 5-How can I make a program automatically run once the OS is booted?

You could add additional programs to run in inittab, but that is not the
usual way.  The preferred method is to add addition files in
/etc/init.d, using the existing files as a model.  The digits in the
file names control the order of execution during startup and shutdown;
ascending numbers on startup and descending on shutdown, if I recall

Or if there is an S90local file in /etc/init.d, then that is the place
to add more startup programs.

Ned Forrester                            
Oceanographic Systems Lab                                  508-289-2226
Applied Ocean Physics and Engineering Dept.
Woods Hole Oceanographic Institution          Woods Hole, MA 02543, USA

This email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
gumstix-users mailing list

Rise to the challenge for Sport Relief with Yahoo! for Good