From: Shawn Jin <shawnxjin@gmail.com>
To: Scott Wood <scottwood@freescale.com>
Cc: ppcdev <linuxppc-dev@ozlabs.org>
Subject: Re: kernel boot stuck at udbg_putc_cpm()
Date: Sun, 11 Jul 2010 23:26:45 -0700 [thread overview]
Message-ID: <AANLkTinRCzjFdozxBqCS91deuzVRvenFYq21XVpQnzBh@mail.gmail.com> (raw)
In-Reply-To: <20100709105946.68832b3e@schlenkerla.am.freescale.net>
> 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. =A0Check to make sure the brg
> config is correct (both the input clock and the baud rate you're trying
> to switch to). =A0Commenting out the call to cpm_set_brg can be
> a quick way of determining if that's the problem.
It seems that the last CP command RESTART_TX never completes in the
cpm_uart_console_setup(). I commented out the writes to brgc1 in
cpm_setbrg() in cpm1.c so that the brgc1 value stays the same as
previously set.
The registers related to SMC1 are dumped below before the last
RESTART_TX command. The CPCR was 0x0090. But after issuing the
RESTART_TX command the CPCR kept at 0x0691. Is there any other obvious
reason for CPM not completing the command? It got to be something
related to the settings.
BDI>rd cpcr
cpcr : 0x0090 144
BDI>rd rccr
rccr : 0x0001 1
BDI>rd rmds
rmds : 0x00 0
BDI>rd rctr1
rctr1 : 0x0000 0
BDI>rd rctr2
rctr2 : 0x0000 0
BDI>rd rctr3
rctr3 : 0x802e -32722
BDI>rd rctr4
rctr4 : 0x802c -32724
BDI>rd rter
rter : 0x0000 0
BDI>rd rtmr
rtmr : 0x0000 0
BDI>rd brgc1
brgc1 : 0x00010618 67096
BDI>rd smcmr1
smcmr1 : 0x4823 18467
BDI>rd smce1
smce1 : 0x00 0
BDI>rd smcm1
smcm1 : 0x00 0
Thanks,
-Shawn.
next prev parent reply other threads:[~2010-07-12 6:26 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
2010-07-12 6:26 ` Shawn Jin [this message]
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=AANLkTinRCzjFdozxBqCS91deuzVRvenFYq21XVpQnzBh@mail.gmail.com \
--to=shawnxjin@gmail.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=scottwood@freescale.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).