From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
Cc: "U-Boot Version 2 (barebox)" <barebox@lists.infradead.org>
Subject: Re: how does one enable barebox's low-level debugging?
Date: Tue, 4 Dec 2012 07:10:08 -0500 (EST) [thread overview]
Message-ID: <alpine.DEB.2.02.1212040706440.4812@oneiric> (raw)
In-Reply-To: <20121204115246.GF8327@game.jcrosoft.org>
On Tue, 4 Dec 2012, Jean-Christophe PLAGNIOL-VILLARD wrote:
> On 17:21 Mon 03 Dec , Sascha Hauer wrote:
> > On Mon, Dec 03, 2012 at 10:45:41AM -0500, Robert P. J. Day wrote:
> > >
> > > looking through common/startup.c and decided i wanted to see
> > > confirmation of all the initcalls running here:
> > >
> > > for (initcall = __barebox_initcalls_start;
> > > initcall < __barebox_initcalls_end; initcall++) {
> > > debug("initcall-> %pS\n", *initcall);
> > > result = (*initcall)();
> > > if (result)
> > > pr_err("initcall %pS failed: %s\n", *initcall,
> > > strerror(-result));
> > > }
> > >
> > >
> > > so i started from scratch, ran "make menuconfig" for both the x-loader
> > > and barebox to enable "low level debug messages", but i don't see any
> > > difference in the boot output.
> > >
> > > i've perused the barebox wiki and don't see anything regarding that
> > > setting. am i doing something wrong?
> >
> > You have to add a "#define DEBUG" to the file you want to have the debug
> > messages from. Add this *above* the includes, just like in the kernel.
> >
> > Something not mentioned in the wiki is that before the first console is
> > initialized barebox will print the messages into a ring buffer which it
> > will dump when the first console is initialized.
> but also print on the debug console if enabled
> on the current barebox
i thought that was true, i'll add it to my barebox debugging page.
i know i mentioned this before but i've started a series of barebox
pages on my wiki that i may incorporate into some embedded linux
classes in the near future. in particular, i'm currently documenting
the set of initcalls invoked when booting my beagle xM:
http://www.crashcourse.ca/wiki/index.php/Barebox_initcalls_for_the_xM
which is a really convenient way to examine exactly what happens when
the xM powers up. i may now know what to do with pages just yet:
http://www.crashcourse.ca/wiki/index.php/Barebox_pages
but i just want the info available in case the need arises. all still
very much a work in progress.
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
next prev parent reply other threads:[~2012-12-04 12:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-03 15:45 Robert P. J. Day
2012-12-03 16:21 ` Sascha Hauer
2012-12-03 17:46 ` Robert P. J. Day
2012-12-04 11:52 ` Jean-Christophe PLAGNIOL-VILLARD
2012-12-04 12:10 ` Robert P. J. Day [this message]
2012-12-04 16:33 ` Jean-Christophe PLAGNIOL-VILLARD
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=alpine.DEB.2.02.1212040706440.4812@oneiric \
--to=rpjday@crashcourse.ca \
--cc=barebox@lists.infradead.org \
--cc=plagnioj@jcrosoft.com \
/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