From: Scott Wood <scottwood@freescale.com>
To: Shawn Jin <shawnxjin@gmail.com>
Cc: ppcdev <linuxppc-dev@ozlabs.org>
Subject: Re: kernel boot stuck at udbg_putc_cpm()
Date: Fri, 9 Jul 2010 10:59:46 -0500 [thread overview]
Message-ID: <20100709105946.68832b3e@schlenkerla.am.freescale.net> (raw)
In-Reply-To: <AANLkTinNSzP-WvxC2kqZop2kvd1kSUMDuwI01GOBXApE@mail.gmail.com>
On Fri, 9 Jul 2010 00:35:43 -0700
Shawn Jin <shawnxjin@gmail.com> wrote:
> I changed my toolchain and rebuilt the kernel image. This time all the
> messages below magically displayed on the serial port. :-D Are all
> these the early debugging messages?
Yes, it's an alternate output for the regular console (there are
sometimes more messages, if you hook up .progress in your ppc_md, but
that's mainly of interest if you don't get this far).
> Now the kernel stuck at the while loop that waits for transmitter fifo
> to be empty. It seems that the CPM UART stopped working in the middle
> of printing a message. I'm using minicom to connect to the serial
> port. I heard minicom is problematic. Will it be the cause here?
I doubt it...
You're probably getting to the point where udbg is disabled because the
real serial driver is trying to take over -- and something's going
wrong with the real serial port driver. Check to make sure the brg
config is correct (both the input clock and the baud rate you're trying
to switch to). Commenting out the call to cpm_set_brg can be
a quick way of determining if that's the problem.
-Scott
next prev parent reply other threads:[~2010-07-09 15:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-05 7:23 kernel boot stuck at udbg_putc_cpm() Shawn Jin
2010-07-06 20:21 ` Scott Wood
2010-07-06 23:08 ` Shawn Jin
2010-07-06 23:18 ` Scott Wood
2010-07-07 0:17 ` Shawn Jin
2010-07-07 15:42 ` Scott Wood
2010-07-09 7:35 ` Shawn Jin
2010-07-09 15:59 ` Scott Wood [this message]
2010-07-12 6:26 ` Shawn Jin
2010-07-12 18:23 ` Shawn Jin
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=20100709105946.68832b3e@schlenkerla.am.freescale.net \
--to=scottwood@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=shawnxjin@gmail.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;
as well as URLs for NNTP newsgroup(s).