I have a Beagleboard xM and I am searching for the exact source of u-boot that comes with the sd-card. I have tried the mainline u-boot sources, beagleboard validation sources, bitbake angstrom sources but I am not able to locate the exact source for it. I need them for j-tag related debugging purposes.
U-Boot 2011.03-rc1-00000-g9a3cc57-dirty (Apr 01 2011 - 17:41:42)
OMAP3630/3730-GP ES2.1, CPU-OPP2, L3-165MHz, Max CPU Clock 1 Ghz
OMAP3 Beagle board + LPDDR/NAND
I2C: ready
DRAM: 512 MiB
NAND: 0 MiB
MMC: OMAP SD/MMC: 0
*** Warning - readenv() failed, using default environment
You might try Jason's Github repo [1], Gitorious [2], or trying to go
back in the u-boot mainline to that commit (although I don't think
mainline has that SHA, just did a quick check). I don't know the exact
answer. You'll have to go back to that SHA (9a3cc57...).
[1]: https://github.com/jadonk/u-boot
[2]: https://gitorious.org/beagleboard-validation
Regardless of your choice, have fun. That "-dirty" usually means that
it was compiled after modification that wasn't checked into git, yet.
So the git commit short SHA is a good starting point but unless you know
exactly what was changed to make it dirty, you may be SOL.
Best bet is probably to simply recompile u-boot. xM is supported in
mainline. Then you'll know for sure which sources were used. If you
can handle a JTAG, you can probably do a u-boot compile.
-Andrew
Hi,
Regardless of your choice, have fun. That “-dirty” usually means that
it was compiled after modification that wasn’t checked into git, yet.
So the git commit short SHA is a good starting point but unless you know
exactly what was changed to make it dirty, you may be SOL.
Best bet is probably to simply recompile u-boot. xM is supported in
mainline. Then you’ll know for sure which sources were used. If you
can handle a JTAG, you can probably do a u-boot compile.
-Andrew
The U-Boot 2011.03-rc1-00000-g9a3cc57-dirty is the one that works perfectly for me. It will be great if I can get the sources for that 
Here is what I tried so far…
git://git.denx.de/u-boot.git
git://git.omapzoom.org/repo/u-boot.git
git://gitorious.org/beagleboard-validation/u-boot.git
http://www.angstrom-distribution.org/building-angstrom > bitbake u-boot -c configure > got the source from
build/tmp-angstrom_v2012_05-eglibc/work/beagleboard-angstrom-linux-gnueabi/u-boot-2011.12-r8 folder
Regards.
That's how all the factory u-boots are built, I encourage you to use the latest one, 2011.03 is over a year old and unsupported.
From: beagleboard@googlegroups.com [mailto:beagleboard@googlegroups.com]
On Behalf Of Koen Kooi
Sent: Monday, May 14, 2012 7:24 AM
To: beagleboard@googlegroups.com
Subject: Re: [beagleboard] u-boot sources for xm -
2011.03-rc1-00000-g9a3cc57-
dirty
> Hi,
>
>
>
> Regardless of your choice, have fun. That "-dirty" usually means that
> it was compiled after modification that wasn't checked into git, yet.
> So the git commit short SHA is a good starting point but unless you
> know exactly what was changed to make it dirty, you may be SOL.
>
> Best bet is probably to simply recompile u-boot. xM is supported in
> mainline. Then you'll know for sure which sources were used. If you
> can handle a JTAG, you can probably do a u-boot compile.
>
> -Andrew
>
> The U-Boot 2011.03-rc1-00000-g9a3cc57-dirty is the one that works
> perfectly for me. It will be great if I can get the sources for that
>
>
> Here is what I tried so far..
>
> http://www.angstrom-distribution.org/building-angstrom > bitbake
> u-boot -c configure
That's how all the factory u-boots are built, I encourage you to use the
latest one,
2011.03 is over a year old and unsupported.
I agree with Koen. I use the latest u-boot 2011.12 with uImage-V3.2.16 and
it works fine on my Beagle-xM. Start out my erasing your u-boot environment
from flash as this is probably the source of any problems you might be
having.
Regards,
John
-- To join: http://beagleboard.org/discuss To unsubscribe from this group,
send
Hi,
2011.03 is over a year old and unsupported.
I agree with Koen. I use the latest u-boot 2011.12 with uImage-V3.2.16 and
it works fine on my Beagle-xM. Start out my erasing your u-boot environment
from flash as this is probably the source of any problems you might be
having.
I am having problems with the latest version. I have not changed the MLO file just replaced the u-boot image
Texas Instruments X-Loader 1.5.0 (Mar 27 2011 - 17:37:56)
Beagle xM
Reading boot sector
Loading u-boot.bin from mmc
Its stuck at this point.
The name of the file generated from angstrom bitbake is u-boot-beagleboard-2011.12-r8.img
This the default sd-card that came with beagleboard-xm. It has no flash. I havent touched any other file just replaced u-boot since I could not locate the original source of u-boot that came with the card. The original u-boot.img works perfectly with the same sd-card and board.
This is what I get with the original u-boot.
The Angstrom Distribution beagleboard ttyS2
Angstrom 2010.7-test-20110220 beagleboard ttyS2
beagleboard login:
Hi,
Hi,
I am having problems with the latest version. I have not changed the MLO file just replaced the u-boot image
Texas Instruments X-Loader 1.5.0 (Mar 27 2011 - 17:37:56)
Beagle xM
Reading boot sector
Loading u-boot.bin from mmc
Its stuck at this point.
Solved this problem by replacing both the u-boot.img and MLO file.
Now its stuck at
Starting portmap daemon: portmap.
portmap: fork: No such devicenet.ipv4.conf.default.rp_filter = 1
net.ipv4.conf.all.rp_filter = 1
hwclock: can’t open ‘/dev/misc/rtc’: No such file or directory
Tue Apr 19 20:57:00 BST 2011
hwclock: can’t open ‘/dev/misc/rtc’: No such file or directory
You should use the MLO that u-boot built for you. Format your FAT
partition, then copy MLO on, then copy u-boot.img (note, it's not called
u-boot.bin anymore) and uEnv.txt. X-loader has been deprecated, it's no
longer maintained.
-Andrew
Hi,
Hi,
I am having problems with the latest version. I have not changed the MLO file just replaced the u-boot image
Texas Instruments X-Loader 1.5.0 (Mar 27 2011 - 17:37:56)
Beagle xM
Reading boot sector
Loading u-boot.bin from mmc
Its stuck at this point.
Solved this problem by replacing both the u-boot.img and MLO file.
Now its stuck at
Starting portmap daemon: portmap.
portmap: fork: No such devicenet.ipv4.conf.default.rp_filter = 1
net.ipv4.conf.all.rp_filter = 1
hwclock: can’t open ‘/dev/misc/rtc’: No such file or directory
Tue Apr 19 20:57:00 BST 2011
hwclock: can’t open ‘/dev/misc/rtc’: No such file or directory
As a rule, anytime I update u-boot, I always reformat the FAT32 partition, make it bootable and then copy MLO first, then u-boot and then uEnv.txt (I only used this file for tftp/nfs). Use the MLO generated by Angstrom when you build u-boot.
Regards,
John
– To join: http://beagleboard.org/discuss
To unsubscribe from this group, send email to:
beagleboard+unsubscribe@googlegroups.com
Frequently asked questions: http://beagleboard.org/faq
Can you provide a full boot log including boot loaders?
6 lines probably isn't enough to see what's wrong.
-Andrew