From: Brendan John Simon <Brendan.Simon@ctam.com.au>
To: Wolfgang Denk <wd@denx.de>,
linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: mpc8xx-2.2.13 kernel hangs during boot.
Date: Tue, 01 Feb 2000 23:16:35 +1100 [thread overview]
Message-ID: <3896CEA3.EBA97957@ctam.com.au> (raw)
In-Reply-To: 200002010035.BAA26304@denx.local.net
Wolfgang Denk wrote:
> In message <3896BF04.55AD7C4F@ctam.com.au> you write:
> >
> > I based my port on the BSEIP board as it is the simplest.
> > The IMMR is at 0xff000000 and all peripherals are mapped above 0x80000000
> > except for DRAM which is mapped at 0x00000000.
>
> Do youmean you have any peripherals mapped at addresses in the
> 0x80000000 ... 0xC0000000 range? I don't think this will work...
Sorry about my ignornace but why can't I use the address range
0x80000000-0xBFFFFFFF for my peripherals ?
Is 0xC0000000-0xFFFFFFFF ok ? What address range would be recommended ?
> > I didn't think so. The embedded-2.2.5 kernel works fine with the same
> > bootloader. I forgot to mention the the embedded-2.2.5 kernel is compiled
>
> What does "works fine" mean? Can you run any serious applications
> which *use* (nearly) all your available memory?
No I haven't tried any serious applications. I just got a simple test app
working with dynamic linking using the embedded-2.2.5 kernel compiled with
binutils-2.9.5.0.24/gcc-2.95.2. I would prefer to use mpc8xx-2.2.13.
I now have to put some serious applications together such as telnetd, snmpd,
etc.
> > How can I look at this memory area ? With a BDM debugger ? I thought BDM
> > can't be used.
>
> Of course this will work with a BDM debugger. Why should it fail???
There have been many postings to this list stating that BDM will not work after
the kernel is running. I think it has something to do with the MMU. The
debugger does not know how to translate VMA to PMA. Do you believe this
statement is correct ? Can you confirm that the kernel can be debugged using a
BDM ?
> > Can a serial debugger be used ?
>
> What is a serial debugger? Do you have any type of boot monitor with
> debugging features, or what?
I was thinking of gdb with a serial connection. I do not have a boot monitor
with debugging features but I can write some gdb stubs if it is possible. I
was basically asking whether it is possible or not to debug the kernel and/or
apps via a serial connection.
Thanks,
Brendan Simon.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next parent reply other threads:[~2000-02-01 12:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200002010035.BAA26304@denx.local.net>
2000-02-01 12:16 ` Brendan John Simon [this message]
[not found] ` <38968BC0.6FD6E801@netx4.com>
2000-02-01 23:09 ` mpc8xx-2.2.13 kernel hangs during boot Brendan John Simon
2000-02-01 16:07 ` Dan Malek
[not found] ` <0001311713560A.00776@alan.corp.packetengines.com>
2000-02-01 12:58 ` Brendan John Simon
2000-02-01 1:49 ` Alan Mimms
2000-02-01 13:38 ` Brendan John Simon
2000-02-01 3:42 ` Alan Mimms
[not found] <48256878.00018A59.00@mail.zhongxing.com>
2000-02-01 11:47 ` Brendan John Simon
2000-02-01 7:32 ` Dan Malek
2000-02-01 10:00 Brendan John Simon
2000-01-31 23:40 ` Dan Malek
2000-02-01 11:09 ` Brendan John Simon
2000-02-17 11:05 ` dony
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=3896CEA3.EBA97957@ctam.com.au \
--to=brendan.simon@ctam.com.au \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=wd@denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.