Beagleboard and barebox problem
vm.rod25 at gmail.com
Tue Oct 26 00:07:21 EDT 2010
On Mon, Oct 25, 2010 at 10:39 PM, Sascha Hauer <s.hauer at pengutronix.de> wrote:
> Hi Victor,
>> I fix the problem of envfs: wrong magic on /dev/env0 with your thread
>> And every thing works fine
>> uboot> addpart /dev/nand0 256k(uboot),128k(env),2048k(kernel),-(rootfs)
> I think on the beagle board the first space in Nand is occupied by the
> xloader and xloader itself expects the second stage loader at offset
> 512k, but I don't know the exact situation off my head. Michael, maybe
> you can comment on this?
>> setenv bootargs console=ttyS2,115200n8 noinitrd root=/dev/mmcblk0p2
>> rootfstype=ext2 rw rootdelay=1 nohz=off
>> But is not working for bare box
>> How do you save the boot args ?
> have a look at /env/config (using the edit command). Every file there is
> saved into the environment using saveenv.
>> The next step will be
>> uboot> tftp uImage-mx27ads /dev/nand0.kernel.bb
>> And the same for a ram disk File System in the nand0.rootfs.bb right ?
> Right, dont forget to erase the partitions with 'erase
> /dev/nand0.kernel.bb' beforehand, otherwise you'll have garbage in your
You mean to erase the part of the nand where the kernel is saved
before copy the ramdisk to its partition? or before i run the 'boot'
>> uboot> bootm /dev/nand0.kernel.bb
> In principle, yes. The normal process is to simply run 'boot' which is a
> script under /env/bin. This will setup things like the commandline
>> But my second question is How the kernel know were is the File
>> System, where should I set something similar to boot args ?
> Have a look at the files under /env, I think this will answer your
> questions (we have ls, cat and edit for this).
> I'm sorry the situation on the beagle board is still a bit rough and
> unclear. I hope we find time working on this.
Yes I could give some free time to work on this :) but could you
please give me more information about the mmc dirver I am new on
barebox but I would like to help to improve it :)
Which other board is using this MMC driver ? I can check the code.
The problem is that beagle board is much more familiar with booting by
mmc because it does not have any RJ45 connector in order to transfer
by TFTP or NFS the uImage.
By the way about the small piece of code for the beagle board nand. Do
you consider that is good enough for an small patch ?
Thanks a lot
> Pengutronix e.K. | |
> Industrial Linux Solutions | http://www.pengutronix.de/ |
> Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
> Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
More information about the barebox