Hello
I was trying to install ubuntu-Karmic on the beagleboard, following the instructions given at http://elinux.org/BeagleBoardUbuntu
However after changing the nand parameters the board got stuck after the following lines:
Texas Instruments X-Loader 1.4.2 (Feb 19 2009 - 12:01:24)
Loading u-boot.bin from nand
I am guessing i wasnt able to set the nand parameters rite, and the board is now not able to find u-boot at the address specified in the nand. Since the board is now not responding to any of the user inputs from the key board i am at a loss as to how to perform a recovery. It would be best if i could some how reset the board to its original factory settings.
The uboot version i have installed is u-boot-beagleboard-2009.11-rc1+r42+gitra5cf522a91ba479d459f8221135bdb3e9ae97479-r42.bin, as listed on the above link. Also, the x-loader version installed is X-Loader 1.4.4ss.
I am using beagle boards on iRobot’s iCreate for a project. This u-boot mess up is the last thing i needed as i am running very short on a deadline. I have installed ubuntu-karmic before on another beagle, and its running fine.
If any one has a fix to this problem, it would be immensely appreciated
Regards
Hello,
Hello
I was trying to install ubuntu-Karmic on the beagleboard, following the
instructions given at BeagleBoardUbuntu - eLinux.org
However after changing the nand parameters the board got stuck after the
following lines:
Texas Instruments X-Loader 1.4.2 (Feb 19 2009 - 12:01:24)
Loading u-boot.bin from nand
Simple fix... Notice ^... Well it can read it from the mmc card if
you copy 2009.11-rc1 u-boot to the first partition of your SD card.
sudo wget http://rcn-ee.net/deb/tools/u-boot-beagleboard-2009.11-rc1+r42+gitra5cf522a91ba479d459f8221135bdb3e9ae97479-r42.bin
sudo mv u-boot-beagleboard-2009.11-rc1+r42+gitra5cf522a91ba479d459f8221135bdb3e9ae97479-r42.bin
u-boot.bin
Then when it boots into u-boot, make it permanent by following the
nand write directions here:
http://elinux.org/BeagleBoardUbuntu#Upgrade_U-Boot
I am guessing i wasnt able to set the nand parameters rite, and the board is
now not able to find u-boot at the address specified in the nand. Since the
board is now not responding to any of the user inputs from the key board i
am at a loss as to how to perform a recovery. It would be best if i could
some how reset the board to its original factory settings.
The uboot version i have installed is
u-boot-beagleboard-2009.11-rc1+r42+gitra5cf522a91ba479d459f8221135bdb3e9ae97479-r42.bin,
as listed on the above link. Also, the x-loader version installed is
X-Loader 1.4.4ss.
Those are incompatible...
X-loader 1.4.2 only works with everything before 2009.11-rc1
X-loader 1.4.4ss only works with 2010.03+
You "can-not" use X-loader 1.4.4ss with 2009.11-rc1
I am using beagle boards on iRobot's iCreate for a project. This u-boot mess
up is the last thing i needed as i am running very short on a deadline. I
have installed ubuntu-karmic before on another beagle, and its running fine.
Well good time learn the first rule of project management, never
upgrade right before a deadline...
Regards,
Hello
I changed u-boot as you had said Nelson, but the problem still persists. What i did was replace u-boot with 2009.11-rc1 u-boot. Also, just to let you know the entire ‘case history’ of this u-boot problem, while initially trying to setup ubuntu on the board i did not make the changes in nand for X-loader as suggested at http://elinux.org/BeagleBoardUbuntu#Upgrade_X-loader Instead i skipped directly to the uboot part http://elinux.org/BeagleBoardUbuntu#Upgrade_U-Boot.
Could you please guide me as to what should be done now.
Thanks
Hello
I changed u-boot as you had said Nelson, but the problem still persists.
Would you please "pastebin.com" something so we can actually see
what's going on... (X-loader, u-boot, etc)
What i did was replace u-boot with 2009.11-rc1 u-boot. Also, just to let
you know the entire 'case history' of this u-boot problem, while initially
trying to setup ubuntu on the board i did not make the changes in nand for
X-loader as suggested at
BeagleBoardUbuntu - eLinux.org Instead i skipped
directly to the uboot part
BeagleBoardUbuntu - eLinux.org.
Could you please guide me as to what should be done now.
Sure, repartition your SD card with MLO in the first sector followed
by u-boot.bin, then reboot your beagle and hold the "user" button...
DL this script: "wget http://rcn-ee.homeip.net:81/dl/testing/setup_boot.sh"
Put MMC card in USB adapter..
Run it "./setup_boot.sh --mmc /dev/sdX" where /dev/sdX is your MMC card...
Remove MMC card from PC, plug into the beagle..
Power on beagle, holding the 'user' button.. U-boot prompt should
appear, if it doesn't "pastebin.com" your output...
Follow both guides here, ignoring the media downloads, as both
"x-load.bin.ift" and "u-boot.bin" are already on the pre-build sd card
via the script...
http://elinux.org/BeagleBoardUbuntu#Upgrade_X-loader
http://elinux.org/BeagleBoardUbuntu#Upgrade_U-Boot
Remove all old u-boot.bin's from your other SD cards you use with this beagle..
Regards,
Would you please “pastebin.com” something so we can actually see
what’s going on… (X-loader, u-boot, etc)
It doesnt show much:
Texas Instruments X-Loader 1.4.2 (Feb 19 2009 - 12:01:24)
Loading u-boot.bin from nand
After the second line above, the board seems to get stuck.
It shows you aren't holding the "user" button after power up, with a
properly formated SD card.
Holding done the "user" key will force this:
Texas Instruments X-Loader 1.4.4ss (Apr 1 2010 - 07:01:03)
Beagle Rev Ax/Bx
Reading boot sector
Loading u-boot.bin from mmc
U-Boot 2010.03-rc1 (Apr 01 2010 - 06:56:39)
OMAP3530-GP ES2.1, CPU-OPP2, L3-165MHz, Max clock-600Mhz
OMAP3 Beagle board + LPDDR/NAND
I2C: ready
DRAM: 128 MB
NAND: 256 MiB
*** Warning - bad CRC or NAND, using default environment
In: serial
Out: serial
Err: serial
timed out in wait_for_bb: I2C_STAT=1000
timed out in wait_for_pin: I2C_STAT=0
I2C read: I/O error
Unrecognized expansion board: 0
Beagle Rev Ax/Bx
Die ID #316e00020000000004013ef10301b017
Hit any key to stop autoboot: 0
OMAP3 beagleboard.org #
with this SD card contents:
OMAP3 beagleboard.org # fatls mmc 0:1
23976 mlo
23976 x-load.bin.ift
205364 u-boot.bin
555 boot.scr
4 file(s), 0 dir(s)
Regards,
Ok. The uboot problem has been fixed. Loads of thanks Nelson.
Kernel loading problem has now surfaced though:
http://pastebin.com/uTVpHySx
I did the following in preparing the rootfs:
Please indicated as to what should be done next
Thanks for the complete, dmesg.. Your issue is at line 59:
[ 0.000000] Kernel command line: console=ttyS2,115200n8 console=tty0 root=/d0
Your boot.scr got mangled at some point..
Normally, it's like:
[ 0.000000] Kernel command line: console=ttyS2,115200n8
console=tty0 root=/dev/mmcblk0p2 rootwait rootfstype=ext3 ro
Here's the directions for reference, to rebuild your boot.scr:
http://elinux.org/BeagleBoardUbuntu#Create_U-Boot_boot_image
Regards,
I did follow the link while making boot.scr. Though i cant check the contents of boot.scr, i did check ubuntu.cmd which is used in making boot.scr
ubuntu.cmd contents: http://pastebin.com/YfN2i263
the lines seem to follow whats given in the link http://elinux.org/BeagleBoardUbuntu#Create_U-Boot_boot_image with the exception of ext2 inplace of ext3.
How then can boot.scr get mangled ? Is there anyother way i can fix it.
I did follow the link while making boot.scr. Though i cant check the
contents of boot.scr, i did check ubuntu.cmd which is used in making
boot.scr
Actually, just "cat boot.scr" just ignore the header noise...
ubuntu.cmd contents: http://pastebin.com/YfN2i263
the lines seem to follow whats given in the link
BeagleBoardUbuntu - eLinux.org with the
exception of ext2 inplace of ext3.
ext2 should work, although in my experience it's not worth the extra
effort over ext3 on systems with no battery backed RTC...
Regards,
“cat boot.scr” returns http://pastebin.com/JR8k4n1s
It looks okay to me.
What do you say.
Nelson you have been of great help in fixing the u-boot problem. Please do look into the current boot.scr problem too when convenient.
I am running short of a deadline, so if possible do let me know of the fix a bit early.
When you changed to ext2, did you also change /etc/fstab to match?
Regards,
When you changed to ext2, did you also change /etc/fstab to match?
Yes i did
Nelson could it be that this new kernel version http://www.rcn-ee.net/deb/kernel/beagle/karmic/v2.6.32.11-x12/. is problematic? May be the vmlinuz file it yields is not rite or the armel-rootfs file is problematic.?
Please do let me know of your thoughts on this problem
Well, i don't know then...
I re-spun the karmic image last night with a newer kernel and tested
it with multiple types of rootfs partitions (ext2,3,4)...
http://elinux.org/BeagleBoardUbuntu#Karmic_9.10
Regards,
Since the kernels are working fine with you, there is a high probability i am doing something wrong. I have listed below all the steps i have done for installing ubuntu. Please let me know where i go wrong:
-i build the demo image using the commands given at http://elinux.org/BeagleBoardUbuntu#Demo_Image.
-The above step gives me armel-rootfs-.tgz and vmlinuz-2.6.
-Then i go to the section http://elinux.org/BeagleBoardUbuntu#Development_PC:_Format_SD_Card
- I create uImage as instructed. Add/Edit ubuntu.cmd(changing ext3 to ext2), then use ubuntu.cmd to make ubuntu.scr .
- I copy first uImage and then ubuntu.scr as boot.scr to FAT32 partition of my sd Card. Before copying these files, i prepare my sd card using the following shell script sent by you:
setup_boot.sh
I have modifed this script slightly so that instead of creating a FAT 16 partition, it creates a FAT 32. Also i then use the program ‘gparted’ to format my remaining space on the sd card to type ext2.
- After the above step, i copy the ubuntu rootfs as instructed at
http://elinux.org/BeagleBoardUbuntu#Copy_the_Ubuntu_rootfs
- I edit e2fsck.conf and then sources.list as instructed.
-Then i put in the sd card into the beagle and it gets stuck as i have mentioned in my earlier posts.
Please do let me know if the above steps are rite.
Your prompt response to so many of my queries has me very much in gratitued to you.
Yeap, on first pass of reading over this, everything looks correct.
This is just really weird, it's bombing at that point, since I wasn't
able to replicate the issue at all, it might just come down to you
dd'ing your sd card so i can test it..
But for sanity sake, I rebuilt a new Karmic Image last night, tested
on a bunch of my machines (B5, B6, C2, C4) with different rootfs types
(ext2/ext3/ext4) and then uploaded it last night.. GIve it a quick
boot test, shouldn't take more then 15mins, from download to first
boot..
You can retrieve it:
wget http://rcn-ee.net/deb/rootfs/ubuntu-9.10.2-minimal-armel.tar.7z
Unpack:
7za x ubuntu-9.10.2-minimal-armel.tar.7z
tar xf ubuntu-9.10.2-minimal-armel.tar
cd ubuntu-9.10.2-minimal-armel
Then Install via:
./setup_sdcard.sh --mmc /dev/sdX --rootfs ext2
Regards,
Ugh Use:
./setup_sdcard.sh --mmc /dev/sdX --rootfs ext2 --ignore_md5sum
The md5sum routine is still not ready...