From: Sascha Hauer <s.hauer@pengutronix.de>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: "U-Boot Version 2 (barebox)" <barebox@lists.infradead.org>
Subject: Re: what is the earliest i can get MLO to print out debugging info?
Date: Fri, 10 Feb 2012 15:35:14 +0100 [thread overview]
Message-ID: <20120210143514.GK3852@pengutronix.de> (raw)
In-Reply-To: <alpine.DEB.2.02.1202100755520.10458@oneiric>
On Fri, Feb 10, 2012 at 07:59:08AM -0500, Robert P. J. Day wrote:
>
> as a (sort of) followup to my last post on extending barebox to
> recognize pandaboards, at the moment, i have a build that boots nicely
> on an original panda but produces absolutely *no* output at all on a
> panda ES.
>
> i know that barebox currently doesn't recognize the ES, but i'm
> wondering if that's the real problem, and where i can put debugging
> statements in to show something along the lines of, "hi, i'm just
> starting to run MLO".
>
> surely there's an initial part of MLO that has to run before even
> checking the revision of the board, so can i add some debugging that
> would show that, or is it not even possible to set up the console
> before recognizing the board? thanks.
Is there a LED on the board? Then you could use it for bisecting the
code. Setting up a console is not that easy as it may require setting
up the iomuxer. Another way would be to setup a regular U-Boot on the
board and start the MLO from there. Then you can just do a writel to
the UARTs tx register.
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:[~2012-02-10 14:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-10 12:59 Robert P. J. Day
2012-02-10 14:35 ` 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=20120210143514.GK3852@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=rpjday@crashcourse.ca \
/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