From: Sascha Hauer <s.hauer@pengutronix.de>
To: Baruch Siach <baruch@tkos.co.il>
Cc: barebox@lists.infradead.org
Subject: Re: testing barebox on calao sbc35-a9260 board
Date: Wed, 30 Jun 2010 09:02:14 +0200 [thread overview]
Message-ID: <20100630070214.GP12115@pengutronix.de> (raw)
In-Reply-To: <20100628083215.GF2681@jasper.tkos.co.il>
On Mon, Jun 28, 2010 at 11:32:15AM +0300, Baruch Siach wrote:
> Hi Sascha,
>
> On Mon, Jun 28, 2010 at 10:04:42AM +0200, Sascha Hauer wrote:
> > On Fri, Jun 25, 2010 at 11:31:49AM +0200, Belisko Marek wrote:
> > > I have a calao board sbc35-a9260 with u-boot pre-installed on it.
> > > I would like to try barebox running on that board (also make some development).
> > > I build at91sam9260ek_defconfig to try it out. I became to situation
> > > that I don't know how to load image to board :)
> > >
> > > I try via tftp but u-boot automatically try to boot it and I got some
> > > error about magic number.
> > > I think about possibility just download binary to some RAM address and
> > > then use go command in u-boot
> > > to test if barebox binary will work.
> > >
> > > There exist some how-to or example how to do this?
> >
> > It's perfectly fine to start barebox from U-Boot with the 'go' command.
> > Try 'setenv autostart no' in U-Boot to stop U-Boot from autostarting
> > images.
>
> Is there a way to do the same on Barebox? Currently 'go barebox.bin' in ramfs
> returns -EINVAL from memmap.
If stored in a file it is indeed not runnable as the file is fragmented
in memory. It would be possible to copy it to a linear memory to memmap
it, but currently this is not implemented and I'm not sure this is a
good idea. It's possible to do a 'tftp barebox.bin /dev/ram0; go
/dev/ram0' instead. (or 'memcpy -s barebox.bin <sdramadr> 0x0 <size>; go
<sdramadr> if the file is already in the filesystem)
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-06-30 7:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-25 9:31 Belisko Marek
2010-06-28 8:04 ` Sascha Hauer
2010-06-28 8:32 ` Baruch Siach
2010-06-30 7:02 ` Sascha Hauer [this message]
2010-06-28 9:08 ` Belisko Marek
2010-06-28 9:17 ` Eric Bénard
2010-06-28 9:36 ` Juergen Beisert
2010-06-28 10:37 ` Belisko Marek
2010-06-30 6:57 ` Sascha Hauer
2010-06-30 11:39 ` Belisko Marek
2010-06-30 7:03 ` 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=20100630070214.GP12115@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=baruch@tkos.co.il \
/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