linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "dong in kang" <dkang@east.isi.edu>
To: "'Mark A. Greer'" <mgreer@mvista.com>
Cc: <linuxppc-embedded@lists.linuxppc.org>
Subject: RE: Kernel parameters (Sandpoint X3 with Altimus MPC755)
Date: Tue, 20 May 2003 13:56:53 -0400	[thread overview]
Message-ID: <001401c31ef9$329f8170$45a97241@Minjoo> (raw)
In-Reply-To: <3ECA67C0.5070306@mvista.com>


 As a debugging tool, I'm using Metrowerks Codewarrior v.6.0 running on
Windows 2000 platform.
The BDI2000 for Codewarrior is connected to the JTAG port of the Sandpoint
X3.
I used the Codewarrior to load the linux kernel to the SDRAM of the
Sandpoint X3.
Of course, I used GCC to compile Montavista Linux kernel.
(I heard that BDIgdb is the best tool for Linux kernel debugging.
I'm considering purchasing BDIgdb. Currently, I have a problem of enabling
mmu.
After the initial boot part of the Linux finishes setting up BATs and
enables the mmu,
the address translation is not done properly. So, when the kernel jumps to
0xC0000000, it jumps to physical address 0xC0000000.
It crashes there. I suspect BDI2000 with Codewarrior does not support mmu.

 Dong-In


-----Original Message-----
From: owner-linuxppc-embedded@lists.linuxppc.org
[mailto:owner-linuxppc-embedded@lists.linuxppc.org] On Behalf Of Mark A.
Greer
Sent: Tuesday, May 20, 2003 1:37 PM
To: dong in kang
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Kernel parameters (Sandpoint X3 with Altimus MPC755)



dong in kang wrote:

> Hello,
> I'm trying to boot Montavista Linux kernel on Sandpoint X3 with
>Altimus MPC755 CPU without bootloader and without using DINK32. (I'm
>using BDI2000 with Metrowerks Codewarrior v.6.0).
>
What do you mean when you say, "I'm using BDI2000 with Metrowerks
Codewarrior v.6.0"?

>I could read/write SDRAM before manually loading zImange.initrd.
>However, I don't know how to setup kernel parameters and command lines.
>What information should I put for kernel parameters? and where?
>
>
You shouldn't need any cmdline arguments unless you're doing something
special.  If you are, look in Documentation/kernel-parameters.txt for more
info.

Mark


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2003-05-20 17:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-20 16:06 perl under eldk for ppc8xx XOL
2003-05-20 16:13 ` Mark Hatle
2003-05-20 16:23   ` Re[2]: " XOL
2003-05-20 16:42     ` Mark Hatle
2003-05-20 17:25     ` Kernel parameters (Sandpoint X3 with Altimus MPC755) dong in kang
2003-05-20 17:37       ` Mark A. Greer
2003-05-20 17:56         ` dong in kang [this message]
2003-05-20 18:14           ` Mark A. Greer
2003-05-20 19:26             ` dong in kang
2003-05-20 19:35               ` Wolfgang Denk
2003-05-20 22:45               ` Mark A. Greer
2003-06-10 18:22                 ` dong in kang
2003-05-20 19:23     ` Re[2]: perl under eldk for ppc8xx Wolfgang Denk
2003-05-21 17:26     ` Wolfgang Denk

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='001401c31ef9$329f8170$45a97241@Minjoo' \
    --to=dkang@east.isi.edu \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=mgreer@mvista.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).