From: Sam Ravnborg <sam@ravnborg.org>
To: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
Cc: barebox@lists.infradead.org
Subject: Re: Observations with AT91SAM9263-EK
Date: Mon, 3 Jul 2017 23:07:51 +0200 [thread overview]
Message-ID: <20170703210751.GA28383@ravnborg.org> (raw)
In-Reply-To: <08E6B5A4-F877-410B-9BDB-9AA0BE065C07@jcrosoft.com>
On Tue, Jul 04, 2017 at 12:34:58AM +0800, Jean-Christophe PLAGNIOL-VILLARD wrote:
>
> > On 4 Jul 2017, at 12:19 AM, Sam Ravnborg <sam@ravnborg.org> wrote:
> >
> > Hi all.
> >
> > I recently purchased an AT91SAM9263-EK from ebay and
> > have played around a little with barebox.
> > For now only some observations.
> >
> > I had the impression that I could
> > drop AT91BootStrap when using barebox.
>
> Yes Wrote the support for that but on the 9263 you are limited.
>
> you have 2 choice boot a small barebox <= 72kiB
>
> or use a console less barebox to boot the second barebox
>
> as the rom code on at91 will load the barebox from the SD or Nand
> into SRAM
Thanks for the info.
I will try to collect this in a at91.rst file in Documentation/boards/
When there is something useful I will post a patch for review.
> >
> > But I could not make it boot until I deployed
> > at91bootstrap (named BOOT.BIN) on the SD-card.
> > And I named arch/arm/pbl/zbarebox.bin => u-boot.bin
> > on the SD-card.
> >
>
> on 9263ek you have a nor flash so why not flash it
>
> in this case barebox will boot by itself
>
> without the bootstrap
The EK only have NAND, the NOR is not mounted.
But anyway - the idea here is to have a testbed for my at91
patches that I can use before I send them upstream.
I have a proprietary at91sam9263 based board that
I will try to add support for in barebox.
But only the parts touching the atmel boards are relevant for the
upstream barebox.
Step 1 was to get barebox workign with the EK, and with
the two small patches I already sent it looks like I
had some luck there.
Sam
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2017-07-03 21:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-03 16:19 Sam Ravnborg
2017-07-03 16:34 ` Jean-Christophe PLAGNIOL-VILLARD
2017-07-03 21:07 ` Sam Ravnborg [this message]
2017-07-03 20:17 ` [PATCH 1/2] clk: fix clk_get error handling Sam Ravnborg
2017-07-04 6:11 ` Uwe Kleine-König
2017-07-04 6:53 ` Sam Ravnborg
2017-07-03 20:22 ` [PATCH 2/2] gpio: fix null pointer exception when there is no oftree Sam Ravnborg
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=20170703210751.GA28383@ravnborg.org \
--to=sam@ravnborg.org \
--cc=barebox@lists.infradead.org \
--cc=plagnioj@jcrosoft.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