From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: barebox@lists.infradead.org
Subject: Re: Observations with AT91SAM9263-EK
Date: Tue, 4 Jul 2017 00:34:58 +0800 [thread overview]
Message-ID: <08E6B5A4-F877-410B-9BDB-9AA0BE065C07@jcrosoft.com> (raw)
In-Reply-To: <20170703161922.GA24614@ravnborg.org>
> 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
>
> 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
Best Regards,
J.
> I wanted to boot barebox - but nothing happened.
> So I tried older versions af barebox:
>
> v2017.06.0 => Boots OK (did not try to load a kernel)
>
> v2017.07.0 => Boots but emits:
> NULL pointer dereference at address 0x00000014
> ### Please RESET the board ###
> (A bit more was written to the serial console)
>
> master from git => Nothing written to the console at all
>
> I will as time permits dig deeper into this.
> Seems like we are facing two bugs:
> One that causes the NULL pointer, and another that
> prevents any output.
>
> As barebox is quick to build and the bug is simple to spot
> I will likely just try to bisect and see where I end up.
>
> Sam
>
> _______________________________________________
> barebox mailing list
> barebox@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/barebox
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2017-07-03 16:35 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 [this message]
2017-07-03 21:07 ` Sam Ravnborg
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=08E6B5A4-F877-410B-9BDB-9AA0BE065C07@jcrosoft.com \
--to=plagnioj@jcrosoft.com \
--cc=barebox@lists.infradead.org \
--cc=sam@ravnborg.org \
/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