linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Junqiang Hu" <jqhu936@yahoo.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Linux booting problem on Xilinx ppc
Date: Sat, 15 Sep 2007 21:09:07 -0600	[thread overview]
Message-ID: <fa686aa40709152009k2b27ffc9kfb3fd0848f6b16d@mail.gmail.com> (raw)
In-Reply-To: <12694083.post@talk.nabble.com>

On 9/15/07, Junqiang Hu <jqhu936@yahoo.com> wrote:
>
>
> Dear friends,
>
>    I'm trying to run Linux in AvNet (Memec) Xilinx-XC2VP50-EVKT-FF1152
>  board.  The Linux version I'm using is 2.4; the cross-compiler is
> gcc-4.1.0, glibc 2.3.6.  When booting the kernel, it shows:
>       loaded at:     00400000 004B51E4
>       board data at: 00000000 00000018
>       relocated to:  0040526C 00405284
>       zimage at:     00405B2B 004B177C
>       avail ram:     004B6000 60000000

I strongly recommend moving to a 2.6 kernel.  Recent mainline has
support for the Xilinx ppc built in.
>
>       Linux/PPC load: console=ttyS0,9600 root=/dev/xsysace/disc0/part3 rw
>       Uncompressing Linux...done.
>       Now booting the kernel
>
> Then it hangs. First it seems to me that the "avail ram" is not correct,
> since I configured only 32MB SDRAM.  Moreover, if it's first powered on, the
> end address of "avail ram" would be FFD9FBED. Then I tried to investigate
> the problem using xmd.  When  launched, it says:

(If you're using u-boot) You might have a mismatch between the board
info structure used by u-boot and the one used by Linux.

Also, you should use your debugger to inspect the __log_buf memory of
the kernel.  A common problem is the kernel starts booting, but the
console is setup incorrectly and so you see nothing.  But, you can
read the console output directly from memory if you look at the
__log_buf region (find the address in the System.map file; you might
need to subtract 0xC0000000 from the address to view the memory)

Cheers,
g.

-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195

  parent reply	other threads:[~2007-09-16  3:09 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-15 21:26 Linux booting problem on Xilinx ppc Junqiang Hu
2007-09-15 21:29 ` Junqiang Hu
2007-09-16  3:09 ` Grant Likely [this message]
2007-09-16  4:39   ` Junqiang Hu
2007-09-16 15:37     ` Stelios Koroneos
2007-10-15 18:46     ` aauer1
2007-10-15 19:17       ` Koss, Mike (Mission Systems)
2007-10-15 19:20       ` Grant Likely
2007-10-16 15:08       ` Sergey Oleynichenko
2007-10-16 18:02         ` aauer1
2007-10-16 19:37           ` Grant Likely
2007-10-16 20:12             ` T Ziomek
2007-10-16 20:14               ` Grant Likely
2007-10-16 20:13             ` Ack, sorry! [was Re: Linux booting problem on Xilinx ppc] T Ziomek
2007-10-17 12:09             ` Linux booting problem on Xilinx ppc aauer1
2007-10-17 14:54               ` Grant Likely
2007-10-17 18:12                 ` aauer1
2007-10-17 18:23                   ` Grant Likely
2007-10-17 18:56                     ` aauer1
2007-10-18 23:27                     ` 转发: " keng_629

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=fa686aa40709152009k2b27ffc9kfb3fd0848f6b16d@mail.gmail.com \
    --to=grant.likely@secretlab.ca \
    --cc=jqhu936@yahoo.com \
    --cc=linuxppc-embedded@ozlabs.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).