From: "Greg Griffes" <ggg@ieee.org>
To: "Krzysztof Jankowski" <kjankow@poczta.onet.pl>
Cc: <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: early stage boot progress indication
Date: Sat, 13 Apr 2002 05:43:16 -0400 [thread overview]
Message-ID: <001a01c1e2cf$a36e3160$6401a8c0@attbi.com> (raw)
In-Reply-To: 3CB6B3D7.8030007@poczta.onet.pl
Krzysztof ,
> I know that at this stage kernel's addresses were remapped
> from 0x0000xxxx to 0xc000xxxx (am I right?) due MMU being enabled by
Yes, you are right.
> 'turn_on_mmu'. So I remapped UART's memory space by 'io_block_mapping' - but
this
> didn't help.
You need to map this IO above the kernel. Mine was mapped at 0xEC00_0000.
I was advised to use ioremap instead of io_block_mapping (which limits the
kernels
mapping ability later on.)
>
> What's going on ? Why I'm not seeing characters now ? Did the kernel hang
> somewhere in the middle or am I tottaly wrong in the early debugging idea ?
>
You are not wrong. I did the exact same thing, however, it took some debugging
to get it to work. The kernel probably hung because you have a memory access
violation from the MMU. You can tell by looking in the log_buf area of memory
(you need a jtag debugger to do that.) It will give you the location you were
running
in when the violation occurred, the address you tried to access and all the ppc
registers. It's very nice if you can get to it.
Greg
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2002-04-13 9:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-12 10:15 early stage boot progress indication Krzysztof Jankowski
2002-04-13 9:43 ` Greg Griffes [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='001a01c1e2cf$a36e3160$6401a8c0@attbi.com' \
--to=ggg@ieee.org \
--cc=kjankow@poczta.onet.pl \
--cc=linuxppc-embedded@lists.linuxppc.org \
/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).