From: kindredvendetta <ja...@ec...> - 2009-11-17 14:03:12
|
Hello, I have an Overo Earth and Summit expansion board and am trying to enable more of the GPIO pins for use. I have 6 of them working, but others I cannot access when testing through the sysfs interface - they will not respond to a change in applied value. Not tried through C, but I assume it would be the same. Namely, I would like to get the GPIO171-175 (The SPI port), as well as 144 and 145 if possible. I've already built a kernel with SPI support disabled, and can see from posts on the forum that I have to alter the pin multiplexing in order to use pins as GPIO, but I'm not sure how. I would like to do it without rebuilding the kernel, if this is possible... I've seen some references to "edit the muxing in u-boot" but not sure what this is or what changes to make. If it is necessary to patch the kernel, could someone also give me quick instructions as I've not managed to do this successfully yet. Any help would be very greatly appreciated! Thanks James -- View this message in context: http://old.nabble.com/Overo%3A-How-do-I-adjust-the-pin-mux-to-enable-more-GPIO-pins--tp26390426p26390426.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Brett G. <gr...@ro...> - 2009-11-17 14:27:55
|
To mux the omap pins you can use a program like devmem2 to change the omap registers directly (or mmap /dev/mem yourself in C). To know what registers to change, take a look at the 'System Control Module Functional Description section in Ch7 (System Control) of the Omap35xx reference (look at pages 29 to 39). On Tue, Nov 17, 2009 at 9:03 AM, kindredvendetta <ja...@ec...> wrote: > > Hello, > > I have an Overo Earth and Summit expansion board and am trying to enable > more of the GPIO pins for use. I have 6 of them working, but others I cannot > access when testing through the sysfs interface - they will not respond to a > change in applied value. Not tried through C, but I assume it would be the > same. Namely, I would like to get the GPIO171-175 (The SPI port), as well as > 144 and 145 if possible. > > I've already built a kernel with SPI support disabled, and can see from > posts on the forum that I have to alter the pin multiplexing in order to use > pins as GPIO, but I'm not sure how. I would like to do it without rebuilding > the kernel, if this is possible... I've seen some references to "edit the > muxing in u-boot" but not sure what this is or what changes to make. > > If it is necessary to patch the kernel, could someone also give me quick > instructions as I've not managed to do this successfully yet. > > Any help would be very greatly appreciated! > > Thanks > > James > -- > View this message in context: http://old.nabble.com/Overo%3A-How-do-I-adjust-the-pin-mux-to-enable-more-GPIO-pins--tp26390426p26390426.html > Sent from the Gumstix mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: Dirk B. <dir...@go...> - 2009-11-17 14:34:02
|
kindredvendetta wrote: > Hello, > > I have an Overo Earth and Summit expansion board and am trying to enable > more of the GPIO pins for use. I have 6 of them working, but others I cannot > access when testing through the sysfs interface - they will not respond to a > change in applied value. Not tried through C, but I assume it would be the > same. Namely, I would like to get the GPIO171-175 (The SPI port), as well as > 144 and 145 if possible. > > I've already built a kernel with SPI support disabled, and can see from > posts on the forum that I have to alter the pin multiplexing in order to use > pins as GPIO, but I'm not sure how. I would like to do it without rebuilding > the kernel, if this is possible... I've seen some references to "edit the > muxing in u-boot" but not sure what this is or what changes to make. U-Boot is the boot loader used to load the kernel. So yes, you can modify pin mux in boot loader without changing the the kernel. But you have to rebuild the boot loader U-Boot. Overo U-Boot support is in U-Boot mainline: git clone git://git.denx.de/u-boot.git u-boot-main cd u-boot-main git checkout --track -b omap3 origin/master Build (assuming Code Sourcery GCC): make CROSS_COMPILE=arm-none-linux-gnueabi- mrproper make CROSS_COMPILE=arm-none-linux-gnueabi- omap3_overo_config make CROSS_COMPILE=arm-none-linux-gnueabi- There, pin mux is done in file board/overo/ overo.h http://git.denx.de/?p=u-boot.git;a=blob;f=board/overo/overo.h;h=4c7ac27fa6818d4f474bc42330134fd0a5520a37;hb=HEAD To get an idea how to change pin mux there have a look to http://elinux.org/BeagleBoardPinMux#U-Boot (it's done the same way for Beagle and Overo). Best regards Dirk |
From: colinfp <co...@be...> - 2010-03-28 02:05:58
|
Hi, I know that this is a little outdated... but I am having trouble finding where in the open embedded file system the /board directory is. If anyone could give me a little direction I would really appreciate it. Thanks! Colin Dirk Behme-2 wrote: > > kindredvendetta wrote: >> Hello, >> >> I have an Overo Earth and Summit expansion board and am trying to enable >> more of the GPIO pins for use. I have 6 of them working, but others I >> cannot >> access when testing through the sysfs interface - they will not respond >> to a >> change in applied value. Not tried through C, but I assume it would be >> the >> same. Namely, I would like to get the GPIO171-175 (The SPI port), as well >> as >> 144 and 145 if possible. >> >> I've already built a kernel with SPI support disabled, and can see from >> posts on the forum that I have to alter the pin multiplexing in order to >> use >> pins as GPIO, but I'm not sure how. I would like to do it without >> rebuilding >> the kernel, if this is possible... I've seen some references to "edit the >> muxing in u-boot" but not sure what this is or what changes to make. > > U-Boot is the boot loader used to load the kernel. So yes, you can > modify pin mux in boot loader without changing the the kernel. But you > have to rebuild the boot loader U-Boot. > > Overo U-Boot support is in U-Boot mainline: > > git clone git://git.denx.de/u-boot.git u-boot-main > cd u-boot-main > git checkout --track -b omap3 origin/master > > Build (assuming Code Sourcery GCC): > > make CROSS_COMPILE=arm-none-linux-gnueabi- mrproper > make CROSS_COMPILE=arm-none-linux-gnueabi- omap3_overo_config > make CROSS_COMPILE=arm-none-linux-gnueabi- > > There, pin mux is done in file > > board/overo/ overo.h > > http://git.denx.de/?p=u-boot.git;a=blob;f=board/overo/overo.h;h=4c7ac27fa6818d4f474bc42330134fd0a5520a37;hb=HEAD > > To get an idea how to change pin mux there have a look to > > http://elinux.org/BeagleBoardPinMux#U-Boot > > (it's done the same way for Beagle and Overo). > > Best regards > > Dirk > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 > 30-Day > trial. Simplify your report design, integration and deployment - and focus > on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > -- View this message in context: http://old.nabble.com/Overo%3A-How-do-I-adjust-the-pin-mux-to-enable-more-GPIO-pins--tp26390426p28056783.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: ScottEllis <sco...@gm...> - 2010-03-28 11:22:33
|
There are two board files, one for u-boot and another for the linux kernel. OE extracts and builds u-boot and linux under ${OVEROTOP}/tmp/work/overo-angstrom-linux-gnueabi/ The u-boot board file is in the u-boot directory ../u-boot-omap3-<latest-version>/git/board/overo/ The files are overo.c and overo.h For the linux kernel, its ../linux-omap3-2.6.<latest-version>/git/arch/arm/mach-omap2/ The file is board-overo.c colinfp wrote: > > Hi, > I know that this is a little outdated... but I am having trouble > finding where in the open embedded file system the /board directory is. If > anyone could give me a little direction I would really appreciate it. > Thanks! > Colin > > > > Dirk Behme-2 wrote: >> >> kindredvendetta wrote: >>> Hello, >>> >>> I have an Overo Earth and Summit expansion board and am trying to enable >>> more of the GPIO pins for use. I have 6 of them working, but others I >>> cannot >>> access when testing through the sysfs interface - they will not respond >>> to a >>> change in applied value. Not tried through C, but I assume it would be >>> the >>> same. Namely, I would like to get the GPIO171-175 (The SPI port), as >>> well as >>> 144 and 145 if possible. >>> >>> I've already built a kernel with SPI support disabled, and can see from >>> posts on the forum that I have to alter the pin multiplexing in order to >>> use >>> pins as GPIO, but I'm not sure how. I would like to do it without >>> rebuilding >>> the kernel, if this is possible... I've seen some references to "edit >>> the >>> muxing in u-boot" but not sure what this is or what changes to make. >> >> U-Boot is the boot loader used to load the kernel. So yes, you can >> modify pin mux in boot loader without changing the the kernel. But you >> have to rebuild the boot loader U-Boot. >> >> Overo U-Boot support is in U-Boot mainline: >> >> git clone git://git.denx.de/u-boot.git u-boot-main >> cd u-boot-main >> git checkout --track -b omap3 origin/master >> >> Build (assuming Code Sourcery GCC): >> >> make CROSS_COMPILE=arm-none-linux-gnueabi- mrproper >> make CROSS_COMPILE=arm-none-linux-gnueabi- omap3_overo_config >> make CROSS_COMPILE=arm-none-linux-gnueabi- >> >> There, pin mux is done in file >> >> board/overo/ overo.h >> >> http://git.denx.de/?p=u-boot.git;a=blob;f=board/overo/overo.h;h=4c7ac27fa6818d4f474bc42330134fd0a5520a37;hb=HEAD >> >> To get an idea how to change pin mux there have a look to >> >> http://elinux.org/BeagleBoardPinMux#U-Boot >> >> (it's done the same way for Beagle and Overo). >> >> Best regards >> >> Dirk >> >> ------------------------------------------------------------------------------ >> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 >> 30-Day >> trial. Simplify your report design, integration and deployment - and >> focus on >> what you do best, core application coding. Discover what's new with >> Crystal Reports now. http://p.sf.net/sfu/bobj-july >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> >> > > -- View this message in context: http://old.nabble.com/Overo%3A-How-do-I-adjust-the-pin-mux-to-enable-more-GPIO-pins--tp26390426p28058077.html Sent from the Gumstix mailing list archive at Nabble.com. |