Hello to all,
I'm sorry but I have a problem booting the kernel.
After powerup the beagleboard I stop the autoboot process and then I
send this command:
mmcinit
fatload mmc 0 0x80300000 uImage
setenv bootargs 'console=ttyS2,115200n8 console=tty0 noinitrd root=/
dev/mmcblk0p2 rw rootdelay=2 rootfstype=ext3 video=omapfb:vram:2M,vram:
4M';
bootm 0x80300000
After the bootm command the kernel starts but the beagle reboot during
the "Uncopressing Linux..." process.
The MLO, x-load.bin.ift, u-boot.bin and uImage files are from Angstrom
demo site [1]. I make a SDCard with two partition and inside the
second there is the this image [2] ( I did a sudo tar -xjf Ang....
from a linux machine).
This is the console output:
Good news!
I rewrite all the files like uboot.bin and uImage from a linux
machine, directly into the FAT32 partition.
Now I'm booting the kernel but it hang after the Uncompressing
process:
Uncompressing
Linux..............................................................................................................................
......... done, booting the kernel.
I'm using files from this site:
http://amethyst.openembedded.net/~koen/index.php?path=beagleboard%2Fdemo/
Again: any help will be much appreciated...
TIA
Clemente.
Serching the google group, I found a msg from Khasim [1]:
...
The u-boot and x-loader are for 166Mhz DDR, the kernel image might
hang if
power mods are not done on the board.
...
I'm using uboot: U-Boot 1.3.3 (Jul 30 2008 - 13:15:50)
is it possible that my kernel hang for this reason? Which u-boot can I
use?
TIA
Clemente
[1] http://groups.google.com/group/beagleboard/msg/409deeaa9b0916cf?pli=1
Serching the google group, I found a msg from Khasim [1]:
...
The u-boot and x-loader are for 166Mhz DDR, the kernel image might
hang if
power mods are not done on the board.
...
I'm using uboot: U-Boot 1.3.3 (Jul 30 2008 - 13:15:50)
is it possible that my kernel hang for this reason? Which u-boot can I
use?
Not likely. If you purchased your board from Digi-Key rather than one
of the couple dozen prototype give-aways, then you have Revision B4 or
newer. These have the power mods.
Not likely. If you purchased your board from Digi-Key rather than one
of the couple dozen prototype give-aways, then you have Revision B4 or
newer. These have the power mods.
Thanks a lot Jason for your replay.
Yes, I have rev.B5.
OK, but now: which steps I can follow? I need quickly to put the
beagleboard running with a demo image to build something like a "demo
of capability", and from the next month I need to start a development
project to connect a 1M sample/s ADC to the beagleboard. Waiting for
the rev.C version next year.
I'm using files from this repository: [1], [2]. [3]. And I format my
SDCard at least 2 time, following this instruction [4].
...any help will be much appreciated...
TIA
Clemente.
[1] http://www.angstrom-distribution.org/demo/beagleboard/
[2] Openembedded-Hotels, Villen, Unterkünfte in Leipzig
[3] http://code.google.com/p/beagleboard/wiki/BeagleSourceCode
[4] Google Code Archive - Long-term storage for Google Code Project Hosting.
Not likely. If you purchased your board from Digi-Key rather than
one
of the couple dozen prototype give-aways, then you have Revision B4
or
newer. These have the power mods.
Thanks a lot Jason for your replay.
Yes, I have rev.B5.
OK, but now: which steps I can follow? I need quickly to put the
beagleboard running with a demo image to build something like a "demo
of capability", and from the next month I need to start a development
project to connect a 1M sample/s ADC to the beagleboard. Waiting for
the rev.C version next year.
I'm using files from this repository: [1], [2]. [3]. And I format my
SDCard at least 2 time, following this instruction [4].
...any help will be much appreciated...
Try the steps on Google Code Archive - Long-term storage for Google Code Project Hosting.
. If those fail, I'd suggest getting a replacement using Return Materials Authorization - BeagleBoard
.
c.dicaprio wrote:
setenv bootargs 'console=ttyS2,115200n8 console=tty0 noinitrd root=/
dev/mmcblk0p2 rw rootdelay=2 rootfstype=ext3 video=omapfb:vram:2M,vram:
4M';
I'm not a linux expert by a long shot, but I'm using only one console argument (the ttyS2 one) on my board and I'm seeing the console output fine on the serial port.
I'm not a linux expert by a long shot, but I'm using only one console argument
(the ttyS2 one) on my board and I'm seeing the console output fine on the
serial port.
Hello Justin,
thanks for your response.
I'm not a linux expert too 
So I just take this command from this file [1] to startup the beagle
with some demo software.
Are you suggesting a command like that:
setenv bootargs 'console=ttyS2 noinitrd root=/dev/mmcblk0p2 rw
rootdelay=2 rootfstype=ext3 video=omapfb:vram:2M,vram:4M';
TIA
Clemente
[1] http://www.angstrom-distribution.org/demo/beagleboard/README.txt
c.dicaprio wrote:
So I just take this command from this file [1] to startup the beagle
with some demo software.
Are you suggesting a command like that:
setenv bootargs 'console=ttyS2 noinitrd root=/dev/mmcblk0p2 rw
rootdelay=2 rootfstype=ext3 video=omapfb:vram:2M,vram:4M';
Sorry - I should have provided the full setup the first time around.
setenv bootargs console=ttyS2,115200n8 root=/dev/mmcblk0p2 rw rootdelay=1 nohz=off video=omapfb:mode:480p60,vram:2M,vram:4M
setenv bootcmd 'mmcinit;fatload mmc 0 0x80300000 uImage;bootm 0x80300000'
Now that I look at it, I also don't see nohz=off in your command, which is a magic incantation I've seen pointed out before.
AIUI nohz=off is only needed on the old TI kernels. I run all my omap
boards with nohz on and don't have any problems, everything including
dsplink works.
Hello Koen and Justin,
thanks for your response,
I solved my problem; all my problem with the beagleboard! 
For powering the board I use a "DC Power Supply" limited in current at
circa 300mA. This limit is enough for another project I'm working on
with a dsPIC. Changing the limit to 550mA make the difference!
I'm be able now to boot the kernel and run the AngStrom demo image.
...Fantastico!
Many thanks to all.