Hi Victor, > I fix the problem of envfs: wrong magic on /dev/env0 with your thread > > http://www.mail-archive.com/u-boot-users@xxxxxxxxxxxxxxxxxxxxx/msg10197.html > > 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 nand. > > And > > 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 correctly. > > 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. Sascha -- 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 | _______________________________________________ barebox mailing list barebox@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/barebox
