linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Ricardo Ayres Severo" <severo.ricardo@gmail.com>
To: linuxppc-embedded@ozlabs.org
Subject: Howto get __log_buf on a Xilinx FPGA
Date: Tue, 12 Feb 2008 17:30:38 -0200	[thread overview]
Message-ID: <5ee408090802121130m2a641637s4b75a8a144ec2efc@mail.gmail.com> (raw)

Hi all,

I'm trying to boot linux 2.6.24 on a XUP Virtex II Pro evaluation
board. It uncompresses ok but doesn't show nothing more on the
console. I tried to change the console to ttyS0 and ttyUL0. Now I want
to see the __log_buf but I don't if I am doing it the right way, it
only returns trash. What I'm doing is the following:

$ grep __log_buf System.map
c01f3d5c b __log_buf

$ xmd -xmp system.xmp -opt etc/xmd_ppc405_0.opt
(xmd starts ok, mdm is not enabled)

$ powerpc-eabi-gdb arch/ppc/boot/images/zImage.elf
(click on run, the image is loaded and started)

this is the output on the terminal:
---output start---
loaded at:     00400000 004F119C

board data at: 00000000 0000007C

relocated to:  00404048 004040C4

zimage at:     00404E34 004EE12C

avail ram:     004F2000 7C9E2378


Linux/PPC load: console=ttyS0,9600

Uncompressing Linux...done.

Now booting the kernel
---output end---

after a while I stop the debugger and type rst in xmd.
then I ask gdb to dump the memory from position 0x1f3d5c to 0x1f3fff
and only trash is returned.

What am I doing wrong? Or the kernel really isn't being executed?

Thanks,

-- 
Ricardo Ayres Severo <severo.ricardo@gmail.com>

             reply	other threads:[~2008-02-12 19:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-12 19:30 Ricardo Ayres Severo [this message]
2008-02-12 19:36 ` Howto get __log_buf on a Xilinx FPGA Grant Likely
2008-02-12 19:43   ` Ricardo Ayres Severo

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=5ee408090802121130m2a641637s4b75a8a144ec2efc@mail.gmail.com \
    --to=severo.ricardo@gmail.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).