gumstix

Hi Mathias,

On Mon, Nov 29, 2010 at 10:04 AM, Mathias Kriebel
<mathias_kriebel@...> wrote:
> Hello,
>
> I'm trying to get a interruption pin on the Overo by using gpio-event.
> I have tried " bitbake gpio-event" and get the results below. I have also
> looked at "bitbake -c menuconfig virtual/kernel" but I have not found
> anything there.
> Someone know how could I get a gpio-event module or a kernel with gpio-event
> enabled?
>
> Maybe the cross-compiler is not properly configured? Whats the right path
> for it?

I've never used the gpio-event that comes with OE. It appears to be an
old one. The most recent one is on my subversion server.

There are some instructions for putting it into your user.collection here:
<http://www.gumstix.net/wiki/index.php?title=GPIO_Event_Driver#Integrating.2FBuilding_with_Open_Embedded>

-- 
Dave Hylands
Shuswap, BC, Canada
http://www.DaveHylands.com/

mathiasfk@...$ make
make -C module 
make[1]: Entering directory `/local/mathiasfk/overo-oe/gpio-event-wiki/module'
make -C /local/mathiasfk/overo-oe/tmp/sysroots/overo-angstrom-linux-gnueabi/kernel M=/local/mathiasfk/overo-oe/gpio-event-wiki/module modules
make[2]: /local/mathiasfk/overo-oe/tmp/sysroots/x86_64-linux/usr/armv7a/bin/arm-angstrom-linux-gnueabi-gcc-4.3.3gcc: Command not found
make[2]: Entering directory `/local/mathiasfk/overo-oe/tmp/sysroots/overo-angstrom-linux-gnueabi/kernel'
  CC [M]  /local/mathiasfk/overo-oe/gpio-event-wiki/module/gpio-event-drv.o
/bin/sh: /local/mathiasfk/overo-oe/tmp/sysroots/x86_64-linux/usr/armv7a/bin/arm-angstrom-linux-gnueabi-gcc-4.3.3gcc: No such file or directory
make[3]: *** [/local/mathiasfk/overo-oe/gpio-event-wiki/module/gpio-event-drv.o] Error 1
make[2]: *** [_module_/local/mathiasfk/overo-oe/gpio-event-wiki/module] Error 2
make[2]: Leaving directory `/local/mathiasfk/overo-oe/tmp/sysroots/overo-angstrom-linux-gnueabi/kernel'
make[1]: *** [modules] Error 2
make[1]: Leaving directory `/local/mathiasfk/overo-oe/gpio-event-wiki/module'
make: *** [module] Error 2

I have corrected the makefiles and it created the files.
I was naming CROSS_COMPILE $(OVEROTOP)/tmp/sysroots/x86_64-linux/usr/armv7a/bin/arm-angstrom-linux-gnueabi-gcc-4.3.3
and not $(OVEROTOP)/tmp/sysroots/x86_64-linux/usr/armv7a/bin/arm-angstrom-linux-gnueabi-
But i still dont know why I dont have 'tmp/cross' and the cross compiler inside it.

Thanks,
Mathias


From: mathias_kriebel@...
To: gumstix-users@...
Date: Tue, 30 Nov 2010 13:58:10 -0200
Subject: Re: [Gumstix-users] Gpio-event module








> I've never used the gpio-event that comes with OE. It appears to be an
> old one. The most recent one is on my subversion server.
> 
> There are some instructions for putting it into your user.collection here:
> <http://www.gumstix.net/wiki/index.php?title=GPIO_Event_Driver#Integrating.2FBuilding_with_Open_Embedded>
> 
> -- 
> Dave Hylands
> Shuswap, BC, Canada
> http://www.DaveHylands.com/


Thanks for the reply,
I have tried this one too, but I have some doubts about it.
In the makefiles that is something like this:
CROSS_COMPILE    ?= $(OVEROTOP)/tmp/cross/armv7a/bin/arm-angstrom-linux-gnueabi-

but in my 'tmp' directory there is no 'cross'.
I think the cross-compiler maybe is in $(OVEROTOP)/tmp/sysroots/x86_64-linux/usr/armv7a/bin/arm-angstrom-linux-gnueabi-gcc-4.3.3
By replacing CROSS_COMPILE I get the errors attached.

Thanks,
Mathias
 		 	   		  

------------------------------------------------------------------------------
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev
_______________________________________________
gumstix-users mailing list
gumstix-users@...
https://lists.sourceforge.net/lists/listinfo/gumstix-users

The OE file layout changed over the summer.

Besides the cross -> sysroots change, the build system reference
'x86_64'-linux
is also new. If you built on a 32-bit system it would be 'i686'-linux.

Something like this would be more robust:

$(OVEROTOP)/sysroots/`uname -m`-linux/usr/armv7a/bin/...

-- 
View this message in context: http://old.nabble.com/Gpio-event-module-tp30333032p30341802.html
Sent from the Gumstix mailing list archive at Nabble.com.

Hi Mathias,

On Tue, Nov 30, 2010 at 9:37 AM, ScottEllis
<scottellis.developer@...> wrote:
>
> The OE file layout changed over the summer.
>
> Besides the cross -> sysroots change, the build system reference
> 'x86_64'-linux
> is also new. If you built on a 32-bit system it would be 'i686'-linux.
>
> Something like this would be more robust:
>
> $(OVEROTOP)/sysroots/`uname -m`-linux/usr/armv7a/bin/...

That looks good.

The use of CROSS_COMPILE uses ?= which means that if the calling
environment defines CROSS_COMPILE (i.e. OE/bitbake) then the one
provided will be used.

The CROSS_COMPILE is only used when building things in standalone mode
(i.e. not from within OE/bitbake). I edit it as needed...

-- 
Dave Hylands
Shuswap, BC, Canada
http://www.DaveHylands.com/

Hello again,

I've used successfully used ' read(fileno(fs), &value, 1) ' to block my C program until an interruption line is high.
But I have one more question: Can I use the gpio-event driver to write on a pin? 
Or will I have to use something like ' system("echo 1 > /sys/class/gpio/gpio146/value") '
I think writing this way would be slower.

Thanks
Mathias

Hi Mathias,

On Tue, Dec 7, 2010 at 10:37 AM, Mathias Kriebel
<mathias_kriebel@...> wrote:
> Hello again,
>
> I've used successfully used ' read(fileno(fs), &value, 1) ' to block my C
> program until an interruption line is high.
> But I have one more question: Can I use the gpio-event driver to write on a
> pin?
> Or will I have to use something like ' system("echo 1 >
> /sys/class/gpio/gpio146/value") '
> I think writing this way would be slower.

Or you can just open /sys/class/gpio/gpio146/value once in your program:

int fd;
fd = open( "/sys/class/gpio/gpio146/value", O_RDWR );

and do something like:

write( fd, "1", 1 );

when you want to set it.

Or you can use the gpio driver that I wrote over here:
<http://www.gumstix.net/wiki/index.php?title=User_GPIO_Driver>
which reflects the kernel gpiolib API into user-space.

-- 
Dave Hylands
Shuswap, BC, Canada
http://www.DaveHylands.com/

Thanks, Dave. I will try it.