LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Gong Zhuo" <gongzhuo@163.net>
To: "Linux PPC Mailing List" <linuxppc-embedded@lists.linuxppc.org>
Subject: How to use ppcbug to debug my program with mmu?
Date: Fri, 21 Jul 2000 16:45:07 +0800	[thread overview]
Message-ID: <004e01bff2ef$fb03d0a0$4607a8c0@LocalHost> (raw)


Hi:
   I am using MVME2600 SBC and I want to debug my program under PPCbug.
According the PPCbug Firmware Package User's Manual chapter 2, a program
with mmu enable should be debugged using PPCbug if some rules are obeyed.
   Those address ranges
         0x0 -- 0x0fffffff,
         0x10000000 -- 0x1fffffff ,
         0xe0000000 -- 0xefffffff,
         0xf0000000 -- 0xffffffff
   have been mapped from physical address to logical address 1 to 1 using
BAT mothed .  Exception vectors 0x100 , 0x700, 0xc00, 0x2000 and spr272,
spr273, spr274, spr275 are not being used.
   I write the code like this under ppcbug at address 0x40000:
          1.     initial all the BAT register
          2.     isync
          3.     msr | 0x30  ==> msr    # open the mmu
          4.     do sth. else
    But it always not come back to PPC1-bug> status after I use command
'T'to singlestep run step 3.
    I also used the mothed like this :
          1.     initial all the BAT register
          2.     isync
          3.     msr | 0x30  ==> srr1    # open the mmu
          4.     logical address of 6. => srr0
          5.     rfi
          6.     do sth. else
    The same error happened when singlestep 5.

   Can this code be debugged under ppcbug? If can , how?


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

             reply	other threads:[~2000-07-21  8:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-21  8:45 Gong Zhuo [this message]
2000-07-21  9:17 ` How to use ppcbug to debug my program with mmu? Gabriel Paubert
2000-07-24 11:43   ` Gong Zhuo

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='004e01bff2ef$fb03d0a0$4607a8c0@LocalHost' \
    --to=gongzhuo@163.net \
    --cc=linuxppc-embedded@lists.linuxppc.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