From: Sascha Hauer <s.hauer@pengutronix.de>
To: gianluca <gianlucarenzi@eurek.it>
Cc: barebox@lists.infradead.org
Subject: Re: iMX6Q First boot
Date: Fri, 26 Feb 2016 14:01:25 +0100 [thread overview]
Message-ID: <20160226130125.GQ3939@pengutronix.de> (raw)
In-Reply-To: <56D01BA9.9080707@eurek.it>
On Fri, Feb 26, 2016 at 10:32:25AM +0100, gianluca wrote:
> On 02/25/2016 08:27 PM, Andrey Smirnov wrote:
> >On Thu, Feb 25, 2016 at 5:50 AM, gianluca <gianlucarenzi@eurek.it> wrote:
> >>Hello list,
> >>I am trying to bootup my custom designed board (actually a rev.0, but I know
> >>it will need a rev.1 ASAP ;-).
> >>
> >>I started with the latest (2016.02) barebox version, adding my board to the
> >>Kconfig & Makefile stuff, copying the udoo stuff to the
> >>arch/arm/boards/eurek-ek360 (as the board name is EK360) and cut-off any
> >>unneeded initialization.
> >>
> >>I am using imx_v7_defconfig as a starting point for configuration.
> >>
> >>I kept the device tree file as short as possible, keeping only the model,
> >>memory, gpio-pinmux for uart (debug) and the uart3 configurator.
> >>
> >>In attachment there are the board.c, the lowlevel.c and the device-tree
> >>file.
> >
> >gianluca, the information you included is somewhat incomplete.
> >Attached file is a .dsti file (include file, not a standalone .dts)
> >which references phandles not defined in the file itself, so it seems
> >like there should be more to it.
> >
>
> The .dts file is almost empty. In attachment there is such a file. ;-)
>
>
> >However there are a couple of things to note about the code you included:
> >
> > - The device tree code that you provided doesn't have
> > chosen {
> > linux,stdout-path = <something>;
> > };
> > which means that BB's console subsystem doesn't have a assigned
> >"stdout" device, which might explain why you don't see the output
> >
>
> Even if it says: linux,stdout-path = .... ??? I suppose it was good only for
> Linux Kernel.
Both barebox and the kernel treat the "linux,stdout-path" and
"stdout-path" property equally. It doesn't matter which one you use, but
one of them must be present. Otherwise barebox won't find the console
device. "stdout-path" is preferred over the linux, variant.
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
prev parent reply other threads:[~2016-02-26 13:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-25 13:50 gianluca
2016-02-25 19:27 ` Andrey Smirnov
2016-02-26 9:32 ` gianluca
2016-02-26 13:01 ` Sascha Hauer [this message]
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=20160226130125.GQ3939@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=gianlucarenzi@eurek.it \
/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