linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@netx4.com>
To: Damjan Lampret <damjan.lampret@arnes.si>
Cc: linuxppc-embedded@lists.linuxppc.org,
	Jurkas Vasja RDSS <jurkas@iskratel.si>
Subject: Re: Data TLB error exception
Date: Sun, 27 Feb 2000 22:14:41 -0500	[thread overview]
Message-ID: <38B9E821.1E486142@netx4.com> (raw)
In-Reply-To: 002601bf81dc$184f9480$0a01010a@gamma


Damjan Lampret wrote:

> I am playing with 2.2.13 kernel on custom MPC860 board and I have a problem
> with DTLB error (1400h) exception. I downloaded my kernel via BDM and it

BDMs with MMU and caches are a bad combination.  With the exception of
KGDB, there are no debuggers that understand the Linux kernel once
the MMU is enabled.  The debugger tools normally used with BDMs trap
MMU exceptions as a "bad thing" or at least try to invoke some monitor
support code that is supposed to reside in the kernel.

The MMUs and caches work fine on the 8xx processors when running Linux/PPC.
I have been running them all day, every day, for years and have several
products deployed in the field without trouble.

If you are using BDMs for downloading Linux, that is all you can do with
them.  Once the kernel executes the first few lines of code to enable
the MMU, you are done.  If you can't disable _all_ debugging from the
BDM tool, including show cycles, you can't use it with Linux.


	-- Dan

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

  reply	other threads:[~2000-02-28  3:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-02-28 11:08 Data TLB error exception Damjan Lampret
2000-02-28  3:14 ` Dan Malek [this message]
2000-02-29 14:06   ` Damjan Lampret
     [not found] <200002291827.TAA13080@denx.local.net>
2000-03-17 16:53 ` Damjan Lampret

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=38B9E821.1E486142@netx4.com \
    --to=dan@netx4.com \
    --cc=damjan.lampret@arnes.si \
    --cc=jurkas@iskratel.si \
    --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;
as well as URLs for NNTP newsgroup(s).