I need to use some interfaces in the expansion connector and I read
that I have to rebuild the uboot to configure the expansion connector
(am I right?)
My question is, where can I find the uboot source to compile?. I'm so
lost about this.
I need to use some interfaces in the expansion connector and I read
that I have to rebuild the uboot to configure the expansion connector
(am I right?)
My question is, where can I find the uboot source to compile?. I'm so
lost about this.
Sorry for the question but which kernel did you used?
Angstrom pulls from the git repository at u-boot's home:
git://git.denx.de/u-boot.git
Which branch/commit to use depends on how narcissus builds. I've used
commit ID ca6e1c136ddb720c3bb2cc043b99f7f06bc46c55 based on what I've
gleaned from Angstrom's build recipes. However, I recently switched to
the following alternative.
There is also the BeagleBoard validation git repository on gitorious:
git://gitorious.org/beagleboard-validation/u-boot.git
There are a number of branches and commit IDs you can use here as well.
I'm current using commit ID 3f6a11d8a37f11bef4611345b3d3fe38cc086a17
which allows me to build an identical u-boot binary to the one
referenced on the C3 validation page: http://code.google.com/p/beagleboard/wiki/BeagleboardRevC3Validation
Michael, I never used a git repository, how do I use this?.
I'm running an Ubuntu on my pc.
Do a google search for "GIT Tutorial". There are several available and
the one that usually shows up at the top of the list when I do that is
pretty good.
How do I know if the u-boot source is compatible with my rec.C4
board?...
U-boot is configurable for specific boards using files found under
includes/configs. There is a config for the BeagleBoard there
(omap3_beagle.h). When you build, you use the "omap3_beagle_config"
target and that will use that config file. That will get you
compatibility with the C4 board.
Which repository you clone (re: get the source) from - gitorious or denx.de - can affect how well u-boot supports your board. gitorious is
a bit more bleeding edge, so might have better hardware support but also
might have more problems. denx.de has stable branches that probably
have less hardware support. Angstrom pulls from denx.de. The
validation images pull from gitorious. Choose your poison.
Actually, I hadn't noticed that. It's good to know. Would the kernel
repo at beagle-validation/linux also be the same as angstrom's? I'm
just trying to find the most appropriate kernel to get S-video working
in my custom build system. Right now the kernels I've tried so "no
displays found" when omapfb tries to init itself at boot time.
You do not need to touch u-boot. You just need to configure the pin-muxes that you need. If it is kernel driver related, you do it in arch/arm/mach-omap2/board-omap3beagle.c. Otherwise, you do it in your app.
The official u-boot release v2010.09 supports all beagleboard devices
(C4, xM...).
You can retrieve and cross-compile it from the mainlaine git
repository:
git clone git://git.denx.de/u-boot.git u-boot-main
git checkout v2010.09
make omap3_beagle_config
make
I have tried building my own version of u-boot by downloading the source
from denx and the version as mentioned below and compiling them with
code sourcery lite(the latest version
arm-2010.09-50-arm-none-linux-gnueabi) with out success. I issue these
commands
make CROSS_COMPILE=arm-none-linux-gnueabi- mrproper
make CROSS_COMPILE=arm-none-linux-gnueabi- omap3_beagle_config
make CROSS_COMPILE=arm-none-linux-gnueabi-
No errors are encountered. A u-boot file does get created. I copy it to
the SD card with a copy of the MLO file from the angstrom SD that came
with my BB xm(I know u-boot and MLO are required to see some action as I
have tested this with MLO and u-boot from said SD card)
What I get is :
Texas Instruments X-Loader 1.4.4ss (Aug 19 2010 - 02:48:27)
Beagle xM Rev A
Reading boot sector
Loading U-boot.bin from mmc
then a bunch of garbage for about 5 seconds.
I tried changing the baud rate a bunch of times bet never saw anything
that made sense.
Did you compile v2010.09 of Das U-Boot?
I has similar issue with CodeSourcery ARM EABI 2010.09
Please try to use previous one (2010q1) to re-compile it.
> From: David Wiebe dwiebe2@telus.net > Subject: Re: [beagleboard] Re: uboot source… > To: beagleboard@googlegroups.com > Date: Friday, November 26, 2010, 11:05 PM > > Hello, > > I have tried building my own version of u-boot by downloading the source > from denx and the version as mentioned below and compiling them with > code sourcery lite(the latest version > arm-2010.09-50-arm-none-linux-gnueabi) with out success. I issue these > commands > > make CROSS_COMPILE=arm-none-linux-gnueabi- mrproper > make CROSS_COMPILE=arm-none-linux-gnueabi- omap3_beagle_config > make CROSS_COMPILE=arm-none-linux-gnueabi- > > No errors are encountered. A u-boot file does get created. I copy it to > the SD card with a copy of the MLO file from the angstrom SD that came > with my BB xm(I know u-boot and MLO are required to see some action as I > have tested this with MLO and u-boot from said SD card) > > What I get is : > > Texas Instruments X-Loader 1.4.4ss (Aug 19 2010 - 02:48:27) > Beagle xM Rev A > Reading boot sector > Loading U-boot.bin from mmc > > then a bunch of garbage for about 5 seconds. > > I tried changing the baud rate a bunch of times bet never saw anything > that made sense. > > Can anyone tell me what I am doing wrong? > > Thanks! > > David > > On 10-11-26 11:56 AM, daicav wrote: > > Thanks. am on it… > > > > On Nov 24, 7:58 am, Cedric Madianga <cedric.madia…@gmail.com> wrote: > >> Hi all, > >> > >> The official u-boot release v2010.09 supports all beagleboard devices > >> (C4, xM…). > >> > >> You can retrieve and cross-compile it from the mainlaine git > >> repository: > >> git clone git://git.denx.de/u-boot.git u-boot-main > >> git checkout v2010.09 > >> make omap3_beagle_config > >> make > >> > >> Regards, > >> > >> Cedric > >> > >> On Nov 23, 6:02 pm, Carlo Caione <carlo.cai…@gmail.com> wrote: > >> > >> > >> > >> > >> > >> > >> > >>> On 23/11/2010 17:48, Michael J. Hammel wrote: > >> > >>>> Which repository you clone (re: get the source) from - gitorious or > >>>> denx.de - can affect how well u-boot supports your board. gitorious is > >>>> a bit more bleeding edge, so might have better hardware support but also > >>>> might have more problems. denx.de has stable branches that probably > >>>> have less hardware support. Angstrom pulls from denx.de. The > >>>> validation images pull from gitorious. Choose your poison. > >> > >>> Last git (denx.de) version of u-boot doesn’t work for me on beagleboard > >>> xm rev.A > >>> I’m currently using the validation version onhttp://gitorious.org/beagleboard-validation/ > >> > >>> Regards, > >> > >>> – > >>> Carlo Caione > > > > – > You received this message because you are subscribed to the Google Groups “Beagle Board” group. > To post to this group, send email to beagleboard@googlegroups.com. > To unsubscribe from this group, send email to beagleboard+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/beagleboard?hl=en.