LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Ramkumar J" <ramkumarj2000@gmail.com>
To: linuxppc-embedded@ozlabs.org
Subject: XMD to debug Linux kernel 2.6
Date: Wed, 12 Mar 2008 23:15:16 +0800	[thread overview]
Message-ID: <4f8c3030803120815o7dcf5e8xb74650c8b993d26d@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 620 bytes --]

Hi All,
I need to dump the TLB entries, i-cache and d-cache entries on a ML-403
board ( I use a PowerPc based design) using the Xilinx Parallel-4 Cable.
When I download the zImage.elf using dow command on XMD, I m not able to
access the TLB and cache address special memory mappings as displayed by the
XMD. I suspect that XMD only allows the dump for sections inside the elf
file. If its true, then how to access the sections of kernel.
Could XMD be used to debug a linux kernel by dumping the registers, TLBs,
cache entries,etc. Am I missing anything. Any pointers would be very
helpful.

Thanks and Regards,
Ramkumar

[-- Attachment #2: Type: text/html, Size: 664 bytes --]

             reply	other threads:[~2008-03-12 15:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-12 15:15 Ramkumar J [this message]
2008-03-12 16:01 ` XMD to debug Linux kernel 2.6 John Linn

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=4f8c3030803120815o7dcf5e8xb74650c8b993d26d@mail.gmail.com \
    --to=ramkumarj2000@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