From: Sam Ravnborg <sam@ravnborg.org>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: Kernel fails to start on at91sam9263 target
Date: Mon, 4 Jun 2018 10:23:07 +0200 [thread overview]
Message-ID: <20180604082307.GA32467@ravnborg.org> (raw)
In-Reply-To: <20180604075821.pu4tuecex74pcwmk@pengutronix.de>
Hi Sascha.
On Mon, Jun 04, 2018 at 09:58:21AM +0200, Sascha Hauer wrote:
> On Sun, Jun 03, 2018 at 11:14:16PM +0200, Sam Ravnborg wrote:
> > Hi all.
> >
> > I have a proprietary target with an AT91SAM9263 CPU.
> > I have at91bootstrap running and barebox load fine.
> >
> > When I try to boot the kernel it stop after Uncompressing...
> >
> > Log snip:
> >
> > chunk_get_cached: found 7287 in 7
> > fat_read: 0 3421056 3421056 23bab76c
> > OF: ** translation for device /ahb/nor_flash@10000000 **
> > OF: bus is default (na=1, ns=1) on /ahb
> > OF: parent bus is default (na=1, ns=1) on
> > OF: empty ranges; 1:1 translation
> > OF: with offset: 10000000
> > OF: reached root node
> > OF: ** translation for device /ahb/nor_flash@10000000 **
> > OF: bus is default (na=1, ns=1) on /ahb
> > OF: parent bus is default (na=1, ns=1) on
> > OF: empty ranges; 1:1 translation
> > OF: with offset: 10000000
> > OF: reached root node
> > eth_of_fixup_node: no valid mac address, cannot fixup
> > __request_region ok: 0x21495000:0x2149c300
> > commandline: root=/dev/disk0.1 rootfstype=ext4 rw rootwait console=ttyS0,115200
> > booting kernel with devicetree
> > exitcall-> 0x23e073c0
> > exitcall-> 0x23e0c004
> > exitcall-> 0x23e415c8
> > Uncompressing Linux... done, booting the kernel.
> >
> >
> > The barebox commands to boot the kernel was:
> > $ mount -a
> > $ bootm /mnt/disk0.0/zImage
>
> The output of bootm -v might be useful. Have you tried earlyprintk or
> earlyconsole?
Nope, I will try this. Thanks for the hints.
I somehow missed the -v option to bootm yesterday but
increased the loglevel as can be seen above.
> You have specified the memory in the devicetree. This should not
> disturb, but looks unnecessary.
The intent is to make the DT as complete as possible, for
use by both barebox and the kernel. So in the end I have
only one DT, which is passed from barebox to the kernel.
I plan to use fixup's to select the correct display.
The timing needs to be included in panel-simple, but
using fixups allows the logic to be part of the
barebox board specific parts and not a hack in the kernel.
But let me get the kernel started first...
Sam
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2018-06-04 8:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-03 21:14 Sam Ravnborg
2018-06-04 7:58 ` Sascha Hauer
2018-06-04 8:23 ` Sam Ravnborg [this message]
2018-06-04 18:18 ` 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=20180604082307.GA32467@ravnborg.org \
--to=sam@ravnborg.org \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.de \
/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