what is the earliest i can get MLO to print out debugging info?

what is the earliest i can get MLO to print out debugging info?

[Robert P. J. Day]

  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.

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

Re: what is the earliest i can get MLO to print out debugging info?

[Sascha Hauer]

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