From: Sascha Hauer <s.hauer@pengutronix.de>
To: Victor Rodriguez <vm.rod25@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: Beagleboard and barebox problem
Date: Fri, 22 Oct 2010 09:05:04 +0200 [thread overview]
Message-ID: <20101022070504.GD22139@pengutronix.de> (raw)
In-Reply-To: <AANLkTinosq5jY41=piCX3JaeFy6Z93gnG1Ym_VRqZ_sJ@mail.gmail.com>
Hi Victor,
On Thu, Oct 21, 2010 at 12:55:16PM -0500, Victor Rodriguez wrote:
> Hey I am new on bare box I have download it from git repo and when I
> make the barebox.bin with omap3530_beagle_defconfig this is the output
>
> Texas Instruments X-Loader 1.4.2 (Feb 19 2009 - 12:01:24)
> Reading boot sector
> Loading u-boot.bin from mmc
>
>
> barebox 2010.10.0-00086-ga14c018 (Oct 21 2010 - 12:19:10)
>
> Board: Texas Instrument's Beagle
> I2C probe
> i2c-omap@i2c-omap0: bus 0 rev3.12 at 100 kHz
> ehci@ehci0: USB EHCI 1.00
> NAND device: Manufacturer ID: 0x2c, Chip ID: 0xba (Micron NAND 256MiB
> 1,8V 16-bit)
> Malloc space: 0x80c00000 -> 0x81000000 (size 4 MB)
> Stack space : 0x80bf8000 -> 0x80c00000 (size 32 kB)
> Open /dev/env0 No such file or directory
> running /env/bin/init...
> not found
> barebox> ls
> . .. dev
> barebox> ls /dev/
> zero mem ram0 twl4030 nand0
> nand_oob0
Then it's up and running, congratulations ;)
What the beagle board is missing is currently a place to store the
environment. You could add an environment to nand by adding something
like this to the board setup function:
devfs_add_partition("nand0", 0x40000, 0x20000, PARTITION_FIXED,"env_raw");
dev_add_bb_dev("env_raw", "env0");
(this adds a partition at offset 0x40000 and size 0x20000 to nand, you
probably have to adjust the offset to not overwrite the X-loader)
Another possibility would be to add mmc support for omap and put the
environment there. We recently gained mmc support for barebox, so all
that's missing is an omap driver. The mmc support is still close to
U-Boot, so the driver won't need many changes.
>
>
> And when I compile with omap3530_beagle_per_uart_defconfig
The per_uart_defconfig is more a X-loader replacement. You can use it to
bootstrap from the serial port. For your case the other config is the
correct one.
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@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2010-10-22 7:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-21 17:55 Victor Rodriguez
2010-10-22 7:05 ` Sascha Hauer [this message]
2010-10-25 22:29 ` Victor Rodriguez
2010-10-26 3:39 ` Sascha Hauer
2010-10-26 4:07 ` Victor Rodriguez
2010-10-26 18:34 ` Sascha Hauer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20101022070504.GD22139@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=vm.rod25@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox