Re: [Gumstix-users] GPIO pin usage

[<cod...@gm...>]

Scott,

I got the name right this time.  HA!  I looked at the wrong line in my inbox
when replying.  Sorry :-P

Thanks for the updated info.  I'll have to try this out.  I'll be in touch
on here if I run into any other issues with this rebuild of u-boot.

On Thu, Dec 31, 2009 at 12:31 PM, ScottEllis <sco...@gm...
> wrote:

>
> I think u-boot-omap3 is the version you want to be using.
>
> scott@quad:~/overo-oe/org.openembedded.dev/conf$ grep -r u-boot * | grep
> overo
> machine/overo.conf:PREFERRED_PROVIDER_virtual/bootloader = "u-boot-omap3"
> machine/omap3.conf:# there is no generic omap3 u-boot, so just build the
> overo one
>
> You might want to manage your changes with a patch file so it fits smoothly
> into the OE framework.
>
> Go ahead and build u-boot-omap3 once so that the source gets extracted into
>
>
> $TMPDIR/work/over-angstrom-linux-gnueabi/u-boot-omap3-1_2009.11+r1+git87d93a1ba2ae23550e1370adb7a3b00af0831165-r1
>
> (The version info after u-boot-omap3 might change.)
>
> (TMPDIR is defined in ~/overo-oe/build/conf/site.conf)
>
> Then to modify git/board/overo/overo.h file, you could do the following
>
> $ cd
>
> $TMPDIR/work/over-angstrom-linux-gnueabi/u-boot-omap3-1_2009.11+r1+git87d93a1ba2ae23550e1370adb7a3b00af0831165-r1
>
> $ cp git/board/overo/overo.h git/board/overo/overo.h-orig
>
> $ vi git/board/overo/overo.h
>
> $ [make your changes and save it]
>
> $ git diff git/board/overo/overo.h-orig git/board/overo/overo.h >
> my-pin-mux.patch
>
> $ cp my-pin-mux.patch
> ~/overo-oe/org.openembedded.dev/recipes/u-boot/u-boot-omap3-git/
> (Note that it is u-boot-omap3<dash>git)
>
> Now edit the u-boot-omap3_git.bb recipe to include the patch.
>
> $ cd ~/overo-oe
>
> $ vi org.openembedded.dev/recipes/u-boot/u-boot-omap3_git.bb
> (Note that it is u-boot-omap3<underscore>git.bb)
>
> ...
> SRC_URI = "git://git.denx.de/u-boot.git;protocol=git \
>           file://fw_env.config \
>           file://tincan.patch;patch=1 \
>           file://gpmc-net.patch;patch=1 \
> +           file://my-pin-mux.patch;patch=1 \
>          "
> ...
>
> When you don't want the patch applied just remove the line you added from
> the recipe.
>
> Then rebuild u-boot
>
> $ cd ~/overo-oe
>
> The clean will remove the
> $TMPDIR/work/overo-angstrom-linux-gnueabi/u-boot... directory
> $ bitbake -c clean u-boot-omap3
>
> The rebuild will apply the patches after extraction
> $ bitbake -c rebuild u-boot-omap3
>
> If it works you'll have a new u-boot-overo.bin file here
>
> $TMPDIR/deploy/glibc/images/overo/u-boot-overo.bin
>
> Seems like a lot of work at first, but at the end you only have to manage
> the patch
> file or files if you have different versions. It also makes it easy to move
> around
> among different build machines.
>
> You can put the new u-boot on a microSD card using these instructions
>
> http://www.gumstix.net/Setup-and-Programming/view/Overo-Setup-and-Programming/Creating-a-bootable-microSD-card/111.html
>
> or first copy it to the overo filesystem and then use the mtd tools to copy
> it to nand using these instructions
>
> http://www.gumstix.net/Setup-and-Programming/view/Overo-Setup-and-Programming/Writing-images-to-onboard-nand/111.html
>
>
> --
> View this message in context:
> http://old.nabble.com/-Gumstix-Users--GPIO-pin-usage-tp26879785p26980554.html
> Sent from the Gumstix mailing list archive at Nabble.com.
>
>
>
> ------------------------------------------------------------------------------
> This SF.Net email is sponsored by the Verizon Developer Community
> Take advantage of Verizon's best-in-class app development support
> A streamlined, 14 day to market process makes app distribution fast and
> easy
> Join now and get one step closer to millions of Verizon customers
> http://p.sf.net/sfu/verizon-dev2dev
> _______________________________________________
> gumstix-users mailing list
> gum...@li...
> https://lists.sourceforge.net/lists/listinfo/gumstix-users
>